Why Pick Other Firewalls Over Comodo Personal Firewall?

I´m glad they fixed the launchpad issue, you now don´t have to load this stupid app anymore in order to access the main GUI. However, the GUI does not remember it´s screensize, this needs to be fixed. But I will keep my eye on this one, so far no other firewall has been able to replace ZA Pro on my system, so let´s see if Comodo can.

 

Coolio10, I posted this question in Comodo Forum and am awaiting an answer, but I hope you can answer it here. I have an Outbound Policy Violation in my Logs. (Access Denied, ICMP=Port Unreachable). Protocol is ICMP Outgoing. Source is my IP address on wireless PC. Destination is 68.87.75.194 and sometimes 68.87.764.146. And message is PORT UNREACHABLE. I get an Inbound violation ocassionally too having to do with this. I beleive it has to do with my Router, and is most likely normal. My question is. Should I allow this and if so how do I do that? I know you said to ask you questions in the Comodo Forum, and everyone there is truly helpful, but I want to make sure this is okay as it may take a little more time to get an answer there. I do appreciate it.

 

Try this " create a rule ALLOW for ICMP Out " in * Network Monitor * see *SS* below and place the new rule ABOVE the " Block & Log = IP In/Out "

http://img471.imageshack.us/img471/9017/rule1bp8.png
http://img79.imageshack.us/img79/4788/rule2rk2.png
http://img372.imageshack.us/img372/838/rule3sn2.png

FYI i've the same info's from my log, creating rule as above solved it ...

HTH

 

Okay thanks storm119 I think I can handle this, but do I just click +add and then change what is already written in the Network Control Rule window that pops up to what you told me?

 

I have installed comodo.

It's so good. It is so strongly in anti leak.

I like it except the lanchpad.

 

lookcity, you can set Launchpad not to load on start up. Right click on LaunchPad click on options and uncheck the two squares. There is much better instructions on how to do this in the Comodo Forums, than what i am telling you. This is all I can remember since doing it on Friday from the instructions I found there. Just saw instructions on how to do this right here in this Forum under New Comodo firewall release.

 

Yup!

For more specific go to --> Main Window --> Security --> Network Monitor --> (in right pane = Network Control Rules) right click --> Add Rule --> Add --> Window pop-up --> Configure the new rule as mentioned above and place the new created rule above the " Block & Log = IP In/Out " ... your're done

Good luck, mate

 

Well here's the one thing I don't like about Comodo Personal Firewall.

When a prompt occurs, you only have a choice of creating rule, but you can't edit the rule created. Oh sure you can then go into application monitor and change it, but that's just double work.

I figured out how to control the type of rule auto created (via the alert frequency slider) but it's not sufficient.

Sometimes I want a broad rule covering both ip address and ports, other times I just want ports, yet other times i want the rule to be ip specifc only. Comodo firewall just doesn't give me the flexibility to change the rule as I need, not without doing a lot of double work.

 

Just did it this morning storm119. I'll let you know how it's working, but I'm sure it will be fine. Thanks very much for your help. Did this have something to do with my PC talking to Router?

 

Same problem here, seems that you are somewhat limited in creating rules.
Some people leave their rules in the Application Monitor's Destination IP and Destination Ports as "ANY" but I dont like that idea.

 

Well you can go the other way, and set the alert frequency to the highest level, then the rules created will be specific ip,port and protocol, but watch out if you just installed a new browser.....

 

So you mean youd rather it let you choose if it asks at every alert that its changeable? If that then im sure that will be in the neext release or not i could put it in the wishlist. CJ now its not lose but i get 12 different alerts id say if you were actually using comodo medium would be right for you.

 

Not sure what you are saying, but surely you have used firewalls other than comodo?

When you are prompted, typically you can accept the rules created, or you can edit it to your liking before accepting. That's all I'm asking for.

Just look at how sygate, kerio,jetico etc etc do it.

 

You suggest that here: CPF Wishlist Rev 3

 

