Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 1 subscriber
  • Views 4797 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why is the client firewall appearing when no policy is set?

emps

Hi all.

We have a problem with some machines deciding to enable/install the client firewall and stopping all traffic. 

We do not have a firewall policy set and it isn't installed when it is pushed out with the AD Sync or when installed manually.

The client AV version is 9.7.5 and it is being managed by a 4.7 Console. These are XP SP3 machines.

The default firewall policy has not been enabled/configured/set up.

How can I work out why this is happening? It doesn't always do it straight away and other computers in the same group with the same policy aren't affected. 

Help!

Thanks in advance

Paul

:17363


This thread was automatically locked due to age.
Parents
  • 0

    Hello Paul,

    in the alc.log (for which you should use the viewer) check the time it mentions the download (i.e. did it suddenly download this additional package). This should correlate with the timestamp of the firewall install log from the \TEMP directory. The corresponding indicator in the ALUpdate logs is the first occurence of Considering product {4DB41E90-DC56-41DC-B91E-9B8E537489A8} . All this still probably won't tell you why - but it's a start. Look for "other" logs with similar timestamp - these might tell you if it was a complete Sophos install.

    Christian

    :17385
Reply
  • 0

    Hello Paul,

    in the alc.log (for which you should use the viewer) check the time it mentions the download (i.e. did it suddenly download this additional package). This should correlate with the timestamp of the firewall install log from the \TEMP directory. The corresponding indicator in the ALUpdate logs is the first occurence of Considering product {4DB41E90-DC56-41DC-B91E-9B8E537489A8} . All this still probably won't tell you why - but it's a start. Look for "other" logs with similar timestamp - these might tell you if it was a complete Sophos install.

    Christian

    :17385
Children
No Data