We have a strange situation at our workplace and we need some help.
We’ve been using the older version of chrome remote desktop, which has been working great (and still does).
Recently chrome remote desktop has been upgraded to a web only interface, and it reccomends users to stop using the old chrome extension and rely exclusively on the new web interface at remotedesktop.google.com.
While the older version still works, we cannot seem to be able to connect to any machine behind our firewall (Unifi USG) while it has Symantec Cloud installed. It’s very strange, as we’ve experimented with several combinations, and the USG and Antivirus seem to be the problematic variables. If the antivirus is NOT installed on a machine within our network, we can connect fine. Also, if the machine is outside of our network, but has the Antivirus installed, it will also connect just fine. It is only when we combine Symantec Cloud WITH our USG firewall that the connection is blocked. Individually, neither presents a problem. It’s difficult to know which is the weak link in the chain.
We’ve tried creating a test group within Symantec and loosening the policies, going so far as to disable all functionality entirely, and disabling the firewall (for testing purposes), but no matter what, if the machine has the Symantec Cloud Endpoing Protection installed, it seems to prohibit remotedesktop.google.com from connecting from behind our firewall.
Our firewall is relatively simple, allowing established traffic and blocking unsolicited inbound connections, and it puzzles me what turning off the Symantec firewall didn’t solve the problem. We even went so far as to temporarily disable windows firewall entirely.
According to the remotedesktop.google.com help page, it functions over:
- Outbound UDP traffic
- Inbound UDP responses
- Traffic on TCP ports 443 (HTTPS) and 5222 (XMPP)
Is it possible that Symantec is blocking use of those protocols, even when the firewall is disabled?
Any help would be appreciated.