But for connection you can also add TCP/UDP Port 5938. Note that now router and master are going up to 16, but that could grow in the future.Īlso if you want the IPs, you can just resolve these endpoints, but some have multiple IPs.įor the ports, you should only need HTTPS (TCP 443) during installation and maybe also HTTP (TCP 80). Here is the list of hostnames / URLs that seem to be currently used by TeamViewer installation. So I went digging in the TeamViewer log (located in the program folder) and tried to watch the connection made during the installation to be able to allow the traffic to the different TeamViewer endpoints. We comply fully with GDPR and are certified according to SOC2, HIPAA/HITECH, and ISO 9001:2015.
TeamViewer installation seems to do an auto-detection of the proxy configuration of the client anyway.įrom my experience, often after the installation the TeamViewer Host would not have retrieved any of the configuration or just partially (UI customization but not the policy…). TeamViewer is protected by end-to-end 256-bit AES encryption, two-factor authentication, granular access management, device authorization and other industry-grade security features. And the problem is that TeamViewer is not giving any details on the URLs or IPs, they just say to whitelist *., but not all firewall supports wildcard like this.Īlso normally it’s possible to specify a proxy in the assignment options parameter, but I’m not sure it’s working. If your client is behind a firewall and/or proxy that might block the installation to fully retrieve the policy and complete the assignment.
However this means that during the installation, your client will discuss with TeamViewer’s back-end to retrieve the config and assignment options as specified.
0 kommentar(er)
