Why does TeamViewer seem uniquely fussy about DNS?
For some reason, a single user of our enterprise license always had their TeamViewer telling them "Not Ready". To get it to connect, I switched the computer's DNS from just our internal DNS resolver, to our internal DNS as well as a public DNS server. Then it connected just fine.
Why is TeamViewer the only web application (that we use) that gets fussy about DNS?
With SO MANY posts about the "Not Ready" issue, could we please get the reason for it to show up in the TeamViewer LOG FILES? CTRL+F searching for "not ready" in them returns 0 hits.