VNC, or Virtual Network Computing, allows technicians to control a desktop remotely through the Internet or through a private network. It shows the technician a current picture of the desktop, and allows the technician to control the mouse and keyboard as if he or she was sitting in front of that desktop.
VNC is appropriate for accessing computers remotely, or for sharing customized desktops between several people. For instance, it might be appropriate in an office that uses Linux on the majority of desktops, but wishes to provide Windows desktops for testing purposes, without setting up separate workstations.
In Windows, VNC necessarily would interfere with a local user's enjoyment of the desktop, at least while the remote technician is working.
In Linux, however, there are several options. One option is to provide a separate desktop from which the technician can work without affecting the enjoyment of any local users. The second option is for the technician to take over the local desktop. The first option is most useful for sharing computer resources such as software or computing power, while the second option is most useful in a 'helpdesk' scenario.
It has been our experience that operating a VNC server on Windows 98 is very slow compared to Linux or Windows 2000/XP. Operating a VNC client does not seem to have posed the same problems.
Both Windows XP and KDE in Linux have provided options for remote desktop sharing that either replace or build upon the VNC concept. In addition, there are several options under Windows for more responsive desktop sharing, such as Citrix Terminal Services. The correct choice is a matter of economics and intended use.
