Native VNC Client
This system implements the VNC protocol, so any
There are several different VNC clients available, all of which should work with this system, as the system automatically detects and makes use of certain extensions to the basic RFB protocol as provided by the VNC clients.
The best client currently is TightVNC (http://www.tightvnc.com). Binaries are available for Windows, Linux, MacOS and many versions of Unix. Source code for all clients is available there too. This version of VNC is being actively developed.
The authoritative version of VNC is available from RealVNC (http://www.realvnc.com). This source base is the original version of VNC, maintained by the original developers of the standard. For a commercial, supported version of VNC, you should consider TridiaVNC (www.tridiavnc.com). Their version of VNC is a superset of TightVNC and contains a number of enhancements for use in a larger corporate environment.
NOTE: Some native VNC clients may require a flag or setting indicating they should use BGR233 encoding by default. If this flag is not set, you may see a garbled picture and the client will fail. The Unix versions of VNC require the flag
SSH Tunnel (with Native VNC client)
If you are using Openssh, the following Unix command is appropriate based on the default settings on a machine at 10.0.0.34:
ssh
Same command, but using the WAN port:
ssh
NOTE:
•A copy of these commands, with appropriate values filled in for your current system setting, is provided in the
•You have 60 seconds to type the second command before the SSH connection will be terminated.
•The port number “15900” is arbitrary in the above example and can be any number (1025...65535). It is the port number used on your client machine to connect your local SSH instance with the VNC client. If you want to tunnel two or more systems, you will need to use a unique number for each instance on the same SSH
client machine.
Instruction Manual
26