I just wonder why the connections as seen in the attachment are blocked automatically. I know it happens when uTorrent is closed because port 54974 is its port and when I start uTorrent those particular incoming connections are not blocked anymore.
So: Why blocked automatically as protocolled though I deleted default all global rules and set COMODO FW-alerts to “very high” level (for testing purpose).
Related to this subject there was another problem: When trying to install IE10 the installer requested internet access which I allowed but yet failed to install. Checking the protocol COMODO blocked some incoming connections again that were necessary to install IE10 - NO ALERT but an automatic block. Disabling the FW temporarily made the installation successful.
I checked all the advanced settings and cannot see any reason for the auto-block. In case of the closed uTorrent the auto-block is actually “okay” and acceptable but but when installing an application it’s disturbing not being asked/warned but only seeing the installation has failed… This behaviour applies to version 5.12 as well as 6.0.
The connections are automatically blocked because the process for handling the connections has been closed. However, the requests continue to arrive. Under Windows connections of this type are passed to a pseudo process called System Idle (PID 0) under Comodo this process is represented as Windows Operating System.
If you don’t want to see the log entries you can create an Application rule for Windows Operating System to block without logging, for TCP or UDP and the desired port.
Related to this subject there was another problem: When trying to install IE10 the installer requested internet access which I allowed but yet failed to install. Checking the protocol COMODO blocked some incoming connections again that were necessary to install IE10 - NO ALERT but an automatic block. Disabling the FW temporarily made the installation successful.
I checked all the advanced settings and cannot see any reason for the auto-block. In case of the closed uTorrent the auto-block is actually “okay” and acceptable but but when installing an application it’s disturbing not being asked/warned but only seeing the installation has failed… This behaviour applies to version 5.12 as well as 6.0.
There shouldn’t have been any unsolicited inbound connections required for the installation of IE10. If the installation failed, it may have been a configuration issue or perhaps a temporary connection problem. As you’ve already removed the Global rules any issues may reside with your Application rules. it helps, you can post screenshots of you rules and logs.
I decided to make a rollback to IE9 which obviously can be installed completely offline on my system. Moreover I reinstalled CIS 5.12 - the new GUI is :-TD - sorry… I cannot get warm with it… :o