Therefore, blocking the connections on network level from any client (incl. by using a transparent proxy, but is totally unnecessary, because the 443 is used before this. Default HTTP port, TCP 80 is the third alternative.Tampering with the data would involve using fake root CA and decrypting the data, and without that it's really hard to detect whether it's TeamViewer traffic or just normal TLS encrypted HTTPS.

This is actually the most problematic part, because blocking the default HTTPS port 443 will block all secure web sites.

If connection fails, TeamViewer tries TCP 443 next.

This is also currently the only port used by Android, Windows Mobile and BlackBerry clients.

TCP/UDP port 5938 is the primary port TeamViewer prefers to use.

(Using port 443 is a common way to get around http proxies).įrom your home computer, you can use 'autossh' to setup a persistent tunnel to 'third-pc' - see and įrom your work computer, you can then ssh up to 'third-pc', then back down the autossh tunnel to your home computer.Just for completeness, TeamViewer uses three different ports in specific order. įor example, here is an entry I have in my ~/.ssh/config: Host A cheap Linux vps hosting is probably the best way to go.įrom your work computer, you can use 'connect' in your ssh configuration to tunnel through the proxy to 'third-pc' - see.

So you need a third computer - preferably running Linux or BSD - call it 'third-pc'. From the sounds of it, there's no particular 'application' that's going to solve your problem, it's more of a networking issue - your home computer is behind NAT and your work computer is behind a proxy (http or socks).

Teamviewer qs vs host