Event 4321 Source NetBT

Haggis McGillicutty

Since adding a new DC to our 2003 AD forest, the new server has been logging
the following at least 5 times a day:

----------
EVENT LOG System
EVENT TYPE Error
SOURCE NetBT
EVENT ID 4321
COMPUTERNAME NTS-E2036-SDC1
TIME 5/30/2007 8:58:14 AM
MESSAGE The name "DOMAIN :1d" could not be registered on the Interface with
IP address x.x.x.207. The machine with the IP address x.x.x.206 did not allow
the name to be claimed by this machine.
BINARY DATA 0000: 00 00 00 00 04 00 56 00 00 00 00 00 E1 10 00 C0
0010: 01 01 00 00 01 00 00 C0 75 00 00 00 00 00 00 00
0020: 00 00 00 00 00 00 00 00
----------

"DOMAIN" represents the non-fqdn name of the domain. x.x.x.206 is another
DC in the same forest.

My research seems to indicate a WINS issue, however none of these servers
are aware of the WINS server in their tcp/ip configurations. Even so, our
WINS server does not have an entry for this server.

Any ideas on where to look next?

Jorge Silva

Hi Haggis
check


If you're sure that no duplicate name exists, check your WINS and clean the
appropriate record for that machine or some old existing one.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Haggis McGillicutty" <Haggis > wrote
in message news:...
> Since adding a new DC to our 2003 AD forest, the new server has been
> logging
> the following at least 5 times a day:
>
> ----------
> EVENT LOG System
> EVENT TYPE Error
> SOURCE NetBT
> EVENT ID 4321
> COMPUTERNAME NTS-E2036-SDC1
> TIME 5/30/2007 8:58:14 AM
> MESSAGE The name "DOMAIN :1d" could not be registered on the Interface
> with
> IP address x.x.x.207. The machine with the IP address x.x.x.206 did not
> allow
> the name to be claimed by this machine.
> BINARY DATA 0000: 00 00 00 00 04 00 56 00 00 00 00 00 E1 10 00 C0
> 0010: 01 01 00 00 01 00 00 C0 75 00 00 00 00 00 00 00
> 0020: 00 00 00 00 00 00 00 00
> ----------
>
> "DOMAIN" represents the non-fqdn name of the domain. x.x.x.206 is another
> DC in the same forest.
>
> My research seems to indicate a WINS issue, however none of these servers
> are aware of the WINS server in their tcp/ip configurations. Even so, our
> WINS server does not have an entry for this server.
>
> Any ideas on where to look next?

Unregistered

Check for the machine in DHCP leases.