Steve,
When I used to run NT firewalls, I wanted to know the same thing.
Fortunately "tlist" from the NT resource kit came to the rescue. Just run
"tlist fw" from a prompt. It'll scroll by all kinds of info, including the
command line fw.exe was called with. That'll tell you what server is eating
all of your ram.
Good Luck - Mark Ingles
At 11:45 AM 1/31/01, Steven Zimmerman wrote:
>Are you running out of physical memory? We have the same problem with NT4.0
>SP6a FW 4.1 SP3. But one of the fw.exe is eating up all the memory. Most
>of the time we can do an FWSTOP/FWSTART and that fixes the problem....for a
>day or two.
>
>I've had a couple people stat the same thing... Anyone know where we can go
>to try to trouble shoot this?? What's the easiest way (if any) to find out
>which security server is associated with which fw.exe??
>
>Thanks in advance!
>
>Steven Zimmerman
>CIO
>IR Network Solutions
>770-277-9877 x224
>770-237-5497 fax
><snip>
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
