Using Putty for Port Forwarding yields poor performance results on Windows, Help?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I need some help with optimizing my ssh tunnels to help get better
performance. I have spent a lot of time trying to get better
performance out of putty and feel like the problem is putty itself. I
wanted to run this by the Experts to see if you all had any solutions.

I am using a putty through a Windows machine to create an ssh tunnel
between my house and my office. I am doing a port forward for port 139
(smb) using the following command:

putty -ssh -C -N -v -noagent -load "" user@hostname [-i "key"] -

I then can mount a share drive by using:
Net use z:\share1 /user:username password

I have setup a Microsoft loopback ( to get around some
issues with sharing over

Now when I start to transfer files I see very slow speed differences.
Below I will provide some test data that will hopefully help
understand the speed. The test was done writing and reading 20 MB
files many time with very consistent results:

Using SSH version 2 with Putty
Writing:  5:31
Reading:  2:06

Using SSH version 1 with Putty
Writing:  3:51
Reading:  0:54

Using Cisco VPN Client (I would of course not use a loopback in this
case but use the IP address)
Writing:  1:59
Reading:  0:47

Using Public (No encryption)
Writing:  1:51
Reading:  0:43

I have read a lot about using blowfish as the cipher and different
options. I have tested this with just a few seconds different results.

For fun I got my Linux laptop and tried the same test. I know this
test isn=19t the same hardware, but the laptop is older than the new

Using SSH2 with Linux
Writing:  1:55
Reading:  0:45

The results were much better on my Linux laptop. I used openSSH that
came with Fedora Core 10.

I tried using localhost instead of the loopback adapter, and
got similar results as well.  This makes me wonder if the problem is
in Putty itself. I did use smbclient on my Linux to get the file over
the ssh tunnel but I don=19t think that would affect my results.

One thing I read was that when bring these scripts over to Windows
there is a problem with the pipes in how they function. Not sure if
this could be some of the issue. This is for cygwin but I wonder if
Putty would have the same issue.
 There's no Windows equivalent for the select function which works on
pipes.  The only function available to test if data is available on a
pipe is a function called "PeekNamedPipe", which is non-blocking.
Source: =
We cannot use cygwin because of it's license. We are going to be using
this for a production application.

Any help with be greatly appreciated.
Start Free Trial

Re: Using Putty for Port Forwarding yields poor performance results on Windows, Help?

Quoted text here. Click to load it

How bout OpenVPN?

Todd H. /

Re: Using Putty for Port Forwarding yields poor performance results on Windows, Help?

On Apr 6, 8:19=A0pm, (Todd H.) wrote:
Quoted text here. Click to load it

I have thought of that. The only problem is that a limited windows
account need access to do this. On XP and vista you are not allow to
add a VPN account from a limited user.
I was looking at the VPN through openSSH by using the -w switch.
Anyone know if this is possible through windows?

Re: Using Putty for Port Forwarding yields poor performance results on Windows, Help?

I think my only option is some type of VPN. I have done some research
on VPN from a Windows computer to a Linux server. I am not finding
what i want, so maybe someone could point me in the correct direct.

Below is the options i have looked into with little luck.

Option 1) I looked at setting up Openswan with L2TP, but when trying
to install L2TP i saw "The l2tpd project is now officially inactive".
So  I did not want to implement something that is dead.

Option 2) I also looked at PPTP because Window can be setup with PPTP
easy. I found many warnings about secure issues. So i did not want to
use that.

Option 3) I looked into just IPSec.After much research to get the
IPsec to work on XP i had to install IPSEC  that would create the
tunnel. I also could not find a way to do this with just a pass phase
or username and password. I had to have a certificate. This was not
going to work installing on 50 computers. (Please see my list below
for more info)

Option 4) I looked into OpenVPN. I am ok to use this, but I havent
found a way to use OpenVPN on the XP machine without a complete
install. If there was a way to just give the exe to a user and send a
username and password then that would be great. But I havent found out
a way to do this.

Below is what i am trying to achieve:
   Connect a Windows XP/2000/Vista computer to a Linux server
   An easy way to get the computer to connect. I would like to install
just an exe into a DIR if possible. Would like to send a username and
password if possible. If i have to use a certification that is fine.
   This is for commerical use so whatever we use we need the rights.
   I wouldnt mind to just use the VPN adapter in Windows.
   Each user needs to be able to have their own access list to the

Let me know if there is a link to a page that might walk me through a
setup that would work for my requirements.


Site Timeline