RE: TightVNC Tunnelled through SSH
Noel Baggett <NBaggett <at> irvinecompany.com>
2008-07-07 16:51:52 GMT
Peter,
Thank you for the reply on this and perhaps I should move away from
using PuTTY. But the way that I have it working for now is that I
configured TightVNC to listen on separate ports for each of the
different locations. I have the tunnels setup for each of the ports
that I have configured. But I couldn't get it working to do a different
local port than the servers host port. Keep in mind that these are all
windows machines that I am using as well. If anyone else can get this
working the other way, it would be much cleaner, but I can't. I don't
know if it has something to do with the fact that I am using
non-standard ports or what.
Thanks,
Noel
-----Original Message-----
From: Peter Rosin [mailto:peda <at> lysator.liu.se]
Sent: Wednesday, June 25, 2008 1:10 PM
To: Noel Baggett
Cc: vnc-tight-list <at> lists.sourceforge.net
Subject: Re: TightVNC Tunnelled through SSH
Noel Baggett skrev:
> Thanks Peter. You have it correct. What I was hoping to find is a
> solution in which I could use the same port on all of the "client"
> machines out in the field and then use different ports to connect to
> them on the "server" box so that each user would be using different
> local ports and they wouldn't clash.
>
> Is this possible using putty? I have tried a few different times
using
> this approach and perhaps I am doing it incorrectly. It seems as
though
> when setting up the tunneling portion it needs to have the exact same
> port on the server side as is on the tunnel side. Is there a change
> that I need to make under the forwarded port configuration? Please
let
> me know your thoughts and I really appreciate your help on this!
I'm not a putty user, but with ssh I would use e.g. this to open the
tunnel to "client1":
ssh -L localhost:5901:localhost:5900 client1
and this to open the tunnel to "client2":
ssh -L localhost:5902:localhost:5900 client2
To use the tunnels I would then use
vncclient localhost:1
to get to "client1", and
vncclient localhost:2
to get to "client2".
If different users sets up these tunnels, they can "borrow" them from
each other. The above also assumes all "clients" have vnc servers on
the standard port (5900).
(the first "localhost:" in the -L argument is optional, but makes ssh
hide the tunnels from random network bandits)
I assume putty has a similar option.
Cheers,
Peter
Notice to recipient: This e-mail is only meant for the intended recipient of the transmission, and may be a
confidential communication or a communication privileged by law. If you received this e-mail in error,
any review, use, dissemination, distribution, or copying of this e-mail is strictly prohibited. Please
notify us immediately of the error by return e-mail and please delete this message from your system. Thank
you in advance for your cooperation.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___________________________________________________________
TightVNC mailing list, VNC-Tight-list <at> lists.sourceforge.net
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
RSS Feed