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
    2021-01-26T12:42:51+00:00

    Yeah, pretty much the same, only the IP and names are changed.   Hmm, was the old NAS Synology as well?   I suppose it could be some kind of interaction with the SMB implementation on the older Synology NAS boxes.  This is an oldish one as well.  That said, it seems people using Windows Server are also having the issue, so maybe not.  We're in the process of migrating this system to new HP mini workstations with SSDs, with the intent of using the NAS to host each WS libraries and .PST file(s).   This is presently unworkable due to the unreliability of the link to the NAS.

    Good luck.

    Geoff

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-01-26T12:38:43+00:00

    Yeah, I'm pretty much at the same place.   Don't bother a reinstall, it won't fix it.  I used a clean version of W10 20H2 on new hardware and it does exactly the same thing as an earlier incarnation of Windows 10.   I've checked the Synology NAS and it seems to be fine, Linux talks to it, in fact I can get XP to talk to it and map drives etc.  No problem.   Just Win 10.  I've also seen this with W7, but far less frequently and was usually associated with underlying network issues that don't exist in this network.

    Best of luck.

    Geoff

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-01-26T07:26:23+00:00

    Yeah the fix with using the IP Address and not the hostname, stopped working for me too. 2021-01-21.
    Incidental, at the same time as I setup my new Synolgy NAS. I am waiting for my new HDD to arrive and in the mean time I have chucked a bunch of spare drives into it, and created three different volumes on it. I have mapped these with IP, and these are currently working fine, but the old one is not. Explorer slows down when this happens too. Disconnecting the old NAS solves that.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-01-25T16:27:44+00:00

    Been bashing my head against this for weeks.   

    The FQDN v IP address 'fix' works for a day or two, then stops and you have to change to the other method to get it to reconnect, even after removing the drive mappings.   You can't even browse to access the NAS.  There is no Windows server in this network, just five W10 workstations and a NAS, so solutions involving Domain Server/Windows File Server 'fixes' are irrelevant.   I've also discovered that a Linux box plugged into the LAN temporarily has no such issues.  

    I've tried re-enabling SMB 1.0 (which I need anyway as our PXE 'server' (on one of the workstations) doesn't play at all without it, so it's back on all of them and the autoremove has been shot in the head.  

    Tried the various registry tricks.   At first, they seem to work, then after a few reboot, suddenly it's lost the plot again and nothing short of removing the mappings and reconnecting via IP if it was using FQDN and using FQDN if it was using IP will restore connectivity.   Win 10 20H2 does NOT change this issue in any way, shape or form.  It remains intermittently popping up on reboot.   This has become a major issue as we are in the process of moving user directories (Documents, Pictures, Videos, Desktop and their Outlook .pst file to the NAS.   This has meant several reboots to try and get it to find the desktop!  This is using a full path to the file, not the mapped drive letter, ie //NAS1/Storage/Manager/Desktop not H:\Desktop.  So the underlying network connection to the Synology NAS is not being restored.   

    If anyone has suggestions (aside from ditching Windows) I'd be pleased to hear from them.

    Geoff

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-01-20T07:44:54+00:00

    Good!

    It has worked for me all the time up until now, and still works, and I have high hopes for it.

    Was this answer helpful?

    0 comments