Duplicate Name in TCP Network

Topic

New Reply

I would appreciate help with this problem which seems to recur almost every day –

The Event Viewer System Log gives this message

Type Error
Source NetBT

Properties for the Error are –

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.

Ran “nbstat -n” at Command prompt – got this response –

Local Area Connection:
Node IpAddress: [192.168.0.1] Scope Id: []

Net BIOS Local Name Table

Name Type Status

DESKTOP UNIQUE Registered
NRMC GROUP Registered
DESKTOP UNIQUE Registered
NRMC GROUP Registered
DESKTOP UNIQUE Registered
NRMC UNIQUE Registered
..__MSBROWSE__. GROUP Registered
DESKTOP UNIQUE Registered
DESKTOP UNIQUE Registered

Problem is that I can not see which name is duplicated, let alone know what to do about it.

Any advice will be most welcome.

Noel

Reply | Quote

Replies

Check to see if you have the same name or IP address on the WINS Server.

Do yo have DHCP? Check and see if you overlapping IP address.

Reply | Quote

Another possible cause: the same Computer Name is already used on the network (under some circumstances, it can be even previous logon of your computer). Try to change your computer name (right-click My Computer icon on the desktop, from pop-up menu choose Properties, then Network Identification button, then click Properties button).
NOTE: Some companies’ policies are strict about computer names used on their networks. Contact your network administrator, if applicable.

Reply | Quote

If you run WINS, it is possible that the database has become corrupted. Unless you have a whole lot of static mappings you would have to add back, the best course may be to delete it and let the WINS server rebuild it.

Reply | Quote

Thank you all three for your helpful suggestions.

I am not running WINS – this is a Win2000 Pro computer operating as the main for a small network of only three other computers. I do of course run DHCP, but have checked all the settings and it all seems OK,

However the suggestion to look at computer names may well be the clue. I shall try that and see if that fixes things.

Thank you again – your help is really appreciated.

Noel

Reply | Quote

I had the same problem but with 2K Server which was running multihomed (dual nic card). I made an older single NIC card server the Wins server and the event went away. Lessons learned from this is don’t run WINS on a multihomed Server nor don’t run DNS from one either.

Reply | Quote