Kerio 2.1.5 - Unable to Attach TCP Message
- From: "Martin" <vdp3r@xxxxxxxxxxx>
- Date: Thu, 7 Sep 2006 17:53:22 +0100
Windows 2000 SP4 with Kerio firewall 2.1.5.
After closing port 445 using
either Windows Worms Cleaner or by editing the registry, I get the message
on boot up " Kerio Personal Firewall Driver : Unable to attach 'TCP"
followed by similar messages for other protocols. Google indicates this is
a known bug. Nevertheless, on running the ShieldsUp probe, my computer is
still stealthed despite the error messages. I tried uninstalling Kerio,
closing the port, then reinstalling Kerio, but that didn't fool it.
I can't see any fix for this bug on Google. And after running ShieldsUp, I
don't know if the error message is spurious or a genuine indication of a
problem in the firewall.
Any thoughts? (In the meantime, I have reversed the registry changes so
that port 445 shows as listening but is at least protected by the firewall.)
Thanks.
Martin
.
- Follow-Ups:
- Re: Kerio 2.1.5 - Unable to Attach TCP Message
- From: Wolfgang Ewert
- Re: Kerio 2.1.5 - Unable to Attach TCP Message
- Prev by Date: ZoneAlarm Update Wont Install
- Next by Date: Re: Sonicwall 2040 can't block MSN Messenger 4.7
- Previous by thread: ZoneAlarm Update Wont Install
- Next by thread: Re: Kerio 2.1.5 - Unable to Attach TCP Message
- Index(es):
Relevant Pages
|