Windows 2000 SErver Problem inEVent Viewer EVENT ID 4319
Home > IT Answers > CIO > Windows 2000 SErver Problem inEVent Viewer EV...
management
0 pts.
0
Q:
Windows 2000 SErver Problem inEVent Viewer EVENT ID 4319
Tech support, Help Desk, Networking, Networking services, DNS, Active Directory, LDAP, Microsoft Windows, DHCP, Vendor support, Bind, NFS, WINS, Novell NDS
Hai ??..

In my domain controller am getting in event viewer an error a Duplicate name has been detected on the TCP networks. The IP address of the machine that sent the message is in that data. Use nbtstat ?n in a command windows to see which name is in the conflict state EVENT ID 4319
Last three years I have no problem in my network this happed two days back without any reason. My problem is I can not browse my other computers through my network place.
I checked all the machine there is no duplicate IP addresses. And used the above command also.

My network details. 150 Clients all are windows 2000 professional and my domain controller are windows 2000 server I have two domain controllers one is running as a back up server with active directory. DNS server its running fine. Am not using WINS. This above error am getting in my primary domain controller.

For solving this problem I did the following things, in my LAN properties -> tcp/ip properties -> Advanced -> Wins -> I selected disable NetBIOS over tcp/ip, after this I didn?t get any error in event viewer but the problem now in my network place I can see my domain name only but computers are not listing there. Its fully blank????

Please help me in this problem?????

Regards,
Niyas.
Niyas@gsh-sa.com
ASKED: Feb 2 2005  2:27 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
0ct0pus
0 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
hi niyas,
based on my experience if you disable the netbios you won't be able to browse the computers.

the error shows abt duplicate name, not duplicate IP. you may search if any client is using the same netbios name as your PDC. nbtstat -a might help.

gd luck
Last Answered: Feb 2 2005  9:46 PM GMT by 0ct0pus   0 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

csmmis   0 pts.  |   Feb 4 2005  8:25AM GMT

Niyas, there is a great website where you can often find helpful (free) info on Event ID’s: <a href="http://www.eventid.net" title="http://www.eventid.net" target="_blank">http://www.eventid.net</a>. As 0ct0pus indicated, 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 check which name is in the conflict state. Hope this helps.

 

Howard2nd   0 pts.  |   Feb 4 2005  4:20PM GMT

Not duplicate IP, therefore not DHCP problem.
And yes turning off NetBIOS over TCP disables computer browser - it relies on a table of netbios names.
Duplicate Name - ghosted any machines recently? When you load ‘Window’ do you accept the miserable made-up name it provides or try for one that has some meaning?
Every time I have seen this error sequence - it was a new or retasked system tha generated the error when trying to join the domain. So who is NOT getting in? Duplicate names in a workgroup with different ip addresses work for anything NOT requiring ‘Name’ resolution. Domains require names to be unique.

 
0