Norton’s "Smart Firewall" often resets these rules after a definition update. I have had to re-allow RDP three times this month.
If you are searching for "norton security allow remote desktop connection," here is the reality check: norton security allow remote desktop connection
Once you find the setting, it works solidly. Norton doesn't corrupt the RDP stack; it just firewalls it. The "Silent Mode" is helpful for troubleshooting, but that’s a temporary fix. Norton’s "Smart Firewall" often resets these rules after
If you are a sysadmin or power user needing RDP, Norton is a headache. If you are a home user who only needs RDP once, follow a YouTube guide for "Norton allow port 3389." Do not expect it to work out of the box. Norton doesn't corrupt the RDP stack; it just firewalls it
Finally figured it out: Norton blocks RDP by default (3/5 stars)
It is buried deep in the settings. You cannot just click "Allow." You have to go into Settings -> Firewall -> Traffic Rules -> Configure and manually create a rule to allow System and svchost.exe for port 3389 (TCP). Alternatively, you have to switch the firewall from "Auto" to "Private" and manually move your network to "Trusted."
I spent two hours troubleshooting why I couldn’t Remote Desktop into my home PC from my laptop. I kept getting the "Remote Desktop can't connect to the remote computer" error. Turns out, Norton Security was silently blocking the connection.