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: Newest
Most helpful Newest Oldest
  1. 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
  2. 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
  3. Anonymous
    2020-11-30T13:01:16+00:00

    Roger!

    Then this will not help me, as this is still a issue for me.

    I am on windows version 20H2.

    I did try a lot of tips when I googled this, adding things to task manager or startup folder running scripts and what not without luck. Some of them worked, but slowed down windows explorer, and it did not work ones I fixed that. It was so slow it was faster to just disconnect and reconnect everytime.

    Kind of annoying to reconnect everytime I boot up my PC though.

    The search for an solution contiunues.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. Anonymous
    2020-11-30T08:59:21+00:00

    Adding the following Registry Entries solved my problem.

    HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>CurrentVersion>Policies>System

    add DWord(32bit): EnableLinkedConnctions

    Set Value Data to 1

    HKEY_CURRENT_USER >Network>Drive Letter

    add DWord(32 Bit): ProviderFlags

    Set Value Data to 1

    Hi!

    What if the folders does not exist. Can I create them? Right clicking and chosing new does not allow for a folder to be created.

    I am missing CurrentVersion>Policies>System and >Drive Letter

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments