If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Startup: ZoneAlarm unable to connect to server

Dear Correspondent:

When I startup my computer (Toshiba E205-S1904) running Windows 7 (Home Premium, Service Pack 1), the Wi-Fi (2wire) is enabled and connected but no browser is running. I always get a message that ZoneAlarm (free, 9.2.102.000) is unable to connect with the server, check to see if my internet connection is okay...etc., etc.

Why is this happening? Am I missing out on updates?

The same thing happened when I tried to install ZA, but the error message suggested that I download the full installation software. I did this and it worked. Now, there is no suggestion as to why I am getting this error message with every boot, what it means or how to fix it.

Re: Startup: ZoneAlarm unable to connect to server

This may depend on many different factors from incorrect OS configuration, to other security tools conflicts, to the way you connect to internet (router, modem, 3G, cable, etc), malware infections, incorrect configuration of ZA, corruption of ZA settings.... really impossible to guess without been in front of your PC.

Assuming its a ZA issue and you are connected to internet while booting your PC, the steps below will resolved it.

1. Download and save on your desktop the latest version of ZAfree from here: Looking for the latest version?
2. Remove your current version of ZA via Windows 7 control panel --> unistall a program. Reboot the PC
3. Run the ZA removal tool to ensure no main left overs are still present on the system. Reboot the PC
4. Install ZAfree you have downloaded from 1.

Re: Startup: ZoneAlarm unable to connect to server

I will follow the steps that you have outlined for completeness' sake. As I mentioned, I am running Zone Alarm free version 9.2.102.000. If this is the latest version, then the procedure will not introduce anything new, but perhaps there is a random or chance interaction that might 'correct itself' with the second install. We will see...