I am having an 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.

Hi,Maby I`m missing somethink but, how you want to access other computer on network througt local loopback IP? it will work for sure when you use proper private IP for network connection 192.168.x.xdruid

Hi, To narrow down the issue, firstly, please check if this Windows 7 computer can establish the Remote Desktopconnection to other computers without the SSH tunnel. Thanks. Nicholas Li - MSFT

To add...What SSH client are you using?MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"

Yes direct connection works and so does SSH tunneled connection using localhost. Only 127.0.0.1 never works.

I am using JSCH from JCraft. ( http://www.jcraft.com/jsch/ ) integrated in a Java application. I have also tried OpenSSH and putty and got same results.

Have you tried 127.0.0.2 instead? There was an old problem using 127.0.0.1 in the early XP days, ie prior to SP2. I suppose its possible its rearing its ugly head again but as always YMMV...MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"

The answer is no ... 127.0.0.2 fails right away with error that it can not connect to remote computer My test was as following: 1. Setup tunnel on port 10681 and make sure is OK 2. start mstsc 127.0.0.1:10681 --> Stuck forever in Configuring remote session... 3. start mstsc 127.0.0.2:10681 --> Connection error right away 4. start mstsc localhost:10681 --> Connection is fine and I am prompted to input the username and password of target machine Here is a screen with the problem: http://img8.imageshack.us/img8/5354/rcerrorp.jpg

I just setup a SSH server, ie. the copSSH package, on my Windows Home Server as a test. In my case I use the Tunnelier SSH client. I had no problem establishing the SSH connection from my Windows 7 Ultimate (build 7600) laptop to the SSH server. I then connected to my wife's XP Pro desktop through the SSH tunnel with Remote Desktop [RDC]using the addressing form localhost:3391 or 127.0.0.1:3391 without problems. Here is how I had Tunnelier configured for Remote Desktop access to my wife's PC, ie. Norman.http://theillustratednetwork.mvps.org/Ssh/Client06.jpgNow I also configured the Win7 RDC client like this because I am connecting to a PC that does not use NLA protection when in host mode.http://theillustratednetwork.mvps.org/ScreenShots/RDC-NLAandServerAuth/ClienttoServer-NoServerAuth.jpgFWIW here are my old recommendations for configuring Tunnelier so you can access an example network ofthree computers, ie. Ashtabula (the SSH server) and twoother computers(Norman and Miami) with RDC through a SSH tunnel.http://theillustratednetwork.mvps.org/Ssh/Configure-Tunnelier.htmlMy old general SSH page...http://theillustratednetwork.mvps.org/Ssh/SecureShell.html MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"

That's good to know but for me using Tunnelier SSH client is not an option. I have an application which does some checks and then establishes an SSH tunnel, checks the setup and once everything is complete invokes the mstsc.exe /v:127.0.0.1:10681. Like I said in all versions of windows I tested so far XP, XP64, Vista, Vista64, 2003, 2008, 2000 it works fine. In Windows 7 i run into this. Are there any logs I can check on either the client or the target box to see why it gets stuck ? Thanks

That's good to know but for me using Tunnelier SSH client is not an option. I have an application which does some checks and then establishes an SSH tunnel, checks the setup and once everything is complete invokes the mstsc.exe /v:127.0.0.1:10681.Like I said in all versions of windows I tested so far XP, XP64, Vista, Vista64, 2003, 2008, 2000 it works fine. In Windows 7 i run into this. Are there any logs I can check on either the client or the target box to see why it gets stuck ?Thanks I'm not saying you have to use Tunnelier. What I am saying is I don't seem to have the problem you have. If its not working with PuTTY then its not going to work with Tunnelier or as you have found with your other clients. You could check the event logs for possible clues. Here is a nice writeup on that...http://www.petri.co.il/vista-event-viewer.htmI presume your c:\windows\system32\drivers\etc\hosts file is the original and has not been modified.FWIW Tunnelier can also be used from the command line. I have never had a need to do this so as always YMMV. Its just nice to have an alternative SSH client.http://cid-25ab668da65c8fbe.skydrive.live.com/self.aspx/Windows%20images/TunnelierCommanLineHelp.pngMS-MVP Windows Desktop Experience, "When all else fails, read the instructions"

Actually the answer was to install the latest Windows 7 updates and then it started working without anything else. Which is very very strange. I am not sure which update fixed the issue because there were quite a few I had installed.