If your security policy requires you to specify explicit domain or IP ranges, then configure your firewall exceptions for outbound TCP ports 8200, 443, and 80 as well as UDP ports 82 for the GoTo domains or IP ranges, including those of our third-party provider networks. To address this problem, verify that the domains or IP ranges will not be scanned or filtered by specifying exception domains or IP ranges. If your firewall includes a content or application data scanning filter, this may cause a block or latency, which would be indicated in the log files for the filter. Maintenance and failover events within our infrastructure may cause you to connect to servers within any of the ranges. These changes are necessary to continue to provide the maximum performance for our products. Use of IP ranges instead of domain names for the firewall configuration is discouraged unless absolutely necessary because our IP ranges and those of our provider networks need to be periodically audited and modified, creating additional maintenance for your network. I have had a bunch of support cases logged for it but. When we started using and paying for it 5+ years ago it was blazing fast but today it's more or less useless. Also, the client-to-host connection uses peer-to-peer connections, encrypted within an HTTPS tunnel where data is encrypted with AES-256 symmetric cipher. It's so slow and laggy when connected to a client (LogMeIn client from macOS to macOS) that the only use for it is to remote in and start teamviewer. It is recommended to use wild card rules whenever possible while allow listing or blocking any GoTo services on your network as sub-domains of the domains listed above are included. If you are using GoTo Resolve, see Fixed IP Addresses below for the relevant TURN server information you need. Fastpath: This is not for use with GoTo Resolve.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |