"golfwithdrawalsuffer" <
[email protected]>
wrote in message
My outlook was working just fine with Norton Firewall on, but then it
stopped
being able to connect. Are there specific settings in Norton firewall
that
Outlook needs?
Norton Internet Security (NIS) already has known rules for Outlook. If
you enable the automatic program control option in the firewall, NIS
will automatically add its known rule for Outlook and not interfere. If
you disabled that automatic rule option (which, in my opinion, is the
correct setup), you should get a prompt saying Outlook is attempting to
make a connection. You get to decide if it gets a connection or not,
and whether or not to remember your decision (so you don't get prompted
again).
Sometimes NIS seems to lose track of its application rule matching. It
may have an application rule added for Outlook but not permit a
connection and it doesn't alert like the first time that Outlook wants a
connection. It ends up blocking quiescently. When this happens, go
into the program control section of NIS' firewall and delete the
application rule for Outlook. Then run Outlook again and you should get
prompted by NIS that Outlook is trying to make a connection (or it will
re-add the rule if you have the automatic option enabled). NIS sees an
application for which it already has an application rule defined, the
hash code matches (so it knows it isn't some rogue pretending to be
outlook.exe or an updated version of it), and then decides to permit
connections based on the application rule that got added for Outlook -
but it never does permit the connection. So delete the rule, let NIS
re-add it, and see if it works then. I've had to do this with NIS every
once in awhile.
