$%^*&#! Ok, what am I doing wrong with pscp or winscp?

[Erich Bloodaxe BSN]

So I've got a wireless network up, with decent speeds, or so I thought. But when I try to use winscp or pscp on a windows 7 box to send files to my linux box over the wireless, the transfer is going at like 135 kilobits a second. Not kilobytes, kilobits. Copying a single large file was set to take 9 hours, which is insane. Now I can download the same file wirelessly onto the winbox FAR FAR faster, so the problem has to be with something about the boxes, and not the wireless.

Ideas?

[Make7]

1. Not sure what the issue might be, but you might try a shared folder...

... on one of your machines to access with the other - just to see if the speed is the same or better (or worse).

http://www.howtogeek.com/176471/how-to-share-files-between-windows-and-linux/

[trotsky]

2. Are you using SFTP or SCP to Linux? n/t

[Erich Bloodaxe BSN]

5. scp, I have ftp turned off.

I keep most of my ports closed all the time on that machine since it's a server.

[trotsky]

6. Well that shoots my theory.

I had a box where WinSCP was draggin' but I was using SFTP. Switching to SCP sped it up considerably.

[discntnt_irny_srcsm]

3. How are making the transfer?

WINSCP on the windows box?
Is the speed the same in the opposite direction?

[Erich Bloodaxe BSN]

4. I tried both winscp on the windows box

to send a file to the linux box, as well as pulling up a command prompt to try pscp to do the same. Transfer rates were the same in both cases. I haven't tried pulling a file across in the other direction yet, since the linux box is also my webserver, and I can just pop files into a directory browsers can get to and pull them down to the winbox quicly that way.

[ChromeFoundry]

7. Are there many other networks in overlap on your Channel?

Last edited Tue Oct 21, 2014, 07:03 PM - Edit history (1)

How many other clients are sharing the bandwidth from the connected Access Point?
Are you using 802.11 n or ac (b/g/n or a/n)?
Band 2.4 or 5 GHz?
Rule out potential sources of interference (ballasts, microwaves, etc)?
What is your signal strength (dB)?
What is the Max Rate (54,130,144 or 300)?
What is the MCS Rate (HT20 or HT40 MHz)?

Have you tried over a wired connection?
Check your MTU on both computers and all switches/routers in between (packet fragmentation).

Disabled Windows 7 QoS Packet Scheduler (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Psched)?

Have you tried to test rates via an SMB/CIFS (Samba) file copy?
looked at NETSTAT -s for TCP fails, errors, retries, jitters, etc..?

Watch traffic with WireShark?

[Erich Bloodaxe BSN]

8. Most of those I'll have to look up.

WEP protected, so only one other machine using the same network (and I did check that specifically early on) and it's mostly used to play a game that's local to that other machine. It's an 802.11 bgn access point, max rate 300Mbps, and I suspect on the 2.4 GHz, although as I said, I'll have to check. I'm not using any X10 type stuff around the house, or fluorescents any more (I don't think LEDs have the ballast issues?) and the only microwave was off. I think there are 2.4 GHz phones around, but they've never given me problems before. I think I left MCS at HT20, which was the default, which, now that you mention it, was probably unnecessary and could be at least a partial bottleneck.

I haven't tried wired, but I suppose I will, since the winbox is a laptop that I can pop upstairs to the server and shove on the hub it's on. If that's fast, I suppose I could skip trying to figure out why the wireless is slow and simply copy everything across via that interface. I think the usb ports on the laptop are fried, or else I could just dump things via a thumbdrive.

Off to check MTUs and status of windows packet scheduler now.

And I'd forgotten about Samba, haven't needed to move anything between the machines in a few years, so it's been about 10 or so OS version upgrades since I last bothered to install it when setting up a new version. Guess I could yum it up again.

Netstat is actually showing a fair number of connection resets and abortions, hmm.