Kaspersky/Active Virus Shield and Comodo

Hello,

I hope someone can help me with my problem. I’ve been using Comodo for some time already and it’s great. My AV at that time was AVG Free Ed. I decided to give Kaspersky AV 6.0 a try. It seems to be a good AV and I’d like to keep it as well as Comodo.

I’ve searched in a lot of places and read many FAQs but couldn’t find anything about my problem. I also browsed the Kaspersky forums and I did everything they suggested.

My problem is that as soon as both are installed, my upload stream stops working, whatever the way I try (FTP, uTorrent or Firefox (speed tests from dslreports.com or by clicking on the gMail Notifier icon, my mailbox doesn’t open)). I added both software in their Trusted Zone.

Is there something I need to do to make them happy together?

Thank you
A very desperate King

Welcome to the forum, Your Majesty.

Only your uploads don’t work? I don’t have Kaspersky, but when you installed CFP was the AV off? Other users have reported that it solved miscellaneous issues for them if CFP was installed first. It would also help to post a copy of your edited log to see if anything was blocked.

On 3 different systems that I have tested kaspersky and CFP I had a lot of problems. https://forums.comodo.com/index.php/topic,411.msg46140.html#msg46140

As requested, I have a log file of Comodo, but I don’t think it will help much.

Log Scope:: Today

Date/Time :2007-03-14 23:31:26
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: UDP Incoming
Source: 86.66.225.96:16901
Destination: 67.70.xxx.xxx:6881
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:31:26
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: TCP Incoming
Source: 86.66.225.96:2242
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:31:21
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 67.70.55.122, Port = ms-rpc(135))
Protocol: TCP Incoming
Source: 67.70.55.122:14935
Destination: 67.70.xxx.xxx:ms-rpc(135)
TCP Flags: SYN
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:31:16
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 67.70.55.122, Port = ms-rpc(135))
Protocol: TCP Incoming
Source: 67.70.55.122:14935
Destination: 67.70.xxx.xxx:ms-rpc(135)
TCP Flags: SYN
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:30:21
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 60.11.125.55, Port = 1027)
Protocol: UDP Incoming
Source: 60.11.125.55:54783
Destination: 67.70.xxx.xxx:1027
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:30:16
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3652
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:30:11
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3652
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:30:06
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3652
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 13

Date/Time :2007-03-14 23:29:16
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: UDP Incoming
Source: 86.66.225.96:16901
Destination: 67.70.xxx.xxx:6881
Reason: Network Control Rule ID = 12

Date/Time :2007-03-14 23:29:06
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: UDP Incoming
Source: 86.66.225.96:16901
Destination: 67.70.xxx.xxx:6881
Reason: Network Control Rule ID = 11

Date/Time :2007-03-14 23:29:01
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 172.184.135.112, Port = 6881)
Protocol: TCP Incoming
Source: 172.184.135.112:1518
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 11

Date/Time :2007-03-14 23:28:56
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3604
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 11

Date/Time :2007-03-14 23:28:56
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: TCP Incoming
Source: 86.66.225.96:2210
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 11

Date/Time :2007-03-14 23:28:51
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: UDP Incoming
Source: 86.66.225.96:16901
Destination: 67.70.xxx.xxx:6881
Reason: Network Control Rule ID = 10

Date/Time :2007-03-14 23:28:51
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 172.184.135.112, Port = 6881)
Protocol: TCP Incoming
Source: 172.184.135.112:1518
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 10

Date/Time :2007-03-14 23:28:51
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3604
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 10

Date/Time :2007-03-14 23:28:51
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: TCP Incoming
Source: 86.66.225.96:2210
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 10

Date/Time :2007-03-14 23:28:46
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3604
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 10

Date/Time :2007-03-14 23:28:46
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: TCP Incoming
Source: 86.66.225.96:2210
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 10

Date/Time :2007-03-14 23:28:31
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 58.19.183.46, Port = 1027)
Protocol: UDP Incoming
Source: 58.19.183.46:37927
Destination: 67.70.xxx.xxx:1027
Reason: Network Control Rule ID = 9

