Windows 10: Mapped Drive will not connect after reboot

After a recent windows update I have had multiple issues with my network drives on my home network. Some of these were caused by my router which I have replaced. Now I have all but one drive working correctly. I cannot figure out the one remaining problem.

If I map the drive by the name \\MyBookWorld\Public the map works OK until I reboot. After reboot, I get the error of "The Specified network name is no longer available". I cannot connect to drive via start>>run either. If I try to access the drive by IP address using start>>run, it works.

If I disconnect the map drive and reboot, I can connect from start run to the drive after every reboot.

If I map the drive by IP address, reboot and then try to use the drive, I get "Microsoft Windows Network: The local device name is already in use". Net use shows the drive disconnected and has an entry to the unc name. It works if I use start>>run to the UNC name.

I have verified that smb is enabled on the machine. I have made sure the services of "comptuer browser", "LanmanServer", and "LanmanWorkstation" are set to automatic start.

I have removed the mapping, made sure that it was not in the net use list in the command prompt and made sure the registries at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 for this drive have been removed.

I have added the mapping to the Hosts file.

I tried mapping to a different drive letter and get the same problem. Any ideas on what in Windows is messing this up?

:)

 

Mapped Drive will not connect after reboot

After a recent windows update I have had multiple issues with my network drives on my home network. Some of these were caused by my router which I have replaced. Now I have all but one drive working correctly. I cannot figure out the one remaining problem.

If I map the drive by the name (\\MyBookWorld\Public) the map works OK until I reboot. After reboot, I get the error of "The Specified network name is no longer available". I cannot connect to drive via start>>run either. If I try to access the drive by
IP address using start>>run, it works.

If I disconnect the map drive and reboot, I can connect from start run to the drive after every reboot.

If I map the drive by IP address, reboot and then try to use the drive, I get "Microsoft Windows Network: The local device name is already in use". Net use shows the drive disconnected and has an entry to the unc name. It works if I use start>>run to the
UNC name.

I have verified that smb is enabled on the machine. I have made sure the services of "comptuer browser", "LanmanServer", and "LanmanWorkstation" are set to automatic start.

I have removed the mapping, made sure that it was not in the net use list in the command prompt and made sure the registries at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 for this drive have been removed.

I have added the mapping to the Hosts file.

I tried mapping to a different drive letter and get the same problem. Any ideas on what in Windows is messing this up?

 

Mapped drive disconnected after reboots

Since fall creators update I am seeing one of my mapped NAS drives always in a disconnected state after a reboot. It’s easily fixed by clicking the drive displaying the red x in explorer to establish the connection. But it seems strange that this has only started after fall creators and is the only one of three mapped drives doing this. And this same mapped drive is mapped in identical state to another machine running fall creators with no such issue. Any ideas on how to fix this? Or why it is happening. It’s only a minor niggle and can live with it as there are no pressing dependencies on the mapped drive but would be nice if there was an easy quick fix

thanks, Wayne

 

windows 10 forgetting mapped drives after reboot after 2004 update

Windows 10 32bit 2004
After update all my mapped drives lost connections, I disconnected each drive and re mapped andI can access all drives
normally. After a reboot all connections fail , i can remap drives and they all work until the next reboot all all are marked to reconnect. Ran SFC and Dism no problems . I ended up reverting back to 1909 and everything working ok.
I have a couple other Pc's 64bit that have not been updated and now I am afraid of the same issue with them .
Any Advice?