I have just setup a pretty fast network / san solution.
All the latest hardware 3.0Ghz and above and maxed out ram on all
systems.

Problem.

Xp Client Copying is MUCH slower than the 2000 Client. Connected to the
same domain. The network constist of

TEST NETWORK.
All GIGE Coppernetwork and 2Gbit Backend FC SAN.
1 Extreme 400 Switch
2 DFS 2003 Enterprise Servers
8 Server Cluster Farm connected to a SAN. Qlogic and DDN Storage
2 XP Pro workstations dual 3gig 2gigram
2 Win2k Pro workstations dual 3gig 2gigram

For the Tests I am using a folder with 1.23GiGs of Sequential Targa
files that are 6MB Each.


When I do a copy on the XP machine from one of the 8 servers
it takes 1 min 25 Seconds to copy the folder.

When I do a copy on the 2000K machine from one of the 8 servers it
takes 34 Seconds.

When I do a copy using a Server2003 Standard Server machine from one of
the 8 servers it takes 32 Seconds.

I have tested this on different hardware and Nics. It seems that the
one consistant factor is XP pro. I tried XP pro without Sp2 same thing.
I have tried Reg Tweeks I have found on the web.. but still the same
performace issue

When the copying is taking place and I am watching the files being
copied. XP seems to copy in little chunks.. copy 5 files then pauses
for a bit them copied 5 more.

Win2k Pro and Server2003 fly through them.

Anyone have any idea what would be causing this?
Thank you all for your time

-Saker

The problem may be SMB signing or LAN Manager authentication level. In
Windows 2003, default server policy forces all SMB traffic to be digitally
signed which seems to cause a problem in some configurations of XP Pro. In
Local Security Policy (Start > Run > secpol.msc > OK) navigate to security
options (Security settings > Local policies > Security) and try disabling
the option for Microsoft network server:digitally sign
communications(always). Ensure you do this on all machines involved (such
as via a GPO for an OU). Run gpupdate /force on the server after making the
change and do the same on the client machine afterwards.

Security settings that can cause a problem with downlevel client access:
http://support.microsoft.com/default...5BLN%5D;811497
http://support.microsoft.com/default...b;en-us;823659

Or since if XP and Windows 2003 computers are involved:
New registry entry for controlling the TCP Acknowledgment (ACK) behavior in
Windows XP and in Windows Server 2003:
http://support.microsoft.com/default.aspx?kbid=328890

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT