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

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 1 Comment 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 somewhere other than "localhost", you'll have to add a -g flag.

    If the terminal services server makes a connection back to the client, you'll have to fiddle around with the -R option, but that's pretty unlikely.

    If TS uses UDP, then you're outta luck. Sorry. (unless anybody else knows how to forward udp over ssh?)

    I use this technique to gain access to work's HTTP proxy, so I can view all the internal sites from home. Works like a champ!

    -Dom

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.