Hello,
I too have had that problem. Since the client I support has not purchased
support I can not address this with Checkpoint. You will find that it is
a single piece of email that the SMTP security server doesn't like.
Here is the procedure I use to get everything going.
1. fwstop
( c:\winnt\fw\bin is in the path right?
Go to the spool directory. c:\winnt\fw\spool by default
2. Make some folders/directories somewhere, Name them Bad1, Bad2, Bad3(3
should be enough.
3. Move all the files from the spool, to the bad1 dir.
4. fwstart
5. move half of the files from the bad1 dir back to the spool dir.
6. Refresh often and wait for either the spool to clear, or another
Dr.Watson
7. If the spoll clears, grab half the remaining files from bad1
7a.If you get a Dr. Watson
7b. fwstop
7b. Move all files from spool to bad2
7d. fwstart
7e. move all files from bad1 to spool
8.No Dr. Watson-- Keep grabing half and dumping to spool.
The point here is to pinpoint the file and clear the spool.
Always remember to grab half the files, makes things faster. Also, you
may need to do a 'fwstop' & 'fwstart' if it seems that the spool is not
clearing fast enough.
I would recommend that after you are done, either reboot(prefered) or do a
fwstop and fwstart.
On Thu, 18 Mar 1999, Richard K. Dineen wrote:
> Is anyone having the same problem?
>
> First the stats: Firewall-1 3.0b 3083 running on NT 4 SP4. Hardware
> is
> a Compaq 1600 model 450 with 196MB of RAM, a built in NIC and a
> dual interface Netelligent NC3122. We are using the HTTP and SMTP
> security servers. It ran for a long time being just fine. Then a
> few
> days ago it started crashing one of the fw processes. When it
> happens,
> there may be 5 to 10 crashes in the course of a minute. And then it
> will
> subside again. The firewall continues to function until it overruns
> memory from the processes. I have tried disabling logging but that
> doesn't help. I was seeing warnings about H323 not having header 03,
> so I disabled H323 to see what that does. The process crash is
> always
> an Access Violation (0xc00005 I think). We are going to upgrade to
> the
> newest version of 4 soon. I was wondering if anyone had seen this
> and
> knew what it might be. Thanks
>
>
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
