Anything that uses sockets, etc (incl Kerio) will fail if the system file ws2_32.dll faults. I guess the fault address within the dll (ordinal?) is the key to finding out what went wrong.
- Vote on answer
- posted
19 years ago
Kerio 2.1.5 crash in ws2_32.dll
Loading thread data ...
- posted
19 years ago
Hi
Kerio 2.1.5 crashed a couple of times yesterday with this error:
Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 14/07/2004 Time: 21:10:32 User: N/A Computer: XXXXXX Description: Faulting application persfw.exe, version 2.1.5.0, faulting module ws2_32.dll, version 5.1.2600.0, fault address 0x00008d72.
This was on XP Pro SP1 with all critical updates applied. AFAICR, this was the first time that Kerio has crashed with this error, and I've been using it for about 18 months. To date it has been very stable.
I've googled for similar error reports but without much success. It is possible, however, that the crash was caused by some exploit. Can anyone confirm this? If so, can Kerio be configured to guard against future attempts? Any ideas or suggestions would be appreciated.
Thanks
Matt M