-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat September 25 2004 01:18, Shawn wrote: > I kinda understand what you're saying, but don't know how to make this > happen. Also, if I tunnel VNC through SSH, does that mean I can't have both > an SSH session to MY server, and a VNC session to the remote server at the > same time? The clients in this case shouldn't have access to my servers at > all - just their own... > > Thanks for the feedback. > > Shawn > > On Friday 24 September 2004 23:35, Neil Bower wrote: > > What may be best is to set up SSH forwarded ports, then tunnel to the VNC > > through the SSH.
You set it up the same way...select an individual port to go to each machine. 111.111.111.111:22 forwarded to newserver:22 111.111.111.111:999 forwarded to oldserver:22 - From the remote computer, you would issue this command: ssh -p 999 -l login_name -L 5901:oldserver_ip:5900 111.111.111.111 - -p tells what port to connect to - overrides the default of 22. - -l (lowercase L) tells what user name to log in as - -L the first part (5901) is the local port, then the ip of the server you want to connect to and the port that you want to connect on. Once that is done and you have logged in, you connect your VNC client to localhost:5901 or localhost:01 (can't remember the exact command) and that will establish a connection to the server. You can still use your SSH session for command line usage even when tunnelling through it. The nice part about having SSH ports forwarded is that one can connect to a specific server using a secure copy program. Hope this helps...kinda have a dead mind at this hour...and I'm assuming that you were talking about desktop VNC. Neil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFBVSVTL5PebEz22pURAvYdAKCodZV8Yh7G9VoATsEhl4nHrtyMvACfWFK1 f/pr7sZdVKL9nsMTha/y9oA= =sbs2 -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
