Free Firewall?

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5 a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone Alarm and finally
migrated following it's seemingly endless incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing *List of ports* rather
than *Any port* in the Port Type field and typing the numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or Outgoing.

Otherwise the rules it installs with along with those you make in the same
way as with Zone Alarm, eg allow or deny Windows Media Player, Outlook
Express etc etc as they try to access the 'net should be adequate.


Thanks for the feedback, Shane.

NP.

Shane

Maybe it would have been better should I have said "I
understand" rather than "Point Taken". To me it means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a lot.
Are there any other setup 'rules' I should be aware of?
I'd hate to shut off ZA (which has provided good security,
despite the lock ups) to instead install an application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing
*List of ports* rather
than *Any port* in the Port Type field and typing the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with those you
make in the same
way as with Zone Alarm, eg allow or deny Windows Media
Player, Outlook
Express etc etc as they try to access the 'net should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.

Have a look he http://www.geocities.com/yosponge/firewall.html

I haven't even downloaded the files, let alone tested them, but this is
referred to by a trusted site (cexx.org).


Shane


"KB" wrote in message
...
Maybe it would have been better should I have said "I
understand" rather than "Point Taken". To me it means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a lot.
Are there any other setup 'rules' I should be aware of?
I'd hate to shut off ZA (which has provided good security,
despite the lock ups) to instead install an application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing
*List of ports* rather
than *Any port* in the Port Type field and typing the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with those you
make in the same
way as with Zone Alarm, eg allow or deny Windows Media
Player, Outlook
Express etc etc as they try to access the 'net should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.

Ignore the fact it talks of 2.1.4., it's obviously a little out-of-date.
Kerio 2.1.5 is the same but with a bugfix.


Shane


"Shane" wrote in message
...
Have a look he http://www.geocities.com/yosponge/firewall.html

I haven't even downloaded the files, let alone tested them, but this is
referred to by a trusted site (cexx.org).


Shane


"KB" wrote in message
...
Maybe it would have been better should I have said "I
understand" rather than "Point Taken". To me it means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a lot.
Are there any other setup 'rules' I should be aware of?
I'd hate to shut off ZA (which has provided good security,
despite the lock ups) to instead install an application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing
*List of ports* rather
than *Any port* in the Port Type field and typing the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with those you
make in the same
way as with Zone Alarm, eg allow or deny Windows Media
Player, Outlook
Express etc etc as they try to access the 'net should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.

Shane and KB:

Hope you don't mind me, butting in with a contributing comment of my own.
Hearing these adverse remarks about ZA makes me feel a lot better especially
since I had to go without it, even though I paid for it.
It was giving me a heap of trouble.
I opted for Avast instead and am wondering, whether it's less effective than
Kerio. Happen to like it a lot (Avast).
Any feedback appreciated.

Harry.


"Shane" wrote in message
...
Ignore the fact it talks of 2.1.4., it's obviously a little out-of-date.
Kerio 2.1.5 is the same but with a bugfix.


Shane


"Shane" wrote in message
...
Have a look he http://www.geocities.com/yosponge/firewall.html

I haven't even downloaded the files, let alone tested them, but this is
referred to by a trusted site (cexx.org).


Shane


"KB" wrote in message
...
Maybe it would have been better should I have said "I
understand" rather than "Point Taken". To me it means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a lot.
Are there any other setup 'rules' I should be aware of?
I'd hate to shut off ZA (which has provided good security,
despite the lock ups) to instead install an application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing
*List of ports* rather
than *Any port* in the Port Type field and typing the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with those you
make in the same
way as with Zone Alarm, eg allow or deny Windows Media
Player, Outlook
Express etc etc as they try to access the 'net should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.

I don't think anyone here minds a kbitz. We're all
friends here, and on the same platform. Like I tell the
folks at the inconvenience called a 'job', we're all on
the same team.

ZA seems to kill many of my system functions, including
but not isolated to, media player, RoadRunner, etc. etc.

Like I said earlier, when the 'ol ME locks, shut off ZA is
the first course of action.

Peace and best wishes.

KB
-----Original Message-----

Shane and KB:

Hope you don't mind me, butting in with a contributing
comment of my own.
Hearing these adverse remarks about ZA makes me feel a
lot better especially
since I had to go without it, even though I paid for it.
It was giving me a heap of trouble.
I opted for Avast instead and am wondering, whether it's
less effective than
Kerio. Happen to like it a lot (Avast).
Any feedback appreciated.

Harry.


"Shane" wrote in message
...
Ignore the fact it talks of 2.1.4., it's obviously a
little out-of-date.
Kerio 2.1.5 is the same but with a bugfix.


