Without changing ANY options, it does make no difference:Ĭan anyone else please try to reproduce it under Vista 64 doing exactly theĭo a clean install (100% default options, i.e. It is dead easy to reproduce, I also tried doing a clean install … So why does it not ask under vista ? This seems like a (big) bug! XP clean install → If Port 135 is contacted for the first time, I get asked. Vista 64 clean install → Port 135 open, “no questions asked” The firewall correctly creates a deny rule for svchost.exe, and consequently port 135 The Port simply is open… -> I have to run the stealth ports wizard to close it.īut under Windows XP, the firewall correctly fires an alert, asking me if I wantĪny communication with “Svchost.exe” - Port 135. If I want to allow any incoming conections with Port 135. If I run the “Stealth Ports Wizard”, Port 135 will be properly “stealthed” afterwards.Īs mentioned above, after cleanly installing Comodo under Vista, I DO NOT GET ASKED If I properly, manually disable Windows FW (so that only comodo is still running), Port 135 will be OPEN! → The Comodo default install does not block it. Obviously, it is blocked by the Windows FW 88) If the Windows Firewall is still active after Comodo has been installed, Port 135 will be closed. Note: The behaviour is also reproducable using a fresh install with 100% default options (see end of post), so my detailed settings are of no particular interest. Were not changed and there were no new rules added after the clean install. All Application AND Global Rules are on default (!), i.e.A fresh & clean install of 3.0.24.368 on Vista 64 SP1 (and on XP SP3 as well).(CPF + Windows FW), and ideed Windows the FW was still acive and runing. The Security Center reported that both firewalls were running After doing a lot of investigations all night, I made some VERY INTERESTINGįirst of all, I noticed that Comodo does NOT DISABLE the Windows Firewall whenīeing installed on Vista 64.
0 Comments
Leave a Reply. |