printmedia
asked on
Microsoft Windows Network: The local device name is already in use
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.
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.
Ryan Smith
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.
ASKER
Server 2 is a domain controller, so there's no local account.
check on server1. I've seen this problem before and it had to do with local accounts.
ASKER
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.
That is most likely the problem.
ASKER
Can I disable it to see if that fixes the issue, or do I have to delete it completely?
I would try to disable it first, or rename it.
Any luck?
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Edited.