Error pushing policy

[parlay]

Hi

Last night everything was working fine with my Checkpoint firewall. I was trying to figure out why my VOIP phones constantly drop everytime I push a new policy. I read a few forums and someone suggested the following. Go to General Properties - Advanced - Connection Persistence - and change from Rematch Conections to Keep all Connections. So I did that. Also suggested was that i find the service that is dropping when the policy is pushed and check the Keep connection open after Policy has been installed under the service. So I did that also. So when i pushed the policy this time, I got "Installation ended with errors". When I hit Show errors, all I see is Advance Security "Operation was unsuccessful". So I did the obvious and changed everything back to the way it was but when I pushed the policy again, i got the same errors! So I tried rebooting the server, and still I'm getting the same errors when I push the policy. I am by no means a Checkpoint expert. We are running Checkpoint NG FP3 on a Dell server running Win2K server. Please let me know what I can do to get rid of this error? I'm guessing i need to get the last successful pushed policy back, but I have no idea how to do that?

Thanks
Ian

[chuachongchee]

Originally Posted by parlay

Hi

Last night everything was working fine with my Checkpoint firewall. I was trying to figure out why my VOIP phones constantly drop everytime I push a new policy. I read a few forums and someone suggested the following. Go to General Properties - Advanced - Connection Persistence - and change from Rematch Conections to Keep all Connections. So I did that. Also suggested was that i find the service that is dropping when the policy is pushed and check the Keep connection open after Policy has been installed under the service. So I did that also. So when i pushed the policy this time, I got "Installation ended with errors". When I hit Show errors, all I see is Advance Security "Operation was unsuccessful". So I did the obvious and changed everything back to the way it was but when I pushed the policy again, i got the same errors! So I tried rebooting the server, and still I'm getting the same errors when I push the policy. I am by no means a Checkpoint expert. We are running Checkpoint NG FP3 on a Dell server running Win2K server. Please let me know what I can do to get rid of this error? I'm guessing i need to get the last successful pushed policy back, but I have no idea how to do that?

Thanks
Ian

Hi,

Can you provide a screenshot of the error for us please?

Also, did you do a backup b4 doing any changes or did a database revision control??

[parlay]

I didn't do a database revision, but i do have a backup of the conf and database folder from september that i would be fine using.

go to these links to see errors:

http://209.205.34.20/stock/error1.bmp

http://209.205.34.20/stock/error2.bmp

Thanks

[parlay]

Any suggestions?

[parlay]

I was able to rebuild my firewall. all is working pretty well except I keep getting the following error in my Win2k server event logs?

FW1: ndis_allocate_packet: Cannot allocate new packets

I keep getting a rash of these errors and then my Checkpoint FW stops responding. only a reboot of the server will solve the problem.

[chuachongchee]

Originally Posted by parlay

I was able to rebuild my firewall. all is working pretty well except I keep getting the following error in my Win2k server event logs?

FW1: ndis_allocate_packet: Cannot allocate new packets

I keep getting a rash of these errors and then my Checkpoint FW stops responding. only a reboot of the server will solve the problem.

What network card and driver you are using? Have you checked the hardware compatability list?

[parlay]

I actually have 4 nic cards in the server. not sure about the compatibility, everything looks fine in windows.

[Thorpuse]

Sounds like a Windows OS problem. Running VPN-1 Gateways on Windows has never been a good idea - I'd strongly recommend you grab the export/import tools and migrate the config to SecurePlatform.

The Windows network driver is notorious for doing strange things when additional kernel drivers sit on top of it. You could spend hours/days/years trying to work this out, or cutover to a much more reliable system in a few hours. You can also use this as an opportunity to upgrade to NGX....

[parlay]

well everything was ruinning smooth for a couple years now until I had to rebuild the other nite. so i think there is some setting i missed. could it be the speed the nics are set to?