Sign in
 

none
Remote desktop to localhost ssh tunnel?

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    How can I make a rdp connection to ssh-tunnel on localhost? In XP I started ssh connection to remote host with tunnel listening on port 3390, then took remote desktop connection to localhost:3390 and my rdp connection was ssh-tunneled and everything worked fine. This doesn't work anymore and I get the following error "Your computer could not connect to another console session on the remote computer because you already have a console session in progress".

    How can this be made in Windows 7 (RC)?
    Monday, August 03, 2009 12:57 AM
    |

Answers

  • Question
    Sign in to vote
    4
    Sign in to vote
    How can I make a rdp connection to ssh-tunnel on localhost? In XP I started ssh connection to remote host with tunnel listening on port 3390, then took remote desktop connection to localhost:3390 and my rdp connection was ssh-tunneled and everything worked fine. This doesn't work anymore and I get the following error "Your computer could not connect to another console session on the remote computer because you already have a console session in progress".

    How can this be made in Windows 7 (RC)?

    I think you will find the RDP 6+ client has issues with the loopback to TCP Port 3390. I suggest using 3391 or another unused higher number port instead. Here is an example using the Tunnelier SSH client.

    http://theillustratednetwork.mvps.org/Ssh/Client06.jpg

    Make sure the Windows Firewall on the PC you want to access with Remote Desktop is configured for TCP Port 3389.

    MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"
    • Marked as answer by Tunnelier Tuesday, August 04, 2009 7:14 PM
    Tuesday, August 04, 2009 11:34 AM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    What is the symptom? Is the connection established, but you cannot logon, or the RDP cannot find the computer?

    I suggest that you change settings on your firewall to allow TCP port 3390, and then check the result again. Or you can temporary disable any firewall and anti-virus, and check the result.

    Arthur Xie - MSFT
    Tuesday, August 04, 2009 10:16 AM
    |
    Moderator
  • Question
    Sign in to vote
    4
    Sign in to vote
    How can I make a rdp connection to ssh-tunnel on localhost? In XP I started ssh connection to remote host with tunnel listening on port 3390, then took remote desktop connection to localhost:3390 and my rdp connection was ssh-tunneled and everything worked fine. This doesn't work anymore and I get the following error "Your computer could not connect to another console session on the remote computer because you already have a console session in progress".

    How can this be made in Windows 7 (RC)?

    I think you will find the RDP 6+ client has issues with the loopback to TCP Port 3390. I suggest using 3391 or another unused higher number port instead. Here is an example using the Tunnelier SSH client.

    http://theillustratednetwork.mvps.org/Ssh/Client06.jpg

    Make sure the Windows Firewall on the PC you want to access with Remote Desktop is configured for TCP Port 3389.

    MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"
    • Marked as answer by Tunnelier Tuesday, August 04, 2009 7:14 PM
    Tuesday, August 04, 2009 11:34 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having the same issue here and is driving me crazy. I setup an SSH tunnel and tested to make sure it is OK. Then I point the RDP of Windows 7 to 127.0.0.1:10051. RDP starts, tells me the machine on the other side is not using RDP 7 ( because it is an XP ), i select to allow it. It does some stuff and then it gets stuck forever in "Configuring remote session..."

    If I do same thing and put localhost:10051 3 out of 4 time connects right away and randomly gets stuck in "Configuring remote session..."

    However with 127.0.0.1 it never connects.

    Using XP to XP or Vista to XP with 127.0.0.1:10051 works all the time
    Thursday, September 17, 2009 4:01 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Using Win7 with putty to tunnel RDP through SSH it works if you use a higher port than 3390. 3391 already works fine!
    Friday, March 19, 2010 7:59 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I run a Ubuntu VM using Sun's VirtualBox on a Win7 Ultimate host and use port 3390 to connect to it.  I had the same experiences as described here, but before finding this thread I found that using 127.0.0.2:3390 would work, while localhost and 127.0.0.1 would not.

    Until I found this thread, I feared that MS had changed the RDP client to not work with any connections to localhost, which would have been a very bad thing, as I use SSH tunnels to connect to remote machines all the time.

    -Jason

    • Proposed as answer by kodiak324 Sunday, March 21, 2010 2:19 PM
    Sunday, March 21, 2010 2:19 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Guys sorry to resurrect this thread but I'm having the same problem and using port 3391 (or any random port, for that matter) doesn't resolve the issue. 

    I've tried localhost:3391, 127.0.0.1:3391, 127.0.0.2:3391 and none work.  I know RDP is working on the host machine as I can connect (directly) without SSH when I'm on the same LAN.  But when I'm trying to tunnel remotely I cannot use the localhost at all and get the standard "Your computer could not connect to another console session on the remote computer because you already have a console session in progress".

    Anyone got some tips/suggestions?

    Do I need the MS loopback adapter installed on the host or client?  I'm authenticating and setting up the tunnel with PuTTY, by the way.

    Friday, January 28, 2011 1:16 PM
    |