Unable to retrieve server list from <master browser>: 64

[Guest J Meyer]

Hi,

 

I was getting browser error 8021 and 8032 in my system log and then my

Windows 2003 std sp2 server would lose communication and have 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

[Guest Meinolf Weber]

Re: Unable to retrieve server list from <master browser>: 64

 

Hello J,

 

Have a look here:

http://support.microsoft.com/kb/135404

 

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 was getting browser error 8021 and 8032 in my system log and then my

> Windows 2003 std sp2 server would lose communication and have 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

>

[Guest J Meyer]

Re: Unable to retrieve server list from <master browser>: 64

 

Thanks, Meinolf.

 

I'm beginning to wonder if the error message are a result and not a cause. I

found this:

 

http://support.microsoft.com/KB/948496

 

and this:

 

http://support.microsoft.com/kb/942861/en-us

 

My NIC is the NC373i. I'm going to try disabling the offload stuff and see

if that helps.

 

Jamie

 

"Meinolf Weber" wrote:

> Hello J,

>

> Have a look here:

> http://support.microsoft.com/kb/135404

>

> 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 was getting browser error 8021 and 8032 in my system log and then my

> > Windows 2003 std sp2 server would lose communication and have 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

> >

>

>

>