7

I map a network drive from a PC (workstation) to another PC (server), that is always on.

When my workstation sleeps and comes out of sleep, I get this error message:

An error occurred while connecting [drive] to [share]. The local device name is already in use. This connection has not been restored.

enter image description here

I get one of those for each explorer window I had open pointing to the network drive.

If I go click the network drive in My Computer, type G: in explorer or really do anything to access the network drive, everything works great again.

How can I avoid this happening?

Both PC's are Windows 8.

1
  • Still an issue with Windows 10 1809 after reboots. I connect 4 shares to FreeNAS-11.1-U6 and an ubuntu 16.04 Samba share. Some shares fail to connect with above error. I can access the share typing the path into the address bar, though.
    – baloan
    Oct 7, 2018 at 9:37

3 Answers 3

2

I found that by starting the Computer Browser service, the drives came back:

net start "Computer Browser"

Another way to fix it is to go browse to \\server (to re-establish the connection), then the drives should work again.

Windows also disconnects server connections after a timeout. If you run this command, it should never drop idle server connections:

NET CONFIG SERVER /AUTODISCONNECT:-1

Another solution could be

Start > Run > type "gpedit.msc" (without quotes) click ok.

Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon

set this to Enable then reboot.
0

To me it seems it's most likely because the NICs are being shut off while it's asleep and the connections won't be restored until you refresh the connection (by trying to access it again with a fresh process).

Try going into Device Manager, and in the properties of your network adapter, go to the Power Management tab, and de-select "Allow this computer to turn off this device to save power".

0

I've had this error popping up as well on every reboot. Tried all possible solutions, but I discovered this error won't recur if I check 'Remember my credentials' option when mapping the network drive

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .