by antipasto on Mon Sep 20, 2004 5:42 pm
I would set up an SSH server on your home machine. Use sshd. Then use an SSH client like PUTTY for windows to connect to your local machine. You can also map your work computer's local ports to local ports on your home machine, and the communications will route through the encrypted SSH tunnel.
You can also run Terminal Services through this... Map the appropriate ports (whatever local port on your work machine mapped to the remote control port on your home machine), and run the MS Terminal Services client (Connect to a Remote Computer) in Windows 95 compatibility mode (you'll need to make a copy of it to somewhere else on your machine first, but this is so it can connect to "localhost" servers. The client prevents this by default...)
Then, you can do whatever the hell you want. Make your SSHd server run at port 80 if your company's firewall prevents other connects or is a proxy. Also, you'll want to punch a hole in your local firewall, naturally, for this service, but not for any other service you want to connect to (keep your remote control port protected at all times!), becase the SSH connection then places you behind that firewall, and all port mapping is done over that connection.
Anyway... ssh tunneling is the way to go. Sort of an ad-hoc VPN. You can map any port, or set of ports... you can even provide your home computer access to work stuff if you leave it logged into your home, but I wouldn't recommend that.
