Each network subnet running older Windows Clients and Servers automatically elects a Domain Master Browser amongst the systems on the subnet, this makes one of the systems act like a mini name resolution server on a subnet. Well good? Well...no really, if the Master Browser is a PC or laptop that gets regularly shutdown, this forces network traffic because it forces another election because the Master Browser is gone...the subnet needs a new one! Also, if the Master Browser becomes a PC or Laptop then its performance could be reduced and I have seen clients crash because they cannot handle the load. Here is a good link Domain Mster Browser and Microsoft's own article kb188305
On a server that serves the subnet...edit the registry
Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Services\Browser\Parameters
Type: REG_SZ
Name: IsDomainMaster
Value: True
Type: REG_SZ
Name: IsDomainMaster
Value: True
This should set the server as domain master browser and relieve client systems to do just their thang!!!
No comments:
Post a Comment