Jerome R. Westrick
jerry "at" westrick.com
Sat Jun 5 11:33:01 2004
5900 to machinex:5900
5901 to machiney:5900
5902 to machinez:5900
vncviewer ext-ip-addres:0 to connect to machinex
vncviewer ext-ip-address:1 to connect to machiney
vncviewer ext-ip-address:2 to connect to machinez
On Sat, 2004-06-05 at 04:26, daniel akacki wrote:
> First question, I have VNC set up on my network as my primary remote
> system, the only way I know of so far to set it up is set up port
> forwarding on my router to forward to one specific IP address, so when I
> connect over the internet I put in the public IP of my network and
> connect to only that one computer, and if say I want to go to my desktop
> instead of my server I have to change the setting in my router or do a
> VNC inside a VNC which is, as I'm sure you know, UNGODLY SLOW. Is there
> a way to set it up so I have a choice of which unit I want to VNC into?
> What different ports can I use for VNC and how can I specify in the view
> which PC I want to go to?
> Second how can I make a VNC connection to a private network over the
> internet more secure? I've been trying to read up on how to tunnel VNC
> through SSH...and I think I get the jist of it...kind of like putting an
> egg inside a steel tube for protection right. the egg (data) gets
> transferred back and forth thru the tube (SSH of whatever protocol I
> use) and noone can break (hack) it...am i'm understanding this
> after that i'm kind of lost, how do I implement something like this??
> anything i've been finding on SSH has been ported mainly towards Unix
> and to to use it with Windows you have to jump through a thousand
> hoops...is SSH my only option, what else can do with this?
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: