![\"\"\/](\"http:\/\/www.softwaresecretweapons.com\/jspwiki\/images\/out.png\")
<\/figure>\n\n\n\nYou\u2019ll need an SSH server installed at home. I\u2019ve used OpenSSH, but any SSH implementation will work. Windows users can use OpenSSH for Windows<\/a>; Unix (including Mac OSX and Linux) users can use the standard OpenSSH distribution. You can secure SSH by using SSL and various kinds of encryption.<\/p>\n\n\n\n If you\u2019re using a router or firewall at home, make sure to allow incoming connections on the SSH port (port 22 by default).<\/p>\n\n\n\n You\u2019ll also of course need an RDP (Remote Desktop Protocol) client in your office. Windows users can use Microsoft\u2019s Remote Desktop Client that is part of Windows XP. Unix users can use RDesktop<\/a>.<\/p>\n\n\n\n Ensure that your home computer is setup to accept remote connections for a specific user account. Go to Start > Settings > Control Panel<\/strong> and then double-click the System<\/strong> icon. On the Remote tab, select the Allow users to connect remotely to this computer<\/strong> check box.<\/p>\n\n\n\n And finally, obviously you\u2019ll have to leave your workstation running (though you should log off).<\/p>\n\n\n\n Securing RDP with SSH tunnel<\/strong><\/p>\n\n\n\n The SSH client software like PuTTY<\/a> can be used connect to home SSH server from the office. From your computer at the office, SSH into the home \u201cSSH Server\u201d with PuTTY or by executing the following command from the prompt:<\/p>\n\n\n\n You should now have a command prompt on the home \u201cSSH Server\u201d. From there, execute the following command to enable traffic tunneling:<\/p>\n\n\n\n This will tunnel all traffic arriving from source office.username@office.ip.address port 3390 to destination home.ip.address port 3389. Now from your computer at the office, use your Remote Desktop client to connect to localhost:3390<\/strong>, this will connect you to the home computer. The Remote Desktop traffic will be tunneled over SSH. If localhost<\/strong> does not work, try to use 127.0.0.1:3390<\/strong> on Windows XP SP1, or 127.0.0.2:3390<\/strong> on Windows XP SP2. This is due to changes in TCP loopback interface that occurred in SP2.<\/p>\n\n\n\n Securing CVS access with SSH tunnel<\/strong><\/p>\n\n\n\n You can tunnel other kinds of ports (CVS for example) the same way. For CVS traffic tunneling use following command:<\/p>\n\n\n\n This will tunnel all traffic arriving from office.username@office.ip.address port 2402 to destination home.ip.address port 2401. In order to access home CVS from the office connect to localhost:2402<\/strong>.<\/p>\n\n\n\n Windows XP SP2 Patch<\/strong><\/p>\n\n\n\n Please note that something got broken in Microsoft Windows XP Sp2. You must apply patch<\/a> or none of the loopback interfaces will not work, including one required for RDP over SHH.<\/p>\n\n\n\n Comments (25)<\/strong><\/p>\n\n\n\n <a href=\u201dhttp:\/\/tripoverit.blogspot.com\/2008\/08\/ssh-port-forwarding-x11-fowarding-rdp.html\u201d> local port forwarding <\/a>\nComment by eduif \u2014 November 6, 2008 @ 5:42 amMy client PC is a Windows XP SP2 without any patches installed. It did not work with: Many thanks for any advice, Here\u2019s how you can secure your Remote Desktop (RDP) connections with SSH. This can be useful for connecting to your home computer from the office or some other remote location. We use here an advanced SSH feature for TCP\/UDP IP … Continue reading <\/figure>\n\n\n\n<\/figure>\n\n\n\n
\nssh \u2013p<ssh.port.number> home.username@home.ip.address<\/a><\/li>
\n-Will<\/li>
\n– burhanuddin<\/li>
\nhttp:\/\/tripoverit.blogspot.com\/2008\/08\/ssh-port-forwarding-x11-fowarding-rdp.html<\/a><\/li><\/ul>\n\n\n\n
\nplink.exe -ssh -2 -batch -v -L 127.0.0.2:3390:<Remote Desktop Host>:3389 -pw <password> sshuser@sshserver
\nThen use localhost:3390 in the Remote Desktop Application.
\nBut it did work with:
\nplink.exe -ssh -2 -batch -v -L localhost:3390:<Remote Desktop Host>:3389 -pw <password> sshuser@sshserver
\nthen use localhost:3390 in the Remote Desktop Application.
\nThis seems other way arround then explained. Can anyone understand what is going on?\nComment by Rob \u2014 March 12, 2009 @ 4:23 pmWindows 7 apparently won\u2019t let you connect to any local IP. I tried several of these work arounds with no love. Only thing that willrks so far is WiSSH\nComment by Tamas Feher \u2014 April 4, 2009 @ 5:16 amThe recommended SP2 hotfix is obsolete, because Windows XP3 SP3 is now available and needs a new hotfix package!\nComment by John \u2014 October 1, 2009 @ 2:14 amAwesome post! I established an SSH connection and was trying and trying with RemoteDesktop 3389 and couldn\u2019t figure out what was wrong. I saw the article by microsoft and applied the patch to the client (not sure if the client needed it, but did anyway) and still couldn\u2019t get it to work. Once I used the putty UI to set the source port to 3390 and the destination to <computerName>:3389, it worked!!! thanks so much! Great site!\nComment by cheap computers canada<\/a> \u2014 November 2, 2009 @ 12:40 pmWhat is the syntax to enable the RDP access and specify the alternate port? Thanks.\nComment by Jeremy \u2014 December 15, 2009 @ 11:39 amI have tried everything to connect to a Windows 7 (x64 Pro) box and have absolutely no luck. I have tried connecting from Win XP (SP3) and Windows 7 (RC). I have tried the 127.0.0.2 trick, the 3390 trick, and no go. I know my firewall and SSH setup is working properly because I can tunnel a Bonjour for Windows port so that I can stream stuff over iTunes just fine. I even installed a VNC server and got that to work ok too. Everytime I try to connect with Remote Desktop it says \u201cconnecting to localhost:3390\u2033 and then says \u201ccannot connect\u201d.\nComment by Jeremy \u2014 December 15, 2009 @ 11:50 amShould also add that I used to have Vista x64 and everything worked fine. Only a problem in Windows 7. I have verified my Windows Firewall setup and made sure Remote Desktop is allowed.\nComment by Jeffy \u2014 December 16, 2009 @ 8:35 pmYep, I got it working great.Windows 7 Client \/ Windows 7 Remote End \/ Debian SSH server, Added Local 3391 port to the tunnels section of the PuTTY config and set the destination as int.ip.address:3389 and saved the config. Then used remote desktop as 127.0.0.2:3391 and voila.\nComment by Steven Roberts \u2014 March 3, 2010 @ 10:43 pmon windows 7 release localhost:3390 wouldn\u2019t work for the port forward but localhost:3391 or :3392 worked just fine. weird.\nComment by Kathryn \u2014 March 4, 2010 @ 7:51 amHi,
\nOK, I got a bit lost reading these posts\u2026(am new to all this..).
\nWhat I want to do is connect FROM Win7 (home\/remote location) TO Win XP Professional (office). I will have no desktop PC in my office to create a RDP because my new laptop IS my work PC. So, what I need is to connect externally to the company\u2019s network drives and work from them as if they were local.
\nIs this SSH thread\/idea the solution?
\nIf not..does anyone how this can be done?\n<\/p>\n\n\n\n
\nKathryn\nComment by Mohit Gidwani \u2014 April 12, 2010 @ 11:01 am@Steven
\nI\u2019m trying to connect from Win 7 to a machine running Vista. I tried the 3391 thing you recommended but i\u2019m still not getting through. Is there any other work around for this? (*grumbles*)\nComment by Ephram \u2014 April 15, 2010 @ 5:36 pmI don\u2019t think OpenSSH works with Windows 7 x64 properly. I tried installing it and could not get the service to launch. The log files weren\u2019t exactly helpful, either.I might try setting up a linux box to SSH into and then tunnel to my Windows 7 through that.\nComment by max \u2014 May 19, 2010 @ 12:04 pmwindows 7 : local connection to 127.0.0.2:3391 to my.server:3389 was the only thing that finally worked. cheers!<\/p>\n","protected":false},"excerpt":{"rendered":"