Firewall problems with Firefox?

I'm a little leery about updating to 3.0 in the light of Firefox problems caused by other security product firewalls every time there is an update. There are numerous threads about this at Mozillazine forums, none so far regarding nod32.
It seems these firewalls can be a little too vigilant and intrusive, I would hate to install and find the next time FF updated I could no longer get onto the net or worse. Any feedback would be appreciated.
Edit: The firewall only applies to Smart Security not 3.0 AV I guess.

 

Sure it is FF and not TB? TB used to get blocked by my Trend PC cillian Firewall everytime it updated and there is no problem that I have come across relating to FF & Firewalls.

I suppose with ESS you could leave the Firewall to Automatic, and if it fails then you can change to interactive filtereing and remove the blocked FF rule and re install FF and allow the connection.Or if you see the FF update page go to interactive and pray it spots the new connection.
Will have to wait and see on that 2.0.0.10 can't be far away at the moment..

 

Yeah it's FF Steve, lots of firewall problems after updates.
After reading the threads here (many thanks to all) I think I'll stay with 2.7 until things get sorted.
I do however find it somewhat disappointing that Eset has not informed users that a new version exists. I get 'you have the latest version' when I check for an update and the only way I found out 3.0 was out was at FileHippo.
Not very good PR for a product and company I am extremely happy with and have successfully recommended to quite a few other folks.

 

In my opinion, the marketing campaign has been much better than with any previous version. It simply makes no sense to upgrade all users from v2 to v3 after a week since the final release and cease supporting v2.

 

Fair enough Marcos, I just think paying customers should be the first informed when a new version is available and advised as to how to download it should they wish to. As to Eset ceasing support of 2.7, please explain if and when that will happen, I was not aware of this.

 

Surely you cannot be thinking of ceasing support of 2.7!! I tried 3.0.56 yesterday and had installed it, and had it running a couple of hours, I could not shut down my computer. I thought it was just a minor glitch at first, so I waited several more minutes with the computer doing nothing but sitting there frozen, so I then just turned off the switch manually (something I never do unless there is no choice). Today boot-up went normally and everything seemed fine. Then after some hours I had to do a re-boot, and again my machine would not close down; it froze at the "Windows is shutting down" window. I even thought it might be doing something exotic with the registry, so I left it to go eat dinner. When I came back the screen was the same: "Windows is shutting down". No good.

So I un-installed V. 3., re-installed 2.7, and now everything seems to be working fine again (I've had nod32, first 2.5 then 2.7, for more than a year and have been very pleased with it; fulfilling my expectations for what I wanted from nod32: light, fast, and very competent.)

If you don't get Version 3 sorted out fairly soon, and if you also stop support on V. 2.7, it will create a huge hole in your AV systematic support. I hope that never happens. V. 3 is no where near ready for public use, as all the problems -- my own personal experience included -- indicate.

Please don't stop support for V. 2.7 until *at least* the fixing of V. 3., and even then I would keep support for 2.7 for some months after, since it will take some time for subscribers to switch over to V. 3 (and some may not want to do that for a longer time than a few months). You will lose a lot of us loyal buyers of your product.

SamSpade


|||