Discussion Locked

4319 netBT Error - cause of

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

We have begun to get these things off & on on serveral of the servers and the technet says they are harmless along with a 4320 netBT error. Both are related to 'duplicate names' detected on the network.

"A duplicate name has been detected on theTCP 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."

The trouble is that when we resolve the duplicate name, it is not, in fact, remotely related to the conflicting machine. The ultimate problem is that this seems to cause the 'server' service to stop running as a side effect, but not all the time. The machines stays up and can be pinged, but quits functioning.

2 replies

by mckaytech

You've obviously already found your way to Technet so you're probably aware of article Q131470 that lists a bunch of causes for this.

I would be looking very closely at your DHCP and WINS databases for evidence of corruption - TechNet has rebuildprocedures for both. We've occasionally seen this type of problem and most often it has responded to a rebuild of either WINS or DHCP.

paul

by fpillow

Thanks - did find some relation to DHCP earlier and cleaned that. Will try to get rest of enterprise to Re-Sync WINS.

This discussion is closed to new replies.