Virtual Network Computing or VNC is a setup where the GUI of a remote computer or server can be controlled from a local computer. The server can be Cloud VPS. The reason to give a hint Cloud VPS is – actually the RAM can be increased to 30 GB or like such, such configuration is normally not possible on a physical computer.
Basics on Virtual Network Computing or VNC
So with Virtual Network Computing or VNC one can work on a remote computer as if sitting right in front. Virtual Network Computing or VNC implements the Remote Frame Buffer protocol and in contrast to other remote control software, it is platform independent.
We previously wrote how to actually set up a Virtual Network Computing or VNC, that will give you a good impression about Virtual Network Computing.
A number of developers who are also still working on the AT & T Research Lab, who were behind Virtual Network Computing or VNC includes the inventor Tristan Richardson, team lead Andy Harter and Quentin Stafford-Fraser , James Weatherall, Ken Wood, Andy Hopper, Charles McLachlan, Paul Webster and Hendrik Ekkelenkamp. In 2002, the Virtual Network Computing project closed and open source version under the GNU General Public License was published. At 2002 no one probably guessed the possibility of Virtual Network Computing or VNC will increase with Cloud Computing.
Virtual Network Computing or VNC uses the client-server model. The server program runs on the server, while the client programs receive the screen output and in turn can use keyboard and mouse input to the server.
Usages and Notes on Virtual Network Computing or VNC
As the remote computer needs not to be maintained physically and RAM can be increased to virtually an oddly high level, which has been possible with Cloud Computing, for individual research workers the computing power can be delivered readily, without the need of more complex and costly Datacenter setup with Virtualization Layers. This was however not the original intention of Virtual Network Computing or VNC.
Image : Our demonstration of Virtual Network Computing or VNC using TightVNC.
The red boxed area is the remote server's window running Ubuntu 12.04 LTS,
Firefox is loading the tutorial webpage using the Server provider's (Rackspace)
Internet Connection. Higher resolution is available without red boxed area on request for
any Open Source Project under GPL 2.0
TightVNC is a Virtual Network Computing server and client software under the GPL license, available for Windows and various Unix derivatives such as Linux, also a platform independent implementation exists written in Java (client only). TightVNC is an extensive development of the Virtual Network Computing, most notably at the compression options to enable VNC even with narrowband connections easily (“Tight” encoding). The program can only transmit encrypted passwords, the data transfer itself is not encrypted.
UltraVNC is another Virtual Network Computing server and client for Windows under the GPL. It offers additional features such as file transfer for broadband connections (such as DSL or a local network ), as well as the “Tight” encoding of TightVNC. With UltraVNC is possible to authenticate not only the regular password encryption, but also about the Microsoft Logon authentication methods. To encrypt the data stream between the server and client of external UltraVNC DSM plug-in modules can be used. The DSM plugin modules allow AES encryption of 128 bits.
There are many other server and client Virtual Network Computing software available including Client software for mobile devices.
With Internet Load Balancing, connection speed is not a barrier today. Due to popularity of Virtual Network Computing, there are multiple screen enabling systems are available, which makes Virtual Network Computing more suitable for usage and gradually is replacing online DHTML and PHP based on browser operating systems for powerful works.