Virtual Network Computing (VNC) is the remote administrative tool of choice for many IT professionals. IT consultant Erik Eckel explains how to configure TightVNC, the more robust version of VNC, for secure access to remote systems.
This article is also available as a TechRepublic download.
Numerous
remote administration and connectivity tools exist to help support technicians
and IT administrators troubleshoot, maintain, and access systems in different
locations. Some are easy to use and require no firewall configuration. Others
possess expensive and potentially prohibitive licensing requirements, while
delivering more advanced functionality.
Often,
VNC—which stands for Virtual Network Computing—is the remote administrative
tool of choice for IT professionals. In its earlier iterations, VNC offered a
simple, relatively straightforward method of affordably implementing fairly
secure access to remote systems.
Over
time, the open source community revised and improved the remote access tool.
Developer Constantin Kaplinsky,
in particular, maintained a project dedicated to delivering an improved VNC remote administration tool that addressed VNC’s shortcomings. The result is a more capable
application known as TightVNC.
Advertised
as an OS-independent client/server package enabling remote network access to
graphical desktops, TightVNC is a free tool
organizations can use to solve remote connectivity needs. The software is
distributed under the GNU General Public License. The self-installing
Windows package can be downloaded
from SourceForge.net.
Linux, UNIX, and Java (viewer only) versions are also available.
Among
the enhancements in TightVNC not found in standard
VNC implementations are the ability to transfer files from the local system to
the remote workstation (referred to as the server, in VNC parlance) or vice
versa and adjustable compression levels to better mate connection speeds with
the work being performed via the remote connection.
Other
improvements include improved cursor handling (cursor movements are all
processed locally to prevent performance issues), optimization for slower
Internet connections, JPEG compression enabling better display performance, Web
browser improvements that support up to 24-bit color modes, tightened security
through the use of two passwords (one for full control and another for read-only access), and automatic SSH connectivity within UNIX.
To
install TightVNC on the workstation or server you
wish to access remotely, begin by downloading the self-installing TightVNC package. Once you have the installation file ready
(the current version at the time of this writing is tightvnc-1.2.9-setup.exe), follow these steps:
|
Figure A |
![]() |
| The TightVNC Setup program enables registering TightVNC Server As A System Service during installation. |
Once TightVNC is installed, follow these steps to configure the host system:
|
Figure B |
![]() |
| Use the WinVNC: Current User Properties dialog box to configure connection options. |
|
Figure C |
![]() |
| Advanced TightVNC connection options are configured using the Current User Advanced Properties menu. |
On other firewalls, port 5900 may be required to enable VNC traffic to pass
properly. (Other VNC implementations sometimes use ports 5500 and 5800.)
For best security, administrators should test configurations to determine
the minimum ports that need be opened to enable the connection to work
within their specific environments.
Connect
to a TightVNC-enabled remote host by installing TightVNC on a local system and following these steps:
|
Figure D |
![]() |
| Enter the IP address of the system to which you wish to connect within the Connection Details screen. |
|
Figure E |
![]() |
| Configure connection options using the settings provided in this dialog box. |
|
Figure F |
![]() |
| Once the proper session password is supplied, the remote workstation’s desktop appears on the local system. |
Erik Eckel is a managing partner at Louisville Geek and president of Eckel Media Corp. He previously served as Executive Editor at TechRepublic. He received Microsoft Engineer accreditation from Sullivan University and earned his Bachelor's Degree in English from the University of Louisville. He's earned Network+, Windows NT 4.0 MCP+I and MCSE, and Windows 2000 Professional MCP accreditations.