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

Firewall Disabled?

Hi!

SESC 9.5 firewall is telling me that it's deactivated but it appears to work? Since a few days I have this strange thing that the tray bar icon is indicating a yellow exclamation mark. The tooltip tells me that the firewall configuration is letting through all data traffic. In the SESC 9.5 GUI the firewall entry says "deactivated", active location: "primary".

I tried to reconfigure the firewall but in the fw config menu the checkbox for "allow all data traffic" is disabled for the primary location. I haven't configured any secondary location.

This all started a few days ago after the update for the engine was distributed. I haven't installed it and just hibernated my win xp for several days. But then suddenly, there was a message telling me the system wanted to connect to my local network on 192.168.178.255 on UDP port 137 what I initially disallowed. It followed another alert for a connection to another LAN computer on UDP port 55400 which I disallowed, too. But then the internet connection didn't work any more so that I restarted the system. Nevertheless, this activated the SESC update but didn't solve the connection block so that I removed both firewall rules.

After another restart I got the UDP 137 alert again and allowed it as well as the UDP 55400 to the LAN computer. Now, the internet connection works again. The firewall says it has been disabled but it still prompts me from time to time with HTTP-connection requests from the SVCHOST-Service which I generally block by adding new rules each time. So the firewall appears to work from my point of view and I don't get the impression that all data traffic is going through.

What is this all about? As anyone experienced the same issue or has anybody an idea how to solve it?

Thanks in advance,

Holger

:5838


This thread was automatically locked due to age.
Parents
  • Hello Holger,

    92.122.188.x is Akamai Technologies, a "Web Acceleration" provider. Many vendors provide downloads/updates using this service. So it's very likely a normal http-request and not WebDAV (as you described it it's probably the Acrobat Reader).

    If your primary update location for Sophos is UNC (and not http) and the server is not reachable over internet (but perhaps over VPN) WebDAV might kick in. Normally you'd see that update failed but it might as well be that it switches to the VPN connection "in time" so you might not notice. And - connections over VPN can be slow.

    trustworthy traffic company

    It's probably written in the Beförderungsbedingungen (terms of transportation for our those not fluent in German) ... he was just doing it by the book. You don't want him to get mugged because he carries enough change with him to see you a ticket when all you have is a €50 note, do you?

    Christian

    :6067
Reply
  • Hello Holger,

    92.122.188.x is Akamai Technologies, a "Web Acceleration" provider. Many vendors provide downloads/updates using this service. So it's very likely a normal http-request and not WebDAV (as you described it it's probably the Acrobat Reader).

    If your primary update location for Sophos is UNC (and not http) and the server is not reachable over internet (but perhaps over VPN) WebDAV might kick in. Normally you'd see that update failed but it might as well be that it switches to the VPN connection "in time" so you might not notice. And - connections over VPN can be slow.

    trustworthy traffic company

    It's probably written in the Beförderungsbedingungen (terms of transportation for our those not fluent in German) ... he was just doing it by the book. You don't want him to get mugged because he carries enough change with him to see you a ticket when all you have is a €50 note, do you?

    Christian

    :6067
Children
No Data