Comments on: Remote Desktop via a PuTTY tunnel

By: Frank

Frank — Mon, 30 Jan 2012 14:09:28 +0000

One other note: I'm using Windows 7.

By: Frank

Frank — Mon, 30 Jan 2012 13:57:14 +0000

I've tested a lot w/ all and a combination of most all on this page with no luck. :-(
Though, I think I've gotten to the point where RD is talking to the port Putty is listening to, but Putty is not forwarding the data over the tunnel. Here's my settings:
Local: 127.254.254.254:3306
Destination: 24.60.229.XXX:3389
RD: 127.254.254.254:3306
Now the reason I think that RD is communicating with Putty is b/c when I run it I get the login prompt at my local PC. If I change the RD port number up or down a port number, I get the message that the remote computer is not found... This tells me that there is a Terminal Service process listening on 127.254.254.254:3306. It has to be Putty. But, why isn't Putty forwarding the data/request over the tunnel?
All responses are welcome...
F

By: Vanessa

Vanessa — Wed, 23 Nov 2011 15:01:34 +0000

Thanks for this detailed description, we are currently testing if the Remote Desktop solution is something that we could use in our company. This descriptions helps us to utelize it better.

By: ankit

ankit — Wed, 20 Jul 2011 09:14:30 +0000

i couldnt do it!!!

By: dancehall974

dancehall974 — Wed, 06 Apr 2011 20:26:56 +0000

Is it possible to have a configuration such as :
Local Computer --> TUNNEL --> FIREWALL --> TUNNEL --> Remote Computer ?

By: Steve

Steve — Tue, 01 Mar 2011 17:01:38 +0000

Yes, make sure when you remote desktop you connect to 3390.

By: itauthor

itauthor — Thu, 18 Nov 2010 12:47:23 +0000

Thanks! Very funny comment.
Glad you found it useful.
:-)

By: Venevus

Venevus — Wed, 17 Nov 2010 20:26:20 +0000

sweet mother of god! you're my hero, I've been searching for hours as to why the magic that everyone else was experiencing wouldn't work for me. Finally someone who actually knows some shit and doesn't just copy-paste from other sites. you rock.

By: Dixie

Dixie — Thu, 06 May 2010 08:54:43 +0000

Had the same problem with windows XP (it tries to setup an rdp session to the localhost regardless of the port forwarding in putty)

I think that perhaps doing:

Source: localhost:3390
Destination: remote.pc.example.xyz:3389

Is even a bit more transparent than the suggestion by peliroco and for me it works just as well.

By: peliroco

peliroco — Wed, 24 Mar 2010 23:16:45 +0000

I also ran into this problem. I managed to solve it by setting the local source port to an IP address within my LAN (i.e. i didn't use 127.x.x.x at all). For example: if i know my local IP (the computer you are sitting at) is 192.168.2.20 then i'd input 192.168.2.20:3390 into Source port and 192.x.x.x:3389 into destination. Then using RDP try connecting to 192.168.2.20:3390. This should get around the localhost problem.

By: coolbeans

coolbeans — Wed, 17 Feb 2010 15:17:28 +0000

Use an IP forwarding service like dynDNS and enter that as the address.

By: Alistair

Alistair — Mon, 11 Jan 2010 15:11:54 +0000

Sorry to hear it doesn't work for you. I feel your pain!
If you find a solution please do post a link here. Thanks.
-Alistair

By: Window2008

Window2008 — Mon, 11 Jan 2010 14:47:13 +0000

Hi M8. The above works fine if you got the Windows 2003 and older versions. under Win 2008 (peace of Junk !) and W2K8R2, no matter what 127-IPRange does end up to circular connection issue ! I am getting really tired of this Windows Shit. So much time does it cost us all. I am still searching for a solution to the mentioned problem. If I manage to get a solution I will post it here

By: Mark

Mark — Sat, 31 Oct 2009 18:35:51 +0000

To get it to work for me, I had to change the local port to something other than 3389 (i.e. so that I would put 127.0.0.2:3390 into mstsc.) Not sure why but I would always make a rdp connection to the local box if I used 3389.

By: Matthias Rohe

Matthias Rohe — Tue, 20 Jan 2009 15:23:53 +0000

Thanks a lot. That's just what I needed!
Matthias