I posted a message yesterday about the VPN crash I'd seen twice, usually 
after my firewall was up for about 3 weeks.  I updated to 4.1 SP2 on WinNT 
SP5 on Monday, and the crash happened again this morning (not even 2 
days!).  On top of that, I've had this error that keeps showing up every 
hour the VPN is in use, and tech support hasn't been all that helpful 
yet.  Has anyone else seen these?  My FW and VPN have very light usage (2 
users behind the FW with very quiet email and web servers, and 3 VPN users 
right now).

Source: perfctrs  (NT Application Event Log) - happens ~ every hour the VPN 
operates
Type: Error
Description: Unable to read IO control information from NBT device.

This is the event log error messages for when my VPN crashed this morning:

Source: Perflib   (NT Application Event Log)
Type: Error
Description: The Collect Procedure for the "FW1" service in DLL
"...C:\WINNT\FW1\4.1\lib\fwntperfFW1" generated an exception or returned an 
invalid status.
Performance data returned by counter DLL will not be returned in Perf Data 
Block.
Exception or status code returned is DWORD 0.

Source: DrWatson  (NT Application Event Log)
Type: Information
Description: The application, WIN32/fw_strong.exe, generated an application 
error.  The
error occured on 8/2/2000 @ 9:39:48.486.  The exception generated was 
c0000005 at address
77de6a5e (<nosymbols>)

Thanks,

.. Jason Badry

--
    PP     PR
   APPRO CHPRJ   Jason Badry, BSc.           The APPROACH Project
   APPROACHPRJ   System Administrator        1st Floor, ABC 8114
    PPROACHPR                                8440 - 112 St
     PROACHP     Tel. (780) 407-7504         Edmonton, Alberta  T6G 2B7
      ROACH      Fax. (780) 407-6428
       OAC       email: [EMAIL PROTECTED]  http://www.approach.org
        A        http://www.approach.org/jbadry




================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to