Perhaps emule is not a safe application.
But, if I configure CIS4 fw in the same way i had CIS3, and now emule does not work ???, the problem is in CIS4, not in emule.
If you have connectivity problems:
[b]Go at Firewall -> Common Tasks -> Stealth ports wizard [/b]and select
[b]Alert me to incoming connections- stealth my ports on a per-case basis[/b]
Users with a dialup connection (not behind a router) should consider to avoid the above step since it will also cause “Block and Log IP In From IP Any to IP Any Where Protocol is Any” to be removed:
In most cases all they need would be to place new rules to allow inbound connection to emule TCP and UDP client ports before the “Block and Log IP In From IP Any to IP Any Where Protocol is Any” one and if there are still connection problems:
Check the log for any blocked connection pertaining emule or Windows Operating System to start a new topic and attach the Firewall log output.
2. The “All applications” policy got a “Block and Log All unmatching requests” rule (Such policy is not available in “COMODO - Proactive Security” Configuration)
Such “All applications” policy would prevent inbound connections to any application without an assigned policy (but also affect applications whose policy is placed downward/after eg: it will prevent inbound connections to “Windows Updater Applications” group as well )
Emule won’t be able to receive inbound connections until that “All applications” policy is either removed or moved after any existing executable with an “emule” policy