Port forwarding terminal services (RDP) over SSH.

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

After some intense research trying to figure out how to do this, I figured I
would post the results of my efforts for the benefits of all. Comments

Get Microsoft terminal services to port forward over an SSH session from a
Windows XP client machine.

The terminal services client included in WinXP is programmed *not* to allow
connections to, the assumed IP address you are sending your
packets to when you are port forwarding. However, you can configure custom
host and lmhost files in %systemroot%\Windows\system32\drivers\etc to
specify another IP such as which is still considered a loopback
interface according to RFC 3330 found at
http://www.faqs.org/rfcs/rfc3330.html .

Your entry in the hosts file entries might be:    rdp.someserver.com    rdp2.someserver.com

This worked fine for me, however, until I upgraded to XP Service Pack 2. I
discovered that Microsoft took the liberty of only defining as the
loopback address rather than the entire subnet per the RFC spec.
:-/ Fortunately, they also released a post-SP2 patch that converts your IP
stack to once again recognize the whole subnet as loopback
addresses again.


Once the patch was applied, I could once again connect to my .2 and .3

Hope this helps.

Jacob Lane, MCP

Re: Port forwarding terminal services (RDP) over SSH.

Quoted text here. Click to load it

Rumour has it that this behaviour (ie not allowing TS connections to was changed in SP2.

Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Re: Port forwarding terminal services (RDP) over SSH.

dtucker@dodgy.net.au (Darren Tucker) wrote in message
Quoted text here. Click to load it

That is the case, they removed the restriction from the SP2
version of mstsc.dll.

Chad Amberg

Site Timeline