I am running the latest Comodo FW and have the same wireless issues that existed with Comodo 3 years ago. I’d really like to get this sorted as Comodo is great otherwise.
Everything works fine until my Linksys wireless cuts out - which it does numerous times throughout the day. Once that happens, I cannot reconnect. Windows shows my wireless as disabled and will not allow me to reenable it. Shutting down Comodo doesn’t fix it. I am forced to reboot. After reboot everything works fine but this is unacceptable. I typically run my PC for 7-10 days between reboots, not the 2 hours that Comodo is forcing me to do. I have tried uninstalling Comodo and doing so alleviates the problem. I have repeated this twice just to be sure the issue is in fact Comodo. I have allowed the range of 5 IPs that I have set for my network. I have encryption off so that is not an issue.
Are your computers set to a fixed IP address and is DHCP disabled on your router?
On a sidenote. Crashing router may be because of too many connections going on (read p2p clients that are not set properly). Encryption off? May be one of your neighbours is hosing your connection (with ARP spoofing that shouldn’t be hard)?
See, this is bad support. This problem is posted on these very forums numerous times and can be found on Google easily as well. Denying the issue is why it hasn’t been resolved in the 2+ years it has been reported.
The problem only occurs when Comodo is installed and is resolved by uninstalling Comodo. You can repeat this 2, 3 20 times and the result is always the same. As I already mentioned, you can also reboot but that is not acceptable. As for “repairing” the connection, Windows can’t repair a connection that isn’t broken.
I have no idea where you got the impression of a “crashing router” either. Nothing is going wrong with the router. DHCP is known to cause WiFi disconnects on XP and Vista occasionally during refreshes and has always been. Normally it’s no problem because it reconnects a few seconds later. This is where the problem with Comodo comes in as it does not allow the reconnect.
You are extremely rude considering you are a mod btw. I come here seeking help and you instantly get defensive and offer up silly excuses instead of offering some suggestions as to how to fix the issue with Comodo.
I assumed it was a router issue hence my reply (with Linksys I think router). I am not on wireless so I don’t know from experience Windows XP and Vista have a problem with reconnecting when DHCP lease gets renewed (is that correctly understood? In case of DHCP problem extend the lease time as a workaround).
Windows shows my wireless as disabled and will not allow me to reenable it. Shutting down Comodo doesn’t fix it. I am forced to reboot. After reboot everything works fine but this is unacceptable. I typically run my PC for 7-10 days between reboots, not the 2 hours that Comodo is forcing me to do. I have tried uninstalling Comodo and doing so alleviates the problem I have repeated this twice just to be sure the issue is in fact Comodo. .
I over read this statement. My bad here and apologies for that.
Back on topic and let’s get to grips with the problem. When during the process I think it may be a bug I will move the topic to the bug board so the devs will definitely see it. With what version fo CIS did the bug start? You only have firewall and D+ installed?
To be sure we are on the same wave length. Windows can repair a connection of a network device. To do so look up the network device in the Network screen and click right and choose the appropriate action. (Sorry for the not to the point directions. Currently on triple boot Windows and the Network screen is different on all three of them).
What I want to know does the repair function help or not? I just disabled my ethernet connection on Win 7 beta and started the repair routine. It says I can fix it by enabling the ethernet connection. Is this possible in your situation with Comodo installed or not?
When the above doensn’t help are you willing to do a clean install of Comodo with instructions I will give you after this? A clean install is more than just uninstalling and includes manual removal of possible left overs that the uninstaller forgot.
Yes, only the fw and D+ are installed. I have the current version installed on Vista x64. I had the same version installed on XP x86 last week or so. I have the same problem with both OS and completely different hardware. I am not sure in what version the problem started but a bit of Googling shows reports of the issue and no solution suggested back a couple years. I am sure there is a solution but it is not easily found it seems.
There is no issue reported with the connection so nothing for Windows to repair unfortunately. Actually Windows states you are still connected initially. Windows is unable to find or repair a problem when using the repair option. Disabling the wireless adapter and re-enabling it causes the network to display as disconnected and nothing will reconnect it short of a reboot.
When the above doensn't help are you willing to do a clean install of Comodo with instructions I will give you after this? A clean install is more than just uninstalling and includes manual removal of possible left overs that the uninstaller forgot.
I have reinstalled Comodo a number of times and as above, on 2 different OS with the same exact result. I run VMWare though so I can happily install and uninstall 100x if need be during the troubleshooting process. However, without some new advice, I couldn’t see the point as 3 times wouldn’t help anymore than 2 times if nothing changes.
Are both systems using the same wireless connector or are they different brands and types? Is your router using the latest firmware? Just covering bases here. Does the same thing happen with the latest v3.9 RC2? If you are still willing to try a clean install here is the drill:
Start with exporting your configuration to a folder that is not part of the Comodo folder under Program Files. This way you can restore your configuration after the reinstall.
Uninstall CIS and reboot. Then run [url=https://forums.comodo.com/comodo_system_cleaner_fileregistryprivacy_cleaner/comodo_system_cleaner_116494436_released-t37631.0.html]Comodo System Cleaner[/url] to get rid off registry keys.
Then delete the Comodo folders under Program Files, Program Files\Common Files, C:\Documents and Settings\All Users\Application Data\ .
Users%username%\appdata\local, Users%username%\appdata\roaming\ and \Users%username%\appdata\local\virtual store
To be even more thorough open Device Manager and set it to show hidden devices under menu option View. Then see if there are Comodo driver(s) left in non Plug and Play drivers. If so select the driver → click right → uninstall and reboot.
Now delete the following:
C:\boot.ini.comodofirewall (this file may not exist).
WARNING: Do not mistakenly remove the original “boot.ini”.
a. HKEY_CURRENT_USER\Software\ComodoGroup\CFP and HKEY_CURRENT_USER\Software\ComodoGroup\Comodo Internet Security
b. HKEY_LOCAL_MACHINE\SOFTWARE\ComodoGroup\CDI\1 *
*(If you have other Comodo products installed, delete only the values
s. HKEY_LOCAL_MACHINE\SYSTEM\Software\Comodo\Firewall Pro
u. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDAGENT *
v. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDGUARD *
w. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CMDHLP *
x. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_INSPECT *
y. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_CMDAGENT *
z. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_CMDGUARD *
aa. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_CMDHLP *
bb. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\Root\LEGACY_INSPECT *
cc. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_CMDAGENT *
dd. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_CMDGUARD *
ee. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_CMDHLP *
ff. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Enum\Root\LEGACY_INSPECT *
gg. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CMDAGENT *
hh. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CMDGUARD *
ii. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_CMDHLP *
jj. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_INSPECT *
kk. HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CFP_Setup_18.104.22.1686_XP_Vista_x32
ll. HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CFP_Setup_22.214.171.1246_XP_Vista_x64
mm. HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CFPLog
nn. HKEY_CURRENT_USER\Software\Local AppWizard-Generated Applications\CPFFileSubmission
oo. HKEY_LOCAL_MACHINE\SYSTEM\Software\Comodo\Firewall Pro
Two last questions before I move your post to the bug board. This problem doesn’t happen when using a wired connection to your router? Can you post a screeny of your Global Rules and the Application Rules for System and svchost.exe?
Edit: do you use a Linsksys router as well? I came across two topics with problems with Linksys router. I am just trying to establish whether there might be a connection.