Link to home
Start Free TrialLog in
Avatar of Steve Knight
Steve KnightFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Slow transfer speeds from Windows 7 PC TO and NT4 server

OK, this one has had me scratching head.  Next option is look what is happening over the NIC with wireshark etc. but for now any bright ideas, sorry for the long details but imagine most initial thoughts would be things already tried otherwise?

"old" situation.  XP machine, transferring files to NT4 server.  This has special transfer software to an ancient piece of CNC equipment so for the time being isn't changing, though I may virtualise it if it stays much longer.  Transfer rates from here are fine, think they were in the order of 800Kbytes a second, haven't looked yet but assume the NT4 box has a 10Mbit card.

So the XP machine is moved to a new location in the plant, same transfer, fine.

It is plugged into a small 5 port 10/100 switch as there is only one cable coming into that office.  In that switch there is also now a Windows 7 machine.  Same software, drive mapping etc.  It can READ from that share at the same sort of rate 800Kb/sec but writing to it is next to a crawl, i.e. a 15Mb file is predicted around the 3+ hours mark, something like 1Kb/sec, no it isn't connected via 9600 serial cable!

Connected my Win 7 laptop to the same switch, gave it relevent IP address range and same transfer speed issues.

There is no anti-virus, firewall or other software in the way here.  NIC is on latest drivers etc. and all on "Auto" for duplex etc.  Binding order correct, IPv6 off.

Changing NIC to 100/full fixed brings the transfer speed up to 30Kb/sec but the full line speed comms to other servers then drops to 300Kb/sec from 4.5Mb/sec or so like a duplex mismatch issue.  Other NIC settings don't make any real difference including flow control etc.

Now... Windows XP mode Virtual PC installed on that same machine will happily transfer through the same NIC and network at the full 800Kb.sec again.

So that pretty well rules out NIC, cable, switch, server leaving Windows 7 handling of file transfers to NT4?

Most internet searches etc. come back with the normal issues of duplex mis-match etc.  Are there any parameters that you think may help?

thanks

Steve
ASKER CERTIFIED SOLUTION
Avatar of David
David
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You don't happen to have Kaspersky Endpoint Security installed on the Windows 7 machines do you? If you do, have you tried completely exiting out of it?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Steve Knight

ASKER

Thanks for the comments. Half duplex makes things worse / little different from a Windows 7 PC, 100/full improves about 30 times but kills the transfer to the 2003/2008 servers.

The server shouldn't be an issue here as fine from the PC next to it (XP) and from XP virtual machine on the same slow PC and through the same NIC, cable, switch etc.

So Iain may well be onto something there.  I tried all the configs available within the NIC settings but not any tuning to SMB settings etc. yet.   I was hoping that talking to something that old that I'm sure doesn't even know SMB2 exists would be OK but Windows might be stupidly trying smething over and over again.

I am probably not on the site until Thursday now and adjusting NIC settings on workstations remotely isn't the best thing to do...

Will try as suggested and fire up wireshark if not to get some more clues.

Steve
To answer the other comments, no Kaspersky anywhere near it, and without any firewall/AV installed or enabled on it does the same.

Switches for the last comment we are talking Netgear managed gigabit switches but this site location is connected to a cheap 5 port netgear 10/100 with cat-5 to another basic 10/100 switch and some old 10/100 fibre converters back to the main server room.

But... from the pc next to and the same NIC on the same machine from the XP VM it is fine so frankly MUST be Windows 7 config then?

When I am there next my Win 7 laptop also had the same slow transfer so to be sure will fire that up again with an IP for that network and work my way back through the other switche to the server room.

Steve
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks, will feedback as soon as I can get to the site for testing (probably Thurs).
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Not ignoring this and your comments, I tried turning of autotuning earlier today when I eventually made it to the site and that seemed to make a bit of a difference.  Turning of SMB2 didn't.

I looked through wireshark trace of the connection and it seemed to be a right mess but I didn't have time to look much.

The NT4 server had 100/full fixed on it's NIC and various other possible oddities including having two different IP ranges defined on it's one NIC.  Have made some changes here but need to reboot to take effect being NT4.

Next time I'm there will boot the NT4 box and check before any other changes made and test out with Windows 7 box on same switch in case of some network issue.

thanks

Steve
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.
Apologies for leaving this.  Priorities changed and the issues here are still present.  I hope to pickup again with the next week so would like to keep it open and the channel to the people offering helpful comments so far.

thanks

Steve
Coming back to this one, sorry for the delay.

I tried all options given to my knowledge.  Got it a bit faster (50Kb/sec) adjusting the settings on the NT4 server NIC itself.

From XP VM on WIn 7 physical machine was fine still.  From Win 7 host machine or my laptop etc. plugged in slow.

Just tried a load more and out of curiosity tried rocbocopy (same 50Kb/sec) and xcopy.... BUT xcopy /z (network restartable mode) it flies through at full speed.  xcopy without and it doesn't.

So does anyone have an idea of what /z does and whether I can do that through the gui.  meanwhile I'll make him a shortcut using xcopy!

Steve
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Can you try xcopy /J ?
Still not sure what is going on specifically, or having enough time on this site to investigate in depth - I will one day later this week hopefully!

