Re: NetBT Event ID 4321 Error in System log
Meinolf Weber
Look here:
http://www.eventid.net/display.asp?eventid=4321&eventno=1822&source=NetBT&phase=1
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> Hi,
>
> I can't find any useful information on the below listed error
> that I'm getting on a DC at a remote site. Has anyone had this issue
> before or know what causes it? Thanks.
>
> The name "MYDOMAIN :1d" could not be registered on the Interface
> with IP address 192.168.126.19. The machine with the IP address
> 192.168.126.4 did not allow the name to be claimed by this machine.
>
> All FSMO roles are located on 192.168.126.4.
>
rileymartin
handy. One of those posts led me to the fix for my problem. I thoght I was
just forwarding DHCP requests on the router however I was forwarding the
NetBIOS broadcasts unknowingly as well. As a result another DC was
preventing this DC from becomming the segment master browser. As soon as I
blocked the NetBT broadcasts the problem went away. Thanks again.
Meinolf Weber
Yes this website is really helpful, even if you are not a member. Nice to
hear that you find your solution.
thejamie
rather than a xp workgroup, but the error, 4321 is the same on a machine in
our workgroup. In our case, it is a xp HOME machine on a xp PRO network.
Several things changed recently, a new anti-virus on the XP Home machine, a
laptop fan repair, another machine added to the network (a Windows 7 machine
which may be using IPv6 and not IPv4).
The HOME machine, a Dell laptop, started jumping from its standard IP
address of xxx.xxx.xx.197 to xxx.xxx.xx.198 and then later when that failed,
it started up a xxx.xxx.xx.199. I thought about hard coding the IP address
into the network card, but it seems to be a problem because, I for one cannot
remember that the card has a hard coded IP address and it takes time to
figure that out when there are other workgroup issues so I prefer to leave
the wireless NIC card set to auto-resolve.
The name "MSHOME :1d" could not be registered on the Interface with
IP address xxx.xxx.xx.198. The machine with the IP address xxx.xxx.xx.197 did
not allow the name to be claimed by this machine.
Given these circumstances, the 4321 Event ID appears because the XP Pro,
owner of the workgroup, doesn't recognize the laptop under the new IP
address. The laptop wireless doesn't understand what is blocking it, drops
the wireless connection and tries to pick it up again, or will try to find a
new IP address that is not blocked and the whole mess just repeats itself.
One suggested solution is to dump the workgroup, create a new one and re-add
the machines to the new workgroup. This appears to be a temporary solution
and disturbs others on the workgroup who do not have this problem.
The solution might be to alter the hosts file in the XP Pro machine, owner
of the workgroup. I would do this, as it seems a decent solution, then when
the HOME machine jumps to a new IP, the hosts file can be changed to
accomodate the renegade HOME machine.
My question is more of security. Is using an old (pre-IPSEC ??) solution to
resolve this, secure? We are behind a NAT. All machines run Zone Alarm.
The XP Pro runs CA, Windows 7 - Avast, and the Windows HOME runs AVG.
Is there a way to enable NetBIOS on the HOME laptop that I am missing?
Would that be a more viable solution? Any suggestions appreciated. There
does not appear to be one solution that solves everything.
--
Regards,
Jamie