----- Original Message ----- From: "David T-G" <[EMAIL PROTECTED]> [snip] > % and/or have name resolution working you can point to any machine you want > % (or multiple machines). > > Yeah. Now as I understand it I'd have to assign different ports on the > gateway for each server in the house -- something like > > 51900:localhost:5900 win1 # "display" 00 on win1 > 52904:localhost:5902 linux2 # display :4 on linux2 > 57900:localhost:5900 win7 # "display 00 on win7 > > or so -- to avoid port confusion, right?
The VNC client sets up the port forwarding, not the gateway. All traffic too and from the gateway goes through SSH port 22. > % > % Check out the "More Advanced Use" on > % http://www.uk.research.att.com/vnc/sshvnc.html. > > Saw that; thanks. The challenge is that I'm on some foreign computer > where I can drop vncviewer in with little trouble but going to the effort > of setting up tunneling each time is a stinker. > > I already have putty and its registry settings on my web page so that I > can click and run; I suppose implementing an ssh client and tunneling > rules the same way can't be that much tougher. Not that I like it a lot, > though *stomp* *whine* :-) > PuTTY is an SSH client, and does SSH tunneling. Another thought would be something like MindTerm which uses Java to implement the SSH client. -- William Hooper I'm going crazy. Wanna come along ? _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
