Quote:
Originally Posted by linuxinvasion
How can I use XDMCP with the putty ssh tunnel?
Thanks again.
|
Look in the tunnel part of the session manager for putty. There you can define tunnels. Keep in mind the following:
Local means you're forwarding a port on the local computer so that it connects to a port on another machine. The following is useful to ssh to a machine, and create a secure tunnel to a port ON THAT MACHINE. Let's say you want to make a typical FTP tunnel, where all the data goes on port 20.
Local port: 21
Remote: localhost:21
Local port: 20
Remote: localhost:20
Then, to use it, you would establish an FTP session to your own machine:
ftp> open localhost
You can also use it to access other machines, with the apparent connection coming from the box you are ssh'ed into host. For example, I use it to get to the config page of a printer or router behind a firewall.
Local port: 8080 (can be anything)
Remote port: 192.168.1.100:80 (whatever ip:port is appropriate)
then browse to
http://localhost:8080/
So, whatever port(s) you need for XDMCP, forward those through the tunnel like that,
and have Exceed connect to localhost on those ports.
Hope that makes enough sense.
Note: Your tunnels may linger active for a while even after you've ended your ssh shell session. Exiting putty will close the tunnels.
Also note: in a Linux shell, the preceding examples become:
ssh -L 21:localhost:21 -L 20:localhost:20 user@host
-- and --
ssh -L 8080:192.168.1.100:80 user@host
It looks like Plink takes the same arguments, if you don't really need a shell session at the same time.
see also:
http://the.earth.li/~sgtatham/putty/...doc/index.html
This is really useful for all kinds of things, including VNC. Personally I do NOT AT ALL feel safe having a listening VNC port exposed to the bare 'net.
Dang, this is a longer reply than I expected to write.
-- Nate
