Event ID 4319 in system log on win 2k server

[ryoun1b]

I have an event ID 4319 in my system log that comes up hourly.

The description of the message in the error log states:

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.

When I try nbstat -n from a dos prompt it is not recognized as a command or batch file. When run path c:\winnt\system32 is in my path, and I can see nbstat.exe in that directory, but cannot seem to run it to determine the problem.

Can anyone tell me how to identify the duplicate name or how to successfully run nbstat -n

Thanks!!

 

[GlenJohnson]

http://www.zdnet.co.uk/news/specials/2000/10/enterprise/techrepublic/2002/02/article002.html

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Since we cannot know all that there is to be known about anything,
we ought to know a little about everything."
Blaise Pascal

 

[ryoun1b]

Good article, except that it doesn't help the fact that I cannot run nbstat from a command prompt.

when I try to run it I receive the error "nbstat is not recognized as an internal or external command, operable program or batch file"

C:\winnt\system32 is in my path and nbstat is there however, I cannot seem to run it from a dos shell (command prompt).

Any help is appreciated.

 

[roachchip]

Make sure you are typing "nbtstat -n" not "nbstat -n".

 

[sdibias]

I was just going to comment on that, you're using the wrong command... Visit www.netwerkin.com
MCSE 2000, MCSA, MCP, A+

 

[ryoun1b]

nbtstat works fine...

Problem ends up being because I have a multi-honed NIC configuration The network name was trying to register itself twice once on each NIC/adapter. Fix was to team the NIC's using Intel Pro Set utilities/drivers.

Thanks for the replies!