Weird Master/Backup Browser issue on network with ~40 computers

[Maverick2002]

We're having a strange issue with our Master/Backup Browsers in a Workgroup network consisting of ~40 computers. Running Browstat.exe shows that most computers are seeing our Win2k server as the Master Browser (as it should be, since it's our only server OS), but a few XP boxes (both 32 and 64 bit) see themselves as the Master Browser with the Win2k box as a Backup Browser.

I haven't been able to figure out why this is. We're all on the same subnet, so we shouldn't have multiple Master Browsers. I'm inclined to say it's just a "characteristic of Workgroup networks once you get past X amount of PCs", but I'm hoping there's a better explanation than that.

In light of that, I've also looked into switching over to a Domain based network, but am wondering how much it's actually going to benefit us.

Any light on this would be much appreciated 🙂

 

[spidey07]

You'll need to run a netbios name server, WINS. And change the netbios node type on all machines to hybrid. Otherwise a single misconfiguration on a single machine will mess with your browse list.

 

[imagoon]

Since spidey answered this already...

Ditch WINS. NetBIOS is a nightmare, "enhancing it" is more of a nightmare. Even without a domain you can use DNS registration and server short names. Just handout a search path. (Connection-specific DNS Suffix) and run DNS on the server. Point all the clients (via DHCP) at the DNS server, let the DNS server handle "the internet" also. Do not put any other DNS entries in the clients or the server.

\\shortserver

will still work because the 2k and XP machines will use dns to do the look up should netbios not be there. It will lookup shortserver.searchpath.local and get the IP.

To respond to your other comment. Domains give you centralized security. This might be of value since it eliminates having 40 passwords (local). It also allows your admins to maintain the machines via domain policies rather than going to 40 machines to set one setting. Typically something like WSUS is a great use of a domain, allowing you to force out patches rather than praying that all 40 machines are pulling patches properly. It also reduces the internet load since the server gets the patches once and rolls them out vs 40 pcs each getting a copy.

 

[spikespiegal]

In light of that, I've also looked into switching over to a Domain based network, but am wondering how much it's actually going to benefit us.

It generally eliminates all the goofy browser elections affecting anything once you go full DNS, but I'm one of the few that doesn't see the need to force small businesses into Active Directory for no reason. Otherwise, screwy Master Browser elections generally don't have any bad consequences (unlike NT4). It can cause slow network browsing, but by now you should be using start>run>\\%computername% rather then dicking around with network_neighborhood and NetBIOS handshakes.

You have to remember that Microsoft makes pier to pier networks as redundant as possible because they assume there won't be a lot of technical support. Doesn't always explain the algorithms and voodo that results in master browser elections. Just be thankfull netBEUI is no longer a default protocol like it was on NT 4, although I hear Spidey likes it (JK). Keeps switches warm 🙂

Otherwise, forcing master browser compliance on big NT 4 domains often involved a Ouiji board....and then a baseball bat.

Seriously, I've worked in some pretty big pier to pier Windows networks, and while they can be a pain from an administrative standpoint, they generally work OK if users aren't roaming around a lot. Again, the function of computers is to make the user's job easier - not mine. AD doesn't always make things smoother -depends on the business. A lot of offices are entirely mobile as well. Nice to throw a script down or registry update with a GPO, but that's for advanced classes. What I hate is networks that have a mix of workgroup machines and domain based machines. That will drive you frikken insane.