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: Oldest
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-12-16T20:33:19+00:00

    I've found this soulution on an other forum, and it worked for me.

    Actually, if you are a Windows 10 user (this might apply to Windows 7, 8, and 8.1 as well), the best way to address this issue is to simply create the network shares and assign drive letters as normal and THEN temporarily right click on the drive (make sure it is connected first) and then right-click the mapped drive and select "ALWAYS AVAILABLE OFFLINE." Let Windows start to index and then cancel after a second or two. Now, simply right-click on the same mapped drive and uncheck "ALWAYS AVAILABLE OFFLINE." Let it complete and then reboot. VOILA!! Problem solved. The mapped drives with red "X's" are gone and there is no need to click on each drive to reconnect them anymore. Your welcome!! :) No need to edit registries or use scripts.

    Cheers

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-12-17T09:05:49+00:00

    Hi!

    Thank you for the tip.

    I have tried this several times now, but without any luck.

    Every time I reboot, (cold or not), I still have to disconect network drive and connect to it again in order to be able to access it.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-26T04:08:20+00:00

    The key  HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>CurrentVersion>Policies>System does not exist on my new Win10 PC. The path stops at Microsoft; there is no CurrentVersion and beyond. I have Windows 10 Pro, 1909 version; and Settings tells me it is completely up to date.

    Otherwise, I did the  HKEY_CURRENT_USER >Network>Drive Letter entry. It did not help. I can map a MAS drive to my LAN, using the net use driveletter:  command (as Administrator) with the Persistent:Yes switch  to make the NAS share visible and read/write accessible through File Explorer. After a reboot, the drive is still visible, but no longer read/write accessible. I have come to a complete dead end trying to make my new Synology NAS drive readily available.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-27T06:57:41+00:00

    So, in desperation I logged into my Dlink NAS DNS-345, and did some poking around.

    The clock was off by 15 minutes, as none of the built in NTP's were working anymore. Set the clock to match my computer, reboted the NAS, and for the last three days I have had no problem with the Mapped Drive, after rebooting my PC.

    I also tried to replicate the issue, by resetting the time to the previous faulty time, but I still had access.

    I had tried several reboots of the NAS  earlier without any luck.

    Not sure what really solved the problem or if it will return shortly again or in the future at all...

    Was this answer helpful?

    0 comments