Solved

Microsoft Windows Network: The local device name is already in use

Posted on 2014-04-02
11
2,248 Views
Last Modified: 2014-04-21
Hello,

Lets say we have two servers, server1 and server2.  Server1 is the server where this error is occurring.  If you go on server one and type \\server2 in the run dialog box you get another dialog box that asks for credentials to connect to server2.  Both these servers are on the same domain and it is normal to never have to type in those credentials.  So I go to the network map on server1 that's connected to a shared folder on server2 and double click it which gives me the error in the title of this post (Microsoft Windows Network: The local device name is already in use).  I disconnect the network map, type \\server2 in the run box, connect to the server using admin credentials, and now the problem is fixed and I can re-add the mapped drive on server1.

I'm trying to figure out why server1 seems to be losing its connection to server2.  The same thing happened like two weeks ago, and I fixed it by doing the same thing I described here.  I just want to know if this is an early warning sign to another larger failure or something.

Thank you.
0
Comment
Question by:printmedia
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 6

Expert Comment

by:Ryan Smith
ID: 39972575
check server 2 to see if it has a local account with the same name your logged into as server 1.  That can cause conflicts.
0
 

Author Comment

by:printmedia
ID: 39973297
Server 2 is a domain controller, so there's no local account.
0
 
LVL 6

Expert Comment

by:Ryan Smith
ID: 39973302
check on server1.  I've seen this problem before and it had to do with local accounts.
0
Major Incident Management Communications

Major incidents and IT service outages cost companies millions. Often the solution to minimizing damage is automated communication. Find out more in our Major Incident Management Communications infographic.

 

Author Comment

by:printmedia
ID: 39973322
Yes on server1 there is a local account that's the same name as the account I use to log onto server1 which is a domain account.
0
 
LVL 6

Expert Comment

by:Ryan Smith
ID: 39973324
That is most likely the problem.
0
 

Author Comment

by:printmedia
ID: 39973360
Can I disable it to see if that fixes the issue, or do I have to delete it completely?
0
 
LVL 6

Expert Comment

by:Ryan Smith
ID: 39973373
I would try to disable it first, or rename it.
0
 
LVL 6

Expert Comment

by:Ryan Smith
ID: 39975660
Any luck?
0
 

Author Comment

by:printmedia
ID: 39975836
I just went ahead and disabled it.  Took me a while to do this because there were a couple of SQL jobs running using that account, but it's disabled now.  The error that we were getting in the title of this post was only happening intermittently though.  The last time it happened was about 2-3 weeks ago and that's the first time it's happened in 10 years that the server's been running.  So I'm going to go ahead and assume that this should fix the issue permanently now.
0
 
LVL 6

Accepted Solution

by:
Ryan Smith earned 500 total points
ID: 39975874
It should fix it.  What would be the chances of me knowing that you have a local account with the same name of a domain account on the server.  :)
0
 

Author Comment

by:printmedia
ID: 40012563
Edited.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preface Having the need * to contact many different companies with different infrastructures * do remote maintenance in their network required us to implement a more flexible routing solution. As RAS, PPTP, L2TP and VPN Client connections are no…
Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question