~upd~ | Chrome Remote Desktop And Norton Security

Therefore, using Chrome Remote Desktop forces you to disable Norton’s VPN on the host machine. You are relying solely on Norton’s AV and Firewall, rather than the full "360" protection suite during the session.

The app establishes a direct, encrypted P2P data path between the client and host machine.

Norton Security is designed to lock down the local machine. If Norton detects unusual traffic patterns (like a remote control session from a different country), its "Intrusion Prevention System" may flag the session.

Optimizing Chrome Remote Desktop with Norton Security can conflict when Norton's strict Smart Firewall flags the remote access tool as a potential threat. This behavior is a built-in security defense designed to block unauthorized inbound or outbound network traffic. Users often encounter connectivity drops or endless loading screens because Norton blocks the required WebRTC, UDP, and TCP communication ports that Google uses to establish a remote session. To run both applications safely, you must configure Norton to recognize Google's remote protocol while maintaining active virus protection. Why Norton Security Blocks Chrome Remote Desktop chrome remote desktop and norton security

Norton is too good at its job. By default, Norton’s Smart Firewall and Intrusion Prevention System (IPS) treat Chrome Remote Desktop like a suspicious remote access tool (which, technically, it is).

I spent two weeks stress-testing this combination: using a Norton-secured machine as the host and accessing it via Chrome Remote Desktop from various networks. Here is the full review of the experience, focusing on usability, performance, and most importantly, security.

For a connection to succeed, certain data pathways must remain clear. If your system cannot bypass the firewall, confirm that the security software allows traffic through these specific ports and protocols required by Google: Google Remote Desktop? - Fortinet Community Therefore, using Chrome Remote Desktop forces you to

This setup is ideal for users who need occasional access to a secure home computer and prioritize free remote access over convenience. It is also good for users who are savvy enough to configure firewall rules.

I use Chrome Remote Desktop to access my home PC from my work laptop. I’ve been a long-time Norton 360 subscriber. Here is the honest truth about running both together.

Norton 360 (the current flagship for Norton Security) is a comprehensive suite offering AV, a firewall, a VPN, and a password manager. Norton Security is designed to lock down the local machine

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.

During testing, the initial connection failed immediately. Norton’s firewall automatically blocked the inbound traffic required for the CRD host to handshake with Google’s servers.