| Scenario | Protocol | Port | Destination | |----------|----------|------|--------------| | Direct LAN connections | TCP | 5939 | Local IP range (e.g., 192.168.x.x) | | Incoming remote control (old method) | TCP | 5938 | Public IP of the device | | TeamViewer Meeting (VoIP) | UDP | 5349 | *.teamviewer.com | | Management Console API | TCP | 443 | api.teamviewer.com |
Ensure your firewall allows outbound traffic on TCP/UDP 5938 . teamviewer firewall
# Allow outbound to TeamViewer iptables -A OUTPUT -d teamviewer.com -p tcp -m multiport --dports 80,443,5938 -j ACCEPT iptables -A OUTPUT -d teamviewer.com -p udp --dport 5938 -j ACCEPT | Scenario | Protocol | Port | Destination
For enterprises requiring strict IP whitelisting: However, its use can be hindered by firewall
TeamViewer setup usually adds rules automatically. To verify or manually add:
TeamViewer is a popular remote access and remote control computer software that allows users to access and control computers remotely. However, its use can be hindered by firewall restrictions, which can compromise its functionality and security. This paper provides an in-depth review of TeamViewer and its relationship with firewalls, highlighting the benefits and drawbacks of using TeamViewer in a firewall-enabled environment. We also discuss the security implications of using TeamViewer and provide recommendations for secure usage.
TeamViewer doesn’t use fixed IP addresses; it connects to a massive global network of routers. Instead of whitelisting IPs, whitelist the domain *.teamviewer.com to ensure your client can always find a path to the master servers. Security Best Practices