Symantec Network Security intermediate filter driver

What is it?  I've been having problems connecting to various sites since installing NIS 2013.  Just trying to resolve the problem I turned this off a little while ago and things seem to be working correctly now!  Is this another one of the features in the new package that we don't want or has it been there and just started acting up?


Msradell wrote:

What is it?  I've been having problems connecting to various sites since installing NIS 2013.  Just trying to resolve the problem I turned this off a little while ago and things seem to be working correctly now!  Is this another one of the features in the new package that we don't want or has it been there and just started acting up?


It is the Symantec/Norton IP stack "listener" add-in for the Norton "Network Security Map" functions.  It watches for other "computers and devices" that "show up" on your local network so they can be mapped and monitored by the function.


avjohnnie wrote:

Msradell wrote:

What is it?  I've been having problems connecting to various sites since installing NIS 2013.  Just trying to resolve the problem I turned this off a little while ago and things seem to be working correctly now!  Is this another one of the features in the new package that we don't want or has it been there and just started acting up?


It is the Symantec/Norton IP stack "listener" add-in for the Norton "Network Security Map" functions.  It watches for other "computers and devices" that "show up" on your local network so they can be mapped and monitored by the function.


Any idea why it should start causing problems after the upgrade to NIS 2013?  Disabling it got rid of the problems.

All I can say is that I've not had that particular problem, and that my Network Map is correct and functions as expected.  There was another regular poster who recently noted an issue with devices not being "seen" on their network in the Map display - whether that was/is due to a "listener" related issue or something else, I can't really say.  I'm not even certain at this point if theirs was a 2012 or 2013 issue.

 

I think someone who works for Symantec will need to respond to your question...

 

Kind Regards,

John