Chrome Remote Desktop uses a "relay" architecture. Your traffic goes from your computer -> Google Servers -> your remote device. This is secure (encrypted via SSL/WebRTC), but it bypasses local network restrictions.
Because malicious actors frequently use Remote Access Trojans (RATs) to hijack devices, Norton Security defaults to a high-alert posture. The Norton Smart Firewall flags Chrome Remote Desktop for the following structural triggers: chrome remote desktop and norton security
3 replies. ... Unless they specify a UDP port or port range, I would hesitate to roll that out. HUGE security hole, in my opinion. Fortinet Community Network guide for Chrome Remote Desktop - Google Help Chrome Remote Desktop uses a "relay" architecture
In my testing, when I accessed my home PC from a coffee shop (open Wi-Fi), Norton momentarily flagged the connection attempt as a "High Severity" intrusion attempt. I had to manually whitelist the IP range of my remote location. While this proves Norton is doing its job, it renders "quick, on-the-go access" almost impossible without prior planning. Unless they specify a UDP port or port
Turn off "Silent Mode" in Norton while troubleshooting the connection, otherwise you won't see the pop-ups telling you it blocked the access.
Norton Security offers excellent protection, but it treats remote access protocols with suspicion. Chrome Remote Desktop offers excellent accessibility but requires specific open ports to function. Getting them to play nice requires patience, but once configured, the result is a very secure, free remote working environment.
Chrome Remote Desktop uses a "relay" architecture. Your traffic goes from your computer -> Google Servers -> your remote device. This is secure (encrypted via SSL/WebRTC), but it bypasses local network restrictions.
Because malicious actors frequently use Remote Access Trojans (RATs) to hijack devices, Norton Security defaults to a high-alert posture. The Norton Smart Firewall flags Chrome Remote Desktop for the following structural triggers:
3 replies. ... Unless they specify a UDP port or port range, I would hesitate to roll that out. HUGE security hole, in my opinion. Fortinet Community Network guide for Chrome Remote Desktop - Google Help
In my testing, when I accessed my home PC from a coffee shop (open Wi-Fi), Norton momentarily flagged the connection attempt as a "High Severity" intrusion attempt. I had to manually whitelist the IP range of my remote location. While this proves Norton is doing its job, it renders "quick, on-the-go access" almost impossible without prior planning.
Turn off "Silent Mode" in Norton while troubleshooting the connection, otherwise you won't see the pop-ups telling you it blocked the access.
Norton Security offers excellent protection, but it treats remote access protocols with suspicion. Chrome Remote Desktop offers excellent accessibility but requires specific open ports to function. Getting them to play nice requires patience, but once configured, the result is a very secure, free remote working environment.
