Setting up VNC Server and viewer
jerry "at" westrick.com
Mon Apr 3 15:19:01 2006
On Monday 03 April 2006 15.13, Jaroslaw Rafa wrote:
> John Burns napisal(a):
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > It dose not need to the default is the only portal you will need. ie
> > nnn.nnn.nnn.nnn:0. It states this in the Docs it is just obvious from
> > the documentation. I have set up 30 or so VNC servers and not once have
> > I had to open up a port.
> I still don't get your point.
> Suppose you have 30 VNC servers on a NAT'ed LAN and want to connect to them
> from outside.
> Certainly you will have to forward 30 ports *on the router* to those 30
> machines to be able to connect.
> Ie. if external address of the router is x.x.x.x
> then x.x.x.x:5900 is forwarded to, say 192.168.0.10:5900
> x.x.x.x:5901 is forwarded to 192.168.0.11:5900
> x.x.x.x:5902 is forwarded to 192.168.0.12:5900
> and so on...
> How do you want to connect without port forwarding?
> Jaroslaw Rafa
> raj "at" ap.krakow.pl
Ahh that is the trick...
Port forwarding yes!
Open ports on the router only SSH.
then you can connect to a nated pc inside your network
(in this example I use 192.168.1.101) with the following commands
1) ssh <user>@<ssh-server-address> -L 5901:192.168.1.101:5900
2) vncviewer 127.0.0.1::5901
Of course a little more info is required, like how to use ssh from windows.
P.S. If you are using tightvnc-viewer on unix you do both of the above
as vncviewer 192.168.1.101:1 -via <user>@<ssh-server-address>
wouldn't this be a cool feature for realvnc under windows though?