Discussion Locked

wins name conflict

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
Can you tell me what this means and how to clear this conflict and why it happend

5 replies

by cdcents

This normally means that another computer on the network has the same name as the machine you are working on. This is usually the problem.

If you do not believe that there is another machine with a similar name you could be having a WINS databasecorruption problem. You coud use WINSCL at that point to rectify the problem. Before doing so ensure you have a decent backup of your WINS database.

Go to
support.microsoft.com/support/kb/articles/Q137/5/82.asp

for more help on using WINSCL

by soliboy

I have seen a similar problem once, where the organization I was on contract in had changed from a static addressing system to DHCP, and also to using different subnets, but their WINS server had a couple of mappings for old addresses and names which caused a headache in a seperate part of the WAN when trying to change the PC names. Deleting the mappings from the wins database did the job. (oh, what caused confusion first off was the non-existence of computer accounts for these netbios names inthe domain).

This discussion is closed to new replies.