Shane


"Shane" wrote in message
...
Have a look he
http://www.geocities.com/yosponge/firewall.html

I haven't even downloaded the files, let alone tested
them, but this is
referred to by a trusted site (cexx.org).


Shane


"KB" wrote in message
...
Maybe it would have been better should I have
said "I
understand" rather than "Point Taken". To me it
means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a
lot.
Are there any other setup 'rules' I should be aware
of?
I'd hate to shut off ZA (which has provided good
security,
despite the lock ups) to instead install an
application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one
who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course
of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in
message
...
Point taken, Shane. Noel bailed me out nearly a
year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative
I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll
give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began
with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more
nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose
Administration/Advanced/New

Set or type the following in the appropriate
fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030,
choosing
*List of ports* rather
than *Any port* in the Port Type field and typing
the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with
those you
make in the same
way as with Zone Alarm, eg allow or deny Windows
Media
Player, Outlook
Express etc etc as they try to access the 'net
should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.







.

Harry,

I quit ZA, other than for occassional testing of new builds, about 3 years
ago now. Every subsequent build I've tested has been at best a pita and I
doubt I'll ever even test it again, let alone run it permanently. I used to
swear by it and now I swear at it.

As for Avast!, I tried their AV and hated it. While their DOS version
performed poorly in my tests, that is a trivial reason as AVG's DOS
component did too, and yet I still use AVG in Windows.

Really the reason I hate Avast! is for the interface. I also hate Marmite.
Others love it.

I would suggest that a cluttered or arcane interface is counter-productive
in security software, but Avast! enthusiasts don't appear to find the
interface cluttered or arcane. This suggests to me that this is rather a
left- or right- hemisphere kind of an issue, which actually I find
reassuring, variety and black pepper being the spice etc etc.

However, I won't be trying the Avast! firewall - something of whose
existence I wasn't even aware - so cannot really comment other than to say
that Kerio 2.1.5 strikes me as the pinnacle of software firewall
development, beyond which vendors - including Kerio - are merely tacking on
all kinds of unnecessary fluff. iow for all I know Kerio may not be better
than Avast! but Kerio 2.1.5 is all you need if you also practice Safe Hex.


Shane



"webster72n" wrote in message
...

Shane and KB:

Hope you don't mind me, butting in with a contributing comment of my own.
Hearing these adverse remarks about ZA makes me feel a lot better
especially
since I had to go without it, even though I paid for it.
It was giving me a heap of trouble.
I opted for Avast instead and am wondering, whether it's less effective
than
Kerio. Happen to like it a lot (Avast).
Any feedback appreciated.

Harry.


"Shane" wrote in message
...
Ignore the fact it talks of 2.1.4., it's obviously a little out-of-date.
Kerio 2.1.5 is the same but with a bugfix.


Shane


"Shane" wrote in message
...
Have a look he http://www.geocities.com/yosponge/firewall.html

I haven't even downloaded the files, let alone tested them, but this
is
referred to by a trusted site (cexx.org).


Shane


"KB" wrote in message
...
Maybe it would have been better should I have said "I
understand" rather than "Point Taken". To me it means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a lot.
Are there any other setup 'rules' I should be aware of?
I'd hate to shut off ZA (which has provided good security,
despite the lock ups) to instead install an application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing
*List of ports* rather
than *Any port* in the Port Type field and typing the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with those you
make in the same
way as with Zone Alarm, eg allow or deny Windows Media
Player, Outlook
Express etc etc as they try to access the 'net should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.

"roman modic" wrote in message
...
Hello,

"Shane" wrote in message
...
I figured I ought to look at the 4.1.x series. Once it's configured it's
fine (on XP). I guess I'm still using it for two reasons, that there's
seemingly no reason not to, and to keep abreast of the latest build (now
4.1.3). It doesn't interfere with my drinking - though I had managed not
to
touch a drop today until you brought the subject up!

BTW, there is 4.2 in beta, which will not support ME/9x anymore.
http://www.kerio.com/beta_section.html#kpf
http://www.kerio.com/beta_kpf_history.html


Okay. Thanks. Doesn't surprise me that 9x support will be absent, but I
don't suppose it matters while they still provide the 2.1.5 download.

Shane

Hello,

"Shane" wrote in message
...
I figured I ought to look at the 4.1.x series. Once it's configured it's
fine (on XP). I guess I'm still using it for two reasons, that there's
seemingly no reason not to, and to keep abreast of the latest build (now
4.1.3). It doesn't interfere with my drinking - though I had managed not
to
touch a drop today until you brought the subject up!

