• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Slow Windows 2003 Network Performance

M

MulLa

Golden Member
Hi all,

Here's a long story cut short. I've replaced a Windows 2000 DC with a Windows 2003 DC for a buddy's small business. Everything is running smoothly except for network file copy performance.

When I try to copy a file it take a lot longer than when it was running on the 2000 DC, a 700MB file can take over 100 minutes. I've tried LAN bandwidth benchmarking with SANDRA (just as an indicator) and I'm getting something like 112kb/s!!!

It's a new box with a built in GigE controller and the rest of the network runs on 100Mbit.

I've tried a few MS KB's namely disabling the security signature under the lanmanager in the registry also increasing the TCPAck in the registry, all to no avail. There isn't much more KB articles referring to my problem and there are a few posts about this problem in the MS Forums too but their solutions haven't really helped either.

Anyone here has any similar experience?


Thank in advance.
 
Originally posted by: spidey07
cable problem.
Click to expand...

or some kind of a duplex mismatch. what is the switch port set at (auto?) and the cable attaching the server to the switch (patch cord or jacks involved?)

-edit- jeez, mean't to edit. whoops. 😱
 
Thank for the reply.

Switch involved is just a cheapie unmanaged Intel InBusiness 10/100 that they had from a long time ago.

The NIC on the server is set as auto sense. I've tried 100 full or half duplex and also no good. I've tried using various XP client workstations and they're all getting that kind of transfer speed. Maybe I need to set both server and client to 100 full as I've only been playing with the server settings.

The cable is the same cable that the old Windows 2000 DC was using so I doubt it's the cabling. Could it be that the GigE has problem talking to 100 clients?

What made you so sure it's cable / duplex mismatch? You've seen this somewhere?

I might try to put a 10/100 NIC in there after work tonight and see how that goes.


Anymore ideas guys?
 
Gee thanks Spidey07!!! I think your theory turned out to be true. I've switched it with a 10/100 NIC and performance went back up there comparable to the old Windows 2000 DC.

Care to explain why this is happening? Is it because GigE's might be trying to be a bit too quick for the little old 10/100 netowrks?


Thanks once again!
 
well if the cable is bad then you can get what your describing. "some" cards can detect a tip/ring problem and internally switch them. That's where ping 3 might have green/white and the other side pine three is green.

A duplex mismatch is where the switch is operating in full but the card is half duplex (or the other way around) it happens all the time and is the #1 cause of performance problems.

Leaving it to auto should be fine - just make sure the card and switch are showing the same for speed/duplex.

And it never hurts to switch cables with one you KNOW works well. Sometimes even packaged cat5 cables can be bad. You might think "well it worked on the old one so that means the cable is good" isn't a guarantee unless you can get the cable scanned/certified.

But - I'd gather 95 out of a 100 severe performance problems like you experienced are duplex mismatch or cable related (OSI layer 1)
 
Spidey07, thanks for the explaination. Always help to know the reason behind why stuff happens 😀
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top