Something to consider:
(from Brian Livingston's column)
IF A LAPTOP periodically joins your local-area network, it may create an unnecessary amount of delays for everyone concerned. The problem occurs when the laptop is running Windows NT or Windows 2000 and the LAN consists of Windows 95/98/Me machines in a peer-to-peer network. Everything seems to run fine, and co-workers can share files and printers -- until that roamin' laptop plugs into the network.
In that case, the portable can assert itself as a "master browser" on the network. This has nothing to do with "browsing the Internet." Instead, the master browser on a Microsoft peer network is responsible for maintaining a list of resources -- servers, file shares, shared printers,and so on -- across a workgroup. A Windows NT or Windows 2000 machine has a higher priority than Windows 9x when it joins such a network. So it becomes the "master browser," but it initially has no information about all the other resources on the LAN. The traffic created by the resulting data-collection process can slow the network down for several minutes.
The solution is to change Registry values that are at Hkey_Local_Machine\System\CurrentControlSet\Services\Browser\Parameter.
To keep a machine from becoming a master, change the value of MaintainServerList to false for Windows NT or no for Windows 2000. To encourage a singlehomed computer to become the master, change the value of IsDomainMaster to yes.
See Microsoft articles atsearch.support.microsoft.com/kb/c.asp and search for
article ID numbers Q191611, Q188001, and Q188305. A scenario for Windows 9x machines is at
http://www.help.com/cat/1/106/hto/3311/3.html