Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Slow file copy on LAN
- Thread starter hpsait
- Start date
goombawaho
MIS
Do other PCs on the network have this problem or is it just your laptop?
If only your laptop:
Try setting your laptop to 100/Full Duplex in the network card settings and see if that helps. Then 100/Half Duplex
Set back to auto and:
Try a new network cable at your end (your laptop to your wall jack)
Try a different network jack (in a different room) with the new network cable
Try going to the back room and plug directly into the switch where the server is plugged in with new network cable
If only your laptop:
Try setting your laptop to 100/Full Duplex in the network card settings and see if that helps. Then 100/Half Duplex
Set back to auto and:
Try a new network cable at your end (your laptop to your wall jack)
Try a different network jack (in a different room) with the new network cable
Try going to the back room and plug directly into the switch where the server is plugged in with new network cable
See if some bandwidth throttling is being caused by this?
See what this says about Disable Autotuning
Windows 7 Network Slow – 6 Easy Ways to Make it Fast
See what this says about Disable Autotuning
Windows 7 Network Slow – 6 Easy Ways to Make it Fast
All good suggestions above, particularly goom's that suggests plugging "directly into the switch where the server is plugged in with new network cable". I also suspect throttling, but let's see where these steps lead first.
Other factors/questions to consider:
1. Are you logged into the laptop and moving the files directly to the server? Or are you moving the files remotely from another workstation connecting to the laptop in the background (i.e. \\computername\c$)? How you select/move the files can make a difference.
2. Are you trying to move a few large files or a lot of smaller files? Disk fragmentation and the overhead associated with managing hundreds/thousands of files in a single move can be a factor for sure.
3. Is that 7 MB/s (megabytes per second) or 7 Mb/s (megabits per second)?
-Carl
"The glass is neither half-full nor half-empty: it's twice as big as it needs to be."
[tab][navy]For this site's posting policies, click [/navy]here.
Other factors/questions to consider:
1. Are you logged into the laptop and moving the files directly to the server? Or are you moving the files remotely from another workstation connecting to the laptop in the background (i.e. \\computername\c$)? How you select/move the files can make a difference.
2. Are you trying to move a few large files or a lot of smaller files? Disk fragmentation and the overhead associated with managing hundreds/thousands of files in a single move can be a factor for sure.
3. Is that 7 MB/s (megabytes per second) or 7 Mb/s (megabits per second)?
-Carl
"The glass is neither half-full nor half-empty: it's twice as big as it needs to be."
[tab][navy]For this site's posting policies, click [/navy]here.
- Thread starter
- #5
File copy shows 7MB/s - so I guess it is megabytes per second.
Most notebook/workstations only get a max of 7MB/s. Some even averages only 3MB/s. I have tested this with new hardware - same results.
What is an exceptable speed to copy files accross a LAN. We have a brand new network with Catalyst switches etc but find it to be realy slow when copying anything to any server.
Most notebook/workstations only get a max of 7MB/s. Some even averages only 3MB/s. I have tested this with new hardware - same results.
What is an exceptable speed to copy files accross a LAN. We have a brand new network with Catalyst switches etc but find it to be realy slow when copying anything to any server.
It depends on traffic obviously, but at any given point in time, 7MB/s would certainly be acceptable on a 100 Mbps (megabits per second) network.
7 megabytes per second is the same as 56 megabits per second, as there are 8 bits in one byte. There is also some overhead associated with the ethernet protocol, and other factors such as the network topography, switch quality/settings, and interference that come into play as well. Though your speed isn't unbearable (you're able transfer over 400 MB/min), I would expect better on a 1 gigabit-per-second network.
-Carl
"The glass is neither half-full nor half-empty: it's twice as big as it needs to be."
[tab][navy]For this site's posting policies, click [/navy]here.
7 megabytes per second is the same as 56 megabits per second, as there are 8 bits in one byte. There is also some overhead associated with the ethernet protocol, and other factors such as the network topography, switch quality/settings, and interference that come into play as well. Though your speed isn't unbearable (you're able transfer over 400 MB/min), I would expect better on a 1 gigabit-per-second network.
-Carl
"The glass is neither half-full nor half-empty: it's twice as big as it needs to be."
[tab][navy]For this site's posting policies, click [/navy]here.
You say your server is 1Gb, pc is 1Gb, but what is your switch?
What is the switches backplane throughput? I've seen many 1gb switches that only have a 1 or 2gb backplane, which actually means if all traffic is blatting the network, they are all limited to 2gb total.
Dou yo go through a router? What's that throughput?
As for fixing the speed this is BAD advice UNLESS you fix the other end as well.
NEVER set to half duplex, that's just daft.
If you are Auto / Auto, the switch MUST be Auto / Auto, otherwise it will default to half duplex.
If you are 1gb / Full, the switch MUST be set to 1gb / Full otherwise it will default to half duplex.
i.e. if the two are set differently it will not work properly (it will work, just badly)
Robert Wilensky:
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true.
What is the switches backplane throughput? I've seen many 1gb switches that only have a 1 or 2gb backplane, which actually means if all traffic is blatting the network, they are all limited to 2gb total.
Dou yo go through a router? What's that throughput?
As for fixing the speed this is BAD advice UNLESS you fix the other end as well.
NEVER set to half duplex, that's just daft.
If you are Auto / Auto, the switch MUST be Auto / Auto, otherwise it will default to half duplex.
If you are 1gb / Full, the switch MUST be set to 1gb / Full otherwise it will default to half duplex.
i.e. if the two are set differently it will not work properly (it will work, just badly)
Robert Wilensky:
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true.
goombawaho
MIS
For TESTING purposes only, it's not daft at all. I've seen cases where the speed/duplex setting makes all the difference in the world. Then you can troubleshoot further from there OR replace a funky network card. I've had a lot experience in these matters, so give me a little credit.
First thing I would do, test to see if the switch you are using is causing the fault or not, by replacing the switch with another known working one, or by hooking the affected machine directly into the server...
Then the following have caused slow LAN transfer rates on other machines:
TCP Chimney offload might be causing issues, on the 2008r2 server I would turn it off (DISABLE):
Using Netsh Commands to Enable or Disable TCP Chimney Offload
SMB2 might also interfere with the transfer speed, the following link explains it nicely and even though it talks about Vista/2008 it still applies to 2008r2 and Win7:
How to Disable SMB 2.0 on Windows Vista/2008
Recommended TCP/IP settings
Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"
Then the following have caused slow LAN transfer rates on other machines:
TCP Chimney offload might be causing issues, on the 2008r2 server I would turn it off (DISABLE):
Using Netsh Commands to Enable or Disable TCP Chimney Offload
SMB2 might also interfere with the transfer speed, the following link explains it nicely and even though it talks about Vista/2008 it still applies to 2008r2 and Win7:
How to Disable SMB 2.0 on Windows Vista/2008
Recommended TCP/IP settings
Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"
goombawaho
MIS
What BBB said - it's all a matter of eliminating each link in the chain as the problem.
From computer to server:
Workstation network card, network cable, wall jack, in-wall cabling, network switch port, switch, server network cable, server network card. All have to be tested/ruled out.
From computer to server:
Workstation network card, network cable, wall jack, in-wall cabling, network switch port, switch, server network cable, server network card. All have to be tested/ruled out.
hairlessupportmonkey
IS-IT--Management
also try an alternative filecopy app like robocopy / Richcopy
ACSS - SME
General Geek
goombawaho
MIS
I don't think that's the point HarilessSupportMonkey. OP thinks he should be getting better performance with just a straight files system copy.
- Status
Similar threads