Date/Time :2007-03-14 23:28:31
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 58.19.183.46, Port = 1026)
Protocol: UDP Incoming
Source: 58.19.183.46:37927
Destination: 67.70.xxx.xxx:1026
Reason: Network Control Rule ID = 9

Date/Time :2007-03-14 23:27:51
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3569
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 7

Date/Time :2007-03-14 23:27:46
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3569
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 7

Date/Time :2007-03-14 23:27:41
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 91.163.38.147, Port = 6881)
Protocol: TCP Incoming
Source: 91.163.38.147:3569
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 7

Date/Time :2007-03-14 23:27:31
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 172.184.135.112, Port = 6881)
Protocol: TCP Incoming
Source: 172.184.135.112:1472
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 7

Date/Time :2007-03-14 23:27:26
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 172.184.135.112, Port = 6881)
Protocol: TCP Incoming
Source: 172.184.135.112:1472
Destination: 67.70.xxx.xxx:6881
TCP Flags: SYN
Reason: Network Control Rule ID = 7

Date/Time :2007-03-14 23:26:36
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: UDP Incoming
Source: 86.66.225.96:16901
Destination: 67.70.xxx.xxx:6881
Reason: Network Control Rule ID = 5

Date/Time :2007-03-14 23:26:26
Severity :Medium
Reporter :Network Monitor
Description: Inbound Policy Violation (Access Denied, IP = 86.66.225.96, Port = 6881)
Protocol: UDP Incoming
Source: 86.66.225.96:16901
Destination: 67.70.xxx.xxx:6881
Reason: Network Control Rule ID = 5

Like? I have KIS and Comodo and I haven’t seen issues yet.

I describe them at the link that I included at my previous post. :wink:

[Is this the right place to report bugs? Otherwise, please move the topic]

For some time now, I use Comodo Firewall Pro in combination with AVG Free. However, some days ago, I stumbled upon Active Virus Shield: a freeware Kaspersky anti-virus. I installed AVS, as a replacement of AVG.
However, since then, my computer randomly crashes: first, some characters disappear, then most of the images. At the end, only edges of windows are visible and the computer is crashed.
I think this is because of the combination of AVS and Comodo: I have seen more people experiencing this:

https://forums.comodo.com/index.php/topic,6168.msg45724.html#msg45724
https://forums.comodo.com/index.php/topic,2046.msg15944.html#msg15944

Hopefully, a new version of Comodo can solve this bug (or comes around the bugs of AVS)

I merged the two topics since both are related with the free and paid Kaspersky AVs. :smiley:

To this point, this topic has not offered a resolution of my Comodo Firewall - Kaspersky AV problem. I have Kaspersky AV Personal 5.0.390 installed, which came “free” with System Mechanic Pro 6 (I cannot upgrade to Kaspersky 6.x without a new purchase of the AV app - Sys Mech Pro 7 now comes with a different AV app; also, another thread mentions that Kaspersky officially states that their 6.x AV is incompatible with Comodo firewall - despite that statement, apparently at least some KAV 6.x users are successfully deploying Comodo firewall).

I have the following Kaspersky exe:
C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus Personal\kavsvc.exe
set to skip parent check, allow all activities, allow invisible connection attempts, and skip advanced security checks. I don’t think it is possible to give any app more freedom than that with Comodo firewall. I have given the same permission level to kav.exe and kavsend.exe. Nevertheless, when I manually request Kaspersky AV to update, Comodo blocks the attempt, “complaining” that Kasperky AV (while specifically blocking kavsvc.exe) will not communicate, and I have to manually permit connection one or more times within Comodo firewall. Furthermore, despite my specifying to skip the parent check, Comodo gives the parent as services.exe (I have not tried to give services.exe the same liberal permissions as the kav*.exe apps specified earlier, nor would I want to do so). In the Comodo pop-up window, there is no check box to allow further such “incidents” to be ignored, i.e. accepted without prompt. Needless to say, this is very annoying, since Kaspersky is set to check for updates every three hours, and each check has to be manually allowed one time or more through Comodo. I could change the Kaspersky update frequency to something longer, but the Comodo intercept would still occur, and I am not always around to permit the connection manually, e.g. when I have a full Kaspersky AV scan scheduled during “off hours”, i.e. when I am not present, Kaspersky will first check for an update before scanning. If Comodo blocks that, which it will, then I can’t do a completely unattended Kaspersky AV HD scan.

