Has anyone figured out the stupid problem with RDP+putty and reverse SSH tunnels yet

[extide]

So, from what I can see, RDP does not work thru a reverse ssh tunnel created by putty. (YET, but since ~2004)

I am convinced it is a bug in Putty, as if I use ‘Tunneler’ I can actually get the reverse tunnel to work perfect and can RDP through the reverse tunnel just fine, but I dont want to use 'Tunneler.' With putty and the exact same config (well the two clients are using different public/private key pairs to auth) it doesn’t work. I get the exact same problem as everyone else, I can see the initial login screen it acts like it is logging in then it hangs and eventually times out and the RDP client closes.

I also tried using plink, with verbose logging on and it didn't show anything abnormal

(FWIW here is the relevant plink output)
Requesting remote port 3388 forward to 127.1.1.1:3389
Remote port forwarding from 3388 enabled
Received remote port 3388 open request from 192.168.1.80:49384
Attempting to forward remote port to 127.1.1.1:3389
Forwarded port opened successfully
Forwarded port closed
Received remote port 3388 open request from 192.168.1.80:49385
Attempting to forward remote port to 127.1.1.1:3389
Forwarded port opened successfully
Forwarded port closed

********************************

I have tried forwarding to:
127.0.0.1
127.0.0.2
127.1.1.1
localhost
actual host name
actual ethernet addres on the nic

everything has the exact same symptoms

BTW Both windows boxes are windows 7 in my case, and the linux box hosting the sshd is a smoothwall box running openssh.

Oh, also, I have tried using the latest released putty/plink as well as the latest development snapshots, as of 11-22-2009. There is no difference, they all have the exact same symptoms.

BTW The ports and routing and all that shit are setup right, that's not the issue so don't try telling me it is.

 

[gsaldivar]

all that shit are setup right, that's not the issue so don't try telling me it is.

 

[extide]

Didn't even bother reading the post eh?

I will also add that this is a fairly well documented problem if you do some googling, although only the problem is documented, there are no solutions.

 

[n0cmonkey]

Have you run a sniffer to see what's going on?

The first two links I see in google document how to set it up. The third is this thread. Any links to more information? Every considered using a decent remote administration software?

 

[Red Squirrel]

I always run RDP through a putty tunnel, seems to work fine... what I had to do is actually connect to like 127.0.0.2 as if I try localhost the RDP client will say I'm trying to connect to myself. (note any IP in 127.x range is localhost - way to waste a class A eh)

 

[goa007]

extide, did you find a fix? I've tried everything you mentioned and much more...still no beef. :\

please let me know, if you found a fix...btw i'm using XP Pro.

 

[glarsson]

I just had the same problem with PuTTY and solved it after many, many hours by using Tunnelier. I noticed that SSH sessions in both directions between my two machines would be interrupted briefly after the initial RDP login screen. Maybe security software caused the interruption, I'm not sure. The interruption may have been enough to hang the PuTTY session. Tunnelier has an option to reconnect automatically if an SSH session is interrupted, I suspect this is why Tunnelier works and PuTTY doesn't (for me anyway).

My configuration:
Computer A: Windows 7, Cygwin sshd (openssh)
Computer B: Windows XP, Tunnelier SSH client with tunnel from computer A port 3300 to computer B port 3389
Run RDP on computer A connecting to localhost:3300

Hope this helps,
Gustav

 

[ninjaxor]

Just in case someone else comes across this thread and has my same situation...
I have a windows based SSH server running on a computer that I want to RDP into. When I set up tunneling I'm able to connect with putty just fine. When I try to use the tunnel to instantiate a remote desktop connection I'm able to submit my credentials and then it hangs/goes blank. I found that I had to make sure that no users were logged into the remote machine in order for it to work. Simple as that for my situation. Good luck.