3.0.17-.22:Lots of Network Connection Problems (MERGED TOPIC)

[sded]

We are still looking for the solution.  Let us know if the workaround fixes it for you.  Or if the reinstall does it by itself. 

[sded]

Thought these had enough in common to merge them and look for common solutions.  One other comment-I have noted with the latest version that sometimes the connection icon shows the  red X, and says there is no connection, even though the connection is still working fine.  I orginally attributed it to the VPN I was using, but removed it and still have the problem.  So please let me know if the connection appears to die or not start and is still working.  Thanks; Ed.

[slimak]

Okay, I uninstalled CFP 3.x--and then ran CCleaner to remove all leftover hangers-on.  I reinstalled a freshly downloaded copy of the latest version from Comodo.  Upon the first re-boot, CFP 3.x ran and behaved properly.

I shut down the PC, had lunch, and turned the machine back on.  "Limited or no connection" icon was back, as was the request to accept the new IP address.

Whatever was added to the latest Feb. 13th update is the cause of this problem, for everything on two seperate PCs was working like a Swiss watch up until this latest release arrived.  On the laptop, the auto-update killed off an already discussed DLL (which made launching/uninstalling the program impossible).  When that little hiccup was fixed with a "transplant," it worked for a while--and then it simply killed off wireless/wired networking.

My desktop didn't share in the DLL "vanishing act," but its networking went adios shortly thereafter.

I'm giving the workaround a shot and will comment on this board whether or not it worked.  In the meantime, can Comodo's crack staff give this latest version's updated code a good re-examination?   

[slimak]

Okay, I can report that the workaround has worked on my wired, desktop LAN connection.     Hopefully, I can get the desktop fired-up and running as well using this same solution.

[sded]

Could you all with this problem let us know what OS you are using?  We are trying to see if this is just a Vista problem, or affects XP too.

[slimak]

Okay, sded, I've run into the problem on two XP machines.

My desktop is a dual-boot unit running primarily WinXP Pro SP2 (Windows Vista Home Premium without CFP is installed on a seperate drive) and a wired connection to the LAN.  My HP laptop is running WinXP Media Center SP2 with a wireless connection to the same D-Link WiFi router.  Both machines are running Sophos AV.

[sded]

There are several reports of loss of DHCP service for wireless with the new build at http://forums.comodo.com/help_for_v3/wireless_connection_problems_merged_topic-t19817.0.html .  I have not been using DHCP, I use a wired fixed IP instead at home.  Doesn't seem to occur with wired.  Switching to wireless DHCP for me only causes loss of the connection up status indication, not the connection itself.  Others report success with switching their wireless to a fixed IP, but not all have evaluated it.  Affects both Vista and XP.  Are there any known changes to .204 that could impact this?  Are there others having this problem?  Not enough to complete a bug report yet, but more help/ideas/experiences  would be appreciated.  So far:

Workaround-use a fixed IP instead of DHCP=seems to work for some (all?)
Put an allow rule for UDP between computer port 68 and router port 67 in WOS
Make sure that the Windows Firewall service is on, even if not using it (from Google for Vista)-prob N/A
Make sure that discovery mapper and responder are on for the NIC
Make sure that SSDP discovery service is on

[sded]

A few other things to try.  1) Make sure the DHCP client service is on.  And the SSDP discovery service.  2) At your NIC, make sure that discovery mapper and responder are on, if applicable.  3)  Try turning on the Windows Firewall Service (not the firewall) even if you are not using it.  And please report back if fixed IP works for you, or at least changes the behavior. 

[chuwl]

OK, where do I begin? 
I am one of those "not so savvy" computer operators.  But I DO KNOW that up until firing up my desktop this morning, I was able to have internet access.  Not so after this morning.  Have spent an ENTIRE DAY on the phone with Time Warner and D-Link, thinking it was one of these two to blame.  Never THOUGHT it would be the firewall, until that "little something," told me to DISABLE IT and try to connect to the internet.  For some reason my IP address was changed to 192.?.?.?  Once I received the correct IP address, and disabled the firewall, I'm great.  I will be leaving commodo disabled permanently, or deleting it all together.....what a PAIN! 
I thought I was CRAZY!  I don't need this HEADACHE! 

[slimak]

chuwl, there's no need to drop Comodo.  They've just updated the program today and it's quite likely that they'd patched the problem.  Don't give up on the best firewall protection "for the money" just because of one hiccup. 

[jpu]

let us know what OS you are using? 

I have similar problems in XP Pro SP2 + D-Link wireless router. CFP is ver 3.0.18.309.
The router and its DHCP server are ok, because my work laptop works fine (without CFP).

Curious thing: connecting to wireless router's Ethernet port by wire (i.e. not WLAN) works fine (using CFP) and after connection is made the wireless connection starts working too.

Static IP seems to work but it cannot be a long term solution.

[sded]

I use static IP at home anyway, but haven't had the problem.  No word from the developers (or anyone else) on the nature of this bug, and no way to repeat it for them.   Since it broke in .18, we can see if .19 fixes it again, but other than using static IP haven't found a solution.  Have you tried the suggestions above to see if there is any change?  I haven't found any reason for DHCP to be blocked, other than some internal change to .18 we don't understand.   

[slimak]

 

Well, after getting my desktop back up and running, my ability to network went adios this afternoon shortly after CFP 3.x was updated on my laptop.

Has anyone back-tracked the code that was changed in the software to figure out why so many folks have lost the ability to network wirelessly or connect to the Internet?   

Things over here have deteriorated to the point that I've uninstalled Comodo firewall and have installed a basic version of ZoneAlarm (temporarily) so that I can have some degree of safety and a fuss-free and usable wireless network that actually works.  Not good...

[DyNaRaX]

Last friday I got a message that a new version of Comodo Firewall was available so I installed the latest version on my desktop.
After rebooting I noticed that I was unable to connect to my network.  I only got a 169.x.x.x instead of a 192.168.1.x address.
I started checking the cables and all settings, I even restored my Windows Xp Pro to a earlier state but I still got the same problem.
With my laptop (running Ubuntu) I was able to connect to the router so I was shure that the router was fine.
I uninstalled Comodo and then I was able to connect to my network again.  Comodo was reinstalled and now everything is fine again.

Today I was working on the laptop of my father and got the same update message and I updated the firewall.
After the reboot I tested the connections, wifi was fine but the wired connection failed, again a 169.x.x.x address.
So I did the same thing as on my desktop, uninstall, reboot, reinstall, reboot.  Under the first account everything was fine.  When I tested a second account I was able to connect via the cable but I failed with the wireless connections.  This was very strange because with the other account I worked fine 2 min before.

Did anybody have simular problems?  I was so p*ssed this morning that I decided to remove Comodo from my father's laptop and we are now using the Windows Xp firewall.

The desktop is running Win Xp Pro SP2 and the laptop Win Xp Home SP2 both accounts that I tested have Admin rights and the desktop and laptop are not connected to the same network.

[sded]

Take a look at http://forums.comodo.com/help_for_v3/wireless_connection_problems_merged_topic-t19817.0.html for similar problems.  Only solution found to work for most is using fixed IP address, as described there.  There is also a bug report at http://forums.comodo.com/bug_reports/3017304_causes_wireless_internet_connection_problems-t19885.0.html that references it.  I'll add you to the thread under help for V3, so you will part of the backup for the bug report.