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-09T03:10:23+00:00

    Thanks John,

    I selected a series of device numbers in my 192.168.1 range that were not close to any of the 15 or so other device IPv4 addresses shown by my router. When I ran that batch file the NET USE /DELETE lines worked - those share are no longer mapped; but the lines to remap, using the selected IP addresses, failed. So I reverted to the original format for NET USE, with the account name and password, that had worked for me when entered manually. It seemed not to work at all, and no NAS shares are now mapped and visible. Some further research indicated that I need to create an "elevated shortcut" for the batch file, to enable it run as administrator in the STARTUP folder. I'm currently learning how to do that. If you have any further advice on this subject, I would be grateful.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-01-07T09:27:15+00:00

    Hi!

    My network drive is not on a server, rather on a NAS without those kinds of setting, but if One has access to the server which the mapped drive is located to, this is a solution.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-01-07T07:55:31+00:00

    Standard local IP Range for home users are normally 192.168.0.xxx or 192.168.1.xxx where xxx is the number for the device. If you are on a office network, the IT department can give you the IP for the Drive.

    As how to find it, depends on where the mapped drive is located. In my instance the IP is available on the display on the NAS, but you could also access it from you Router under DHCP settings.

    Below is an example. If you know the MAC Address too it helps.

    Was this answer helpful?

    0 comments
  4. 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
  5. Anonymous
    2021-01-06T15:49:26+00:00

    Thanks John,

    I had thought about maybe trying a batch file to "remap" the NAS drives at every reboot. However, having not done batch files since DOS days, I didn't know how to proceed. I will certainly try yours, adjusted for my system. But first, how did you arrive at the IP addresses for each network drive? The 192.168 part is clear to me; but how one determines the other two parts isn't. Is it arbitrary, or is there some process to suss out just what they need to be?

    Was this answer helpful?

    0 comments