I use dial up, and my computer is not very fast, so I keep firewall off when I’m not online. I used to have outpost pro (forgot the version, but it was two yrs ago), now I use comodo. The problem is - when my pc boots up (win xp with sp2) all network traffic is blocked, even mysql server that I had installed on localhost. It took about two weeks of pulling my hair to realize that solution is just to start firewall and then I can leave it on, or close it, and everything works. It’s the same with comodo. Is that some process that loads even if main process is off that blocks trafiic (cause both comodo and outpost have one process that must load when system loads or they won’t work), or firewall makes some changes to the system?
Hi miloske85, welcome to the forums.
If by “main process” you’re talking about cfp.exe, then that is just CFPs GUI (Graphical User Interface), it has no real operational impact on CFP directly. It just means that CFP cannot report things to the user. The main CFP process is a service cmdagent.exe. But, I wouldn’t recommend trying to stop that either (CFP might think it’s being attacked… you don’t want that). The bits of CFP that actually perform filtering, blocks, etc… (ie. the bits with teeth) are, in fact, drivers… and CFP probably wouldn’t take too kindly to you trying to stop those either. The best way to “disable” CFP is by using CFP itself.
However, if CFP is blocking something on startup… I would suspect the best method would be to create rules that allow, whatever it is, to happen.
Thanks for the info, I thought that cpf.exe is something more than just a gui, after all it occupies three times more RAM than cmdagent.exe.
Thanks.
No problem. Memory? Ah, yes… that’s probably because cfp.exe needs to load all the Firewall/Defense+ rules, recent logs, etc… into memory (to show to the user).