Meanwhile with robocopy /z or xcopy /z the copying of a file around the 20Mb mark takes about 4 seconds which is what I would expect as maximum and very good frankly!

To re-iterate, GUI or xcopy FROM this NT4 server works fine, copy TO it is very slow.  Copy from save PC using an xcopy virtal machine through the same NIC using NAT works fine too.  So it is how Windows 7 is handling file I/o to NT4.

Bizarre thing with robocopy or xcopy of a directory of files between 50Kb and 20Mb.  The 20Mb file takes 4-5 secs, the 200Kb one takes maybe 30 seconds.  The bigger files are consistently quicker in xcopy /z.

So no doubt there is some limit in xcopy and robocopy that says to use the /z restartable logic only over a certain file size, maybe 1Mb as 1.2Mb file was immediate.

Without the /z the files take forever to copy.

Frankly I need to get them to chuck the NT4 server and hopefully later this week may be possible and/or will try a network trace with an xcopy /z to see what is different between a small and large file.

thanks

Steve
Ran this with a few test files with consistent results:

@echo off
setlocal enabledelayedexpansion
for /f %%a in ('dir /b /a-d *.h') do (

  echo !time!
  xcopy "%%a" Z:\test /y /z)
)
echo %time%

Open in new window


Results (just tidied up, not changed)
14:01:21.48  C:Ag1_BOp11_35.h
14:01:22.22  C:Ag1_BOp12_35.h
14:01:26.20  C:Ag1_BOp1_35.h
14:01:31.41  C:Ag1_BOp2_20.h
14:02:55.52  C:Ag1_TOp11_35.h
14:02:56.41

Open in new window

i.e.

1.4Mb = 0.7 secs
8Mb = 4 secs
76Kb = 5.2 secs
320Kb = 24 secs
1.4Mb = 0.9 secs

Without the "/z" option the bigger files take proportionally as long as the small files.

 Directory of C:\Users\stephen\h

02/03/2015  13:34    <DIR>          .
02/03/2015  13:34    <DIR>          ..
20/11/2007  13:47         1,465,066 Ag1_BOp11_35.h
20/11/2007  13:47         8,006,291 Ag1_BOp12_35.h
20/11/2007  13:46            76,002 Ag1_BOp1_35.h
02/01/1980  00:00           320,041 Ag1_BOp2_20.h
21/11/2007  08:48         1,407,763 Ag1_TOp11_35.h
               5 File(s)     11,275,163 bytes
               2 Dir(s)   3,021,324,288 bytes free

Open in new window

Look, your files are WAY too small to make any assumptions.   These tests of yours do not measure the time it takes to read, transfer, write, and flush to disk.     They only measure the amount of time it takes to read the file and give it to the TCP/IP stack for the smaller files.

Transfer hundreds of megabytes before you can make any assumptions .  Use a SINGLE file to measure network, or use the network socket test from MSFT to just measure that.   Multiple files allow for additional buffering and changes the metrics.

Bottom line, the numbers don't make sense because your tests are no good due to small files.  All that small file buffering is giving you bad data that you are making assumptions with.   Forget everything you learned with previous tests and transfer a 300+ MB zip file or something like that and then report back.
That I appreciate the comments, but this isn't about raw throughput.  The same NIC / PC / network switch / server can transfer files from XP OS at full wire speed (at the same time) and can ready from Win 7 but writing from Win7 = SLOW unless using xcopy /z.

I did try bigger files and they were the same relative speed using xcopy /z, i.e. a 200Mb file was roughly 10 times the 20Mb file above.  From the same machine to another server gives 5-6Mb/sec read and write.

BUT anything under about 1Mb in size eems to not trigger the restartable mode method and so transfers at 10-50Kb/sec, about 100th of the speed which is why I was trying to find what this did differently before I fire up wireshark and try and work it out the hard way!

thanks

Steve
To add to that the only files that need transmitting to this server for talking to it's connected CNC machine are normally a directory of 6-8 programs ranging from 50Kb to 20Mb in size so although I completely agree about file throughput testing with little files being pointless generally, in this case this is what is actually needed.

I'm not on their site any more but going to see what else I can find myself too now I know the xcopy /z works "normally".

Steve
Look, you do not know that the copy/z works 'normaly'. The program returns to the prompt AFTER it has been queued up to transfer, not after the file has been copied and flushed to disk at the other end.
IMO command prompt commands work synchronously unless you specifically run something in a different process with a start command. I dont believe /z works any differently?

Appreciate all responses though!
Respectively, they don't run that way.
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.
Thanks for all your inputs.  I went through and filled this in and closed off before but clearly didn't accept...

We have a workaround and gained access into the CNC configs which appears to only be acecssing an NFS share and nothing to do with the other software on this old NT4 box so trying to get firmware updated on the CNC to allow it to talk to SMB shares or the manufacturer transfer app or if not bolt in a newer NFS server.

Some of the above ended up giving me pointers to things I hadn't thought of checkings, others confirmed my own thoughts.  Easiest option frankly is get rid of this NT4 box now so will go down that route now we have access to what talks to it.

thanks again

Steve
Apologies for grade there, A of course.