Unable to perform a traceroute with NIS 2011 Smart Firewall Enabled

For some reason I'm unable to perform a traceroute on my computer with the Norton Internet Security 2011 Smart Firewall is enabled.

 

I have my local area network set to Full Trust and when I do I traceroute the first hop (my NAT router) and the last hop (for instance, google.com) is able to be pinged but everything between the first initial hop and the final destination hop just times out.

 

I've reset the firewall multiple times using

Settings > Network Settings > Advance Settings > Reset Firewall

 

The only way I seem to be able to make this work is to make a new firewall rule based upon these specifications...

* Allow connections that match this rule.

* Connections to and from other computers.

* Allow Access: Any Computer

* Protocol: ICMP -- Commands: 0-18

* Firewall Rule Name: Allow Traceroutes

 

I then have to move this rule all the way to the top of the rule list for any traceroutes to be able to work properly.

Hi trparky,

 

This is a known issue.  Please see the following thread for information:

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/Tracert-problem-with-NIS2011/m-p/290120/highlight/true#M126494

I ran afoul of this one myself today.

 

May I ask why the referenced thread has been tagged "Problem Solved", thereby preventing any additional postings to it? 

 

I certainly hope they don’t mean to imply that the problem be solved by requiring the user to turn off the Stateful Protocol Filter…  If so, then I certainly agree with the one poster’s suggestion of inserting a superseding, broader scope, rule as being a better solution, but it is still not a proper solution.  A forthcoming fix for this was promised by a Symantec employee respondent in their reply dated September 14th.  Nearly three months is a long time…

 

I received a similar response to my inquiry regarding the Outlook2010 runtime error caused by the NIS2011 Anti-Spam plugin DLL.  That fix was promised back on September 22nd.  I’ll repeat again, nearly three months is a long time…

 

So when will they be fixed?

 

Regards,

John Burns

Software Research

 

Hi avjohnnie,

 

The opening poster makes the determination to mark a thread as solved. and is the only one who can do so, so we are at the mercy of their judgment.  Threads are not closed when they are solved, but they are locked after a period of no activity.  The dates that fixes will be released are almost never announced in advance.  About the best you can hope for is the assurance that a fix is in the works and will be released in a future product update.    

Just follow my directions in making a new firewall rule and the issue will be solved.