• Documentation
  • »
  • User Guide


About This Guide

Chapter 1: Introduction

Principles of VNC remote control

Getting the computers ready to use

Connectivity and feature matrix

What to read next

Chapter 2: Getting Connected

Step 1: Ensure VNC Server is running on the host computer

Step 2: Start VNC Viewer on the client computer

Step 3: Identify VNC Server running on the host computer

Step 4: Request an encrypted connection

Step 5: Connect to VNC Server

Troubleshooting connection

Chapter 3: Using VNC Viewer

Starting VNC Viewer

Starting Listening VNC Viewer

Configuring VNC Viewer before you connect

Connecting to a host computer

The VNC Viewer user experience

Using the toolbar

Using the shortcut menu

Using the VNC Viewer - Options dialog

Managing the current connection

Changing appearance and behavior

Restricting access to features

Chapter 4: Connecting From A Web Browser

Connecting to a host computer

The VNC Viewer for Java user experience

Working with VNC Viewer for Java

Chapter 5: Exchanging Information

Printing host computer files to a local printer

Transfering files between client and host computers

Copying and pasting text between client and host computers

Communicating securely using chat

Chapter 6: Setting Up VNC Server

Licensing VNC Server

Starting VNC Server

Running multiple instances of VNC Server

Working with VNC Server

Configuring ports

Notifying when users connect

Preventing connections to VNC Server

Restricting functionality for connected users

Stopping VNC Server

Chapter 7: Making Connections Secure

Authenticating connections to VNC Server

Relaxing the authentication rules

Bypassing the authentication rules

Changing the encryption rules

Preventing particular connections to VNC Server

Restricting features for particular connected users

Uniquely identifying VNC Server

Protecting privacy

Appendix A: Saving Connections

Saving connections to VNC Address Book

Using VNC Address Book to connect

Managing connections using VNC Address Book

Saving connections to desktop icons

Previous Next Chapter 7, Making Connections Secure

Uniquely identifying VNC Server

VNC Server (Enterprise) and VNC Server (Personal) have a uniquely identifying signature:

•  Under Windows and Mac OS X, this signature uniquely identifies VNC Server among all instances running on the same host computer.

•  Under UNIX/Linux, this signature is shared by instances of VNC Server started by the same host computer user.

Note: VNC Server (Free) does not have a unique signature. Upgrade the host computer to VNC Server (Enterprise) or VNC Server (Personal) if security is important to you.

The VNC Server signature is displayed in the Get Started area of the VNC Server dialog. More on this dialog.

When a user connects from a particular client computer for the first time, this signature is published. The user is asked to verify that the signature they see matches that of VNC Server. See Checking the signature for more information.

A VNC Server signature should not change. The next (and all subsequent) times a user connects from the same client computer, the signature is not published. If the signature changes, it may be because a third party is interrupting the connection between client and host computers and eavesdropping on communications – a so-called ‘man-in-the-middle’ attack. If a user sees a message similar to the following:

WARNING: VNC Server’s signature has changed since you last connected to it.

Unless there is a good reason for the signature to have changed, you should not continue connecting.

The new VNC Server signature is fa-a5-76-c9-3d-df-ca-1d.

Do you wish to accept the new signature and continue connecting?

then it is recommended that they do not connect.

Note: The signature does change if VNC Server is re-installed on the host computer.