Slow File Copy Strange Problem

I have been trying to figure out why I have the following difference in file
copy performance over a 100 MHZ network. Copying one 100 meg file from the
client to the server is about 10 secs. Copying the same file from the server
to the client is about 8 minutes ? any ideas. I have given up trying to
explain why the problem is only in one direction. The Serve is a 2003 SBS
and the client is XP pro. All updated service packs are applied.

"Conrad Gotzmann" <Conrad (E-Mail Removed)> wrote in
message...
>I have been trying to figure out why I have the following difference in
>file copy performance over a 100 MHZ network. Copying one 100 >meg file
>from the client to the server is about 10 secs. Copying the same file from
>the server to the client is about 8 minutes ? any ideas. I >have given up
>trying to explain why the problem is only in one direction. The Serve is a
>2003 SBS and the client is XP pro. All updated >service packs are applied.

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

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

These settings were allready applied.


I have tested using the following method. created a 100 meg file in c:\test
called test.dat. I am using the copy command line application.

PC 1 2003 SBS Server
PC 2 XP Pro Client
PC 3 XP Pro Client.

When I am coping the file the command is be executed on the Machine with the
source file.

Test 1 copy from PC 1 to PC 2 8 minutes
Test 2 copy from PC 2 to PC 1 10 sec.
Test 3 copy from PC 2 to PC 2 10 sec.
Test 4 copy from PC 1 to PC 3 10 sec.

Only when PC 1 copies to PC 2 is there a problem ?






"Todd J Heron" wrote:

> "Conrad Gotzmann" <Conrad (E-Mail Removed)> wrote in
> message...
> >I have been trying to figure out why I have the following difference in
> >file copy performance over a 100 MHZ network. Copying one 100 >meg file
> >from the client to the server is about 10 secs. Copying the same file from
> >the server to the client is about 8 minutes ? any ideas. I >have given up
> >trying to explain why the problem is only in one direction. The Serve is a
> >2003 SBS and the client is XP pro. All updated >service packs are applied.
>
> 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
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>

In news:E1EB3224-D584-4EA7-BDDC-(E-Mail Removed),
Conrad Gotzmann <(E-Mail Removed)> made this post,
which I then commented about below:
> These settings were allready applied.
>
>
> I have tested using the following method. created a 100 meg file in
> c:\test called test.dat. I am using the copy command line
> application.
>
> PC 1 2003 SBS Server
> PC 2 XP Pro Client
> PC 3 XP Pro Client.
>
> When I am coping the file the command is be executed on the Machine
> with the source file.
>
> Test 1 copy from PC 1 to PC 2 8 minutes
> Test 2 copy from PC 2 to PC 1 10 sec.
> Test 3 copy from PC 2 to PC 2 10 sec.
> Test 4 copy from PC 1 to PC 3 10 sec.
>
> Only when PC 1 copies to PC 2 is there a problem ?

Conrad,

" Test 3 copy from PC 2 to PC 2 10 sec." ? You mean from drive to drive?

I would check PC2 since receiving data is different than sending data and
requires authentication, and other factors. Anything different on PC2 than
the others? Was anything changed on it? A personal firewall? Any other
services running on it? VPN, NIC driver, etc etc etc? What are the SMB
signing settings on the clients? Were they changed?


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================

Copy from PC2 to PC2 error
should be PC2 to PC3 my error.

After more testing.
What is comes down to upload to PC1 10 sec
Download from PC1 8 minutes.

using the perfmon the difference is the packets / sec
upload 1000+ packets / sec
download 200 packets /sec

Nothing has changed since this has been a problem since day 1.


"Ace Fekay [MVP]" wrote:

> In news:E1EB3224-D584-4EA7-BDDC-(E-Mail Removed),
> Conrad Gotzmann <(E-Mail Removed)> made this post,
> which I then commented about below:
> > These settings were allready applied.
> >
> >
> > I have tested using the following method. created a 100 meg file in
> > c:\test called test.dat. I am using the copy command line
> > application.
> >
> > PC 1 2003 SBS Server
> > PC 2 XP Pro Client
> > PC 3 XP Pro Client.
> >
> > When I am coping the file the command is be executed on the Machine
> > with the source file.
> >
> > Test 1 copy from PC 1 to PC 2 8 minutes
> > Test 2 copy from PC 2 to PC 1 10 sec.
> > Test 3 copy from PC 2 to PC 2 10 sec.
> > Test 4 copy from PC 1 to PC 3 10 sec.
> >
> > Only when PC 1 copies to PC 2 is there a problem ?
>
> Conrad,
>
> " Test 3 copy from PC 2 to PC 2 10 sec." ? You mean from drive to drive?
>
> I would check PC2 since receiving data is different than sending data and
> requires authentication, and other factors. Anything different on PC2 than
> the others? Was anything changed on it? A personal firewall? Any other
> services running on it? VPN, NIC driver, etc etc etc? What are the SMB
> signing settings on the clients? Were they changed?
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If this post is viewed at a non-Microsoft community website, and you were to
> respond to it through that community's website, I may not see your reply
> unless that website posts replies back to the original Microsoft forum.
> Therefore, please direct all replies ONLY to the Microsoft public newsgroup
> this thread originated in so all can benefit or ensure the web community
> posts it back to the original forum.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>

Good morning Conrad.
From what you say, I would exclude an hardware bottleneck.
It REALLY seems an SMB security signatures problem.

