FireWall-1 FAQ: Various Bugs with Build 3072
Please note: This content was from when I was operating my FireWall-1 FAQ site, which I stopped operating in August 2005. For some reason people still have links to this stuff on the Internet that people are still clicking on.
I am making this information available again AS IS. Given how old this information is, it is likely wildly inaccurate. I have no plans to update this information.
If you're still running versions of Check Point VPN-1/FireWall-1 where this information is still relevant to you, do yourself a favor and upgrade to a more recent release. If you happen to be running a current release and the information is useful, it's by happenstance :)
Bugs that some have reported with build 3072 include:
- Problems managing non-build 3072 firewalls with a build 3072 management console
- Using the System Status Viewer on an NT management console to view the status of remote firewalls
- The CPU goes to 100% when using the Security Policy Editor or Log Viewer
A:
A hotfix for build 3072 was planned for the first week of September, 1998. Check Point released it and subsequently pulled patch 3078 (which was intended to replace 3072). SP8 or SP9 for FireWall-1 3.0b should resolve these issues. Meanwhile, there are workarounds:
-
For build 3072 management problems and the System Status Viewer, you will need to make a change to $FWDIR/lib/snmp/mib.txt replacing:
OBJECT IDENTIFIER ::= { enterprises 2620 }
with
OBJECT IDENTIFIER ::= { enterprises 1919 }
- For the CPU going to 100% on the GUI problem, you will need to get a couple of new DLL files from your reseller (MFC42.DLL and MSVCRT.DLL). There are specific versions of these DLL that have been made available through Check Point’s Partner Support pages.
