Network Access Requirements

Follow

To establish cloud connections, computers and devices running VNC Connect must be able to communicate with RealVNC’s cloud service at the locations in the tables below. If a proxy or firewall is blocking outgoing communications, cloud connections cannot be established.

You don’t need to comply with these requirements if you only establish direct connections.

Note on SSL/TLS Proxies

Strict certificate signature checking is used in VNC Connect clients (VNC Viewer and VNC Server) - SSL/TLS proxies that intercept SSL/TLS connections and mint new certificates will cause connections to fail. If SSL/TLS proxies or endpoint security software with SSL/TLS inspection are used in your organization, please ensure the IP addresses detailed below are whitelisted/bypassed.

If you are sure endpoints have network access but you still cannot establish cloud connections, check our service status page.

IP Addresses

IPv4 address TCP port UDP port Role

146.101.60.86

443 n/a Update notification service (optional)
146.101.60.69
443 n/a API gateway service

212.119.29.178

443 n/a Cloud team management services
165.254.191.246 443 n/a
165.254.191.230 443 n/a
212.119.29.179 443 n/a
165.254.191.247 443 n/a
165.254.191.231 443 n/a
212.119.29.177 443 n/a Cloud bootstrap services
165.254.191.245 443 n/a
165.254.191.229 443 n/a
212.119.29.128/28 443 3478

11000-20000*
Cloud connectivity services
165.254.239.128/28 443 3478

11000-20000*
165.254.191.192/28 443 3478

11000-20000*

* required for High Speed Streaming and Audio

Domains

If your network proxy or endpoint security software requires hostname/DNS entries instead of IPs, such as zScaler, or restrict DNS lookups on your network, you must allow the following domains:

Domain Role
downloads.realvnc.com VNC Connect Single Installer (optional)
*.services.vnc.com VNC Connect cloud connectivity services
Was this article helpful?
58 out of 91 found this helpful

Comments

0 comments

Article is closed for comments.