4319 netBT Error – cause of

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.