RE: [FW1] unknown established tcp packet

[Aeon Hale]

I just want to throw my 2cents into all this.  I wish I could go back in time and stop myself from putting SP4 on our Firewall.  Since then, we have had lost connections from clients, 4 crashes, and 1 primary firewall go down completely (i'm reinstalling as I type).  What's extremley funny is that the backup firewall (which is currently in production) is on SP3, has a worthless processor, hardly NO RAM and still runs better than our main FW server (the one that I am reinstalling) with SP4.   Thanks for the service pack, i needed the overtime!!!!!       -----Original Message----- From: Dorny [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 25, 2001 8:46 PM To: [EMAIL PROTECTED] Subject: [FW1] unknown established tcp packet Once again another e-mail titled unknown established tcp packet.  I have looked through the list but I was not able to find a definitive solution for this error.  Here is my problem after applying the latest check point service pack (SP4) I began seeing my logs fill up with dropped packets by rule 0 with the unknown TCP error.  Now I have customers telling me that they cannot ssh, run restores, ect through their firewalls which upon further investigation I noticed that all the packets were being dropped by rule 0.  I am also seeing lots of in-bound packet to customer web sites being dropped by rule 0 with the same error.  None of this was happening when I was at SP 1 or 2.  Anyone out there have a solution for this???? --Richard Dornhart