ZoneAlarm Internet Security Suite 6.0

[Guest]

Did Anyone have any problem using MSAS beta 1 alongside
ZoneAlarm Internet Security Suite 6.0

 

[plun]

Hi

Some reports about problem with MSAS and Zone Alarms firewall.
MSAS must be manually opended according these reports.

GIANTAntiSpywareMain.exe:2600 TCP .205.147:3194 216.32.240.29:80 ESTABLISHED
GIANTAntiSpywareMain.exe:2600 TCP .205.147:3196 207.46.236.25:80 ESTABLISHED
GIANTAntiSpywareMain.exe:2600 UDP 127.0.0.1:3195 *:*

 

[Guest]

do you know how good is the antivirus on zonealarm? i
heard that it's not as good as mcafee and norton.

 

[Alpha]

The antivirus module bundled with ZoneAlarm is from Computer Associates,
which is EZTrust AntiVirus, at 32-bit~~


| do you know how good is the antivirus on zonealarm? i
| heard that it's not as good as mcafee and norton.
|
| >-----Original Message-----
| >Hi
| >
| >Some reports about problem with MSAS and Zone Alarms
| firewall.
| >MSAS must be manually opended according these reports.
| >
| >GIANTAntiSpywareMain.exe:2600 TCP .205.147:3194
| 216.32.240.29:80 ESTABLISHED
| >GIANTAntiSpywareMain.exe:2600 TCP .205.147:3196
| 207.46.236.25:80 ESTABLISHED
| >GIANTAntiSpywareMain.exe:2600 UDP 127.0.0.1:3195
| *:*
| >
| >--
| >plun
| >
| >
| >[email protected] wrote on 2005-08-18 :
| >> Did Anyone have any problem using MSAS beta 1
| alongside
| >> ZoneAlarm Internet Security Suite 6.0
| >
| >
| >.
| >

 

[Rob]

Yes I did.
Every time I tried to update MSAS definitions it gave me a "Could not connect to the
internet" message.

When I remembered that the only thing I'd done recently was upgrade ZA to V6 I checked and
discovered
that it reset my Allow/Block programs list and blocked MSAS (along with a few others).

I went to the ZA forum and found that they have a (big) problem with the new version. I
was "lucky" that I use ZA free as it appears as though the corruption of my settings is a
small item in comparison to what the users of the paid version are experiencing (less
features-less to go awry(?)).

The header at the forum;
http://forums.zonelabs.com/zonelabs
pretty well says it all, but if you scroll through the "Installation, uninstall and
upgrade" section you'll see what I mean.

Kind of disappointing in that I've used ZA for quite a while and never had any problems.

 

[dreamweaver]

As a matter of fact, I did, too.

I don't know if my problem is a direct result of using ZA
6.0, but it is definately suspect, since in their new
version, ZA incorporated their own form of anti-spyware
protection, which may have some sort of conflict with
MSAS.

Everytime I tried to open MSAS beta after installing, I
got "Warning: Microsoft Windows AntiSpyware has
encountered a critical error (Error 101). Please restart
Windows AntiSpyware and run the program again."...
I did, and same error. I've upgraded ZA to ver.6.0
first, a while ago, then installed MSAS tonight, and then
got this error.

Any suggestions on fixing this anyone? MSAS seems like a
good program, and I'd like to try it out. Shame if it
doesn't work because of this all.

 

[Rob]

I think if you search this (and the other MSAS groups) for "Error 101" you'll see that
it's a "common" error although I did not see a definitive solution (may have missed it).
In my case (corrupted settings), once I reset ZA to allow MSAS everything returned to
normal.

 

[Rob]

"dreamweaver"
Right after I posted my message to you I decided to look at the Help function in MSAS (if
all else fails...).

They have a section on the error you are encountering (search on "error 101" - brings the
"Release notes" then scroll through the notes).

HTH

 

[dreamweaver]

