Firewall blocking updates

cwatling · October 30, 2018, 10:20pm

Hi,

I have been testing Comodo One and I have installed the client security v10 on a couple of machines, We created our own policy and I have added the “COMODO Client - Security” ruleset to the firewall policy but the product will not update.

If I go to the machine and run a manual update it fails with an error, but if I turn the Comodo firewall off and then run a manual update it works.

Any suggestions to what I have missed?

Rick_C · October 31, 2018, 12:27am

We would like to clarify from you @cwatling, which ‘product’ are you referring to that fails to update?

cwatling · October 31, 2018, 1:18am

Hi,

It’s the Comodo Client - Security (the Antivirus + firewall). We select the device in Comodo One and click Install Additional Comodo Packages and tick the “Install Comodo Client - Security”

I am trying to update the AntiVirus Database for the virus package.

Thanks

Rick_C · October 31, 2018, 2:06am

Hi @cwatling
Is it for all the database in the Comodo Client - Security (CCS)? Or just on one (or a few) update category? Is this update behavior happening on all of the endpoints or just a few?

One thing you can try is to reinstall CCS (at least on one device) and try updating again.

We also would like to share the following help guides for an unhindered client-server communication.

Endpoint Manager (formerly ITSM) Services - IP Nos, Host Names and Port Details - EU Customer

cwatling · October 31, 2018, 10:36pm

Hi,

Thanks, I ended up just changing the policy from the one we had created to a Comodo made template and then machine updated fine, so I just cloned one of the templates and made the changes we needed rather than creating a policy from scratch.

I’m not sure if we will keep using the CCS going forward though as it has a HUGE impact on system performance and made the machines that we were testing it on almost unusable.

Thanks
Chris

Rick_C · November 1, 2018, 1:03am

Hello @cwatling
You may want to check the Security Sub-Systems (especially Containment) to know what processes were ‘affected’ by CCS. It is set up to run on a ‘Default Deny’ principle. A properly set up profile and exclusion list renders an endpoint (near!) invulnerable from malware and unwanted intrusions.