Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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.

share|improve this question

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".

share|improve this answer

In my experience, this usually happens when a folder/drive that has been shared is deleted/removed without first removing the share.

To fix this, I have re-created the folder, shared and then unshared it, THEN deleted/removed the folder/drive. This forces the system to remove the old information for that share.

This usually requires only a logout and login, but (for some unknown reason) sometimes a reboot, to complete the process.

Once that process is complete the name and mapping for that folder/drive will be gone and you can go on from there.

I hope this helps you.


share|improve this answer
Please read the question again carefully. Your answer does not answer the original question. The OP does not havev a problem wuth deleted shares. – DavidPostill Jun 24 '15 at 12:35

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:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.