Setting up VNC Viewer for the first time is genuinely quick — most of the work is deciding how you want to use it. This guide takes you from a blank machine to a working, password-protected remote session, and flags the choices that actually matter for security along the way.
Before you start
You'll be installing software on two computers: the host (the PC you want to reach) and the controller (the PC you'll sit at). On the host you need the VNC Viewer server; on the controller you need the viewer. It's fine to install both on every machine so you can go either direction.
- Administrator rights on the host PC
- Both computers on the same network for your first test
- The host computer's IP address (run
ipconfigto find it)
Step 1: Download VNC Viewer
Always get the package from the official project source. Fake VNC download pages are a common malware vector, so this one step matters more than any setting later. You can start from our download section, which points at the GitHub source ZIP.
Tip: If you downloaded a compiled installer, verify it came from the official release channel before running it.
Step 2: Run the installer
Launch the installer and accept the licence. When it asks which components to install, choose the server, the viewer, or both. If this machine will be reached remotely, make sure the server is selected.
- Choose the install folder (the default is fine).
- Select VNC Viewer Server and/or Viewer.
- Decide whether to register the server as a system service now or later.
- Finish the installer.
Step 3: Set a strong password
Open the VNC Viewer Server properties and set an access password. This is your primary defence, so make it long and unique — not the same password you use elsewhere. Some builds let you set a separate view-only password for people who should watch but not control.
A weak VNC password is the single most common reason these setups get compromised. Treat it like the key to the machine, because it is.
Step 4: Make your first connection
On the controller PC, open VNC Viewer and type the host's IP address (for example 192.168.1.42). Click Connect, enter the password, and the remote desktop appears. You now have full mouse and keyboard control.
If nothing happens, the usual culprit is Windows Firewall on the host blocking the VNC port. Our troubleshooting guide walks through that fix.
Step 5: Secure the session
A working connection isn't the finish line. Before you rely on it, add encryption with a DSM plugin, or tunnel the session through a VPN or SSH. Our security guide covers this properly. If you want the machine reachable at any time, see unattended service mode.
Frequently asked questions
Only if you want the machine to work in both directions. The host needs the server; the computer you control from needs the viewer. Installing both everywhere is convenient.
The most common cause is the host firewall blocking the VNC port, followed by a mistyped IP address. Confirm the server is running and allow the port through Windows Firewall.
No. Set a strong password and add encryption or a VPN/SSH tunnel before exposing VNC Viewer beyond your local network.
Remember: always download VNC Viewer from the
official project source, keep it updated, and never expose a raw VNC port to the
internet without a VPN or SSH tunnel. When you're ready,
head to the download section.
