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
    2021-01-28T06:22:30+00:00

    Geoff, after much research, this worked for me. Correction, it did for a little while - see last line. Sigh

    You need to allow anonymous access to your shares on the NAS.

    Use gpedit to edit your local policy:

    Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options

    Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers

    Set to Allow All

    Computer Configuration > Administrative Templates > Network > Lanman Workstation.

    Set Enable insecure guest logons to Enable.

    Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options

    Double-click Microsoft network client: Digitally sign communications (always) and set it to Disabled. Click OK.

    I also went into properties for the workstations ethernet interface, selected Internet Protocol V4 properties, Advanced, and set Enable Netbios Over TCP/IP  to on.

    Bad news edit: I was happily accessing the NAS shares finally, then I shutdown File Explorer and tried to access the mapped shares again. Timed out with reconnection error. OMG! I rebooted the workstation and tried to access the mapped drives in File Explorer - it worked. Shutdown File Explorer and retried. Timed out with reconnection error. What?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-01-27T01:18:16+00:00

    The SMB might be a way to the answer, as I had tick off SMB1, on my sons computer in order for it to connect to the old NAS, after it had been shut down for a longer period of time. I have not tried to connect to the new NAS on that computer yet, and I have not found anything concrete in regards to the SMB.

    SMB 1.0 being present doesn't seem to fix it, though I think it helps.  (we needed it for other reasons to do with a PXE implementation on one of the workstations).   I'm reduced to pushing all the data back from the NAS to the workstation that I can and implementing backup regimes.   This doesn't eliminate the need for network connections or drives unfortunately, but at least they can get into their desktops, documents and mail reliably.  

    I'm now trying to figure out how one of the WS seems to have magically changed the location path for Desktop to one for a different server???   Frankly they're not bright enough to have even tried to mess with this so not sure WTH happened there.  

    I'm going to tinker with the NAS and do firmware upgrades today, not because I've any real hope it will fix it, but because I've got nothing else left to try.

    IF Mr. MS is listening, this really needs fixing as a matter of urgency.

    Cheers

    Geoff

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-01-27T01:10:45+00:00

    Group Policy Management | Default Domain Policy-Edit | User configuration | Preferences | Windows Settings | Drive Maps create new mapped drive -Action Replace - Reconnect ticked- make sure that mapping is targetted to the users that you need.

    Turn off reconnect mapped drives at sign-in locally.

    Now each time a user signs in the drives are mapped with no conflicts.

    Ok, unfortunately this can't be implemented in a NON AD/Windows Server environment.   The issue is in an organisation that uses a Synology NAS and Windows 10 Pro workstations - no AD, no Domain Controller etc.

    Thanks anyway, hopefully it will help someone out.   And word from anyone in the MS universe when/if this might be addressed?   The silence has been deafening.

    Cheers

    Geoff

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-01-26T13:07:08+00:00

    The old NAS is a D-Link DNS-345, which I bought in January 2012.

    The new NAS is a Synology DS1821+.

    I'll se how long the Synology will stay connected...
    The SMB might be a way to the answer, as I had tick off SMB1, on my sons computer in order for it to connect to the old NAS, after it had been shut down for a longer period of time. I have not tried to connect to the new NAS on that computer yet, and I have not found anything concretete in regards to the SMB.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-01-26T12:49:15+00:00

    Did the first of these some time back, doesn't seem to make any difference.  Still happens every few reboots.

    The second key beyond Network doesn't exist ie no Drive Letter can you post a copy of your key?

    Thanks

    Geoff

    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

    Was this answer helpful?

    0 comments