Mapped Network Drive Keeps Disconnecting

[rmgdnz]

Hi everyone,

 

I have a WD MyCloud NAS that I have been using for several years. On my Windows 10 PC, I simply mapped it as a network drive and connected using the credentials I set up on the NAS. After updating the firmware of the NAS, I changed my login information and remapped the drive on my PC. However, the mapped network drive fails to connect every time on startup. I have to unmap it and remap it for it to connect again. I checked the boxes "Reconnect at startup" and "Sign in using different credentials" but it still does this.

 

Strangely enough, I have the backup software Veeam Agent running on the same PC and that is able to connect to my NAS and backup data to it even though I can't connect through file explorer. 

 

Additionally, my Mac remains connected to the NAS with no issues.

 

Any help would be appreciated!

[Haraikomono]

does your nas has a static ip ?

Are you trying to connect via hostname ?

 

[Jarsky]

Do you mean it shows in 'Disconnected' status?

If you try clicking on it after say a minute or so, does it then auto connect? 

 

It could be that its trying to mount before your network has initialized. 

If this is the case, in the Linux world there is AutoFS which you can use to mount shares and delay it till after the network is up.

In Windows you could use task scheduler with the net use command to mount the drive say 1 minute after login.

 

You could even go as far as to write a basic little .bat file to ping say your router, and only connect the network drive once it receives a successful ping in an if else. 

Looking at this script appears to do just that: https://stackoverflow.com/a/26196535

[rmgdnz]

On 6/6/2021 at 3:20 PM, Haraikomono said:

does your nas has a static ip ?

Are you trying to connect via hostname ?

 

Yes, it is configured with a static ip. I have been using hostname, I'll see if using the ip instead works.

[rmgdnz]

On 6/6/2021 at 5:11 PM, Jarsky said:

Do you mean it shows in 'Disconnected' status?

If you try clicking on it after say a minute or so, does it then auto connect? 

 

It could be that its trying to mount before your network has initialized. 

If this is the case, in the Linux world there is AutoFS which you can use to mount shares and delay it till after the network is up.

In Windows you could use task scheduler with the net use command to mount the drive say 1 minute after login.

 

You could even go as far as to write a basic little .bat file to ping say your router, and only connect the network drive once it receives a successful ping in an if else. 

Looking at this script appears to do just that: https://stackoverflow.com/a/26196535

It does not connect later unfortunately, I have to remove it and re map the drive. Thanks for the information though! This did give me an idea, perhaps a .bat file to automate the remap on login if I can't figure this out. 

[rmgdnz]

On 6/6/2021 at 3:20 PM, Haraikomono said:

does your nas has a static ip ?

Are you trying to connect via hostname ?

 

Looks like using an ip instead of host name is working, thank you!! Any clues as to why it doesn't work with the hostname?