Kaspersky Update

Hi,

please post a screenshot of your exception and which firewall rule is blocking the update?

Ian

Hi, the firewall rule blocking the update is the Rule 0. Below is the Printscreen of the exception. 

Thanks For The replay.

Hi,

from my limited regex experience your exception looks correct. If it is being blocked by rule 0 that means no rules are seeing the request as valid.

You create a rule at the top of your firewall rules source LAN -> any -> destination WAN -> FQDN (Kaspersky) -> any service (until you identify which service they use). You are assuming the kasparsky.com is the update site, I suspect it is not.

Ian

Update investigation:- 

https://support.kaspersky.com/13211

Update servers for Kaspersky Security Center 10 and Kaspersky Endpoint Security 10 have changed:

• Requests to /updates/bin/kes10/* are redirected to bincdn.kaspersky-labs.com/.../.
• Server bincdn.kaspersky-labs.com/.../ saves data from /new/updates/bin/.

The changes improve speed and stability of updates delivery. 

Hi,

from my limited regex experience your exception looks correct. If it is being blocked by rule 0 that means no rules are seeing the request as valid.

You create a rule at the top of your firewall rules source LAN -> any -> destination WAN -> FQDN (Kaspersky) -> any service (until you identify which service they use). You are assuming the kasparsky.com is the update site, I suspect it is not.

Ian

Update investigation:- 

https://support.kaspersky.com/13211

Update servers for Kaspersky Security Center 10 and Kaspersky Endpoint Security 10 have changed:

• Requests to /updates/bin/kes10/* are redirected to bincdn.kaspersky-labs.com/.../.
• Server bincdn.kaspersky-labs.com/.../ saves data from /new/updates/bin/.

The changes improve speed and stability of updates delivery. 

Oh, that was the issue! i added this to the exception and the updates works fine!.

Thank You!.

Hello,

I am suffering from this as well and cant get past it.  We already have this under our exceptions:

Ok looks like by URL bypass has been accepted but would rather like to learn why the regex didnt allow it and clean it up if you can assist that would be great.