![]() It's wonderful to see those two big green ticks at last.lol. I learnt a few new things about ports, and so it has all been worth it. Then I changed the 4500 port for another, and viola! Success on both occasions. I knew I was on the right track then! Hah, hahhhh!.lol. But I guess to Comodo, me and my ip's server make a network?Īt first I used 4500 for the UDP Port, cos I read in your post that you shouldn't use the default port, which gave me a test result of fail (although the TCP port I set succeeded). I didn't think of the Network rules because I'm not actually on a network. I had actually searched this forum and had come across that post and had tried to configure my firewall, but I obviously didn't take in that it was the Network Monitor rules I had to deal with, not the Application Monitor. This might help youĪhhh M8h.you are my hero! Thanks for that. If you want to allow something in then you have to create a rule for that in there. While this seems to be more a quirk (feature?) of comodo than of cirrus, it is certainly worth being aware of and might be worth working around if possible.Application Monitor affects applications only, but for incoming connections there is the Network Monitor blocking the unwanted incoming traffic before it reaches any apps. However attempting to copy these files with the internal copy command in JP software's 4NT shell does not result in any file lock (though access is still denied.). ![]() Attempting to copy these files with Total Commander results in an identical result: Total Commander pgm file is locked by Comodo.Ĥ. I searched the forums and saw the thread where Malwarebytes detected the file I am refer. I have Malwarebytes Anti-malware, Super Antispyware, and Avast antivirus installed on my computer. After excluding all these files from the backup session, the problem disappears.ģ. I am using Comodo Firewall version 0.1355, running Windows XP service pack 3. All these files had "access denied" which resulted in comodo locking cirrus.exe, apparently permanently until rebooting.Ģ. I do a nightly mirror of my system/program drive to a backup drive, and this mirror included a number of exe and dll files (and data.edb) in the Comodo program dir, as well as two sys files in system32\drivers. Also run Command Prompt as admin and type 'set devmgmt shownonpresentdevices1' then 'start devmgmt.msc' without quotes then go to View > Show Hidden Devices then expand the Non-Plug and Play devices and delete the Comodo file and reboot. Comodo agent permanently locks cirrus.exe whenever cirrus tries to copy any of a number of a Comodo program files to which read access is denied. For a start, of course, I'll go offline, shut down comodo and try to install cirrus without rebooting!ġ. ![]() I have very little troubleshooting time available, but I will see what else I can quickly learn about this odd behavior, in particular whether I can observe when these locks develop. I wonder whether cirrus does something unusual which attracts comodo's attention in an unusual way, or perhaps fails to release some resource when it terminates? This process has cirrus.exe opened 5 times (5 different handles.) Interestingly, though I have 13 applications and 78 processes running on my system at the moment (and cirrus is not one of them!), cirrus.exe is the *only* file proper locked by cmdagent (in process explorer's "file" category, cmdagent also locks the win32 system folder, and some /Device objects which are mostly named pipes, but no other normal files.) As to Private Firewall, it has 3 main components: (1) firewall, (2) HIPS, (3) narrow scope anomaly detection (accessed from GUI by File>Settings>Advanced). Zone Alarm's PRO Firewall (NOT free) offers a behavior blocker, over & above its very competent firewall component. Today, when this problem occurred again, I used process explorer to determine that the locking process is cmdagend.exe, a service which is part of the Comodo 2.4 firewall. For a FREE FW+HIPS, the only choices I know of are Comodo & Private FW. Comodo community forum to discuss and help people using security products. ![]() I reported by email several weeks ago that I have been unable to install cirrus updates in recent months without rebooting because the file cirrus.exe is locked. Thank you for reporting, kindly refer the below link and download comodo firewall version only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |