ZoneAlarm starts last - causing problems at boot

Lars-Erik Østerud wrote:
For some reason ZAclient is the last thing that starts when I boot XP.
This causes some problems:

1) The DHCP and DNS clients are blocked at boot (log full of "DNS"
entries)
This often causes "unable to get DHCP adress trouble" (using static
IP for now)

2) Atomtime.exe is blocked from updating time (log full of "Daytime"
entries)
This causes Atomtime either to hang, or to give a "unable to
connect" message

Is there a way to fix this, why does ZLclient have to start, can't the
True Vector service see that these programs are allowed from the setup
file before ZLclient starts ?

What starts first, services, the registry "Run" section, or the
"StartUP" folders?
And in what order are programs started (alfabeticly? then "zlclient"
is last :-)?


The solution is probably within ZoneAlarm itself. Put
essential [and proven] IP addresses into the "trusted"
zone. The ISP should be put into the "Internet" zone.
This is done in the Zones applet of Firewall in ZA.

Crusty,

Could it be because the real question is about the sequence of
loading/running startup items in WINDOWS?

Fred


Richard Urban wrote:
You're asking this question in a Microsoft news group instead of the
ZoneLabs news groups because????

His question was "Is there a way to fix this, why does ZLclient have to
start, can't the
True Vector service see that these programs are allowed from the setup
file before ZLclient starts ?"

Both True Vector service and ZoneAlarm client are part of - guess what -
ZoneAlarm. He should ask them why the service has to start.


--

Regards:

Richard Urban

aka Crusty (-: Old B@stard :-)


"Fred S" "Fred wrote in message
...
Crusty,

Could it be because the real question is about the sequence of
loading/running startup items in WINDOWS?

Fred


Richard Urban wrote:
You're asking this question in a Microsoft news group instead of the
ZoneLabs news groups because????