I would appreciate some comment from Comodo personnel, if possible. I most definitely do not want to switch back to ZoneAlarm Free, the latest version of which caused a number of problems with my PC! Nor do I want to have to try another firewall app - preferably a free one, of course - when I know that Comodo is rated so highly for overall security. I definitely like Kaspersky AV, and do not wish to switch to another AV app if I can help it. Playing AV app - firewall app roulette, until some pairing works, does not sound very desirable to me…

In my opinion, Comodo (or any firewall) should allow a user to specify that any particular app NEVER be blocked, whether it is “refusing communication” or not. Comodo does not appear to be flexible enough to work with Kaspersky AV Personal 5.x, at least.

PS: I have tried to resolve this by changing the only “block” default rule in Network Monitor to “allow” (i.e. all other rules were already “allow”). This did not prevent Comodo firewall from blocking kavsvc.exe. Even though all Network Monitor rules were at that point “allow”, I do not know if I would still have to add in one or more “allow” rules to solve the Kaspersky AV-Comodo problem…

PS: Since installing Comodo yesterday and logging off (i.e. the PC would only “awaken” with an acceptable password), I came back today to find that Ctrl-Alt-Del would not bring up the window where I could enter the password. I had to manually shut off the PC, then turn it back on. I am not saying this new problem was due to Comodo firewall or even Comodo firewall - Kaspersky AV conflict, but that possibility exists. I guess I will wait and see if the same problem occurs in the future.

G’day and welcome to the forums,

I’m pretty sure you’ll find that the pop-up from the firewall says something like “the application has refused communications with …”. This type of behaviour is definitely not typical of normal applications and this is the reason why CFP will not allow you to “remember” either “Allow” or “Block”. The firewall is not “complaining” - it is warning you that an app on your system is refusing normal communications.

It isn’t Comodo that isn’t flexible enough. It is Kaspersky V5 that is being totally inflexible.

Please understand that I’m not saying Kaspersky V5 is bad. It’s a very good AV. I just trying to explain why CFP is behaving the way it is. There are sound, logical reasons for its behaviour.

Hopefully one of the Comdo staff will jump in with a more detailed explanation.

Cheers,
Ewen :slight_smile:

Hi, i’m french and a new user of Comodo.
Sorry for my english.
I’ve find this forum because i have the same problem with Kaspersky 5.0.712 and i am searching a solution.
But i am surprise because this problem occur only on my new proper installation of Windows XP (with full security updates). On my actual running system Comodo and Kaspersky works perfectly together. The message of no communication from Kaspersky to Comodo appear only on my new installation.
So there is an hope !
They can work together !

By

drs.

Weird. I have been running Comodo and Active Virus Shield fine now. I have the newest releases to. I have windows xp home. Must be your setup.

Perhaps,
for the moment the only solution i 'v found is to close Kaspersky and re-open it.
drs

drs, which problem is yours: the crash or can’t upload? This is a bit confusing since pandlouk merged two different threads into one here. If it’s about incompatibility in general why it works for some but not others, it could also be due to an outdated version. I don’t know since I don’t have any Kaspersky products.

I couldn’t figure out Majesty00’s issue based on the logs because there are no blocked outgoing connections.

Hi,

I’m using Kaspersky for windows Workstation 5.0.712 and Comodo 2.4.18.184.
The problem is they don’t load together correctly at windows startup.
Comodo told me that Kavsvc.exe refuse to communicate.
To solve this problem i must unload KAV (or not load him at startup) and (re)load it manualy.
After that, all work fine and i’ts ok for me because i don’t reboot very often.
Thanks.

drs

I run Comodo Firewall and wished to trial Kaspersky A.V. 6.0.2 . On running the installer KAV tells me that it conflicts with Comodo Firewall - please remove it to continue.
I aborted the set-up - but IS there an answer?