BTW, there is 4.2 in beta, which will not support ME/9x anymore.
http://www.kerio.com/beta_section.html#kpf
http://www.kerio.com/beta_kpf_history.html

Cheers, Roman

Thank you for the feedback, Shane.
I thought of Kerio as an Antivirus program, but you mention firewall.
Which is it or does it cover both?
My firewall is Sygate.

Harry.


"Shane" wrote in message
...
Harry,

I quit ZA, other than for occassional testing of new builds, about 3 years
ago now. Every subsequent build I've tested has been at best a pita and I
doubt I'll ever even test it again, let alone run it permanently. I used
to
swear by it and now I swear at it.

As for Avast!, I tried their AV and hated it. While their DOS version
performed poorly in my tests, that is a trivial reason as AVG's DOS
component did too, and yet I still use AVG in Windows.

Really the reason I hate Avast! is for the interface. I also hate Marmite.
Others love it.

I would suggest that a cluttered or arcane interface is counter-productive
in security software, but Avast! enthusiasts don't appear to find the
interface cluttered or arcane. This suggests to me that this is rather a
left- or right- hemisphere kind of an issue, which actually I find
reassuring, variety and black pepper being the spice etc etc.

However, I won't be trying the Avast! firewall - something of whose
existence I wasn't even aware - so cannot really comment other than to say
that Kerio 2.1.5 strikes me as the pinnacle of software firewall
development, beyond which vendors - including Kerio - are merely tacking
on
all kinds of unnecessary fluff. iow for all I know Kerio may not be better
than Avast! but Kerio 2.1.5 is all you need if you also practice Safe Hex.


Shane



"webster72n" wrote in message
...

Shane and KB:

Hope you don't mind me, butting in with a contributing comment of my
own.
Hearing these adverse remarks about ZA makes me feel a lot better
especially
since I had to go without it, even though I paid for it.
It was giving me a heap of trouble.
I opted for Avast instead and am wondering, whether it's less effective
than
Kerio. Happen to like it a lot (Avast).
Any feedback appreciated.

Harry.


"Shane" wrote in message
...
Ignore the fact it talks of 2.1.4., it's obviously a little
out-of-date.
Kerio 2.1.5 is the same but with a bugfix.


Shane


"Shane" wrote in message
...
Have a look he http://www.geocities.com/yosponge/firewall.html

I haven't even downloaded the files, let alone tested them, but this
is
referred to by a trusted site (cexx.org).


Shane


"KB" wrote in message
...
Maybe it would have been better should I have said "I
understand" rather than "Point Taken". To me it means the
same, although to others it doesn't.

nous? What's that mean?

Great detailed setup instructions, Shane. Thanks a lot.
Are there any other setup 'rules' I should be aware of?
I'd hate to shut off ZA (which has provided good security,
despite the lock ups) to instead install an application
that lets my system get compromised, especially
considering I'm no longer using dial up.

It's reassuring to hear that I'm not the only one who's
had difficulties with ZA on ME. Every time I have a
lockup or problem, shut off ZA is the first course of
action, for me.

I'll let you know how things turn out.

Thanks again!

KB

I do appreciate the feedback.
-----Original Message-----

"KB" wrote in message
...
Point taken, Shane. Noel bailed me out nearly a year
ago
so not only do I enjoy his posts but respect his
guidance. It's one of those things.

No point intended bar to reinforce the affirmative I'm
sure you'll get from
Noel.


ZA really fights with a lot of things. I'll give 2.1.5
a
whirl (by itself of course) and see how it works.

I think all us Kerio users here probably began with Zone
Alarm and finally
migrated following it's seemingly endless
incompatibilities with Win ME.
However, Kerio 2.1.5 does require a shade more nous than
ZA for closing
certain ports via custom rules.

For instance, to block port 135:

R-click tray icon, choose Administration/Advanced/New

Set or type the following in the appropriate fields:

Description: eg, Block 135
Protocol: TCP and UDP
Direction: Incoming

(Local Endpoint)
Port Type: Single Port
Application: Any
Port Number: 135

(Remote Endpoint)
Address Type: Any address
Port Type: Any Port

Rule Valid: Always
Action: Deny

Do the same for TCP ports 1024 through 1030, choosing
*List of ports* rather
than *Any port* in the Port Type field and typing the
numbers seperated by
commas, eg 1024,1025,1026 etc.

Also block attempts by System or ICMP, Incoming or
Outgoing.

Otherwise the rules it installs with along with those you
make in the same
way as with Zone Alarm, eg allow or deny Windows Media
Player, Outlook
Express etc etc as they try to access the 'net should be
adequate.


Thanks for the feedback, Shane.

NP.

Shane


.