SUMMARY: Network Optimization of (ugh) Windows

From: Chris Hoogendyk <choogend_at_library.umass.edu>
Date: Tue Sep 03 2002 - 17:09:53 EDT
As has been said many times: This list rocks!

I got zero replies from the nt admin list (and my post was nice).

My favorite network list (net-troubleshooting@wildpackets.com) was taken
out by a fire. They did have off-site backups, and are buying new
servers and rebuilding.

----------------

Thanks to the following from this list (especially those checked):

      Sirisena, Navi <Navi.Sirisena@gs.com>
   -> Martin Hepworth <martinh@solid-state-logic.com>
      John Martinez <john@mtbiker.net>
   -> Ian Clements <ian@artisan.com>
      joe.fletcher@btconnect.com
      Mark Ryan <mryan@proquent.com>
      Kevin Metzger <kevin.metzger@ieee.org>
 *->> Larye Parkins <LParkins@niaid.nih.gov>
 *->> Brian Dunbar <Brian.Dunbar@plexus.com>
   -> Fogg, James <JFogg@vicinity.com>
      Peter Ondruska <petino@hotmail.com>
      Benjamin Ritcey <sunmanagers@ritcey.com>
      John Eisenschmidt <jweisen@eisenschmidt.org>
      
----------------

Here are a couple of good sources:

http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winntas/maintain/featusability/ntopt1.asp

http://www.microsoft.com/windows2000/server/evaluation/performance/reports/perftune.asp

http://hallwebtools.com/software_design/63.shtml

http://www.microsoft.com/MSPress/books/3211.asp

----------------

Aside from the standard recommendations of monitoring the network and
documenting the facts of the situation, there are actually a significant
number of detailed changes that are recommended for tuning windows after
it is installed.

The basics include:

removing excess bindings for network protocols. this could be choosing
TCP/IP and eliminating NetBEUI and NetBIOS (and of course IPX).
basically, a lot of NT overhead traffic is replicated over all available protocols.

remove unnecessary services from NT installations. leave only services
that are explicitly required for your network design -- particularly for
workstation installations that are ghosted over many dozens of machines.

clamp down on browser traffic by resetting the registry keys that cause
a PC to keep a maintain a server list or compete to be the browsemaster.
use only designated browsemasters. 

control roaming profiles.

the references above also had a variety of other registry settings.

of course, I was specifically looking for NT or Win2000 tuning
information. suggestions like using fixed network speeds rather than
autonegotiated at both ends are useful, but I already knew that and have
been arguing that. Also, check netmasks, use mrtg (got it running), etc.

Thanks to everyone.


---------------

Chris Hoogendyk

-- 
   O__  ---- Network Specialist & Unix Systems Administrator
  c/ /'_ --- Library Information Systems & Technology Services
 (*) \(*) -- W.E.B. Du Bois Library
~~~~~~~~~~ - University of Massachusetts, Amherst

<choogend@library.umass.edu>

---------------
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Tue Sep 3 17:10:47 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:54 EST