You do not have to open any ports in order to work with TeamViewer!Īs later described in the paragraph 'Encryption and Authentication,' not even we, as the operators of the routing servers, can read the encrypted data traffic The rest of the connections are routed through our highly redundant router network via TCP or https-tunnelling.

After the handshake through our master servers, a direct connection via UDP or TCP is established in 70% of all cases (even behind standard gateways, NATs and firewalls). When establishing a session, TeamViewer determines the optimal type of connection. This is what the company says in their Security Statement: You make a connection to a Teamviewer ID, and TeamViewer passes the connection down through the TeamViewer client's established tunnel to the destination and you then you are prompted for password and then the connection establishes afterwards. When you run TeamViewer, you are assigned an ID on their broker server. This website accepts the initiated request from the remote computer and keeps the connection alive to listen for a remote session request. On your computer, outside of the network of the LogMeIn computer, can access this computer remotely through LogMeIn's website.

Since this client initiated the request, no port forwarding on the Firewall is required. This is due to the fact that the software that you installed on the remote machine (the LogMeIn client) initiates an outgoing request to the LogMeIn servers.

You will notice that there are no external configurations required for this type of remote session. TeamViewer, LogMeIn and any other program that allows a zero config remote desktop session uses a third-party server.įor example, LogMeIn is a program similar to TeamViewer where you are able to remotely login to a computer outside of the network that you're currently on.

Teamviewer app