A RealVNC Connect session always involves two pieces of software - RealVNC Viewer and RealVNC Server - brought together either by RealVNC's cloud service, by a direct network address, or by a one-off Code Connect code. This article covers each of the three in turn: what RealVNC Viewer does, what RealVNC Server does, and how RealVNC Connect brokers the connection between them.
RealVNC Viewer
RealVNC Viewer is installed on the device you want to control from - that is, the device you're sitting in front of. It's the app you use to reach a remote device, and it supports all three connection methods.
| Connection method | What you do in RealVNC Viewer |
|---|---|
| Cloud connection | Sign in with your RealVNC account. The remote device appears automatically in your team list - click or tap it to connect. No address or code needed. |
| Direct connection | Enter the remote device's IP address or hostname into the search bar, for example 192.168.5.127 or my-pc.local. If RealVNC Server is listening on a non-default port, qualify the address with it, for example 192.168.5.127::80. You don't need to sign in. |
| Code Connect | Enter the 9-digit code given to you by the person at the remote device and click Connect. They must confirm the session before it starts. |
Note: Install RealVNC Viewer and RealVNC Server on two separate devices. If you install both on the same device and try to connect to yourself, you'll end up looking at an infinite "hall of mirrors" rather than anything useful.
For full setup steps, see All About Cloud Connections, All About Direct Connections, or Sharing your screen using Code Connect.
RealVNC Server
RealVNC Server is installed on the device you want to control remotely - the "host". It's what RealVNC Viewer actually connects to, and it's where each connection method is enabled and, where applicable, authenticated.
Enabling cloud connectivity
Sign in to RealVNC Server at install time using your RealVNC account credentials. This adds the device to your team, so it appears automatically in RealVNC Viewer for anyone signed in to the same team.
Enabling direct connectivity
Direct connectivity is only available on subscription plans that include it - see current plans and pricing. Once enabled, RealVNC Server shows you the device's IP address, which you'll need to give to whoever is connecting. By default, RealVNC Server listens on port 5900 TCP/UDP, so this port must be allowed inbound through the device's firewall - and forwarded on the router too, if connecting over the Internet.
To maximise security, RealVNC recommends using a cloud connection rather than a direct connection when connecting over the Internet.
Generating a Code Connect code
Generate a 9-digit code from within RealVNC Server and share it with the person who needs to connect. The code is valid for 120 seconds - after that, it expires and a new one must be generated. When they attempt to connect, you'll be asked to confirm the session before it starts.
Authenticating incoming connections
Whichever method is used to reach it, RealVNC Server always authenticates the incoming connection before granting access. Which credentials it asks for depends on your subscription and configuration - see what credentials RealVNC Server asks for.
RealVNC Connect
RealVNC Connect is the overall product: RealVNC Server, RealVNC Viewer, and the cloud service that ties them together under your RealVNC account.
For cloud connections, the RealVNC Connect cloud service does the brokering. Where possible, it negotiates a direct peer-to-peer session between the two devices for the best performance. If intermediate network hardware prevents this, it automatically falls back to a relay session instead, so the connection still succeeds. Relayed session data is encrypted end-to-end, so it can't be read by RealVNC or anyone else.
For direct connections and Code Connect sessions, the cloud service isn't involved at all - RealVNC Viewer and RealVNC Server negotiate the session between themselves, using the address or code you supply.
Your RealVNC Connect subscription determines which of these methods are available to you: cloud connectivity is included on every subscription, while direct connectivity and Code Connect depend on your plan. See current plans and pricing to check what's included.
Inbound and outbound connections
Every connection has two ends: an inbound side (the device being controlled - the Server role) and an outbound side (the device doing the controlling - the Viewer role). Which side your device is on depends on what you enable, not on which product you happen to have installed.
In RealVNC Server and RealVNC Viewer (v7), inbound and outbound are separate installations - RealVNC Server only ever handles inbound connections, and RealVNC Viewer only ever handles outbound ones. In the unified RealVNC Connect v8 app, both roles live in the same app, under Settings / Inbound and Settings / Outbound - so one installation can be controlled by others and control other devices.
Allowing inbound connections
Enabling inbound connections lets other devices connect to and control yours.
- On the device you want others to be able to control, open RealVNC Server (v7) or RealVNC Connect (v8).
- Sign in with your RealVNC account. This joins the device to your team and enables inbound cloud connections automatically.
- The device now appears in the team list of anyone signed in to the same RealVNC account, ready for them to connect.
To let someone outside your team connect just once, generate a Code Connect code from the device instead of adding them to your team - see Sharing your screen using Code Connect.
- On the device you want others to be able to control, open RealVNC Server (v7) or RealVNC Connect (v8).
- Enable direct connectivity - in RealVNC Connect v8, this is the Allow inbound connections toggle under Settings / Inbound.
- Note the device's IP address or hostname, and give it to whoever needs to connect. Allow the listening port (5900 TCP/UDP by default) inbound through the firewall, and forward it on the router if connecting over the Internet.
Making outbound connections
Enabling outbound connections lets your device connect to and control others.
- On the device you want to control from, open RealVNC Viewer (v7) or RealVNC Connect (v8).
- Sign in with your RealVNC account.
- Select the target device from your team list and connect. If it's outside your team, enter the Code Connect code it's showing instead.
- On the device you want to control from, open RealVNC Viewer (v7) or RealVNC Connect (v8).
- Enter the target device's IP address or hostname in the search bar (add the port if it's not the default, for example
192.168.1.10::5901). - Authenticate with the credentials the target device is asking for.
Comments
Article is closed for comments.