Windows Server 2003 Performance Issues

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

We switched to a file server running Windows Server 2003 back in
January, and last week, we started having performance issues. It is
taking a long time to copy files to the server, and I'm trying to track
down the problem. I've been told to run a baseline monitor at night,
and then repeat the monitoring each day for a while, changing the time
each day (to get a representative sample, I believe). I was also told
to schedule a file transfer during the monitoring time, and see what the
usage is before/during/after, and compare it to the daytime transfers of
the same file.

Now here's the question: What things should I monitor? I will be using
Microsoft's Network Monitor (from my workstation).

Thanks in advance.

M. Surprenant

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Sounds like corruption in the tcp/ip stack on the W2k3
machine. If you can try and reinstall the stack by first
removing tcp/ip then re-enabling it..

"Melissa" <msurprenant@siumed.edu> wrote in message news...
> We switched to a file server running Windows Server 2003 back in January,
> and last week, we started having performance issues. It is taking a long
> time to copy files to the server, and I'm trying to track down the
> problem. I've been told to run a baseline monitor at night, and then
> repeat the monitoring each day for a while, changing the time each day (to
> get a representative sample, I believe). I was also told to schedule a
> file transfer during the monitoring time, and see what the usage is
> before/during/after, and compare it to the daytime transfers of the same
> file.
>
> Now here's the question: What things should I monitor? I will be using
> Microsoft's Network Monitor (from my workstation).
>
> Thanks in advance.
>
> M. Surprenant