Mapped Drive will not connect after reboot

Anonymous
2020-07-24T15:46:02+00:00

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?

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

52 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-12-04T20:35:17+00:00

    Argh!!! Just updated to 20H2 and the issue reoccurred. Needed both registry entries to make mine work plus SMB 1.0 enabled.

    WC

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-11-30T12:44:51+00:00

    Hi,

    Looks like with latest updates of version 2004 the HKLM may not be necessary. I just noticed I don't have this entry either after installing the latest updates. 

    The HKCU is still there and the NAS drives still correctly map.

    Thx

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-29T19:18:25+00:00

    Provided they are logging in to the network and are on AD the server policy will work.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-29T10:19:16+00:00

    Hi Stephen,

    forgive my noobishness here, user is connecting via VPN, will that matter with GPO? should still kick in correct?

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more