NetBT--Event ID 4319

[Guest]

I have several PCs which are receiving the following error. After heavy
review and many night of lost sleep I simply cannot fine the supposed "rogue"
system. I have found no conflicts and nbtstat -n shows no names in conflict
state. Any ideas regarding this one?
The PC is a Windows 2000 Pro on a Windows 2000 Domain network.
Aslso a reboot stopped the message but I noticed it starting on a completly
different PC..ARGHH!!!
------------------------------------------------------------------------
Source: NetBT
Category: None
Event ID: 4319

Description:
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.
----------------------------------------------------------------------

Thanks in advance !!


Rick

 

[Phillip Windell]

There may not even be a rogue machine.

Are you running a WINS Server?

 

[Guest]

Yes, we are running WINS here. And you are right, I honestly feel there is
no Rogue system. It is just something that is filling my logs and would like
to clear it up if possible.

Thanks !!

Rick

There may not even be a rogue machine.

Are you running a WINS Server?

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I have several PCs which are receiving the following error. After heavy
review and many night of lost sleep I simply cannot fine the supposed "rogue"
system. I have found no conflicts and nbtstat -n shows no names in conflict
state. Any ideas regarding this one?
The PC is a Windows 2000 Pro on a Windows 2000 Domain network.
Aslso a reboot stopped the message but I noticed it starting on a completly
different PC..ARGHH!!!
------------------------------------------------------------------------
Source: NetBT
Category: None
Event ID: 4319

Description:
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.
----------------------------------------------------------------------

Thanks in advance !!


Rick

 

[Phillip Windell]

I have had this happen due to the WINS database getting fouled up. I had a
machine that had its IP# changed but the WINS database kept listing it by
the old IP#, so when the workstation booted up and contacted WINS it saw
what "appeared" to be another machine at a different IP# using the same name
(hence a "duplicate name").

I cleared out the bad entry (deleted not "tombstoned) and that corrected it.
In worst cases I cleared the entire WINS database and let it rebuild itself.
It will rebuild on its own, you don't relly have to do anything.

I think the same thing can happen in a DNS database but I don't recall any
instance that I actually know of it happening.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------

Yes, we are running WINS here. And you are right, I honestly feel there is
no Rogue system. It is just something that is filling my logs and would like
to clear it up if possible.

Thanks !!

Rick

There may not even be a rogue machine.

Are you running a WINS Server?

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I have several PCs which are receiving the following error. After heavy
review and many night of lost sleep I simply cannot fine the supposed "rogue"
system. I have found no conflicts and nbtstat -n shows no names in conflict
state. Any ideas regarding this one?
The PC is a Windows 2000 Pro on a Windows 2000 Domain network.
Aslso a reboot stopped the message but I noticed it starting on a completly
different PC..ARGHH!!!

------------------------------------------------------------------------

Source: NetBT
Category: None
Event ID: 4319

Description:
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.
----------------------------------------------------------------------

Thanks in advance !!


Rick