What build of E-safe are you on? Build 100 is not stable and you should go back to 99 if you are on 100. -----Original Message----- From: Mario Toma [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 15, 2000 6:59 AM To: #Checkpoint; [EMAIL PROTECTED] Subject: RE: [FW1] [FW-1] eSafe CVP hangup with FW-1 SP6 Gerd, Check if you have a valid eSafe license. Recent builds of eSafe Gateway give exactly this problem if the license is expired. After license expiration only the update feature should be blocked, but currently the software 'stops' working each day... (According to Aladdin this will be fixed in the upcoming 3.0 release.) Best regards, Mario Toma B.Sc. Senior Security Consultant >>>------------------------------------------------<<< Triple P Systems & Networks Open Systems Mario Toma B.Sc. Senior Security Consultant e-mail address: [EMAIL PROTECTED] Telephone: +31(0)347 35 3380 Telefax: +31(0)347 35 3301 >>>------------------------------------------------<<< PGP Public key available on standard keyservers. Key Fingerprint: 7922 15EE 9721 30F5 1A3F 531F 9F6E 8C79 D5D6 EB8F >>>------------------------------------------------<<< -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of #Checkpoint Sent: dinsdag 15 augustus 2000 12:04 To: [EMAIL PROTECTED] Subject: [FW1] [FW-1] eSafe CVP hangup with FW-1 SP6 Importance: High Hello all, we are nearly dispairing!!! After we upgraded our FW-1 4.0 to SP6 we have SEVERE problems with our eSafe protect gateway Version 2.1 (meanwhile build 99). Every one/two days the RSERVER.EXE process from eSafe jumps to 100% CPU utilization and the eSafe server was in "nearly hangup state" (nearly means: response time for a simple login approx. 20 - 30 MINUTES; so a restart is always required). As soon as this effect happens, no more scanning of our services http, ftp and smtp is possible (so these communications are blocked) and all mails are stored in directory $FWDIR/spool of our AIX system 4.2.1 (RS/6000 model P43, 128 MB memory). Everything (not really everything, as the http 1.1 eSafe problem caused lots of troubles, so we had to move to SP6 and modified the objects.C file as recommended in FW-1 release notes) worked fine BEFORE this upgrade to SP 6. We executed all advice from our consultant but without success (updating the eSafe software, deactivating the automatic update feature). So we will now do a specific debug which may bring us and our consultant more detailed information for the analysis. However, if there is ANYONE WHO KNOWS THIS PROBLEM PLEASE CONTACT US!!!!!!!! Thanks a lot in advance. Best regards, Best regards Gerd Lienemann Pilkington Gelsenkirchen IS Communications Tel +49 209 168 2620 Fax +49 209 168 2289 ============================================================================ ==== 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 ============================================================================ ==== ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
