Mapped Drive will not connect after reboot

Anonymous

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?

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

Anonymous

2021-07-23T20:25:43+00:00

I think the path should be

HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>Windows>CurrentVersion>Policies>System.

This seemed to work for me so far
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-05-06T12:03:16+00:00

I haven't been able to find a solution since September. Well one was to restart 2 times and that would work. But had a user yesterday couldn't access the drive even after reboot 3 times. I couldn't even disconnect the drive explorer would hang. Even tried net use to delete the drive nothing.

So since I could browse the path I added to quick access and she was able to access it that way, while the mapped drive to same location still didn't work.

Then I stopped Workstation service as you said, then started it. Instantly I was able to access all the shared drives including the already mapped drives to nas. Then I restarted 4 times and at no time did I lose access. It's so strange that restarting the PC didn't have the same affect as stopping this services and starting it up. It must clear something when stopped.
Was this answer helpful?

0 comments No comments
Anonymous

2021-05-04T07:24:09+00:00

"..Or it will be mapped and throw an incorrect password the first time they try to re-connect, which is causing AD accounts to become locked after some many "Bad" password attempts."

I guess the VPN account of your offsite user are same as NT account but password is not the same which will cause AD account locked out. change the VPN account name will make it works.
Was this answer helpful?

0 comments No comments
Anonymous

2021-04-26T08:36:02+00:00

Hi!

Yeah the new Synolgy DS1821+ works flawlessly.
My old DLINK NAS DNS-345 not so much!

I got this message today when trying to map it.

Found this information: Microsoft

And this information from DLINK: DLINK

Meaning that my old NAS does not Support SMB2 and I have to activate it in Windows, See DLINK link how. Most likely after each windows update it seams too, as Microsoft deems it nessecary due to SMB1 not being safe enough.
Was this answer helpful?

0 comments No comments
Anonymous

2021-04-26T01:14:22+00:00

20H2 made it worse
Was this answer helpful?

0 comments No comments