Re: Norton Personal Firewall 2003

From: Alsvik Ture (ture@alsvik.dk)
Date: 12/09/02


From: "Alsvik Ture" <ture@alsvik.dk>
Date: Mon, 9 Dec 2002 16:05:43 +0100

Thank you for your interest and replies!

First, i know i said server - but that is just the role it has on my
nertwork, it is a normal w2k pro os.
I tried with the w2k server but it just wasn't able to run the programs i
needed. Like NPF - it doesn't support server os's. I would have to buy a
Corp. Edition and it was just way to expensive.

Regarding the uninstall's and reinstall i - offcourse - used the control
panels add/remove function, used the tool from Symantec to remove it
entirely and then removed all entries in regedit with words: "Symantec" and
"Norton". So my system was totally free from symantec products and registry
entries.

I don't think that NPF2003 is lesser of a firewall than NPF2002, it just
doesn't fit to my kind of use.
Before i felt safe nowing it would block scan attempts and that it would
also filter out traffic to the other computers on the network. That is not
the case now, and i guess i will have to find a different solution.
I'm not interested in having both NPF and NAV on all my machines because it
tends to slow them down. So i'm using nav on all machines, but i'm only
interested in having one machine act as a firewall.

Most firewalls do not have port scan detection - and i don't know if it is
necessary, but i feel more safe with that feature. I guess i have a lot of
confidence in grc.com's advice about that being the most often used reason
for an intruder/hacker to select your machine as a target!

Often a computer is selected because it's a challenge to the hacker/cracker,
or because it just announcing it self to much. But most "scriptkiddies" and
"home-hackers" just do a port scan on a ip-range within a well-known ISP,
that provides dsl or cable connections.

I still haven't heard from Symantec :o(

Ture A.

"David" <davidwnh@adelphia.net> wrote in message
news:PUZI9.4569$VA5.738611@news1.news.adelphia.net...
> Keep in mind that uninstalling more often than not does not clean up after
> itself. A lot of registry entries and often settings/configuration files
and
> databases are left behind so that settings are not lost if someone is
> reinstalling due to other problems or for upgrades.
>
> > I upgraded to NPF2003/NAV2003 and everything was wrong again ( i didn't
> > upgrade, but uninstalled the prog's and installed the new ones.) No port
>
> As these posts go on you are including new information. You are now saying
> server. I should have picked that up when you mentioned running so many
> services. Are you running Win2K server? Over time I have seen Symantec's
> workstation products become less and less compatible with Server OS's.
This
> may be the whole problem. I have seen one other poster here and a couple
> elsewhere who were having problems getting their rules to work in NPF2003
on
> a server. Maybe incompatibility with your OS is the problem? Although much
> of the underlying code is the same there are some crutial differences
> between server and workstation os's that could severely hinder a firewall
> that isn't designed and tested with a server OS. I wouldn't doubt that
this
> is your rules problem.
> > I have a ghost of the server with NPF2002/NAV2002 and i applied the
image
> > and rebooted. And NPF2002 would detect any scans and allow the
p2p-traffic
>
>
>
>



Relevant Pages

  • Re: CEICW fails at firewall config
    ... Do you or do you not have ISA 2000 or ISA 2004 installed on the SBS server? ... Do you have 2 NICs in the SBS? ... CEICW fails on firewall configuration every time. ... >>> Call to Creating the protected networks access rule returned ok. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 Firewall Question
    ... Basic firewall checkmarked). ... directly to a router port to "remote" into the server, ... I don't use Symantec AV, ...
    (microsoft.public.windows.server.sbs)
  • Re: Recycler security issues on IIS server
    ... > latest upates to the server. ... > like to see the server put behind our firewall, ... other software, install all patches, IISlockdown, URLscan, use the correct ... the procedures you follow may vary depending on your security needs. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Clients unable to access secure websites
    ... Also, double-check for firewall issues - for example, could the non-working machines have a 3rd party firewall like zone alarm or something that's packaged with the AV? ... In trying to research this, firewall seems to be a primary cause of TLS failures. ... > Installed an SBS 2003 R2 server in a company with a mixture of new and> all ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 PCs not visible in net view or network browsing - Why?
    ... >> And they all specify the same WINS server? ... > unixoid dedicated machine serving as firewall.. ... >> Between the working machines ... >> Domain Master Browser. ...
    (microsoft.public.win2000.networking)