Master browser conflict

[Guest]

I have a Win 2000 server domain and a mix of WinXP Pro and Win2000
workstatiosn. All behaved well until recently when one XP machine bagan
conflicting with the server over the master browers.

On the XP the TCP/IP settings are to get an IP address automatically and to
get the DNS server name automatically and the other configurations are
default. The XP can log into to the domain ok but network resources are not
available. It can access the internet but can't interact with the other
computers or the server. when the XP logs in, a system error is generated on
the server. It reads:

"The master browers has received a server announcement from the computer
(computer name) that believes that it is the master browser for the domain on
transport NETBT_Tcpip_{EE226A9D-DD3D-41C1-. The master browser is stopping
or an election is being forced.

The Microsoft knowledge base action for this message was to change the
TCP/IP protocol configuration to the correct subnet mask. This can't be the
fix because on the XP, with auto settings, there are no subnet mask entries.

Anyone familiar with this problem and know how to fix it?

Thanks in advance.

 

[Doug Sherman [MVP]]

Try:

1. On the XP machine go to Administrative Tools/Services.

2. Double click on Computer Browser and set the Startup Type to Manual.

3. Reboot the XP machine.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[Guest]

Setting the registry entry for MaintainServerList to False in the XP solved
the master browser conflict. However the XP still can't see the network. It
can get to It can get to My Network Places\Entire Network\Microsoft Windows
Network\Domain Name.

At that point it retnrs the message stating. "DomainName is not accessible.
You Might not have permission to use this network resource. Contact the
administrator to find out if you have access permissions. The list of
servers for this workgroup is not currently available"

The XP can ping the server and read the server using Net View.

What would be causing this? This machine was running fine for over a year
until just recently.

thanks,

Andy

 

[John Wunderlich]

At that point it retnrs the message stating. "DomainName is not
accessible. You Might not have permission to use this network
resource. Contact the administrator to find out if you have
access permissions. The list of servers for this workgroup is not
currently available"

The XP can ping the server and read the server using Net View.

What would be causing this? This machine was running fine for
over a year until just recently.

I have seen problems like this caused by firewalls. Are you running
any firewalls on your machines? If so, try disabling them as a test.


-- John

 

[Guest]

To clarify,

Net View with the servername returns the server info. Net View without the
servername returns a "network is not accessible error."

There is no firewall between the machine and the server, but there is
between the internal network and the internet. The windows internal firewall
is disabled. The other XP machines do not have this problem. this machine
did not either until recently.

 

[YorS]

You may have a firewall you never installed. One of the Service Packs for XP
installed and automatically turned on a personal firewall. Make sure it is
disabled (control panel).
Thanks MS

 

[Guest]

Actually there was a firewall. User had Norton Internet security installed
and somehow, she swears she didn't do it, the firewall settings were reset to
exclude viewing local computers both in and out.

This explains why it was only this XP machine and I would surmise that the
Master Browser conflict message on the server was in response to the XP
firewall being on.

Thanks all for your help.

Andy

 

[John Wunderlich]

To clarify,

Net View with the servername returns the server info. Net View
without the servername returns a "network is not accessible
error."

There is no firewall between the machine and the server, but there
is between the internal network and the internet. The windows
internal firewall is disabled. The other XP machines do not have
this problem.

The symptoms point to an inability to find a local master browser.
The only other thing I can think of is that one of your computers has
an incorrect Subnet Mask setting in the network settings and does not
"see" the other machine that is Browse Master.
You might try using the Browstat program in the resource kit to help
troubleshoot.

Good Luck,
John