Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

mako132 (2925)

mako132
  esejamesNO@SPAMyahoo.com

Journal of mako132 (2925)

Saturday August 09, 2003
05:47 PM

Chomping at the bit

[ #14023 ]
I have all these ideas for testing, but I can't access the machines from home - they're all behind the firewall, and we can't get VPN working for us Mac OS X folks. I'll probably end up ssh-tunnelling for my Unix systems, but I need to figure out a way of getting Windows Terminal Services work through an ssh tunnel.

List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Chomping at the bit 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If windows terminal service uses TCP connections from client to server in the usual manner, then you can probably get away with using ssh port forwarding. Assuming (I don't know it should be) that terminal services lives on port 9876, the command would be:

    ssh -L 9876:windowshost:9876 unixhost

    Then, you just point your terminal services client at localhost:9876 and it should "just work" whilst the ssh connection is up.

    Note that if you want to connect to the machine doing the port forwarding from somewhe

  • It works (Score:2, Informative)

    by jhorwitz (4227)
    You're in luck -- terminal services uses TCP port 3389. I use SSH to tunnel it all the time. However, the remote desktop client shipped with XP doesn't want to connect to localhost (at least on my machines), so use the Win2K version if you're on XP and you have access to it.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.