Periodically some of our servers report Event ID 4320--"Another machine has sent a name release message to this machine probably because a duplicate name has been detected on the TCP network. The IP address of the node that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. .". First of all, I have confirmed that there are no other devices using that name. I have used nbtstat to check the name in the conflict state and it reports the user account name that I had recently logged in with (i.e. administrator). The username is registering itself with the IP address of the workstation. It appears the unique username is registering itself (which is normal, I believe, in that you can find who is logged on a workstation remotely using "nbtstat -a wsname". It may be that somehow the username is registering and placing itself first in the list of NETBIOS names. This only happens directly after logging into a couple of servers. Even then, it only happens periodically. If anyone has ANY ideas please reply. Thanks.

Have you look up this error message on Microsoft's web site. There are a number of articles there.

I've thoroughly researched Technet for any explanations, but found no resolution. I can rule out a bad WINS server because the problem only occurs on a couple systems. And it only occurs on those systems when I log into them locally. Within a few minutes I may get the IP address conflict pointing the username that I logged in with as the name in conflict. Thanks.

I'm a little confused as to wether you are saying you have a computer name or netbios name or ip address conflict, and to sort it out you need to be clear on that, but my experience is that ip conflicts are most common. If it is then I would check that your servers have static ips and that these ips are excluded in dhcp. if a static ip logs in but that ip is not excluded in dhcp it can still be allocated , and wins will send a name release to both owners. also if you are on a server/wkstn which is on the network then log in locally then it won't request a renewal of its ip so after the lease is up it may be given elsewhere but your pc won't reset its ip I imagine. look in the wins database as the answer may be in there with two pcs having the same ip.

For further clarification: The error is Event ID 4320--"Another machine has sent a name release message to this machine probably because a duplicate name has been detected on the TCP network. The IPaddress of the node that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. .". NBTSTAT shows the name causing the IP conflict as being the administrator's username, not a workstation name. Static IPs are used.. No DHCP is configured on the network.. Wins Database never shows another PC with the same IP. Apparently, somehow the workstation broadcasts the logged-in username as a NETBIOS name. Hopefully with these clarifications, someone may come up with an idea...Thanks.

if you have checked that the computer name is correct. then checked in the dns tab of tcp/ip properties that the same name is in hostname, as this is taken from the netbios name by default. then clear the cache with nbtstat -R and checked for a dodgy lmhosts. then I would rename the pc. I hope you are aware that you must make it a member of a workgroup, reboot, change the name, reboot, add to domain. if you short-cut this procedure you can divorce the comp name from the netbios name and get something like what you already seem to have!

In the error message, there are four groups of hex address. If you convert each number to dec and reverse the order you will get an ip address. Check this address. Shane