| Author |
Message |
Gray McCordq
Guest
|
 Posted:
Tue Jan 18, 2005 8:46 am Post subject:
S looow file transfers on w2K3 server |
|
|
I'm stumped. I have a small network with a single w2K3 domain
controller. Something has happened that is causing file transfers to
be so slow That it takes 2-3 hours to move a file between the server
and networked systems (all winXP) that normally takes 5-10 minutes.
Does anyone have any ideas what could be causing This?
Thanks in advance! |
|
| Back to top |
|
 |
Todd J Heron
Guest
|
| Posted:
Tue Jan 18, 2005 10:03 pm Post subject:
Re: S looow file transfers on w2K3 server |
|
|
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.aspx?scid=kb;%5BLN%5D;811497
http://support.microsoft.com/default.aspx?scid=kb;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.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Gray McCordq
Guest
|
| Posted:
Wed Jan 19, 2005 5:05 am Post subject:
Re: S looow file transfers on w2K3 server |
|
|
Todd J Heron wrote:
| Quote: | 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.aspx?scid=kb;%5BLN%5D;811497
http://support.microsoft.com/default.aspx?scid=kb;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'll give this a look! |
|
|
| Back to top |
|
|
Gray McCord
Guest
|
| Posted:
Wed Jan 19, 2005 7:26 pm Post subject:
Re: S looow file transfers on w2K3 server |
|
|
Todd J Heron wrote:
| Quote: | 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.aspx?scid=kb;%5BLN%5D;811497
http://support.microsoft.com/default.aspx?scid=kb;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 |
|
| Back to top |
|
|
Derek
Guest
|
| Posted:
Sat Jan 22, 2005 3:54 am Post subject:
Re: S looow file transfers on w2K3 server |
|
|
I am experiencing the same issue however I have Wink2 clients performing
poorly to a 2003 file server.
"Gray McCord" <gmccord@intergate.com> wrote in message
news:10uso0k8i0fgq2a@corp.supernews.com...
| Quote: | 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.aspx?scid=kb;%5BLN%5D;811497
http://support.microsoft.com/default.aspx?scid=kb;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 |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in