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-06T16:23:53+00:00

    I have posted this before and it has worked perfectly for me and other users for some time now after trying almost every other method. It's a little complex and you do have to follow every step. If you are not clear about any step reply and I will try to help.  This does depend on being on a domain.

    I have solved this for a number of users by setting up a Group Policy for mapped drives on the server.

    These are the steps:

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. 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
  3. Anonymous
    2020-11-19T13:54:06+00:00

    For what it's worth, in our particular situation applying the new Windows 10 202H update fixed the issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-28T13:15:26+00:00

    I have solved this for a number of users by setting up a Group Policy for mapped drives on the server.

    These are the steps:

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-10-28T09:47:56+00:00

    Hi Guys,

    Same issue here, i have a customer who can start up in the morning, connect to a mapped drive on a web server, but once he reboots or signs out of laptop and signs back in i can not for the life of me reconnect to the drive, no matter what i do. I just get the error "The local device name is already in use"

    any ideas?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments