From: Phil Stracchino <alaric@ca...> - 2003-05-21 16:34:09
I've become aware of a minor problem involving Bacula clients on Win2K
and ZoneAlarm that Bacula users should probably be aware of. I don't
think it's Bacula's fault, I don't know if it occurs only on Win2K, and
I don't know if it's limited to certain versions of ZoneAlarm, but it's
something tob e aware of.
The issue is this: For some reason, each time the Bacula client loads,
ZoneAlarm seems to think it's a new executable that it hasn't seen
before. Consequently, you have to re-authorize Bacula-fd to talk on the
network through ZoneAlarm each time the machine is powercycled. If this
isn't done, backups will fail with a apssword mismatch error until you
update ZoneAlarm's auth lists.
I don't know why it happens, but there's a fairly simple workaround.
Any time you have to bounce one or more 2K boxen with Bacula clients and
ZoneAlarm installed, open the console and issue a "status all" command,
then just walk around your win2K boxen looking for ZoneAlarm auth
request popups. Click "Yes and remember" for "access the network" and
"act as a server", and you're ready to go.
This may also affect XP and 9x. On the other hand, it may not affect
your ZoneAlarm version. If in doubt, it's not hard to test.
.********* Fight Back! It may not be just YOUR life at risk. *********.
: phil stracchino : unix ronin : renaissance man : mystic zen biker geek :
: alaric@... : alaric-ruthven@... : phil@... :
: 2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold) :
: Linux Now! ...Because friends don't let friends use Microsoft. :
Get latest updates about Open Source Projects, Conferences and News.