Kerrio personal firewall question

  • Thread starter Thread starter Francois
  • Start date Start date
F

Francois

Using v2.. on xp (SP1). Am a bit concerned with its errors on boot up
when port 445 is disabled on xp, using the well konwn registry trick
[google for removing port445 on WinXP] Can anyone recommend the later
(v4) version)? Or is there a better and equally small pfw for XP (SP1)?

TIA

Francois
 
Francois said:
Using v2.. on xp (SP1). Am a bit concerned with its errors on boot up
when port 445 is disabled on xp, using the well konwn registry trick
[google for removing port445 on WinXP] Can anyone recommend the later
(v4) version)? Or is there a better and equally small pfw for XP (SP1)?
Click to expand...

Dunno.

Do you have problems with reversing the 'well known reg trick' in XP and
using your FW for this sort of thing?
 
jo said:
Using v2.. on xp (SP1). Am a bit concerned with its errors on boot up
when port 445 is disabled on xp, using the well konwn registry trick
[google for removing port445 on WinXP] Can anyone recommend the later
(v4) version)? Or is there a better and equally small pfw for XP (SP1)?
Click to expand...

Dunno.

Do you have problems with reversing the 'well known reg trick' in XP and
using your FW for this sort of thing?
Click to expand...

No is the short answer. I've also since found this free great little
utility for closing down the offending ports on XP:

http://www.firewallleaktester.com/wwdc.htm

Kerio 2 has a bug that if port 445 is closed it'll give a nerror
message. Fixed in kerio 4, so it looks as though I'll opt for kerrio 4.

Francois
 
Francois said:
Using v2.. on xp (SP1). Am a bit concerned with its errors on boot up
when port 445 is disabled on xp, using the well konwn registry trick
[google for removing port445 on WinXP] Can anyone recommend the later
(v4) version)? Or is there a better and equally small pfw for XP (SP1)?
Click to expand...

I tried installing Kerio 2.1.5 on a couple of XP systems, and although
it worked there was always a problem with getting filter rules to
stick. In both cases I uninstalled that version and installed Kerio
ver. 4. That newer version worked flawlessly. Now, however, there is
SP2 to contend with, so I can't say what the result would be.
 
Francois wrote in
No is the short answer. I've also since found this free great little
utility for closing down the offending ports on XP:

http://www.firewallleaktester.com/wwdc.htm

Kerio 2 has a bug that if port 445 is closed it'll give a nerror
message. Fixed in kerio 4, so it looks as though I'll opt for kerrio 4.
Click to expand...

Actually someone posted the solution for that. Just check "for microsoft
networking use these rules".
 
No is the short answer. I've also since found this free great little
utility for closing down the offending ports on XP:

http://www.firewallleaktester.com/wwdc.htm

Kerio 2 has a bug that if port 445 is closed it'll give a nerror
message. Fixed in kerio 4, so it looks as though I'll opt for kerrio 4.
Click to expand...

Kerio 4.1 beta 5 is coming along very nicely. It has stateful
inspection now and seems very stable. In beta 6 they'll have logging of
packets to unopened ports, something I've been waiting for for a long
time. Looks pretty good anyway...
 
Back
Top