Using SSH tunnels

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Greg DePasse (depasseg_at_hotmail.com)
Date: 03/02/04 

Date: Tue, 2 Mar 2004 07:18:02 -0800

Hi-
     I've sucessfully used SSH tunnels with Remote
Desktop on a Windows 2000 machine. It involves setting
up a port forwarding scheme in my SSH client and then
configuring RDC to connect to "localhost:<whatever port I
choose (not 3389)>". This works great.

     However, I am now on the road with a loaner Win XP
Pro machine and whenever I enter "localhost:25389" I get
the following error:

The client could not connect. You are already connected
to the console of this computer. A new console session
cannot be established.

It seems to me that the XP version is disregarding the
port number and focusing solely on the name. Is anyone
else using SSH tunnels (I searched for SSH and localhost,
but didn't find anything relevant, so my guess is no
one). Is there a fix for this?

I've tried telnetting to localhost 25389 and it sits at a
blank screen. Is this the desired output? Is there
something I can type as this point to test it?

Any help would be greatly appreciated.

Greg

Relevant Pages

  • Re: Using SSH tunnels
    ... Al Jarvi (MS-MVP Windows Networking) ... I've sucessfully used SSH tunnels with Remote ... > configuring RDC to connect to "localhost:<whatever port I ... > else using SSH tunnels (I searched for SSH and localhost, ...
    (microsoft.public.windowsxp.work_remotely)
  • Starting SSH tunnel using Xinetd
    ... I managed to set up some ssh tunnels to specfic ports. ... Mysql on port 3306 ... port 3306 and gets fwded to the webserver in a secure way. ... I check /var/log/secure and see that xinetd started the mysql-tunnel, ...
    (comp.security.ssh)
  • Re: Using SSH tunnels
    ... Greg ... > Al Jarvi (MS-MVP Windows Networking) ... >> I've sucessfully used SSH tunnels with Remote ... >> up a port forwarding scheme in my SSH client and then ...
    (microsoft.public.windowsxp.work_remotely)