I have 6gb* of files on my NAS. Copying them over Ethernet took a couple of minutes. Copying it to another machine over WiFi will take about 18 hours!

If I upload the files to the Internet, it will take me a couple of hours and copying it back down (over WiFi) would take another couple of hours... So why does it take four times as long to copy it over the internal network?

The PC is getting the full 38mbps on sweetest over the internet connection, but is copying files at 108kbps.

This is for my iMac, ATIV tablet, a MacBook Pro and 2 Sony laptops.

The problem is, the tablet doesn't have an Ethernet port, so I am stuck with the slow speed, with the others, I can drag them down to the office and connect them to the switch and copy the data in a few minutes.

* that is the first batch of files, in total I have about 28gb to copy.

Does the tablet have USB ?
That might be faster

Is there a problem uploading data? Sometimes it needs to verify and if that data is affected then it can really slow the network. I had a situation with my ISP where the download was officially fine but would not download at full throttle. It was a problem with the upload. When that was fixed it roared along. Maybe your upload speeds are affected so it is sending the slowdown signal to your local host?

It does, but the NAS doesn't. But I'm looking at getting a USB Ethernet.

It is the other way round, copying via the cloud is at mbps up and 35mbps down, no problems, but copying from the NAS on the local network to a local PC on the local network runs at 0,7mbps! Data over the Internet runs at full speed, data that DOES NOT go anywhere near the Internet is slow.

Copying via Ethernet is going at about 160mbps.

I appreciate that, but it was more the principle of uploading verification data that cripples the transfer of data so it reverts to much slower verifiable speeds.

Which protocols are you using? Uploading to web will presumably be https sftp or something. Across your LAN it is likely to be cifs/smb. You might find that if you switch LAN share protocol, the situation might improve.

SMB

smb can be a rotten protocol. can you test with any other?

if not you could try forcing your win8 machine to use the same version of smb as the box (probably v1 only)
http://support.microsoft.com/kb/2696547

The question is still why it runs at full speed over ethernet (160mbps), yet only 800kbps over wi-fi, when the wi-fi is delivering more than 35mbps.

I tried using the Apple (AFP) mode for connecting to the Macs, it didn't make any difference.

How big are the files you're copying?

I'm going to guess on either a conflicting channel for the wireless, something on the wireless network trying to grab the wireless token (I know it's not technically a token but it is half duplex, collision avoidance tech) or they're being slowed down with verification with it being half duplex.

Either that or you've got a subnet mask wrong somewhere

I vaguely remember having a similar problem. One of my computers decided to send data via wifi and it was very slow, it might be done to data verification it was reporting hundreds of hours to complete a transfer. It was much faster over Ethernet. I think I had to turn off wifi so that I could find Ethernet settings.


Sent from my iPad using Tapatalk.

1) Can you try FTP or http, so that you are at least comparing the same protocols?

2) Can you copy files from a PC over the wireless at good speeds? That is, does the problem only happen specifically with the NAS?

3) Assuming it's only the NAS and happens with any protocol, how is it connected to the wireless network? Is it connected directly to a wireless internet router, or via a switch? It could be there is a failure to auto-negotiate so check the relevant ports are reporting the same speed and duplex modes.

Coincidently, I have a not dissimilar problem with a QNAP TS-412U. It transfers at respectable speeds to our Linux servers, but a snail's pace to our Windows server. I'm blaming that on protocol differences; NFS being much faster than SMB... but I've not proved anything yet.