Herbert,
This info may resolve the issue. Found this on Checkpoint's web site:
Solution:
How to make Management Module version 4.1 backward compatibility with
version 4.0 Inspection modules?
NT:
When installing management module 4.1, check the backward compatible option
and Install a 4.0 license on the management module in addition to a 4.1
license
UNIX:
If you install the backward compatibility feature, you will need a valid
Version 4.0 license on the Management Module in order to manage Version 3.0
or Version 4.0 VPN/FireWall Modules.
After installing the backward compatibility feature, install the Version 4.0
license as follows:
1. Set the FWDIR environment variable to point to the directory where
Version 4.0 is
installed.
2. Install the Version 4.0 license using the $FWDIR/bin/fw putlic command.
3. Restore FWDIR to its previous value (that is, to point to the directory
where Version
4.1 is installed).
platform directory:
Solaris /opt/CKPfw
HP /FireWall-1
AIX /usr/lpp/FireWall-1
Regards,
Stephen
"Hines, Stephen (ISSAtlanta)" <[EMAIL PROTECTED]> on 08/16/2000 10:38:11 PM
To: Herbert Zarb/BOV@BOV
cc: [EMAIL PROTECTED]
Subject: RE: [FW1] Checkpoint-1 Remote Management Module Problem
Hello Herbert,
When you installed the Checkpoint software, did you choose the Backward
Compatibility mode which will allow it work with older pre-4.1 firewall
modules? I'm not sure what errors would occur without enabling this check
during installation (in your situation), but this may be the issue.
Regards,
Stephen
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 16, 2000 3:58 PM
To: [EMAIL PROTECTED]
Subject: [FW1] Checkpoint-1 Remote Management Module Problem
Hi,
I've already asked a similar question once but got little help. Trying again
since the
whole matter is getting really frustrating.
I'm trying to set up a centralised Checkpoint-1 Management Console and three
firewall modules. The EMC is 4.1, whereas two modules are also 4.1 (running
on
NT/UNIX boxes) and the last one is a 3.0 module running on an ODS
PizzaSwitch.
I've managed to get the EMC to communicate with the two 4.1 modules with
little
difficulty. However, I just can't get the 3.0 module to authenticate itself
with
the EMC -
all I get are "log authentication failure" and "connection broken while
communication
with x.x.x.x for bloadme" messages on the switch.
Since the firewall module on the switch uses skey to authenticate, I've
tried
playing
around with the control.map file by replacing all occurrences of fwa1 with
skey.
Still,
the behaviour remained the same. I've tried all the normal tricks (ie.
re-entering the
key) several times - same behaviour throughout.
I'd love to hear from anyone who has managed to get a similar setup (at
least a
4.1
management with a 3.0 module) running.
Thanks,
Herbert
============================================================================
====
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
============================================================================
====
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
