Kerio 2.1.5 - Unable to Attach TCP Message
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
read more and respond »Posted 5 years ago by Martin in Networking Firewalls
