Need firewall advice---from the people who use them

[jerry.mahoney]

I use Windows 2000 Pro. I already have AVG Antivirus and Ad-Aware SE. I
use them regularly and keep them updated. I've was told that I need a
firewall (that I cannot afford) so I went looking for freeware.

Try this.

http://www.jetico.com/jpfirewall.htm

 

[ms]

Message-ID<[email protected]>:

snip

Hello Ron:
You seem to be very familiar with Kerio 2.1.5 which I use. This has been a very
informative thread.

I'm having a lot of trouble getting an answer elsewhere, can't seem to post to a
forum, etc. Maybe you have some advice.

On a previous install, this did not occur.
On a recent install, at each daily cold boot, I see the screen: "Opened
Connections at localhost"

This is a screen that in the past I selected for information, but I don't want it
to start automatically when Kerio starts with windows.

How to disable this at startup, just the normal enable when desired?

BTW, I lost many clips and will probably go to a google search, you gave me
several good replies that are gone.

Thanks,

Mike Sa

 

[Ron May]

snip

Hello Ron:
You seem to be very familiar with Kerio 2.1.5 which I use. This has been a very
informative thread.

I'm having a lot of trouble getting an answer elsewhere, can't seem to post to a
forum, etc. Maybe you have some advice.

On a previous install, this did not occur.
On a recent install, at each daily cold boot, I see the screen: "Opened
Connections at localhost"

This is a screen that in the past I selected for information, but I don't want it
to start automatically when Kerio starts with windows.

How to disable this at startup, just the normal enable when desired?

BTW, I lost many clips and will probably go to a google search, you gave me
several good replies that are gone.

Yeah, I saw your posts in the other thread, but I didn't have any help
to offer. Sorry!

I get the purple and white logo splash screen at startup, which is
only on for a second or so. I saw the suggestion about disabl;ing the
screen, but I don't reboot very often, so there's no real advantage to
me in doing it.

When I pull up the "About" screen from the tray icon, I get:

Firewall Engine version: 2.1.5
Created: 30/Apr/2003 15:43:32
Driver version: 3.0.0
Created: 15/Apr/2002 11:28:32
© 2001-2002 Kerio Technologies
All rights reserved.
www.kerio.com

The "Opened Connections at Localhost" window ONLY comes up on demand
when I call for Firewall status.

On my system, a RegSeeker search on "kerio" didn't turn up any keys
that looked promising. I didn't try "persfw" or "pfwadmin" as a
search string, so that may be worth a look to see if you can find one
of those connected to the window title or "Firewall status." I didn't
find a Kerio folder in "Application Data." I couldn't find an *.ini
file in windows or it's subfolders that offered any clue.

My GUESS (and it's ONLY a guess) is that if a search of YOUR system
gets similar results, the problem COULD be in either of the two *.conf
files in the program folder. If that's the case (and I don't know
that it is) A complete uninstall/reinstall, including deleting the
program folder and the *.conf files, could be a royal PITA to go
through, but it's something to keep in mind as a last resort.

Sorry I couldn't be of more help.

 

[ms]

The "Opened Connections at Localhost" window ONLY comes up on demand
when I call for Firewall status.

On my system, a RegSeeker search on "kerio" didn't turn up any keys
that looked promising. I didn't try "persfw" or "pfwadmin" as a
search string, so that may be worth a look to see if you can find one
of those connected to the window title or "Firewall status." I didn't
find a Kerio folder in "Application Data." I couldn't find an *.ini
file in windows or it's subfolders that offered any clue.

My GUESS (and it's ONLY a guess) is that if a search of YOUR system
gets similar results, the problem COULD be in either of the two *.conf
files in the program folder. If that's the case (and I don't know
that it is) A complete uninstall/reinstall, including deleting the
program folder and the *.conf files, could be a royal PITA to go
through, but it's something to keep in mind as a last resort.

Sorry I couldn't be of more help.

Thanks, Ron.

You were on the right track.

In another thread, it was fixed due to Pfwadmin, sure enough.

Mike Sa

 

[Ron May]

Thanks, Ron.

You were on the right track.

In another thread, it was fixed due to Pfwadmin, sure enough.

Mike Sa

Glad to hear you got it fixed!