Hey everyone. I just posted this in the Comodo Forum. I noticed that when I log completely off one account and click to log on mine. After it comes up the Security Center Icon is system tray for a split second and then goes away, but the Comodo Icon is there the whole time. It doesn't happen with a restart or when switching from one account to the other. (I only have two) It is just when I completely lgo off the one. I believe it says my Firewall isn't there, and not my Anivirus because I didn't notice this happening with only using AOL AVS and Windows XP Firewall a fewdays ago. I could be wrong, but the Windows Security Icon goes away so fastI can't read what the pop up says. Take care I'll check back later to se if anyone else experienced this.

 

I disabled the security center so I wouldn't see it on my system(s) anyway.

I just installed Comodo on a couple of my systems and with a minor tweak or two, Comodo seems to be running fine. I added a trusted zone for my LAN and set up a couple of network control rules based on information gleaned from a FAQ on the Comodo forums.

I've had trouble with ZAF in some recent installs killing my network and printer sharing and thought it was time to try something else (other than the Windows firewall).

Initially, Comodo killed my network sharing, but the tweaks mentioned above readily fixed that issue.

 

I understand exactly what you are saying Devil's Advocate. It is the same beef I have with rules creation on the fly with Comodo. It is just too cumbersome as compared with Outpost Pro. With OP I can easily set the port and/or ip range parameters when I am first creating the rule after being prompted on it. With Comodo, it is necessary to go in after the fact to set this up.

That said, I am still extremely impressed with Comodo. After all, once the rules for all necessary apps are eventually fine-tuned to my liking, there is little more I need to do. My goodness, Comodo has developed a first-rate security app here and they are offering it free of charge! All it really needs is some improvement in rules creation, logging and a better way to save the rules configuration, and it will be as close to perfect as one can expect. I feel that Agnitum has done an excellent job with Outpost regarding these three parameters, but Comodo's overall security blanket on the system is the best I have seen since I trialed Tiny pfw a while ago.

My two thumbs up to Comodo

 

That happend to me tonight when I booted up to my main snapshot, but the warning from security center wouldnt go away even though Comodo was up and running. I tested at grc.com and started a couple of applications that did not have any rules to make sure Comodo was working alright. That have not happend before..strange, but who needs security center anyway so I disabled it.

 

I just got another Application Access Denied. This one is (System 0.0.0.0 nbsess(139). Application is, System. Parent is, System. Protocol is, TCP In. And Destination is, 0.0.0.0 nbsess 139. Everything running okay, just not sure what this is. It didn't happen until I changed the other Application Access Denied I posted about earlier, but this may not be the reason. Thanks ahead of time to anyone who lets me know what this one is.

 

The ONLY problem I have with Comodo is the rules creation and saving the rules.
I'm still having trouble saving the rules after I log off and log back on, I'm still getting repeated popups for a program I juts finished creating rules for.

Another thing that wouldn't be so bad is if someone from the Comodo forums could come up with a secure configuration step by step the way Paranoid2000 has done with OutPost Pro on the Agnitum forum.
I see that Stem has already started a thread somewhat the same way.

It seems there are ALOT of questions for a firewall that everyone says is so easy to setup and configure but you could be there for days trying to read everything about Comodo.

 

Initially I thought the same thing, but upon closer inspection if you look very carefully, you may see two or more rules that look exactly the same but then realize that the parent path leads to different parent processes. This is most likely the case if you are using "Very High" for the Alert level. For example, I have no less than four rules for firefox.exe where the direction is in, protocol is tcp, and the destination ip is 127.0.0.1. However, where they all differ is in the parent path where the parent application is different in all cases.

 

Go to: Activity->logs and check for any denied connections, looking for the reason why the block occured. It may be a Network Control rule or Application Monitor rule not yet created. Port 139 is NetBIOS so you may need a global-type rule created for it.

 

My rules are gone.

Some rules stay in place for certain apps but others will disappear for no reason like I never created the rule in the first place.

The other scenario, my rule creation will disappear however the program that I created the rule for will still be there, just no rule in place, it will just show "ANY"
for the destination and port rules and TCP/UDP Out for the protocol

 

Thanks, but do I need NetBIOS for anything?

 

Not if your machine is on its own, and you aren't sharing files on it.