Teamviewer looks blocked but not - Request method caution. What are you doing about this to fix?
We have an issue today where we are unable to still remote to our users. We have followed TV implementation to the dot. You think it is a perfect world that it will just work but guess it is not.
Here is the issue.
Support A, B and C gets similar issue unable to connect to the user. Killed ZSCALER and confirm it is capturing the traffic. Digging deeper let us see what ZSCALER tells us.
It appears there is some DNS name resolution issue happening or maybe that is not setup on TV and it is coming back with IP addresses and the only way to get around it at the moment is to add whitelist on them specifically. Below is a snippet of zscaler report. All of the allowed ones not shown below are the dns names ie. router.tv.com not IP addresses like the one below. Can you get this fixed??? I dont want to be bloody whitelisting all IPs I get and this is not a true block but warning of caution and the TV is unable to handle it properly unlike when on a browser you get a message and interactively do something about but not on the TV client. So now, since you cannot reach your end user it gives a false impression TV is blocked or not working. TV wont give IP addresses either just use the *.teamviewer.com sure but bloody fix the dns name resolution and dont give us ip addresses then!
Some of the IPs I have captured so far and whitelisted are from Austria and SG as below so I know they work but no one wants to do this for goodness sake. If TV isn't able to give an IP range because of forever changing then fix the IP naming resolution then!
#TeamviewerIPRange #teamviewercaution #teamviewernameresolutionfailed
