Comodo v3 Blocking its own update?

http://i4.tinypic.com/73m5mc2.png

Is this normal or need some tweaking? It looks to me as if it is blocking its own update.

Need some advise.

No Problem. CPF is only blocking something unnecessary.

Huh? Are you pulling our leg Gibran? ;D

Lomayok did you let CFP configure itself for safe programs automatically during the installation?

By the way, the first update is out, :BNC I’ve just got it with no problems.

(B)

Anyway there is nothing to be concerned about. Really :stuck_out_tongue:

I installed it by default. I got the 1st update. Everything seems to be working properly. I hope it stays that way.

Thanks guys.

After the update and restart, comodo is now logging too much. I cleared all the logs and these new logs happen in just about one minute. If this is normal, is there a way to stop comodo from logging these kind of things? How?

Under destination port 26979 is the one used by bitcomet but it can be seen from the screen shot that it is not running.

Help please.

http://i5.tinypic.com/878v09s.png

It smells like bittorrent to me :-X

Please try to renew your internet IP.

I don’t have a fix IP, it change by itself every now and then. I tried renewing it using run–>cmd–>ipconfig/release -->ipconfig/renew but I am still getting the same IP.

Comodo is still logging too much.
Should I stop it from logging? How? Or something hostile is trying to get in?

http://i16.tinypic.com/6pqce2c.png

I’m getting the same nonsense attempts, and so are many people. It’s no good logging it once you know it’s happening, what with the processor and hard disc usage, besides it will bury other relevant events. Go to Firewall > Advanced > Network Security Policy > Global Rules tab, double click on the rule reading “Block IP In From IP Any to IP Any Where Protocol Is Any” to edit it, untick the “log as a firewall event if this rule is fired” box, apply, apply. Other app or global rules will still be able to generate logs if set.

Go to Firewall > Advanced > Network Security Policy > Global Rules tab, double click on the rule reading "Block IP In From IP Any to IP Any Where Protocol Is Any" to edit it, untick the "log as a firewall event if this rule is fired" box, apply, apply

I did the above then cleared the log but it is logging fast.

http://i16.tinypic.com/73bmjw6.png

Go back to the rule and see if it’s set not to log as you told it, may have forgotten it. You can also reboot to be sure. Odd, it works over here. Unless, do you have any other blocking global rules above? You can post a screenshot of your global rules if you please.

I meant to disconnect and reconnect to your ISP.
BTW are you using a dialup modem?

Modem connects automatically, no need to dial anything.

I just did this. Will observe the logging if it will continue.

I meant to disconnect and reconnect to your ISP.
BTW are you using a dialup modem?

Here is the global rule:

http://i4.tinypic.com/80vsdgi.png

UPDATE: It is not logging anymore.

Thanks a lot every one.

UPDATE2: The logging is back with more vengeance after another reboot.

http://i13.tinypic.com/6utm16t.png

Need some help here…

Here is what I did: I wrote down two Ip address from the log and opened bitcomet and to my surprise I found those address when I continued the download of some stuff.

I was downloading from bitcomet when I shutdown my PC earlier and It looks to me that when I restarted, those IP address from bitcomet are trying to get in but bitcomet is not open yet and it is being logged by comodo. I cleared the log but it keeps on coming. Then I opened bitcomet and continue the download and then I cleared the log again. Until now not a single log came out.

Is there something wrong with my windows xp or some misconfiguration with comodo or windows?

Please help.

If you use bittorrent many peers will attempt a connection to your IP even if you closed it. If you didn’t use bittorrent and you just connected this should mean that the previous owner of that IP was using BT.

I guess one issue is why you’re getting the attempts, and a separate one why CFP is logging them which is pointless.

CFP logs this because it is unsolicited inbound traffic as no app is actually listening

But if he did have a specific global rule to block it and it was just “block” instead of “block and log”, it wouldn’t be logged any longer, right? I think Lomayok is interested in stopping the pointless massive logging even if he can’t hide himself from the attempts (?).

That will block his BT traffic as well :o