I recently switched out a 10 year old server for a brand new server in a small office and upgraded from Windows Server 2000 to Windows Server 2008 R2. After the switch was complete and some configurations were changed around we are running into what appear to be some bottlenecks in the network speed. Accessing programs on the server is slower (resulting in long loading times, slower report generation, etc.) than it was on the old server hardware.

I am wondering what options or tools I have, if there are any at all, to find out exactly where these hang ups might be coming from.

link|improve this question
1  
are there any relevant alerts in event logs? also, i would like to suggest microsoft's performance monitor called "Performance monitor". It helped me to debug a few issues i had. – Paul Jul 21 '11 at 17:39
Nothing I have seen of interest in the event log. I am a bit confused as to how the performance monitor could help debug. I see that there are many options but maybe I'm just not understanding the actual usage of the application. – Phil Koury Jul 21 '11 at 20:05
1  
Perfmon - if you know your network can transfer 100MBytes/second and Perfmon shows only 2MBytes/second on the NIC, you know the network is not your bottleneck. That's how you use it - measure CPU, memory, paging, network, disk IO. See which numbers seem to correspond to the slowdown, then work out why. – EightBitTony Jul 21 '11 at 20:48
feedback

1 Answer

Along with what EightBitTony has pointed out, you can "net out" the network aspects by hard coding the NIC line settings (vs. the default "autodetect") and copying CD or DVD sized transfers for clocking (i.e. with a stopwatch). The multiple timing of the same transfers will help determine any speed fluctuations.

It will also stress the various points/elements that can be monitored via perfmon for variations as well.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.