On a Vista PC i use i've noticed ZA free v8 alerts me with both those whenever i launch IE or FF. In earlier versions of ZA on XP, i'm sure they only required Internet access and not Server access too. Any clues as to why ? TIA
Hi! don't know how ZA free works but under ZA retail versions IE and FF are set automatically (by the remote ZA white list database) to allow internet access and the server rights only for the trusted zone. So, IE has HIPS (trust level) to SuperTrusted, blocked access to server rights to the internet (red cross) and the rest allowed. Cheers, Fax
What i really want to establish, is why IE & FF require Server access when launched. This is before i visit ANY www ? as i have a blank page set as my home page. fax Thanx
The why I don't know but you can try to investigate it by monitoring IE/FF with tools likes sysinternals TCPViewer and Process Explorer to understand exactly what is happening behind the scene... including understanding if it is just server rights to the trusted zone (often needed for the correct functioning of some software and quite common) and server rights to the internet (less common, unless it is related to IM, P2P, VOIP, etc) Cheers, Fax
StevieO, I'm using ZA Free 5.5.094.000 and my main browser is Firefox. While I don't get an alert when launching FF, every time the browser is updated (like the last 3.5.2 version), after FF is restarted, I get the Server Internet connection attempt ZA prompt. Of course, I deny it and check "remember this." Then, I go into ZA and confirm that the red X is there. From that point forward, FF works without a problem. According to this Mozilla's Configuring ZoneAlarm Free Firewall support article, it states "The entries in the Server column are not relevant" and by that I have to assume that FF does not require Server rights. As a matter of principle, I deny Server rights to all software and have blue question marks attached to a very few Microsoft processes.
Firefox is well known to do a TCP loopback connections (do a "netstat -a" at the command prompt to check) in order to communicate with its own SSL module (among other things). Since it is a localhost (127.0.0.1) connection, it will loop only within your PC and not in your network, let alone the internet. I think ZoneAlarm is a bit paranoid on this one, or simply lacking sufficient info on the comm (don't know, haven't seen ZA in ages). IE uses the same technique but uses UDP protocol instead of TCP. You can allow these connections without worries.