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.
| Source | Event Log | Event ID | Event Type |
|---|---|---|---|
| Nbt | System | 4320 | Error |
A few network occurrences can cause this message. A computer on the network may have the same name, or you may be logging on to multiple computers with the same user name. If you are using WINS, you may have inactive or duplicate names in the WINS database. The WINS server sends this error every time it releases a NetBIOS name from the IP address to a new account that is logged on to the same computer. If you are using DHCP, corruption in the DHCP database can cause this error. The error could also be caused by a multihomed computer. Or, a computer may be configured for one name, but an ipconfig -all command returned a different host name.
When you use the nbtstat -n command, if the IP address is all zeros, look for any Windows for Workgroups computers on the network with the same name. Windows for Workgroups computers sometimes return all zeros for their IP address with this error. If you log on to multiple computers with the same user name, the user names will register with a <03h> and that will be the name in conflict. If the DHCP database is corrupted, clear the DHCP-related entries in the Registry, delete any .MIB files, and then reinstall DHCP. If a computer was configured for a name but the ipconfig -all command returned a different host name, go to the Registry editor and change the computer name in the TCP/IP parameters section.