Once a machine has won the election to be master browser it will stay master browser unless something happens to force a re-election. So if you reboot every PC except say PC Z, PC Z will become master browser and stay in that role until its next reboot, crash or loss of network connectivity. So the machine you prefer as browser needs to be either first up in the morning or the one that gets left on. I suppose you could also force election by stopping the browser service on all the other machines. And there may well be a more elegant way on Technet..
Hope that helps, even though it's a little rough and ready
Re: Master Browser Election
14 years 1 month ago #5561
As you have mentioned, found a great article on Technet. For anyone interested in how Browsers work, how Master Browsers are elected, about server/host announcements etc on an NT4.0 check the below link.
Mainly, when a computer comes on line (if it is set be a browse master), it will force an election. If it is high enough in the pecking order it will take over as browse master. For example:
PDC Win NT server
Win NT server
Win NT workstation
Windows for workgroups
I WFW will only be master of all WFW machines, until something higher shows up (Windows 95, for instance).
BTW. Browse elections can be a killer. I had a rogue 98 machine keep trying to be a browser master and our NT would win. A couple of seconds later, it would try again. Was chewing up our bandwidth (and our NTs resources). We solved the problem by turning the Browse master setting off.
would it be possible that Internet activity (say access to certain URLs) would ceased (or rather unable to query theses sites via DNS) if a force master browser election took place? Would it have something to do with one machine forcing itself to be the master browser or would it be something else? your inputs would be highly appreciated. Thank you.