PDA

View Full Version : Duplicate Name on Network (W2K)



HelpTheMidget
12-02-2003, 12:38 PM
I get the following error message logged in the event viewer every time i restart/login into my Windows 2000 machine.

"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. " Error ID 4319

After running the nbtsat command, no names are listed as being in the conflict state, they all say registered.

While this error does not seem to affect my ability to browse my LAN i wont to try and resolve it. I think it is more than just coincidence that this error first appeared after i installed the latest version of ZoneAlarm (the free version).

What i have observed in my attempts to solve this problem, is that if zonealarm is disabled from start up or the network cable is unplugged the error does not occur. This leads me to believe that maybe ZoneAlarm is blocking something, but i cant work out what after looking through the zonealarm program list.

Does anyone have any thoughts on how to solve this issue.

I am running and IIS server and have got the .Net framework installed (ASP .Net) could these cause a problem like this, as .Net create a new user account named the same as the computer.

*Both computers on my lan have unique names and ips and are part of the same workgroup.<P ID="edit"><FONT class="small">Edited by HelpTheMidget on 12/02/03 12:52.</FONT></P>

Paul S
12-03-2003, 01:19 AM
Do you have two network cards? Is you IP DHCP assigned? If so, then this is the cause. Your DHCP server has assigned two different IP's, one to NIC 1 and one to NIC 2.

Hope this helps...

<font color=green>Paul</font color=green>

<font color=blue>mailto:paul@winguides.com (paul@winguides.com)</font color=blue>

<font color=blue><a target="_blank" href=http://www.paulstoodley.com>Link: My Site</a></font color=blue>

HelpTheMidget
12-03-2003, 08:43 AM
Thanks for your reply Paul but i only have one NIC in the computer and the IP is assigned statically, no DHCP server is used.

The computer that this win2k computer is connected to (the server) has 2 NICS but one card gets its ip automatically and the other card has its ip statically assigned.

HelpTheMidget
12-06-2003, 05:29 PM
It appears that the newest release of the ZoneAlarm has caused this error. I have no idea how it has caused it but it seems to be the most likely cause.

Any one else experiencing the same error?

digipainter
12-14-2003, 08:14 PM
I have Zonealarm 2.6 & I too get that message, not sure what it means, but in both our cases zonealarm is a common clue.