Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Jacob Lane, MCP
October 19, 2004, 4:58 am
rate this thread
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
:: PROBLEM ::
Get Microsoft terminal services to port forward over an SSH session from a
Windows XP client machine.
:: SOLUTION ::
The terminal services client included in WinXP is programmed *not* to allow
connections to 127.0.0.1, 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 127.0.0.2 which is still considered a loopback
interface according to RFC 3330 found at
Your entry in the hosts file entries might be:
This worked fine for me, however, until I upgraded to XP Service Pack 2. I
discovered that Microsoft took the liberty of only defining 127.0.0.1 as the
loopback address rather than the entire 127.0.0.0/8 subnet per the RFC spec.
:-/ Fortunately, they also released a post-SP2 patch that converts your IP
stack to once again recognize the whole 127.0.0.0/8 subnet as loopback
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.
Rumour has it that this behaviour (ie not allowing TS connections to
127.0.0.1) 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.
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum