Firewall alert keeps getting turned back on in SP2

[Ken H]

I use ZoneAlarm (4.5) which isn't detected by the
Security Center in SP2 so have turned off (unchecked) the
Firewall alerts both under "Firewall recommendations"
and "Change the way Security Center notifies me".
However every time I restart my computer I get the
Firewall alert and the boxes are checked again. Any
ideas what's going on?

Thanks.

[Torgeir Bakken \(MVP\)]

Ken H wrote:

> I use ZoneAlarm (4.5) which isn't detected by the
> Security Center in SP2 so have turned off (unchecked) the
> Firewall alerts both under "Firewall recommendations"
> and "Change the way Security Center notifies me".
> However every time I restart my computer I get the
> Firewall alert and the boxes are checked again. Any
> ideas what's going on?
>
> Thanks.
Hi

If the "Change the Way Security Center Notifies Me" doesn't stick when
you reboot, you can do the following:

To "solve" this problem, you can disable the Security Center service.


Start/Run --> services.msc

Find "Security Center" in the list, double click on it, set
"Startup type" to Disabled.


There is also a Group Policy setting available to disable the
Security Center (Start/Run--> gpedit.msc).

Take a look at the chapter for the Security Center in
06_CIF_Maintenance.DOC

What settings are added or changed in Windows XP Service Pack 2?
Group Policy settings (page 26 for me)


06_CIF_Maintenance.DOC ("Changes to Functionality in Microsoft Windows XP
Service Pack 2, Part 6: Computer Maintenance") can be downloaded from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=7bd948d7-b791-40b6-8364-685b84158c78&DisplayLang=en

Note: WinXPSP2_Documentation.zip contains all the .doc downloads...


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

[Ken H]

Thanks for your quick response. However I'd prefer to
know why the setting isn't sticking and address that
rather than working around it by turning off the whole
Security Center.

>-----Original Message-----
>Ken H wrote:
>
>> I use ZoneAlarm (4.5) which isn't detected by the
>> Security Center in SP2 so have turned off (unchecked)
the
>> Firewall alerts both under "Firewall recommendations"
>> and "Change the way Security Center notifies me".
>> However every time I restart my computer I get the
>> Firewall alert and the boxes are checked again. Any
>> ideas what's going on?
>>
>> Thanks.
>Hi
>
>If the "Change the Way Security Center Notifies Me"
doesn't stick when
>you reboot, you can do the following:
>
>To "solve" this problem, you can disable the Security
Center service.
>
>
>Start/Run --> services.msc
>
>Find "Security Center" in the list, double click on it,
set
>"Startup type" to Disabled.
>
>
>There is also a Group Policy setting available to
disable the
>Security Center (Start/Run--> gpedit.msc).
>
>Take a look at the chapter for the Security Center in
>06_CIF_Maintenance.DOC
>
> What settings are added or changed in Windows XP
Service Pack 2?
> Group Policy settings (page 26 for me)
>
>
>06_CIF_Maintenance.DOC ("Changes to Functionality in
Microsoft Windows XP
>Service Pack 2, Part 6: Computer Maintenance") can be
downloaded from here:
>
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=7bd948d7-b791-40b6-8364-
685b84158c78&DisplayLang=en
>
>Note: WinXPSP2_Documentation.zip contains all the .doc
downloads...
>
>
>--
>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn
Norway
>Administration scripting examples and an ONLINE version
of
>the 1328 page Scripting Guide:
>http://www.microsoft.com/technet/scriptcenter/default.msp
x
>.
>

[Torgeir Bakken \(MVP\)]

Ken H wrote:

> Thanks for your quick response. However I'd prefer to
> know why the setting isn't sticking and address that
> rather than working around it by turning off the whole
> Security Center.
Hi

As far as I can see, it is a bug in SP2, heaps of people have this
issue, and no one have come up with a explanation of it.

howiezows have another way to "fix" this, locking down the permissions
on the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center in
registry.

Take a look here if you still want the Security Center enabled,
and with a setting that survives a reboot:
http://groups.google.com/groups?selm=479f69ab.0409052109.46282011%40posting .google.com

I'm a bit reluctant to point to this solution to everybody that have
this problem, because locking down permissions on system files and
system registry keys very often comes back to bite you later on in
upgrade situations (and then you have long gone forgot that you did
this change or you fail to see the connection).


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

[Ken H]

You're absolutely correct about forgetting registry
tweaks later on. Think I'll either put up with the
nuisance or use your original advice.

I've got another problem which may be firewall related
which I'd like to run by you. My brother upgraded to SP2
and turned off the XP firewall because he's also got
ZoneAlarm. Before upgrading we had no problem with voice
communication using Netmeeting. (We use Netmeeting voice
because we've never been able to make Messenger voice
work through ZoneAlarm.) After the upgrade we could
connect through Netmeeting but there was a 1 minute delay
in the voice and his side kept saying "trying to
connect". So he rolled back his system to before the
upgrade. Now we can't get any voice with or without a
delay although it does say we're connected.

I was going to post this in the Netmeeting forum but
thought I'd see if you have any ideas.

Thanks again.

Ken

>-----Original Message-----
>Ken H wrote:
>
>> Thanks for your quick response. However I'd prefer to
>> know why the setting isn't sticking and address that
>> rather than working around it by turning off the whole
>> Security Center.
>Hi
>
>As far as I can see, it is a bug in SP2, heaps of people
have this
>issue, and no one have come up with a explanation of it.
>
>howiezows have another way to "fix" this, locking down
the permissions
>on the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center in
>registry.
>
>Take a look here if you still want the Security Center
enabled,
>and with a setting that survives a reboot:
>http://groups.google.com/groups?
selm=479f69ab.0409052109.46282011%40posting.google .com
>
>I'm a bit reluctant to point to this solution to
everybody that have
>this problem, because locking down permissions on system
files and
>system registry keys very often comes back to bite you
later on in
>upgrade situations (and then you have long gone forgot
that you did
>this change or you fail to see the connection).
>
>
>--
>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn
Norway
>Administration scripting examples and an ONLINE version
of
>the 1328 page Scripting Guide:
>http://www.microsoft.com/technet/scriptcenter/default.msp
x
>.
>

[Torgeir Bakken \(MVP\)]

Ken H wrote:

> You're absolutely correct about forgetting registry
> tweaks later on. Think I'll either put up with the
> nuisance or use your original advice.
>
> I've got another problem which may be firewall related
> which I'd like to run by you. My brother upgraded to SP2
> and turned off the XP firewall because he's also got
> ZoneAlarm. Before upgrading we had no problem with voice
> communication using Netmeeting. (We use Netmeeting voice
> because we've never been able to make Messenger voice
> work through ZoneAlarm.) After the upgrade we could
> connect through Netmeeting but there was a 1 minute delay
> in the voice and his side kept saying "trying to
> connect". So he rolled back his system to before the
> upgrade. Now we can't get any voice with or without a
> delay although it does say we're connected.
Hi

You might use this information to analyze what happens:

Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357

A much more detailed version:
Troubleshooting Windows Firewall in Microsoft Windows XP Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyID=a7628646-131d-4617-bf68-f0532d8db131&DisplayLang=en


More Windows Firewall links:

Description of the Windows Firewall feature in Windows XP
Service Pack 2
http://support.microsoft.com/default.aspx?kbid=843090

Understanding Windows Firewall/Introduction
http://www.microsoft.com/windowsxp/using/security/internet/sp2_wfintro.mspx

The Cable Guy - February 2004
Manually Configuring Windows Firewall in Windows XP Service Pack 2
http://www.microsoft.com/technet/community/columns/cableguy/cg0204.mspx

How to use the Security Alert dialog box in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875353


Windows XP Service Pack 2 problems/The Service Pack 2 firewall
http://www.michna.com/kb/WxSP2.htm#The_Service_Pack_2_firewall



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

Unfortunately I don't think your suggestion will help.
We have XP firewall turned off on both sides since we
both use ZoneAlarm. I've posted my problem on the
Netmeeting group and maybe someone will have an idea.

Thanks again for all your effort.


>-----Original Message-----
>Ken H wrote:
>
>> You're absolutely correct about forgetting registry
>> tweaks later on. Think I'll either put up with the
>> nuisance or use your original advice.
>>
>> I've got another problem which may be firewall related
>> which I'd like to run by you. My brother upgraded to
SP2
>> and turned off the XP firewall because he's also got
>> ZoneAlarm. Before upgrading we had no problem with
voice
>> communication using Netmeeting. (We use Netmeeting
voice
>> because we've never been able to make Messenger voice
>> work through ZoneAlarm.) After the upgrade we could
>> connect through Netmeeting but there was a 1 minute
delay
>> in the voice and his side kept saying "trying to
>> connect". So he rolled back his system to before the
>> upgrade. Now we can't get any voice with or without a
>> delay although it does say we're connected.
>Hi
>
>You might use this information to analyze what happens:
>
>Troubleshooting Windows Firewall settings in Windows XP
Service Pack 2
>http://support.microsoft.com/default.aspx?kbid=875357
>
>A much more detailed version:
>Troubleshooting Windows Firewall in Microsoft Windows XP
Service Pack 2
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=a7628646-131d-4617-bf68-
f0532d8db131&DisplayLang=en
>
>
>More Windows Firewall links:
>
>Description of the Windows Firewall feature in Windows XP
>Service Pack 2
>http://support.microsoft.com/default.aspx?kbid=843090
>
>Understanding Windows Firewall/Introduction
>http://www.microsoft.com/windowsxp/using/security/interne
t/sp2_wfintro.mspx
>
>The Cable Guy - February 2004
>Manually Configuring Windows Firewall in Windows XP
Service Pack 2
>http://www.microsoft.com/technet/community/columns/cableg
uy/cg0204.mspx
>
>How to use the Security Alert dialog box in Windows XP
Service Pack 2
>http://support.microsoft.com/default.aspx?kbid=875353
>
>
>Windows XP Service Pack 2 problems/The Service Pack 2
firewall
>http://www.michna.com/kb/WxSP2.htm#The_Service_Pack_2_fir
ewall
>
>
>
>--
>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn
Norway
>Administration scripting examples and an ONLINE version
of
>the 1328 page Scripting Guide:
>http://www.microsoft.com/technet/scriptcenter/default.msp
x
>.
>

[Nero]

The answer is easy...............
I had same problem.
Just disable/turn off windows firewall in services.
That works.

[Nero]

There will always be a delay with audio/voice in Netmeeting.
You cannot expect it to be instant.