Tags:Microsoft, Windows, Vista / XP, On a Windows 2000 Domain
I have several VPN clients running Vista & XP connecting to a Windows 2000 domain (Some are domain members, others arn't). Each VPN client is on it's own subnet (/30), meaning clients will not find any existing Local Master Browser for their subnet and will self promote to Local Master Browsers.
The problem I have is that the Browser service takes a long time to populate the network list (variously 30s-6mins). I have analyzed the traffic; The client immediately sees the Domain Master Browser (WINS), and promotion to Local Master Browser occurs rapidly (and consistently) in about 20s (after election broadcasts),.
However it then takes another 30s or so before sending a "Get Backup List Request" [SMB command 0x09]. Additionally, the first 2-3 "Get Backup List Requests" are usually broadcast requests (which will not route) before attempting unicast to the Domain Master Browser.
My question is: A) Why does the newly promoted Local Master Browser take so long to send a "Get Backup List Request", and B) Why does the client attempt broadcast "Get Backup List Requests" when it is explicitly configured with a WINS server, and C) Most importantly, how do I force the Local Master Browsers to be quicker AND only send out unicast "Get Backup List Requests".
<Please ignore the 'Beginner on this subject' - I forgot to change it, please feel free to reply technically, I should understand>
I believe most of this is default behaviour of the Browser service. The Browser service is very old and outdated and the timings aren't configurable. We have a highly routed network and had nothing but issues with missing machines etc. So we just disable it and it then is more secure because people won't just click around looking for stuff.
Thanks for the reply Pber. I'd read both of those articles previously, and unfortunately couldn't find a solution in them. With your network setup, do you mean that users are required to manually type the addresses of servers if they wish to browse their shares? Or have you found some way to provision the machines in the network list without the browser service.
With 6000+ desktop and 400+ servers the browse list is nuts. We map user drives using logs scripts. In a smaller environment it might be more useful, but not ours.
We used to just disable the browser on just desktops, then only allowed browsing on server subnets, but we just turn it right off now.
Usually the browse list takes up to 45 minutes or so to fully populate (~15 minutes for each browser hop until it gets to the PDCe). The times are by design, you can't change them.