| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Does anyone have any suggestions? I'm stuck and my Checkpoint support subscription expired :( Firewall version and build: NG with Application Intelligence (R55) 093 This is what happened: I went to the address translation tab in Smart Dashboard, we had one NAT rule there. I added 2 rules below it in an attempt to allow port forwarding. I also deleted a rule from the Security tab that had been disabled and we weren't going to use anymore. I did a Policy, Verify and that was okay. I next did a Policy, Install and the install failed with this error: Reason: Load on Module failed - no memory. So, I went back to the address translation tab and deleted the 2 rules that I had just created and on the security tab I recreated the disabled rule I had deleted. (So, everything should be back to the way it was before the first verify). I did another Policy, Verify and that came back okay. Did a Policy, Install and got the same error message again. I can open SmartDashboard and go to File, Installed Policies and view the policy on the firewall, and by the way, the firewall is working just fine - no complaints from users so far. So, if I could just somehow overwrite the policy that SmartDashboard makes changes to with the installed policy then this may fix the problem. Any ideas? I went to the firewall command line and looked at the dates of these files: $FWDIR/conf: objects.C - dated today objects_5_0.C - dated today rulebases_5_0.fws - dated today $FWDIR/conf/firewall: objects_5_0.C - dated today rulebases_5_0.fws - dated 2 days ago at last successful policy installation What I think I need to do is to replace the $FWDIR/conf/rulebases_5_0.fws with the $FWDIR/conf/firewall/rulebases_5_0.fws. Does that sound right? and if so, how? Thanks for any help, I'd really appreciate it!! |
| |||
| Jules, I know you stated that you have 'undone' all the changes you made prior to the error but can you not just push the original policy back down. Assuming you use db revision control that is? Joncon |
![]() |
| Thread Tools | |
| Display Modes | |
| |