Event 8032 Browser Errors

Hi,

I have a small server network.  Two DC's and an Exchange server.  Both of the DC's are running DNS and RAS for incoming VPN.

I am receiving 8032 browser errors every two hours on the backup DC and the Exchange server.  The main DC is fine.

I am suspecting this is because the main DC, which is is the master browser, is essentially multihomed due to the RAS server which creates the PPP adapter and IP address.

I read all sorts of ideas on how to combat this in terms of registry hacking and such, none of which make me feel comfortable.  I also read this:  http://support.microsoft.com/kb/292822

Is anyone else running RAS on their PDC which is the master browser and had to combat browser errors?  If so, what are the least amount of changes that have to be done?  I was thinking about adding the DisableNetbiosOverTcpip registry value for the Routing and Remote Access service but I wonder what side effects this will cause?

Any ideas will be helpful for my situation.  I of course like to avoid the registry as much as possible if I can for obvious reasons.  I understand multi-homed DC's can be painful for a variety of reasons but I can't imagine putting up a fourth server to run RAS (I definitetly don't want to run it on the Exchange server)

Thank you.Start Free Trial