The local device name is already in use

Anonymous
2021-04-25T21:50:46+00:00

I have a NAS. Every time I try to access it, this is the error I get. It has been going on for a couple of weeks. I deleted the mapped drives and mapped them again. That got me about 6 hours of functionality, but I was just now playing some music from the NAS and playback froze in the middle of a song. Why? Because the music player is suddenly unable to find the file and using Explorer to go look at it yields:

"An error occurred while reconnecting Z: to <server share name> Windows network: The local device name is already in use. This connection has not been restored.

Searching the Microsoft help for this error message gives exactly 3 hits. Two are irrelevant and the third is for a Windows XP client trying to connect to Server 2003. Please.

Is there a permanent fix for this?

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 No comments

7 answers

Sort by: Most helpful
  1. Anonymous
    2021-07-09T17:51:11+00:00

    All computers have this problem every damn day. That's a total of four computers. The only solution is a reboot and hope that it hang in there long enough to do something. Disk Management shows no other device trying to use the drive letter. File and print sharing is enabled, which is the only positive recommendation I've every seen. Windows needs to be able to handle basic file transfer back and forth to a NAS.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-04-26T07:36:38+00:00

    Type these commands in a Command Prompt (cmd.exe):

    net  use  *  /d  /y

    net  use  /persistent:no

    Please remember to mark my reply by clicking "Did this solve your problem?". It's your way of saying "Thank you".

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-05-01T05:23:17+00:00

    Bad to worse. Now it says the drive doesn't exist at all.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-05-01T05:48:01+00:00

    Bad to worse. Now it says the drive doesn't exist at all.

    You must remap the share, either in File Explorer or at the command prompt:

    net  use Z: \ServerName\ShareName

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-05-01T06:01:08+00:00

    The share is still present in File Explorer and cannot be removed. Running the above command in a terminal gives the message System error 67 The Network Name cannot be found. Well it is there and I can see it from other computers.I'm going to reboot this one now, but even if the share reconnects I'm pretty confident that if I access it, I'll get the same error within about half an hour.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments