Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

Immedietly after doing the last Norton Liveupdate, my firewall became
broken.

The problem is with the file IAMAPP.EXE

Upon startup, if Norton Firewall is set to "Load at Startup" then it hangs.
If Norton Firewall is set to "Load Manually", everything loads fine -- but
when Norton Firewall is manually enabled it will only work for a couple
minutes before it hangs. (Sometimes giving a "C++ Runtime Error" dialogue
box for IAMAPP.EXE)

Anyone know what the deal is here? This only started immedietly after the
last Liveupdate (which consisted of a large Norton Firewall update). The
first instance was right after Liveupdate had you reboot for changes to take
effect. Any fix, besides uninstalling and re-installing Norton Firewall --
as whats to say that it won't just do the same thing?

WinXP
Norton SystemWorks and Firewall 2002
(Norton SW and Firewall 2002 have worked flawlessly with XP for the last
couple years, up until now. "Upgrading" to Norton SW and Firewall 2004
isn't an option -- as Norton didn't hesitate to take my money for a
Liveupdate subscription for this year, using SW/Firewall 2002.)

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

After doing a couple re-installs (and redownloading updates), I believe I
found what the problem was.

(Perhaps this might help someone else later.)

Before you download and install the latest Liveupdate patch (which upgrades
Norton Firewall to v4.0.2.3), make sure that WinXP's firewall is disabled.
(Same as how Symantec advises you to turn it off before installing Norton.)

When I re-installed Norton (turning XP's firewall for the install, but
re-enabled it prior to Liveupdate patches), it led to the same problems as
having before. When I re-installed Norton (turning off XP's firewall and
keeping it disabled for patches), everything worked like it should.

Suppose re-enabling XP's firewall after doing the Liveupdates shouldn't
hurt.

Future note for myself, disable XP's firewall before doing updates.
Especially if its a "version update".

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

JasonL said in news:10a73unqnsaia68@corp.supernews.com:
> Immedietly after doing the last Norton Liveupdate, my firewall became
> broken.
>
> The problem is with the file IAMAPP.EXE
>
> Upon startup, if Norton Firewall is set to "Load at Startup" then it
> hangs. If Norton Firewall is set to "Load Manually", everything loads
> fine -- but when Norton Firewall is manually enabled it will only
> work for a couple minutes before it hangs. (Sometimes giving a "C++
> Runtime Error" dialogue box for IAMAPP.EXE)
>
> Anyone know what the deal is here? This only started immedietly
> after the last Liveupdate (which consisted of a large Norton Firewall
> update). The first instance was right after Liveupdate had you
> reboot for changes to take effect. Any fix, besides uninstalling and
> re-installing Norton Firewall -- as whats to say that it won't just
> do the same thing?
>
> WinXP
> Norton SystemWorks and Firewall 2002
> (Norton SW and Firewall 2002 have worked flawlessly with XP for the
> last couple years, up until now. "Upgrading" to Norton SW and
> Firewall 2004 isn't an option -- as Norton didn't hesitate to take my
> money for a Liveupdate subscription for this year, using SW/Firewall
> 2002.)

I have Norton Internet Security 2003. It does not have IAMAPP.EXE.
There is an IAMAPP.DLL file. This version changed to using SYMMONI.EXE
as the executable to load the program. The prior version had the
IAMAPP.EXE that you mention. I don't know if they went back to using it
in NIS2004. My 2003 version is already out of date and unsupported (but
its subscription goes until May 2005 and this may be the last version of
their product that I bother with). I suspect you have NIS2002 or
earlier and is also not supported. The subscription only covers the
signature updates. Makes me wonder if their update doesn't take into
account the components for too-old versions. Have your continually
reran LiveUpdate until it longer offers more updates? Symantec
developers don't seem to coordinate too well in organizing the hierarchy
and dependencies of their patches so you have to run LiveUpdate, it
lists a dozen updates and although all seem to download only a few get
applied, so you have to run LiveUpdate again (usually after a forced
reboot), and repeat until LiveUpdate finds no more updates.

LiveUpdate cannot update itself so you must download the newest version
from their web site. Maybe a new version will recognize the correct
component versions to download to match your old version. Eventually
their products get so screwed up that even they recommend a complete
uninstall and reinstall. Use their 'rnav' and 'rnis' removal tools
after an uninstall to thoroughly clean your system before the reinstall.

--
____________________________________________________________
*** Post replies to newsgroup. Share with others.
*** Email: domain = ".com" and append "=NEWS=" to Subject.
____________________________________________________________

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

> Future note for myself, disable XP's firewall before doing updates.
> Especially if its a "version update".

Sorry, but why exactly do you have to firewalls running? There is no
real use in doing that...

Gerald

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

Thanks for the detailed reply. Got everything working and up to date after
finding the conflict.
(XP's built-in firewall had to be disabled before installing latest update.)

Interesting about the 'LiveUpdate' upgrades though, having to d/l them from
the web site.

Now that everything is working great again, think I'll wait on that
though...

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

JasonL said in news:10a79padhu4idb@corp.supernews.com:
> After doing a couple re-installs (and redownloading updates), I
> believe I found what the problem was.
>
> (Perhaps this might help someone else later.)
>
> Before you download and install the latest Liveupdate patch (which
> upgrades Norton Firewall to v4.0.2.3), make sure that WinXP's
> firewall is disabled. (Same as how Symantec advises you to turn it
> off before installing Norton.)
>
> When I re-installed Norton (turning XP's firewall for the install, but
> re-enabled it prior to Liveupdate patches), it led to the same
> problems as having before. When I re-installed Norton (turning off
> XP's firewall and keeping it disabled for patches), everything worked
> like it should.
>
> Suppose re-enabling XP's firewall after doing the Liveupdates
> shouldn't hurt.
>
> Future note for myself, disable XP's firewall before doing updates.
> Especially if its a "version update".

Use only one firewall. Although you might be willing to manage the
rules or filtering for two firewalls, and even if they permit the same
traffic, they can and will interfere with each other. Same for
anti-virus software (unless you only use one of them as a scanning
application and never as a monitor and cleaner running in the
background).

More is not better. It is worse!


--
____________________________________________________________
*** Post replies to newsgroup. Share with others.
*** Email: domain = ".com" and append "=NEWS=" to Subject.
____________________________________________________________

Archived from groups: comp.security.firewalls (More info?)

> Use only one firewall. Although you might be willing to manage the
> rules or filtering for two firewalls, and even if they permit the same
> traffic, they can and will interfere with each other. Same for
> anti-virus software (unless you only use one of them as a scanning
> application and never as a monitor and cleaner running in the
> background).
>
> More is not better. It is worse!

Yes, I would agree that two software firewalls running on the same computer
wouldn't be a good idea. I certainly wouldn't try running two third-party
firewalls at the same time.

But, found in Symantec's Knowledge Base:
---
Windows XP Internet Connection Firewall:
Symantec recommends that the Windows XP (Home and Professional Editions)
Internet Connection Firewall (ICF) feature be disabled before installing NIS
or NPF. After the installation, the Windows XP firewall feature can be
enabled and will work with NIS and NPF.
---

Also, In another article from their knowledge base, they recommended keeping
WinXP's ICF enabled and allowing it to integrate with Norton. (?)

So, I enabled ICF...

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

I just took a look at the Liveupdate upgrades that could be downloaded from
Symantec's website. The most recent Liveupdate version is the same version
I have running now. Liveupdate is listed as one of the packages that can be
updated in Liveupdate itself. Apparently, Liveupdate must've updated
itself. (?)

Archived from groups: comp.security.firewalls (More info?)

I've also been "paranoid" that Liveupdate (for Norton 2002) would attempt to
upgrade with packages meant for 2004. The packages available for download
seems to always have a description for Norton 2002 though. I guess between
WinXP's last critical update and Norton 2002's most recent updates,
something funky caused some files to be corrupted. At least one another
person has already posted the exact same issue today. Re-installing and
then re-downloading all the updates (and going through like four reboots for
each update, LOL) seems to have fixed it though. Now the only "problem"
(not sure if it will be a problem yet) is that Windoctor is reporting that
the file "symneti.dll" is missing. This file is apparently used by a Norton
file called "SNDSrvc.exe". The other poster that posted about Norton giving
him the same exact problem as I saw today also posted about Windoctor
reporting this file missing. (He also was able to get NPF running again
after an un/re-install, but then ran Windoctor to discover this .dll being
listed as missing.) After reading his post, I ran Windoctor and got the
same exact report. Thought it might be a path issue, like the gapi32.dll
issue a while back, but the .dll is completetly gone. (Searched whole
computer, including hidden files.)

Oh well, everything "seems" to be working now anyway. :^)

Perhaps Symantec will address this .dll issue in the near future.

Thanks!

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

I had the same problem. Your problem is that Symantec detected you were
using NPF 2002 which THEY NO LONGER SUPPORT as of yesterday. I noticed that
when I disabled NPF everything worked fine including live update and getting
mail from my server. When I had symantec scan my system it told me that
they no longer support NPF2002. So I contacted symantec and informed them
that I had paid for subscriptions thru 12/02/04 and they suggested I upgrade
to NPF2004. At which point I contacted the Commonwealth Attorney's office
as Symanted sold me a service they had no intention of supporting. Last I
heard was that the Commonewealth Attorneys office was going to contact
symantec on this matter, and I've so informed Symantec in a follow up
conversation.

Meantime, as I do like the simplicity and way it integrates well with my
hardware firewall, I picked up a copy of NPF 2004, which, howerver strange
sounding, was on clearance for $24.95 at Target with a $20 upgrade rebate.

John
"JasonL" <jasolsspa@re.ms.move.n.com> wrote in message
news:10a73unqnsaia68@corp.supernews.com...
> Immedietly after doing the last Norton Liveupdate, my firewall became
> broken.
>
> The problem is with the file IAMAPP.EXE
>
> Upon startup, if Norton Firewall is set to "Load at Startup" then it
hangs.
> If Norton Firewall is set to "Load Manually", everything loads fine -- but
> when Norton Firewall is manually enabled it will only work for a couple
> minutes before it hangs. (Sometimes giving a "C++ Runtime Error" dialogue
> box for IAMAPP.EXE)
>
> Anyone know what the deal is here? This only started immedietly after the
> last Liveupdate (which consisted of a large Norton Firewall update). The
> first instance was right after Liveupdate had you reboot for changes to
take
> effect. Any fix, besides uninstalling and re-installing Norton
Firewall --
> as whats to say that it won't just do the same thing?
>
> WinXP
> Norton SystemWorks and Firewall 2002
> (Norton SW and Firewall 2002 have worked flawlessly with XP for the last
> couple years, up until now. "Upgrading" to Norton SW and Firewall 2004
> isn't an option -- as Norton didn't hesitate to take my money for a
> Liveupdate subscription for this year, using SW/Firewall 2002.)
>
>

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

"JRF" <bountyhunter@innocent.com> wrote in message
news:HHXoc.145626$f_5.37093@lakeread01...
> I had the same problem. Your problem is that Symantec detected you were
> using NPF 2002 which THEY NO LONGER SUPPORT as of yesterday. I noticed
that
> when I disabled NPF everything worked fine including live update and
getting
> mail from my server. When I had symantec scan my system it told me that
> they no longer support NPF2002. So I contacted symantec and informed them
> that I had paid for subscriptions thru 12/02/04 and they suggested I
upgrade
> to NPF2004. At which point I contacted the Commonwealth Attorney's office
> as Symanted sold me a service they had no intention of supporting. Last I
> heard was that the Commonewealth Attorneys office was going to contact
> symantec on this matter, and I've so informed Symantec in a follow up
> conversation.
>
> Meantime, as I do like the simplicity and way it integrates well with my
> hardware firewall, I picked up a copy of NPF 2004, which, howerver strange
> sounding, was on clearance for $24.95 at Target with a $20 upgrade rebate.

I've got a similar problem. I've been using NPF2003 and System Work 2003 on
a Windows 98 for the past year with no problems. Just recently renewed my
subscription and then a couple of weeks ago downloaded and installed an
update for NPF called Symantec Redirector. When computer was rebooted I got
this: "Windows Protection Error" and computer can't load SymTDI. If do a
selective startup and by-pass this or if I uninstall NPF then windows loads
and SW along with Norton Anti-Virus works fine.

I've followed directions from the Symantec site regarding
uninstalling/reinstalling to no avail. Yesterday I uninstalled everything
Symantec and then reinstalled NPF. Booted up fine. Then ran LiveUpdate and
downloaded only the Symantec Redirector. Immediately ran into the same
problem I had prior.

Currently I have both SW and NPF, minus the offending update, up and running
but NPF keeps telling me I need to download the offending update because the
new definitions can't be updated without it. In addition, Windoctor keeps
finding and repairing some missing Symantec files. Things appear to be
running OK but we'll see.

I've contacted Symantec support via email and heard back once with a very
generic response that didn't say anything that I hadn't already found on the
web site. In addition it plain and simple didn't fix anything. Haven't got
a reply to my second email. I have nearly a whole year left on my
subscription and I'm not a happy camper!!!

So, any idea how to fix this thing?

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

> I had the same problem. Your problem is that Symantec detected you were
> using NPF 2002 which THEY NO LONGER SUPPORT as of yesterday. I noticed
that
> when I disabled NPF everything worked fine including live update and
getting
> mail from my server. When I had symantec scan my system it told me that
> they no longer support NPF2002. So I contacted symantec and informed them
> that I had paid for subscriptions thru 12/02/04 and they suggested I
upgrade
> to NPF2004. At which point I contacted the Commonwealth Attorney's office
> as Symanted sold me a service they had no intention of supporting. Last I
> heard was that the Commonewealth Attorneys office was going to contact
> symantec on this matter, and I've so informed Symantec in a follow up
> conversation.
>
> Meantime, as I do like the simplicity and way it integrates well with my
> hardware firewall, I picked up a copy of NPF 2004, which, howerver strange
> sounding, was on clearance for $24.95 at Target with a $20 upgrade rebate.

Why doesn't any of that suprise me? :-)

After I ruled out malware for breaking NPF, my next cynical thought was that
Norton wasn't going to support NPF2002 -- even though I renewed my
subscription for it up until 3-18-2005! (And, as you know, when the time
came for renewal, Norton specifically asked if you wanted to renew for
NPF2002 or upgrade to 2004.)

Un/re-installing NPF and then redownloading all the Liveupdates "seemed" to
get it working again, but I'm not sure if there are going to be problems
later. Windoctor is now reporting a missing Norton .dll ("symneti.dll" )
that is required by a Norton file called "SNDSvr.exe". (At least one other
person reported the same exact thing as of two days ago.)

I'm using Norton SystemWorks 2002 and NPF 2002. When I look at the
subscription date for Norton AV, it is correctly still showing 3-18-2005,
but now NPF2002 is showing one year from the current date (i.e., today,
5-14-2005).

Likewise, I have really liked Norton up until now. It has worked flawlessly
(except for a couple small hiccups, such as the "gapi32.dll" thing a while
back, which was just a path issue) over the last couple years. I really
like how it integrates together and is, for the most part, seamless and
transparent in the background. Very easy to use and configure as well.

I was planning on getting Norton 2005 products, but, if they renege on this
2004 subscription, I'm going elsewhere. I'm going to contact them as well.

$25 bucks is nothing, but the principle of it kind of pisses me off. I
would be willing to get NPF2004 (and Systemworks 2004), however, *if* my
current paid-for subscriptions will work with it. (If I remember right, out
of the box Systemworks and NPF had only a three month subscription.)

Thanks!

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

Thats exactly the last Liveupdate that orginally broke NPF for me: "Symantec
Redirector"!

NSW/NPF 2002, with a subscription for 3-18-2005.

Likewise, I found un/re-installing "seems" to get things working again, but
Windoctor is reporting missing .dll

I'll be contacting them too!

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

> $25 bucks is nothing, but the principle of it kind of pisses me off. I
> would be willing to get NPF2004 (and Systemworks 2004), however, *if* my
> current paid-for subscriptions will work with it. (If I remember right,
out
> of the box Systemworks and NPF had only a three month subscription.)

Just went back and looked. I bought both in a shrinkwrapped retail box and
they came with one year subscriptions.
(Three months is when Norton comes pre-installed on a new computer.)

So, I'd only settle with getting "NPF 2004" for it's cost MINUS what I paid
for the subscription. All right, to be fair, at least 5/6's of the
subscription cost subtracted for "NPF 2002" (since I did get two months use
out of it).

I'd also like to say that I would get "NPF 2004" if they would waiver 2005
subscription fees, but I don't think they can be trusted with honoring
something a year later.

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

It seems after much checking, and having a friend check out the download,
Norton, When it scanned for LiveUpdates, detected I was running a version no
longer supported and deleted the following file, S32LUHL1.DLL which it seems
disabled NPF. Amazingly, now that I'm running NPF2004, everything works and
the missing .DLL is now amazingly returned to the system. I've taken my
evidence to the Commonwealth Attorney's office and they find it interesting
in the least. In the meantime, I've contacted my attorney and I'm going to
pursue Symantec in small claims court, not for the money, but for the
principle. I paid for 12 months of subscription updates, and by accepting
my money and extending my subscription until December 2, 2004, Norton
entered into a contract with me. By them no longer supporting this version,
and disabling it on my system, they have violated the terms of the contract
entered into with me.

Perhaps if everyone who's had this problem takes Symantec to small claims
court for breach of contract, they'll get the point.
"JasonL" <jasolsspa@re.ms.move.n.com> wrote in message
news:10a9t36ks42fdbb@corp.supernews.com...
> > $25 bucks is nothing, but the principle of it kind of pisses me off. I
> > would be willing to get NPF2004 (and Systemworks 2004), however, *if* my
> > current paid-for subscriptions will work with it. (If I remember right,
> out
> > of the box Systemworks and NPF had only a three month subscription.)
>
> Just went back and looked. I bought both in a shrinkwrapped retail box
and
> they came with one year subscriptions.
> (Three months is when Norton comes pre-installed on a new computer.)
>
> So, I'd only settle with getting "NPF 2004" for it's cost MINUS what I
paid
> for the subscription. All right, to be fair, at least 5/6's of the
> subscription cost subtracted for "NPF 2002" (since I did get two months
use
> out of it).
>
> I'd also like to say that I would get "NPF 2004" if they would waiver 2005
> subscription fees, but I don't think they can be trusted with honoring
> something a year later.
>
>

Archived from groups: comp.security.firewalls,microsoft.public.windowsxp.perform_maintain (More info?)

"JRF" <bountyhunter@innocent.com> wrote in message
news:7c7pc.151065$f_5.62598@lakeread01...
> It seems after much checking, and having a friend check out the download,
> Norton, When it scanned for LiveUpdates, detected I was running a version
no
> longer supported and deleted the following file, S32LUHL1.DLL which it
seems
> disabled NPF. Amazingly, now that I'm running NPF2004, everything works
and
> the missing .DLL is now amazingly returned to the system. I've taken my
> evidence to the Commonwealth Attorney's office and they find it
interesting
> in the least. In the meantime, I've contacted my attorney and I'm going
to
> pursue Symantec in small claims court, not for the money, but for the
> principle. I paid for 12 months of subscription updates, and by accepting
> my money and extending my subscription until December 2, 2004, Norton
> entered into a contract with me. By them no longer supporting this
version,
> and disabling it on my system, they have violated the terms of the
contract
> entered into with me.
>
> Perhaps if everyone who's had this problem takes Symantec to small claims
> court for breach of contract, they'll get the point.
> "JasonL" <jasolsspa@re.ms.move.n.com> wrote in message
> news:10a9t36ks42fdbb@corp.supernews.com...
> > > $25 bucks is nothing, but the principle of it kind of pisses me off.
I
> > > would be willing to get NPF2004 (and Systemworks 2004), however, *if*
my
> > > current paid-for subscriptions will work with it. (If I remember
right,
> > out
> > > of the box Systemworks and NPF had only a three month subscription.)
> >
> > Just went back and looked. I bought both in a shrinkwrapped retail box
> and
> > they came with one year subscriptions.
> > (Three months is when Norton comes pre-installed on a new computer.)
> >
> > So, I'd only settle with getting "NPF 2004" for it's cost MINUS what I
> paid
> > for the subscription. All right, to be fair, at least 5/6's of the
> > subscription cost subtracted for "NPF 2002" (since I did get two months
> use
> > out of it).
> >
> > I'd also like to say that I would get "NPF 2004" if they would waiver
2005
> > subscription fees, but I don't think they can be trusted with honoring
> > something a year later.
> >
> >

Way to go! If I can help let me know!