Actually, the less protocols installed the better, especially on W9x boxes, since they have a tendency to "puke" (official networking term...look it up 😉) when too many interfaces and protocols are loaded. WNT/W2K handle multiple protocols and interfaces much better, but there is still an important reason to eliminate unneeded components: speed.
"Tuning" W9x has become second nature to me over the last several years. Invariably, when I look at a client's computers, I'll see everything under the sun loaded in Network Properties, such as:
Client for MS Networks
Client for Network Networks
Propietary NIC cr@p
NIC (usually multiple times from failed re-installs)
Dial-up Adapter
AOL Adapter
MS VPN adapters
WAN adapters
TCP/IP (bound to EVERY adapter)
IPX/SPX (bound to EVERY adapter)
File and printer sharing (for either MS or NetWare)
ad infinitum
What happens is that the networking stack has to track and process EVERY binding, and sometimes, traffic (such as name resolution requests, print jobs, network file access, whatever) are not sent out over an optimal transport first, and must first time-out before the OS will try the next possible transport. WNT/W2K offers MUCH more granular control over what transports/bindings are preferred for what services, and there are some goofy registry tweaks one can do for W9xif you MUST have all that junk loaded, but for the most part, people (home users, especially) should have the following components in Network properties and nothing more:
Client (for MS usually)
NIC (only one)
Dial-up (if needed)
TCP/IP (no need for ANY other protocol)
Another good tip is to ONLY have ONE default gateway entry on a machine. PERIOD. That means only ONE for all instances of TCP/IP bound to all adapters. There can be exceptions, but I'm talking primarily about SOHO users (by far the bulk of folks on this board).
HTH,
TallGeese