I have a sorta a bad **bleep** patch/hack that seems to be stable.. From reading the other posts it looks like something was/is wrong with DNS lookups. So my "fix" that is **bleep** is not to do dns lookups. sudo vi /etc/hosts (or windows host file C:\Windows\System32\drivers\etc\hosts ) and add # Teamviewer 178.77.120.6 master1.teamviewer.com 178.77.120.104 master2.teamviewer.com 178.77.120.100 master3.teamviewer.com 178.77.120.102 master4.teamviewer.com 178.77.120.6 master5.teamviewer.com 178.77.120.100 master6.teamviewer.com 178.77.120.102 master7.teamviewer.com 178.77.120.104 master8.teamviewer.com 178.77.120.106 master9.teamviewer.com 178.77.120.104 master10.teamviewer.com 178.77.120.100 master11.teamviewer.com 178.77.120.6 master12.teamviewer.com 178.77.120.102 master13.teamviewer.com 178.77.120.106 master14.teamviewer.com 178.77.120.106 master15.teamviewer.com 178.77.120.106 master16.teamviewer.com to it. You may verify all the IPs manually by doing ping master1.teamviewer.com and verify the IPs. I stopped at 16 it looked out of country (of usa) IPs. So there may be more than 16. After adding them I was unable to reproduce the problem. **bleep** because if they change dns entries this will all break. So now you have to maintain a sudo dns table. **bleep** because it could be a security issue as you are not using DNS to verify that is actually teamviewer you are talking to. But end of the day it seems to fix the issue. + it looks like there is many re-used duplicate IPs. Robert
... View more