Thanks much for your help, Rob. I looked in the Release
Notes section like you said, and they just said to try
either updating, or reinstalling MSAS from Add/Remove
Programs. I tried that, and same error. I'm not sure how
you reset ZA to allow MSAS for sure, but I just went in
to my <Program Control> --> <Programs> area of ZA, and
set anything Microsoft Antispyware to allow internet
access, even as trusted zone. I don't think this program
should need to act as a server to allow access, but maybe
I'm wrong. I don't know. Still didn't work, anyway, with
these changes. Same error. Either something else is
messed up on my system, or there is a compatibility
issue. Microsoft states in the Release Notes:
"* You do not need to uninstall other anti-spyware or
antivirus programs to run Microsoft Windows AntiSpyware.
Other programs or Windows AntiSpyware may prompt you to
allow or block an action, but there are no other known
incompatibilities with other anti-spyware or antivirus
programs."
Maybe this is the first one for incompatibility, for ZA6,
or it could just be firewall issues. I use a router, too
(I'm on the direct link side), but seems to me that
shouldn't be an issue, unless there's some internet link
that tries to occur right when it loads up, which gets
intercepted somehow. I see the splash screen, then about
4 seconds later on my 3.0 GHz machine, I get the error.
Oh well. Any suggestions? Thanks.

Dreamweaver.

-----Original Message-----
"dreamweaver"
Right after I posted my message to you I decided to look

at the Help function in MSAS (if

all else fails...).

They have a section on the error you are encountering

(search on "error 101" - brings the

 

[Rob]

Boy, now I'm in over my head!
(FWIW, I'm on a router as well)

My Program Control shows four MSAS items;
MSAS (abbr) "Main", "Service User Interface", "Software Updater" and "Updater".
I set all to "Ask" (Server access is blocked).
Tried the update function and got a hit for "Main" asking for Internet access (so that's
the one that was causing me the problem).

I'm at a loss to advise beyond that.

I would add that, besides my original recommendation to search the MSAS groups, I'd
suggest you post another message with an "Error 101" subject.
(You may want to include your OS as well.)

Good Luck!
--
Regards;
Rob
------------------------------------------------------------------------

Thanks much for your help, Rob. I looked in the Release
Notes section like you said, and they just said to try
either updating, or reinstalling MSAS from Add/Remove
Programs. I tried that, and same error. I'm not sure how
you reset ZA to allow MSAS for sure, but I just went in
to my <Program Control> --> <Programs> area of ZA, and
set anything Microsoft Antispyware to allow internet
access, even as trusted zone. I don't think this program
should need to act as a server to allow access, but maybe
I'm wrong. I don't know. Still didn't work, anyway, with
these changes. Same error. Either something else is
messed up on my system, or there is a compatibility
issue. Microsoft states in the Release Notes:
"* You do not need to uninstall other anti-spyware or
antivirus programs to run Microsoft Windows AntiSpyware.
Other programs or Windows AntiSpyware may prompt you to
allow or block an action, but there are no other known
incompatibilities with other anti-spyware or antivirus
programs."
Maybe this is the first one for incompatibility, for ZA6,
or it could just be firewall issues. I use a router, too
(I'm on the direct link side), but seems to me that
shouldn't be an issue, unless there's some internet link
that tries to occur right when it loads up, which gets
intercepted somehow. I see the splash screen, then about
4 seconds later on my 3.0 GHz machine, I get the error.
Oh well. Any suggestions? Thanks.

Dreamweaver.

-----Original Message-----
"dreamweaver"
Right after I posted my message to you I decided to look

at the Help function in MSAS (if

all else fails...).

They have a section on the error you are encountering

(search on "error 101" - brings the

 

[Bill Sanderson]

I think it is unlikely that the error 101 message is related to an app
compatibility issue.

I don't have a solution to this one that I know works in all situations.
This is what I have cut and pasted, from Steve Dodson of Microsoft:
---------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.
---------------------------------

However, other regulars here tell me this one doesn't work, and that there's
a third party forum "recipe" which is superior. plun recommends reading all
messages in the thread at this URL, and using the methods found therein:

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html


I'd be happy to hear what works!
--

Thanks much for your help, Rob. I looked in the Release
Notes section like you said, and they just said to try
either updating, or reinstalling MSAS from Add/Remove
Programs. I tried that, and same error. I'm not sure how
you reset ZA to allow MSAS for sure, but I just went in
to my <Program Control> --> <Programs> area of ZA, and
set anything Microsoft Antispyware to allow internet
access, even as trusted zone. I don't think this program
should need to act as a server to allow access, but maybe
I'm wrong. I don't know. Still didn't work, anyway, with
these changes. Same error. Either something else is
messed up on my system, or there is a compatibility
issue. Microsoft states in the Release Notes:
"* You do not need to uninstall other anti-spyware or
antivirus programs to run Microsoft Windows AntiSpyware.
Other programs or Windows AntiSpyware may prompt you to
allow or block an action, but there are no other known
incompatibilities with other anti-spyware or antivirus
programs."
Maybe this is the first one for incompatibility, for ZA6,
or it could just be firewall issues. I use a router, too
(I'm on the direct link side), but seems to me that
shouldn't be an issue, unless there's some internet link
that tries to occur right when it loads up, which gets
intercepted somehow. I see the splash screen, then about
4 seconds later on my 3.0 GHz machine, I get the error.
Oh well. Any suggestions? Thanks.

Dreamweaver.

-----Original Message-----
"dreamweaver"
Right after I posted my message to you I decided to look

at the Help function in MSAS (if

all else fails...).

They have a section on the error you are encountering

(search on "error 101" - brings the

 

[Dreamweaver]

Hi again,
Thanks for the info and link. I decided to go right to
the link, and try what was there first, since it sounded
like that was the better deal. I tried it and YES, I WAS
able to get it to work. So MSAS is indeed working great
for me as of now. I just needed to run two other related
EXEs in the same folder first before the main program
each time after I boot to thus get the main program to
load, upon clicking its EXE, but otherwise, running good.
I ran the scan, and it found a bunch of spyware on my XP
system. Not too much, but enough for which a good clean
was in order to help keep things running smoothly.
Doesn't seem to be any further compatibility issues
between ZA6 and MSAS for right now. When MSAS was doing
it's cleaning, ZA6 prompted me if I was sure I wanted to
allow MSAS to do what it was doing, and I confirmed, so
it seems the two get along okay for now.
Thanks a bunch! )


For those others who are reading this post who also have
trouble with ZA6 and MSAS with an error 101 upon
attempting to run the program, I've copied the info from
the link that was given, and pasted here below.....

**************************************

1. Click Start-->run--> type in->C:\WINDOWS\system32
\svchost -k DcomLaunch <enter>
2. Go into Task Manager and kill the gcasServ.exe task ,
and also kill gcasdtserv.exe (if running - probably not)

3. Now open a DOS command prompt by clicking:
Start-->Run-->type "cmd" (no quotes) and hit enter.

For Microsoft AntiSpyware, you must navigate to the
C:\Program Files\Microsoft Antispyware\ directory by
typing the following:
cd C:\Program Files\Microsoft Antispyware\ <enter>

For Giant AntiSpyware, you must navigate to the
C:\Program Files\GIANT Company Software\GIANT
AntiSpyware\ directory by typing the following:
cd C:\Program Files\GIANT Company Software\GIANT
AntiSpyware\ <enter>

Then for both Giant and Microsft AntiSpyware type the
following three commands, one at a time, and hit <enter>
after each one:

gcasdtserv.exe <Enter>
gcasServ.exe <Enter>
GiantAntiSpywareMain.exe <Enter>

Now you should be up and running.


**************************************

In summary:
Just run the 3 exe files, one at a time, related to MSAS:
gcasdtserv.exe, then gcasServ.exe, then finally the main
program GiantAntiSpywareMain.exe. The program should
actually begin to load upon running the second file. The
third one is just the GUI, or something like that.
It seems you also can do this not even in the command
prompt, but through Windows Explorer/My Computer (at
least this worked for me). Just navigate to the directory
of the program, and click each of the 3 program EXEs
(listed above) in turn to open up. The shortcut placed on
my desktop, which I was using to open the program, and
got the error, was just to the final 3rd program. But
seems the other 2 still need to be run first. I still get
the error if I still try to open up the main program
first, but the running the other programs first seems to
fix it. Perhaps Microsoft might fix this in a later
release.

Thanks again for your help, and hope I was able to help
some anyone else who might have this same problem.


-- Dreamweaver --

***************************************

 

[Bill Sanderson]

Terrific--glad it worked, and glad you were able to get cleaned up.
That mirrors my experience when for awhile, I ran a Norton antispyware
product and Microsoft Antispyware at the same time--I got prompts from both
products for things, but they didn't interfere or counteract each other.

--