computer browser service stops for no reason

I have a Windows 2003 domain with PCs on three subnets. The domain
controller is running DNS, WINS and has the registry setting to be the master
browser. I have a server on each of the other subnets with the registry
setting so they are the master browser on their respective subnets. If the
computer browser is started on each of these servers after a while the
service will stop for no reason.

While the service running, users on any subnet can see all the PCs across
all subnets but when the service stops the users get an error message when
trying to browse the network. The event log on the servers just show an
entry with ID 8033 that an election was forced because the master browser has
stopped but there isn't a reason why the service stopped on it own.

How can I keep this from happening?

Are any of your master browsers multihomed or running as remote access
servers? This is the most common cause of browser elections being forced.

If a client tries to get a browse list using the "wrong" IP of the
browse master it will fail. The client will then force an election, because
it can't get a browse list from the master browser.

"Desi" <(E-Mail Removed)> wrote in message
news:6D840C96-A576-4DE0-BEC4-(E-Mail Removed)...
>I have a Windows 2003 domain with PCs on three subnets. The domain
> controller is running DNS, WINS and has the registry setting to be the
> master
> browser. I have a server on each of the other subnets with the registry
> setting so they are the master browser on their respective subnets. If
> the
> computer browser is started on each of these servers after a while the
> service will stop for no reason.
>
> While the service running, users on any subnet can see all the PCs across
> all subnets but when the service stops the users get an error message when
> trying to browse the network. The event log on the servers just show an
> entry with ID 8033 that an election was forced because the master browser
> has
> stopped but there isn't a reason why the service stopped on it own.
>
> How can I keep this from happening?
>
>

No, none are multihomed or remote access servers.

"Bill Grant" wrote:

> Are any of your master browsers multihomed or running as remote access
> servers? This is the most common cause of browser elections being forced.
>
> If a client tries to get a browse list using the "wrong" IP of the
> browse master it will fail. The client will then force an election, because
> it can't get a browse list from the master browser.
>
> "Desi" <(E-Mail Removed)> wrote in message
> news:6D840C96-A576-4DE0-BEC4-(E-Mail Removed)...
> >I have a Windows 2003 domain with PCs on three subnets. The domain
> > controller is running DNS, WINS and has the registry setting to be the
> > master browser. I have a server on each of the other subnets with the registry
> > setting so they are the master browser on their respective subnets. If
> > the computer browser is started on each of these servers after a while the
> > service will stop for no reason.
> >
> > While the service running, users on any subnet can see all the PCs across
> > all subnets but when the service stops the users get an error message when
> > trying to browse the network. The event log on the servers just show an
> > entry with ID 8033 that an election was forced because the master browser
> > has stopped but there isn't a reason why the service stopped on it own.
> >
> > How can I keep this from happening?