<div>
Great! Thanks very much for your help!!
</div>


<div>
<div class="content wysiwyg-content">
I occasionally (two or three times a month) get browser error 8021 and 8032 in my system log and then my Windows 2003 std sp2 server loses communication and has to be rebooted. <br />
Not sure if it's related, but when I later tested with browstat status from <br />
that machine I would get (on average) 10 successful results and then a result <br />
with the line above (the master browser it was using was also the domain <br />
master). I moved the FSMO roles to another DC and then ran browstat status <br />
and received successful results from the new Domain Master Browser every time <br />
(I ran it at least a couple hundred times.) My questions:<br />
<br />
1. Do you think the 8021 and 8032 errors and the browstat error were <br />
related? The server in question runs an application which relies heavily on <br />
NetBIOS.<br />
<br />
2. What kinds of things might have caused the original domain master to be <br />
flaky?<br />
<br />
Thanks!<br />
<br />
Jamie
</div>
</div>


I occasionally (two or three times a month) get browser error 8021 and 8032 in my system log and then my Windows 2003 std sp2 server loses communication and has to be rebooted. 
Not sure if it's related, but when I later tested with browstat status from 
that machine I would get (on average) 10 successful results and then a result 
with the line above (the master browser it was using was also the domain 
master). I moved the FSMO roles to another DC and then ran browstat status 
and received successful results from the new Domain Master Browser every time 
(I ran it at least a couple hundred times.) My questions:

1. Do you think the 8021 and 8032 errors and the browstat error were 
related? The server in question runs an application which relies heavily on 
NetBIOS.

2. What kinds of things might have caused the original domain master to be 
flaky?

Thanks!

Jamie

Is my browstat error related to 8021 and 8032 events and what might have caused it?

The Internet Protocol (IP) is the principal communications protocol in the Internet protocol suite for relaying datagrams across network boundaries, organized in abstraction layers, traditionally called "Link," "Internet," "Transport" and "Application”. Its routing function enables internetworking, and essentially establishes the Internet. IP defines packet structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

Internet Protocols

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).