Todd J Heron wrote:
> 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
>
> See also:
> Slow SMB performance when you copy files from Windows XP to a Windows 2000
> domain controller:
> http://support.microsoft.com/?id=321169
>
> Another possibility involving slowness between XP and Windows Server 2003
> computers:
> 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
>
> Also, within an Ethernet network, all network adapters must transmit at the
> same speed (i.e. 100/mbs, full duplex) and be connected to a hub/switch
> which supports that speed of the network adapters, or otherwise network
> communications will be slow and/or unreliable. The network adapters must
> also be configured to support the cable type being used.
>
>
Thanks, Todd. I did give this a try and have had no luck. When I tried
to change the security signing setting, it was grayed-out. I found it
in the registry and changed it there, but no change. I have two 2K3
servers on my network, and the other one seems to work just fine. Its a
very small network (<5 clients), so I have the two servers acting as
DC's / DNS's / WINS with the problematic one also acting as a file
server. The other 2K3 server, if I configure a share, does not have
this problem at all. I can copy a directory from one server to a XPSP2
client and it takes 2 minutes. From the other server, it takes 2 hours.
I ran the network monitor and did notice that network utilization was
running at less than 5%, typically 1-2%, and on those occasions when
performance is reasonable, it will run closer to 30%.
The only thing I can find in the server logs is on the second DC, where
I am seeing hourly error 8032 / 8021 browser errors and "29" W32time
errors. (I assume poor network performance could cause this....)
Absolutely nothing in the logs of the offending server. It seems very
happy.
I have tried multiple NICs, so it isn't that, and the switch is the same
one that the other server & the client use, so its not that. I'm about
to give that server a "Windows Enema" (reformat / reinstall), but if
there's anything else you can think to try first, I'm open!
Thanks for your help, I really appreciate it.
Gray
Similar Threads
Linear Mode
