It can be a complex process particularly for non-technical users.
In this case, to start a VNC session you'd need to port-forward 5900 on the public IP to port 5900 on the right internal IP. One public IP address may be shared by a number of networked machines behind a NAT. Normally if you are on the same LAN, that's fine, but if you're both in different locations then things become more complex. In order to connect you need to know the IP address of the VNC Server and have a route to it. So what do I mean? Well, without it, a VNC Viewer needs to make a direct TCP connection to a VNC Server listening on TCP port 5900. I said that VNC Cloud is connection brokering service. Virtualisation architecture just adds another layer of abstraction and we need to drive the network card hard to achieve low latency across thousands of concurrent connections per server. VNC Cloud is a connection brokering service that is hosted by RealVNC in its data centers currently in the UK, US East Coast and US West Coast. No, we don't use Amazon or Google or any managed service - VNC Cloud performs optimally on our own bare metal.
