RE: [FW1] problems with 4.1 management server & 4.0 firewalls

["Frost, Timothy E" <timothy.frost@FW1-NOSPAMeds.com>]

Franklin,


You seem to have several problems.

1: There are differences between 4.0 and 4.1 for objects.C.  You need to
merge the new objects.C and the 4.0 objects.C.  To do this:
	put your V4.0 objects.C in $FWDIR/conf as objects.V40
	get the default 4.1 objects.C in $FWDIR/conf as objects.V41

	run fw confmerge, after ensuring that there are no GUI clients
connected to the management station:
	fwstop
	fw confmerge objects.V40 objects.V41 > objects.C
	fwstart

2: The GUI gets the rulebases from rulebases.fws, not from *.W.  To load the
rulebases into rulebases.fws:
	cd $FWDIR/conf
	fwm -g *.W

NOTE:  You need to have the objects.C correct first.  If a rulebase
references an unknown object, then the fwm -g operation will reject that
rulebase file completely.


3: Have you got the backward compatibility module installed on the
management station, and a license for V4.0 installed?  You need these to be
able to load policies to the 4.0 firewall.  This is different from the case
with V4.0 management and a v3.0 firewall, where the software to manage the
3.0 firewall was bundled with the 4.0 software.




-- 
Timothy Frost			mailto:Timothy.Frost@eds.com
EDS New Zealand			Fax: +64-4-495-0473
8 Gilmer Terrace			Phone: +64-4-495-0504
P O Box 3647
Wellington
New Zealand



================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================