Tunneling RDP over SSH

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

I'm trying to remote desktop into one of my clients sites which is behind a
corporate firewall. I am running an SSH server, and in the past I have been
able to tunnel port 3389 to my server from their client machine. Normally, I
have my client download plink from putty and execute this command:
plink -l username -R 4444:localhost:3389 mydomain.com

And then from here I can remote desktop into localhost:4444 on my server and
bypass their firewall.

But it seems that this firewall is still blocking me somehow. When I have
the client turn on verbose output in plink, it appears to work but then the
connection is somehow cut off right away. When they login they get:

Access granted
Opened channel for session
Requesting remote port 4444 forward to localhost:3389
Remote port forwarding from 4444 enabled

And then when I try to connect to localhost:4444 on my server, I get this:

Attempting to forward remote port to localhost:3389
Forwarded port opened successfully
Forwarded port closed

So, I'm wondering if I need to forward more ports or if there is anyway to
debug what is going on here. Perhaps I need to forward some UDP ports?

Thanks for your help.

(By the way, the client is running Windows XP Pro with Remote desktop
enabled and his personal firewalls have been disabled. My server is a
Windows 2000 box.)

.

Relevant Pages

  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: RealVNC
    ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003, Fully patched, and cannot RDP into machine
    ... I try to telnet to port 3389, ... Remote Desktop is enabled and the RDP-Tcp shows up in the Terminal Services ... you have port 3389 forwarded to the SBS NIC? ... Have you rebooted the server a couple of times after hte upgrades? ...
    (microsoft.public.windows.server.sbs)