Two suggestions :
a) try to do the copy using (for a example) FTP. If you have no slow down,
the SMB problem is really likelly.

b) On the server (is it a DC?) and on the client, check the following keys

HKEY_LOCAL_MACHINE\System\Current
ControlSet\Services\LanmanServer\Parameters\Requir eSecuritySignature value
HKEY_LOCAL_MACHINE\System\Current
ControlSet\Services\LanmanServer\Parameters\Enable SecuritySignature value

If they any of them is set to 1, maybe you have secure SMB working.

--
Fabrizio Volpe
MCSE 2003/2000/NT
MCT

Being a SBS 2003 Server it is a DC and yes the reg values of the client are
both = 0 the security setings.
Ftp upload speed 375KB / sec
Ftp download speed 275 KB / sec

This may also have an effect the server has 2 NIC's with one disabled. I
have tried to change the binding order with no effect.

SBM Traffic is slow but but only in one direction. upload is ok download is
slow.





"FabrizioV" wrote:

> Good morning Conrad.
> From what you say, I would exclude an hardware bottleneck.
> It REALLY seems an SMB security signatures problem.
>
> Two suggestions :
> a) try to do the copy using (for a example) FTP. If you have no slow down,
> the SMB problem is really likelly.
>
> b) On the server (is it a DC?) and on the client, check the following keys
>
> HKEY_LOCAL_MACHINE\System\Current
> ControlSet\Services\LanmanServer\Parameters\Requir eSecuritySignature value
> HKEY_LOCAL_MACHINE\System\Current
> ControlSet\Services\LanmanServer\Parameters\Enable SecuritySignature value
>
> If they any of them is set to 1, maybe you have secure SMB working.
>
> --
> Fabrizio Volpe
> MCSE 2003/2000/NT
> MCT

Ok now to add to the confusion. Only some of the clients have good ftp upload
and download some have poor upload and some poor download. So I would assume
there is a problem with hardware somewhere. The Switch or network cards.

The Network cards are Gigbit on 100mhz switch and are set to 100Mhz Full
duplex.



"FabrizioV" wrote:

> Good morning Conrad.
> From what you say, I would exclude an hardware bottleneck.
> It REALLY seems an SMB security signatures problem.
>
> Two suggestions :
> a) try to do the copy using (for a example) FTP. If you have no slow down,
> the SMB problem is really likelly.
>
> b) On the server (is it a DC?) and on the client, check the following keys
>
> HKEY_LOCAL_MACHINE\System\Current
> ControlSet\Services\LanmanServer\Parameters\Requir eSecuritySignature value
> HKEY_LOCAL_MACHINE\System\Current
> ControlSet\Services\LanmanServer\Parameters\Enable SecuritySignature value
>
> If they any of them is set to 1, maybe you have secure SMB working.
>
> --
> Fabrizio Volpe
> MCSE 2003/2000/NT
> MCT

Hi Conrad.
From what you say we have to exclude SMB problems.
I have the impression that you are "losing" network packets somewhere.
If some clients have a good download/upload rate and some clients have not,
we have to exclude the server and look at the client part of the network.
I suggest you to controll the quality of the network cables (if you have
faulty cables you tend to lose packets) and also to check the settings of the
N.I.C. of your clients.

A test could be also to force the speed of the NICs to 10Mb full and see if
you have faster data movements (slowing down the NIc usually reduced data
transmit errors).

Let me know
--
Fabrizio Volpe
MCSE 2003/2000/NT
MCT


"Conrad Gotzmann" wrote:

> Ok now to add to the confusion. Only some of the clients have good ftp upload
> and download some have poor upload and some poor download. So I would assume
> there is a problem with hardware somewhere. The Switch or network cards.
>
> The Network cards are Gigbit on 100mhz switch and are set to 100Mhz Full
> duplex.

My Problems has been solved.
The network cards.
1 . Marvell Yukon 88E8050 PCI-E ASF
2. Intel(R) PRO/1000 MT Network

both had a problem with the 24 port Dlink 100hmz switch.

If you set the connection speed to 100mhz / full duplex this only worked
with a direct connection between server and client (cross-over cable). Any
setting other than auto-sense the packet rate was very slow. So no instead of
setting the Connection rate as I always do I had to leave the default setting
of Auto-sense with this switch. Aleast now the copy speeds are where they
should be.

Thanks for all your suggestions.




"FabrizioV" wrote:

> Hi Conrad.
> From what you say we have to exclude SMB problems.
> I have the impression that you are "losing" network packets somewhere.
> If some clients have a good download/upload rate and some clients have not,
> we have to exclude the server and look at the client part of the network.
> I suggest you to controll the quality of the network cables (if you have
> faulty cables you tend to lose packets) and also to check the settings of the
> N.I.C. of your clients.
>
> A test could be also to force the speed of the NICs to 10Mb full and see if
> you have faster data movements (slowing down the NIc usually reduced data
> transmit errors).
>
> Let me know
> --
> Fabrizio Volpe
> MCSE 2003/2000/NT
> MCT
>
>
> "Conrad Gotzmann" wrote:
>
> > Ok now to add to the confusion. Only some of the clients have good ftp upload
> > and download some have poor upload and some poor download. So I would assume
> > there is a problem with hardware somewhere. The Switch or network cards.
> >
> > The Network cards are Gigbit on 100mhz switch and are set to 100Mhz Full
> > duplex.