Duplicate name exists on the network?
Network administration, Network troubleshooting, Windows Server 2008, Windows XP, Windows XP Professional, Windows XP Professional SP3
We have one unusual issue in one of our workstation here.
Every morning after the PC is idle for a very long time, it will disconnect all of its connection in the Printer, File and exchange servers. We already change the setting to never hibernate, monitor, hard drive always on. Ethernet power save is off.
I tried to ping the printer server and I’m getting a response to it (Printer, File and exchange servers) but if I will browse the server by using it will say “You were not connected because a duplicate name exists on the network”.
Restarting the workstation will solve the issue but restarting every morning makes my user annoyed.
Other Technical details please find below.
Workstation
· Windows XP Prof SP3
· Dell 760 all hardware in normal condition
· Office 2007
Servers
· Windows Server 2008
Any feedback on this would be highly appreciated.
ALEJO
Software/Hardware used:
Windows XP Prof SP3, Dell 760, Office 2007, Windows Server 2008
Every morning after the PC is idle for a very long time, it will disconnect all of its connection in the Printer, File and exchange servers. We already change the setting to never hibernate, monitor, hard drive always on. Ethernet power save is off.
I tried to ping the printer server and I’m getting a response to it (Printer, File and exchange servers) but if I will browse the server by using
Restarting the workstation will solve the issue but restarting every morning makes my user annoyed.
Other Technical details please find below.
Workstation
· Windows XP Prof SP3
· Dell 760 all hardware in normal condition
· Office 2007
Servers
· Windows Server 2008
Any feedback on this would be highly appreciated.
ALEJO
Software/Hardware used:
Windows XP Prof SP3, Dell 760, Office 2007, Windows Server 2008
ASKED:
February 3, 2010 3:26 AM
UPDATED:
February 22, 2010 7:17 PM
Answer Wiki:
Check that there is not a problem with the DNS Cache.
Also, do you have entries in the HOSTS file? this may have an incorrect entry on one or more of the machines in your network.
Also, did you use SYSPREP or cloning to create your PC's?
To see all answers submitted to the Answer Wiki: View Answer History.
Our naming convention on our PC are the service tags… there is no way we could have duplicate names… But we tried that but totally unique name…
We also thought about changing the name but we will break our naming convention of our client PC if we do that.. Probably if we really can’t find any solution to it….
The weird thing is after restart everything is ok like nothing happens…
LOL sometime microsoft software give headage but they are gone automatically when machines are restarted nobody know why.
can i ask is there only 1 client facing the issue?
are you all using AD?
@Jinteik
Actually two of them having the same problem. I suspect that, that’s the other computer his having collide with.
I have checked and both don;t have the same computer name and IP….
@Jinteik
Yes we are using AD, Parent and child Domain on it.
how about deleting these two computer from computers OU and re-assign them one by one to AD.
@SiThu we tried that already.. and still the same..
Try this to check each computer name and what other systems think the computer names are:
On each system run “nbtstat -n”
On another system run “nbtstat -a IPAddress” for each of the problem systems
Give the machine a new SID and re-name it that should do it.
Use this tool
http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx
@RickC
I’ve checked the two machines SID and they have different SID
SID for \Machine1:
S-1-5-21-776561741-1580436667-1417001333
SID for \Machine2:
S-1-5-21-682003330-1659004503-2147069159
sorry for slow reply, just to add, last time I had the same issue too. i formatted the computer, and wanted the pc to rejoin the domain. but upon rejoining, they say the name already exist in the network. Before that i even remove the pc from the OU…I could not continue as I had already resign and assign the task to another person.
but from what i read, they mention that it at times can be the problem with AD or DNS that does not refresh thats why the system always clashes…but since I left the company, i didnt have anymore platform to test….
@ Jinteik
My situation is somehow different. The machines are doing good before, then suddenly this happens when users start to builds up.
have you tried using nbtstat to find the other computer?