Re: Firewall grayed out in xp after gpupdate /force

Tech-Archive recommends: Fix windows errors by optimizing your registry



When the laptop is connected to the domain I am able to turn the firewall on
and off. When it is not connected to the domain the on or off option is
greayed out

"kj" wrote:

Magnetoram wrote:
Thanks, I will try next time the client comes in the office


If this is a laptop then be aware there are two different policies. Domain
and Standard Profiles for the Windows Firewall. I think Dave posted some
troublshooting for NLA and Windows Firewall a while back.


"kj" wrote:

Magnetoram wrote:
I turned it off with GP. I can turn the fw on and off on some of the
machines but not on the one I mentioned. It is grayed out

It is still under control of group policy then. try another gpudate
/force. Then check for event log entries about group policy failures.


"kj" wrote:

Magnetoram wrote:
Thanks for the post. I did disable it using GP. I am not sure what
you mean

Maybe I don't know what you mean either.

If you enable the firewall settings in a Group Policy Object and
then "enable" that policy to be applied to computers, then the
firewall settings will be forced ON and you will not be able to
disable it using the workstation GUI. (Greyed out)

If you disable the firewall settings in a Group Policy Object and
then "enable" that policy to be applied to computers, then the
firewall settings will be forced OFF and you will not be able to
enable it using the workstation GUI. (Greyed out)

There is no middle ground regarding group policy. It's ON or OFF or
"not defined". If it's "not defined" then an Administrator of the
computer can set it on or off at their discretion and it;s not
under the control of Group Policy. (Not Greyed out)

Perhaps clarify which of the above matchs your situation.


"kj" wrote:

Lanwench [MVP - Exchange] wrote:
Magnetoram <Magnetoram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have disabled the firewall using group policy and gpupdate
/force One machine when not connected to the domain has the
firewall enabled and is grayed out so I cannot disable it. I
updated the group policy and disabled the firewall while
connected to the domain. I need to be able to enable and
disable while the client is using certain software.

In addition to KJ's excellent advice - don't disable it for
software; set exceptions as needed (either locally or via GPO).

Any software
that insists you disable your firewall is software to avoid.

Truer words were (almost) never (written) spoken Lanwench.
--
/kj

--
/kj

--
/kj

--
/kj



.



Relevant Pages

  • Re: Printer not visible
    ... I assume that ICF is Internet Connection Firewall. ... the firewall on the laptop because it was controlled by group policy. ... I really do need to figure out how to control group policy. ... Please complete a re-registration process by entering the secure code mmpng06 when prompted. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 & Win2K DC
    ... 872769 You cannot configure Windows Firewall settings or Security Center ... | why a change I made to Group Policy (using gpupdate /force after the ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall grayed out in xp after gpupdate /force
    ... It's at the same hierarchical level as the Domain Profile in the Group ... Domain and Standard Profiles for the Windows Firewall. ... If you enable the firewall settings in a Group Policy Object ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall grayed out in xp after gpupdate /force
    ... Then check the GPO settings for the Standard Profile policies. ... Domain and Standard Profiles for the Windows Firewall. ... It is still under control of group policy then. ... If you enable the firewall settings in a Group Policy Object ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall grayed out in xp after gpupdate /force
    ... machines but not on the one I mentioned. ... Then check for event log entries about group policy failures. ... If you enable the firewall settings in a Group Policy Object and then ...
    (microsoft.public.windows.server.sbs)