Quote:
Originally Posted by atsa2
I eliminated the firewall as the problem remained after I had shut down the firewall... Is it possible that Comodo was still having an effect after being shutdown, or started in safe mode? Just interested as it all adds to my knowledge...
|
It's very likely Comodo was still having an effect even though you had shut it down.
Most firewalls leave processes running when you close the user interface down (by clicking on the "quit" or "exit" menu items from the tool tray icon). In the case of Comodo , it leaves a process named cmdagent.exe running, and this seems to keep on blocking whatever the firewall was blocking before you quit it.
I've not tried starting in Safe Mode so I have no clue how Comodo behaves in that instance.
One thing that surprised me :- there is an option in Comodo Settings to "automatically start the application with Windows (Recommended)". Unticking this , I expected the firewall not to start up on a reboot and thus not block anything. However, cmdagent.exe still gets started and continues to do its blocking - it's just the user interface that isn't started. Weird.
Looks like the only way to test if unexpected behaviour is down to Comodo, is to uninstall it
(unless anyone knows how to kill protected processes in XP ?)