Return to index


Excluding name resolution, probably the bulk of the MS Networking broadcast traffic you'll see is tied to the browser service. All of the following functions are done via broadcast (note, some of this is actually multicast, not broadcast. For simplicity, I won't differentiate).

1) Any machine with sharing enabled (default on all NT machines, File & Print Sharing on 95/98) will register itself with the local Segment Master Browser (SMB) during boot and, at least, every 15 minutes there after. You can reduce the number of broadcasts and the size of the browse list by controlling what machines controlling this.

a) If a 95/98 machine doesn't actually need to share resources (files or printers), remove File & Print Sharing.

b) On an NT machine, you can either:

      1. Disable the Server service (try this on test machines first to be sure it doesn't have unwanted side effects).
      2. Use 'net config server /hidden:no' to tell the machine not to register itself with the local SMB. There is a registry poke you can make to accomplish the same end (details in KB article Q136712 "Common Questions About Browsing with Windows NT"). This is probably the better option, since it leaves the machine able to share resources. So you still have access to the administrative shares.

2) When a machine needs the browse list (e.g. the user opens Network Neighborhood), the machine contacts the SMB or a back-up MB for the list.

a) If I remember correctly, through Policies, you can disable Network Neighborhood.

b) Depending on your situation, you might be able to use persistent drives and shortcuts to reduce the use of browse lists. For example, create a shortcut on the menu of the each client machine for each of the common servers.

3) SMB elections can occur, when (1) a machine that believes it should be the SMB boots or (2) a machine attempts to locate the SMB (to register or resolve a name). By default, all MS machines will participate in browser elections. Exactly who will win can be a rather complex equation, but if there's a PDC on the segment, it should always win. You can reduce unwanted SMB elections by controlling what machines are able to become SMB.

a) 95 has an unfortunate reputation for forcing unnecessary elections and sometimes managing to win them As a general rule, if you have an NT machine on the same endpoint, full time, your best bet is to disable the ability of all 95/98 machines to participate in browser elections. In Control Panel / Network / File & Print Sharing / Properties, set "Browse Master" to Disable (if F&P Sharing isn't enabled, this is unnecessary).

b) NT usually behaves fairly well with the default settings. The default priorities for SMB elections are: PDC, BDC, NT Server, NT Wks. You can use the MaintainServerList to disable an NT's ability to become an MB. You can use IsDomainMaster to give a boost to a machine's priority in an election.

The object is to configure it so that your SMBs are always machines that are online full time. This should eliminate most all SMB elections.

4) A separate browse list is maintained for each 'end point'. An 'end point' is essentially a combination of segment/subnet, domain/workgroup, protocol. The preceding 3 problems apply separately to each browse list. Eliminating unnecessary end points will help reduce broadcasts.

a) If you have additional unnecessary protocols loaded, remove them.

b) Eliminate any rogue workgroups. If they aren't needed for organizational structure, reconfigure the offending machine into common workgroups/domains.

A note about multiple protocols: An NT machine with multiple protocols installed will attempt a connection on all protocols simultaneously. Of the connections that succeed, it will take the one using the highest priority protocol (I haven't checked 95/98's behavior on this). With NetBEUI, this means broadcast traffic (all NetBEUI connections are initiated via broadcast).