VNC® Enterprise Edition User Guide
Chapter 1: Introducing VNC Enterprise Edition
What is VNC Enterprise Edition?
Getting VNC Enterprise Edition ready to use
VNC Enterprise Edition 4.5 connectivity
Chapter 2: Getting Started: Connecting A Client To A Host Computer
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 on the host computer
Step 4: Select an encryption option
Step 5: Connect and authenticate to VNC Server
Configuring VNC Viewer before you connect
Connected: The VNC Viewer experience
Using the VNC Viewer shortcut menu
Using the VNC Viewer Properties dialog
Managing the current connection
Changing the appearance and behavior of VNC Viewer
Restricting access to functionality
Chapter 4: Connecting From A Web Browser
Connected: The VNC Viewer for Java experience
Working with VNC Viewer for Java
Chapter 5: Exchanging Information
Printing host computer files to a local printer
Transferring files between client and host computers
Copying and pasting text between client and host computers
Communicating securely using VNC Chat
Chapter 6: Setting Up VNC Server
Running multiple instances of VNC Server
Configuring network communications
Preventing connections to VNC Server
Restricting functionality for connected users
Authenticating connections to VNC Server
Relaxing the authentication rules
Bypassing the authentication rules
Preventing particular connections to VNC Server
Restricting functionality for particular connected users
Uniquely identifying VNC Server
Appendix A: Saving Connections
Saving connections to VNC Address Book
Using VNC Address Book to connect
Uniquely identifying VNC Server
VNC Server has a signature uniquely identifying it.
• Under Windows and Mac OS X, the signature uniquely identifies VNC Server among all instances running on the same host computer.
• Under UNIX or Linux, the signature is shared by instances of VNC Server started by the same host computer user.
A VNC Server signature is displayed in the VNC Server Status dialog:

(Windows XP)
When a user connects from a particular client computer for the first time, this signature is published. The user is asked to verify it in order to continue connecting:

A connecting user may be able to check that the published signature matches that of VNC Server, for example if a host computer user is present, or if the connecting user set up VNC Server in the first place.
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:

then it is recommended that they do not continue connecting.
Note: The signature does change if VNC Server is re-installed on the host computer.
