Not what you are looking for? Ask the experts!
Norton 360 v3 affects VPN routing.
I have performed a clean install of Norton 360 v 3 on Windows XP SP3 32bit (fully patched as of time of writing).
I could previously establish a VPN connection to my helpdesk so that they could come back down the tunnel and take over my computer via remote desktop, but since installing N360v3 it does not work.
It will work if I enable the "use default gateway on remote network" setting under the properties section of the VPN connection (Properties, Networking, Internet Protocol (TCP/IP), Properties, Advanced), but I do not want to enable that option as it breaks my secure SSH and SSL connections.
If I create a route for the help desk network it still does not work. (route add 192.168.x.y mask 255.255.255.0 [PPP_IP]). I can verify that this absolutely would do the job under normal circumstances.
I use many machines in the same way. The 4 machines that are running N360v3 are all similarly affected. The countless machines that are not running N360v3 are not affected. Pretty conclusive stuff.
Am I overlooking something simple? Why is N360v3 messing with routing anyway? Firewalls don't need to be doing that.