I have seen several other threads in the past regarding VPN and Norton but none have resolved the issue I am having which is:
I am using Norton 360 v4 on a desktop which is running XP SP3 and is set up with a Microsoft server VPN connection.
This is not working as expected.
In order to allow incoming VPN conenctions, I first created :
A Norton 360 Traffic Rule to allow activity on port 1723 which allows connections to/from other computers on TCP port 1723 and moved it to the top of my Traffic Rules List
This then did not work and so from other threads here, I found the only way to get the VPN client to connect was to:
also Turn the "Stealth Blocked Ports" value off in Norton 360.
I am not happy with this as it means my security is reduced.
Why does Norton 360 not take account of the "Traffic Rule" for port 1723, which is the incoming port. Surely the fact that I have a rule for this port should take precedence over the "Stealth Blocked Ports" option.
well I tried it as suggested and modified my rule to allow communication on 1723/500 on both UDP and TCP on local and remote ports.
I also put a log entry on it for when a connection matched the rule.
Still no luck
I got my standard security log message (not my rule above):
"Unused port blocking has blocked communications. Inbound TCP connection from x.x.x.x , local service Port (1723)."
(x.x.x.x being the client ip)
Once I turned off the stealth blocked ports, it connected fine once again, but strangely it did not generate a log message for the VPN connection.
I will need to test I think if I can connect even without my Traffic rule in, as even when I do connect, it doesnt log it as it should. Something is definitely strange with 360.
I think the question is how do you really just open one port, without it being done for a 3rd party program under Program Rules, cos it just doesnt seem to work well in the Traffic Rules section.
So the XP SP3 machine is acting as the server in this VPN scenerio? It is not the client but the actual server of the VPN connection? Is File and Printer Sharing enabled on the XP SP3 system? And what of the client systems?
I have seen several other threads in the past regarding VPN and Norton but none have resolved the issue I am having which is:
I am using Norton 360 v4 on a desktop which is running XP SP3 and is set up with a Microsoft server VPN connection.
This is not working as expected.
In order to allow incoming VPN conenctions, I first created :
A Norton 360 Traffic Rule to allow activity on port 1723 which allows connections to/from other computers on TCP port 1723 and moved it to the top of my Traffic Rules List
This then did not work and so from other threads here, I found the only way to get the VPN client to connect was to:
also Turn the "Stealth Blocked Ports" value off in Norton 360.
I am not happy with this as it means my security is reduced.
Why does Norton 360 not take account of the "Traffic Rule" for port 1723, which is the incoming port. Surely the fact that I have a rule for this port should take precedence over the "Stealth Blocked Ports" option.
Are both the "Server" and the client running Norton? Is File and Printer Sharing set to Automatic in the Norton settings?
The File and Printer Sharing; is the RPC and RPC Locator services both running on each machine? What about COM and DCOM? Any errors showing on those services in the System Event viewer?