You are whitelisting the destination , not the port. If you allow port 5938 to "Any" IP address, malware on your network could use that port to exfiltrate data to a bad server in Russia.
Whitelisting means telling your firewall: "Do not inspect, block, or question traffic coming from TeamViewer’s official servers. Let it pass immediately." teamviewer firewall whitelist
Here is exactly how to configure your "TeamViewer Firewall Whitelist" to ensure flawless remote connections. Many guides tell you to just open port 5938. That works for home users, but in an enterprise environment, you need whitelisting . You are whitelisting the destination , not the port
In 90% of cases, the culprit is a strict firewall. Let it pass immediately
You’ve checked the internet. The remote computer is powered on. TeamViewer is running. So, what gives?
| Protocol | Port(s) | Destination | Purpose | | :--- | :--- | :--- | :--- | | TCP | 443 | *.teamviewer.com | Web login & authentication | | TCP | 5938 | *.teamviewer.com | Primary data channel | | TCP | 80 & 443 | master.teamviewer.com | Fallback & master routing |
Few things are more frustrating in IT support than the dreaded "Connection failed. Partner did not connect to the router." error message.
You are whitelisting the destination , not the port. If you allow port 5938 to "Any" IP address, malware on your network could use that port to exfiltrate data to a bad server in Russia.
Whitelisting means telling your firewall: "Do not inspect, block, or question traffic coming from TeamViewer’s official servers. Let it pass immediately."
Here is exactly how to configure your "TeamViewer Firewall Whitelist" to ensure flawless remote connections. Many guides tell you to just open port 5938. That works for home users, but in an enterprise environment, you need whitelisting .
In 90% of cases, the culprit is a strict firewall.
You’ve checked the internet. The remote computer is powered on. TeamViewer is running. So, what gives?
| Protocol | Port(s) | Destination | Purpose | | :--- | :--- | :--- | :--- | | TCP | 443 | *.teamviewer.com | Web login & authentication | | TCP | 5938 | *.teamviewer.com | Primary data channel | | TCP | 80 & 443 | master.teamviewer.com | Fallback & master routing |
Few things are more frustrating in IT support than the dreaded "Connection failed. Partner did not connect to the router." error message.