I I have a Windows 2003 AD network that is running slow as molasses. The servers are not being taxed in any way shape or form. Here is the setup.
I have three buildings about 600 feet apart each. They are connected via gigabit fiber optic. I am using 3Com 4228 and 4250 switch stacks in all three buildings. The fiber is connected to the fiber ports on the switches.
Each building has its own domain controller. It is set up so that no building is using the data on another buildings server. The only things that should be going between buildings is the WINS replication, DNS updates, DC replication (virtually nothing) and internet traffic. I have 3Com Network Director monitoring the network and have the link utilization thresh hold set so low it is unbelievable. I know the monitoring is thresh hold working because when the backup goes off at night, and I back up one server from another, it trips the utilization monitor on the link.
I think my downfall might have been how I set up the network. I set it up as one big class A network of 10.0.5.X with a subnet of 255.255.255.0 There are 21 computers in one building, 49 in the other and 110 in the third.
I remember the days of hubs when only one packet could be on the network at any given time but there are 3Com switches. Am I doing something very, very wrong in the way I set this network up to cause such a slowness?