There are multiple issues involved. I'm assuming that you have installed VNC on the remote computers and that the VNC server is running. You need to know the LAN IP address of the remote machine you want to connect to. You need to have access to the router at the remote site so that you can setup NAT port forwarding. The router has a WAN IP address. I assume that you know its IP address. You need to configure the remote router to forward a given port number to a machine on the LAN. As an example, say "machine1" with LAN IP address of 192.168.1.100 has its VNC server listening on the default port of 5900. You need to configure the remote router to forward port 5900 to 192.168.1.100. If that is configure correctly, then on your local machine you should be able to simply put the WAN IP address in the VNC Viewer's "VNC server:" box and you will connect to the machine.
If you want to be able to connect to more than one computer at the remote site then you will need to configure each of the VNC Servers to listen on different ports. The default display number is port 5900. Numbers you enter in the VNC Server setup dialog are offsets from 5900. So if you put in the number "10" then the VNC Server would actually be listening on port 5910. So, if you give each computer a different display number then you can configure the router to forward each different port number to the correct machine. It gets tricky if the machines keep changing LAN IP addresses. Somehow you need to keep track of their IP addresses. I like to give my machines static IP addresses on the LAN so that I know which machine is which. Remember that VNC isn't secure. When you connect to a remote computer as described above, the passwords and everything you type is plain text and susceptible to snooping. To get around this I use ssh connections to a linux box on the LAN and use ssh port forwarding. This provides a secure connection. Good luck! VNC is an awesome tool. I've been using it for about six years and couldn't live without it. John From: "Ron Crummett" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Remote VNC Date sent: Fri, 1 Oct 2004 11:57:22 -0600 [ Double-click this line for list subscription options ] I have a question that I have wanted to ask for a long time, but didn't even know where to begin on it. I now feel like I have enough of a grasp to ask, so here goes... I need to be able to VNC into some computers located about two hours from here. During a recent on-site visit I tried to gather the information needed for VNC and this is what I have: The IP addresses are assigned by DHCP and begin 192.168 I have the IP address of the router that the computers connect to My IP address is also a 192.168 address I have the IP address of my router I feel that I have the information necessary to VNC into these "remote" computers, but my question is how? There are so many 192.168 addresses behind routers and whatnot that I know a simple 'ping 192.168.xxx.xxx' will not do the job; any suggestions? I hope that this has made sense. That's it from here. More to come as the plot thickens... Ron Crummett CayNet Consulting, LLC (208) 424-1590 [EMAIL PROTECTED] http://www.caynetco.com [demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat] _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list ________________________________________________________ John R. Larsen <[EMAIL PROTECTED]> http://larsen-family.us _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
