Learn Remote Desktop - TightVNC: Features & Advantages

#Introduction

So far you've practiced with TigerVNC on both Linux and Windows. Episode 9 introduces one more implementation that's very popular in the Windows ecosystem: TightVNC. It was born from the same VNC family, but with a different focus — bandwidth optimization via Tight encoding and ease of use through a graphical interface.

TightVNC is interesting to learn for three reasons: it carries the legacy of Tight encoding, which is efficient on low bandwidth; it provides a Windows server and viewer that are fully configured through the GUI; and it offers a built-in file transfer feature that TigerVNC doesn't have. By the end of the episode, you'll have installed TightVNC Server on Windows, set a password, and connected to it from a TigerVNC or Remmina viewer.

#Getting to Know TightVNC

#Origins and Main Focus

TightVNC is a project started in the early 2000s with the goal of making VNC more bandwidth-efficient. The original implementation ran cross-platform, but the modern 2.8.x releases focus almost entirely on Windows — the server (tvnserver.exe) and viewer (vncviewer.exe) are designed for Windows-dominated environments.

Because of that focus, TightVNC is often the choice in organizations where all workstations are Windows and aren't ready to move to an enterprise solution. It's lightweight, requires no vendor account, and is compatible with other VNC viewers because it speaks the standard RFB protocol.

#The Tight Encoding Advantage

The name "Tight" isn't just branding — it refers to Tight encoding, the compression mechanism that's its hallmark. When the screen is sent, areas with text and flat interfaces are compressed with zlib, while areas with photos and gradients use JPEG. The result is far less bandwidth than generic encoding:

text  ->  zlib  ->  saves bandwidth
photo  ->  jpeg  ->  stays sharp

Because it's efficient, Tight encoding has also been adopted by many other implementations — including the TigerVNC you met in episode 5.

#GUI-Based Configuration

Unlike x11vnc or TigerVNC, which are mostly configured via command-line arguments, TightVNC Server on Windows is configured through a graphical configuration panel. In this panel you set the password, choose the port, decide whether connections can control the screen or only view it, and set behavior when a user logs out.

Administration  ->  New password
Extra Ports     ->  additional ports 5901, 5902
View-only       ->  connections without mouse/keyboard control
Service         ->  start / stop via Windows service

#Installing TightVNC Server on Windows

#Installation Steps

Download the installer from the official tightvnc.com site, pick version 2.8.x for Windows, and run the installer. When the wizard asks about components, make sure both the server and viewer are checked:

TightVNC Server  ->  install (tvnserver.exe)
TightVNC Viewer  ->  install (vncviewer.exe)

After installation completes, you'll be asked to set a password for the server. Use a reasonably strong password — remember the limitations of the classic VNC password we'll dissect in episode 12 — then finish the wizard.

#Running the Server as a Service

TightVNC Server registers itself as a Windows service named tvnserver. Make sure its status is running and set to start automatically at boot:

Get-Service tvnserver
Start-Service tvnserver
Set-Service tvnserver -StartupType Automatic

The Start-Service tvnserver command starts the server service, and Set-Service -StartupType Automatic makes it start automatically. Verify the open port:

netstat -ano | findstr :5900

If netstat -ano | findstr :5900 shows a line with a LISTENING status on port 5900, TightVNC Server is ready to accept connections.

#Connecting from Other Viewers

#TigerVNC Viewer to TightVNC Server

The strength of the RFB protocol is compatibility between implementations. TightVNC Server can be accessed from a completely different vendor's viewer. From Linux, use the already-installed TigerVNC viewer:

vncviewer 192.168.1.30:5900

Replace 192.168.1.30 with the Windows machine's IP address. The vncviewer 192.168.1.30:5900 command will ask for the password set in the TightVNC panel, then display the Windows desktop.

#Connecting via Remmina

For daily use, Remmina is more comfortable because profiles can be saved. Create a new profile by filling in:

• Protocol: VNC - Virtual Network Computing.
• Server: the Windows IP address followed by the port, e.g. 192.168.1.30:5900.
• User / password: leave the user empty; the password is entered when the connection opens.

VNC  +  192.168.1.30:5900  ->  Save  ->  Connect

#File Transfer from the Windows Viewer

TightVNC Viewer Windows' unique feature is built-in file transfer. With an active connection, click the folder icon in the viewer toolbar and choose the transfer direction:

toolbar  ->  Transfer files  ->  Local <-> Remote  ->  pick file

This feature is only available on the Windows side and uses the TightVNC protocol extension. For Linux servers, you still use scp or rsync, which we'll cover in episode 11.

#When to Use TightVNC

#TightVNC's Position in the VNC Ecosystem

In short, TightVNC's position among its siblings:

Use TightVNC if you're in an all-Windows environment and want clickable configuration. Use TigerVNC if you need both Linux and Windows servers, and x11vnc for sharing a running Linux desktop.

#Conclusion

Episode 9 rounded out your knowledge of VNC implementations: TightVNC with its Windows focus, the Tight encoding advantage for saving bandwidth, GUI-based configuration, installing TightVNC Server, and connecting from TigerVNC and Remmina viewers.

Key takeaways:

• TightVNC 2.8.x focuses on Windows: the tvnserver.exe server and vncviewer.exe viewer.
• Tight encoding uses zlib for text and JPEG for photos — saving bandwidth.
• Configuration is done through a GUI panel, not the command line.
• The service named tvnserver is controlled with PowerShell.
• Any RFB-speaking viewer can connect, including TigerVNC and Remmina.
• The built-in file transfer is only available on the Windows side.

In the next episode, episode 10, we cover autostart and service management with systemd — creating .service units for x11vnc and TigerVNC with User, ExecStart, Restart, and Environment, running VNC without a physical login, and enabling services at boot. Make sure your ~/.vnc/xstartup file is ready!