Windows Server 2000/2003 Thread, Slow file copy from XP SP3 to Server 2003 SP2 in Technical; EDIT: Could someone rename the thread to Slow file copy from Server 2003 SP2 to XP SP3, thanks
EDIT: Could someone rename the thread to Slow file copy from Server 2003 SP2 to XP SP3, thanks
Having a bit of trouble finding out the cause of this, here is the background info:
XP SP3 Clients (latest intel network driver - PRO 100 VE onto LAN)
Server 2003 SP2 (Intel 1000 MT onto SAN, Broadcom NetXtreme 1000 onto LAN)
On the XP Client, browse to server share \\server\share\ and copy file.exe (nvidia drivers, around 75MB) from the share to local desktop hard drive, copies 75MB in a few seconds - great.
Rename the file on the XP machine to avoid duplication, try to copy the file back to same file share and it takes 8-10minutes.
On the server, if I make a copy of the file within the SAN drive itself, it copies instantly, so no trouble here.
If I also log into the server and browse to \\server\share from itself, its all near instant.
Copying from the server share to my workstation (gigabit) results in the file being copied in about 2seconds. So clearly not a sending problem from the servers point of view.
Why is it taking a few seconds to read from the file share and 10minutes to copy back to a machine on 100Mbit?
Ive tried updating drivers, disabling Large Send Offload on the server (as directed elsewhere), removing network teams, server & client restarts, none of this has worked.
Network switches are all recently replaced, HP Procurve's, takes 10minutes if the school is full with 500 PCs and laptops in use and is taking 10minutes today with just one or two people in school.
This is duplicated across all our 2003 servers (all SP2)
All things seem to point to OS/driver related, but im not sure what is the culprit!
Last edited by Frazer; 22nd July 2010 at 03:44 PM.
Reason: Thread rename
Frazer, you may be having TCP ACK problems during these SMB copies.
If your servers have security signatures enabled on SMB transfers - incoming file copies using SMB (from XP for instance) require the redirector to process the block at the same time, however the redirector will sit there waiting for a TCP/IP acknowledgement before getting on with the next block - result - a slow upload to the server but downloads appear fine.
If the EnableSecuritySignature or RequireSecuritySignature values are set to 1 then this could be the cause. Setting both values to 0 will negate the problem by switching off the security signature requirement.
Hope this helps - otherwise it's another one you can cross off the list!
Lawson-Broadhead IT Consultancy
EDIT: Just tried the following:
XP SP3 Client 100Mb plugged directly into core switch
All fibre ports disabled (only servers and 1 client left in core switch)
Still same problem, so doesnt seem to be network/trunk/switch related
Last edited by Frazer; 23rd July 2010 at 01:40 PM.
Seems a switch reboot solved it
Only once everything else had been exhausted!
Double check Windows Updates - any recent ones causing the problem? Nope
TCP registry mods, specifically New registry entry for controlling the TCP Acknowledgment (ACK) behavior in Windows XP and in Windows Server 2003 and the above tip from Jon.
Various driver versions
Different locations in school
Firmware update on core + workstation switches - this obviously fixed it since a reboot is needed after updating, but I just had a thought while one was updating, ill try rebooting another and it worked!
Not too sure what actually caused the slow down, as switches arent my forté but annoyed I didnt try one of the simpler things that you always tell other people to try first!