Error - 4321 NetBT

[anthonymel]

I get this error message every 10-20 mintues.

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4321
Date: 4/4/2005
Time: 11:55:56 AM
User: N/A
Computer: WEATHERWOOD
Description:
The name "SMHS :1d" could not be registered on the Interface with IP address 10.5.17.1. The machine with the IP address 10.5.17.6 did not allow the name to be claimed by this machine.

There is no comupter named "SMHS :1d" on my network. The domain is named SMHS. Both IP address listed above are DC's.

10.5.17.1 is also a DNS and DHCP server

What might be causing this problem? This is the only error message I get on either machine.

Thanks in advance,

Anthony

 

[bofhrevenge2]

I've been having the same issue with one of my servers but it only turns up in the event log about once a month, i've never seen any adverse effects but it is annoying.

thread931-1001211

"Horsey to king bish three

 

[anthonymel]

Well, what used to show up every 10 - 20 mintues has not appeared in any error logs in over 4 hours. I think this has to do with the master browers setting on the network. I've been having some difficulty with that server in finding the correct master browser. Its like tug of work between these two DC's

Anyway, if any one has also come across this let us know.

Thanks

Anthony

 

[bofhrevenge2]

I might have this sorted and if so it was my fault.
DC1 (with AD intergrated DNS installed) with IP address 192.168.0.11 had the DNS settings -

P 192.168.0.11
A 192.168.0.12

The second DC also (with AD intergrated DNS installed) had the DNS setttings

P 192.168.0.11
A 192.168.0.12

I've change the settings on DC2 so it uses itself for it's primary DNS and i haven't seen the problem since.

Fingers crossed.


"Sometimes, a cigar is just a cigar." - Sigmund Freud

 

[anthonymel]

I haven't seen that problem in a while on my DC's and I've restart them both a few times since I posted this message. What I did notice was a lot of old DNS records that had multiple IP address pointing to the same address (Host A Records). All has been quite since.


Anthony

 

[PScottC]

The ":1d" suggests to me that the server is trying to register its WINS records with a server that is not a WINS server. Check the IP stack and see if a WINS server is specified in the configuration.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[anthonymel]

Well for some reason this DC used to be a WINS server as well as a DC. I know this is a mistake and I had disabled this feature months ago. So maybe this is just some old info that showed up after a reboot. But since I posted the original thread.

Anthony

 

[bofhrevenge2]

PScottC i know what you are saying and i've checked this but this network is fairly new it is all 2k or above and has never seen a WINS server. So i was a bit stumped on that one.

Cheers.

"Sometimes, a cigar is just a cigar." - Sigmund Freud

 

[PScottC]

Figured I'd throw it in on the off chance.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[pinkpanther56]

This is a problem with the browser service and masquerades as a WINS problem, I was getting it after a problem with a switch.

When the switch went down the servers would lose contact, occasionally when they found each other again one of the servers refused to believe that the PDC emulator was the master and errored every minute. I restarted the browser service on the affected servers and the problem went away.

I very occasionally see it appear once every couple of months in the system log but it usually sorts itself out, only once has it repeatedly shown up multiple time in one day and the service restart sorted it.

 

[anthonymeluso]

Yeah from the research I did when it was a problem pointed me to the browser service. It still crops up every now and then but like you said it sorts itself out.

Anthony