Re: Windows Firewall Group Policy Settings



I have heard of that happening more than a few times. If for some reason you
want to enable the Windows Firewall on your domain controllers I would be
sure to configure the standard profile to be the same as the domain profile
and then you will be covered either way. Otherwise you may want to
reconsider configuring the Windows Firewall on domain controllers and you
could disable the possibility via the Group Policy linked to the domain
controllers container. --- Steve


"Ralish" <Ralish@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:35BD3864-60F4-4C43-80EE-B4577DF79488@xxxxxxxxxxxxxxxx
>I was recently experimenting with the Windows Firewall Group Policy
>Settings
> in my test Windows 2003 Domain with a couple of Windows XP Clients, when I
> noticed something odd. The Domain Profile of the Windows Firewall Settings
> was not being applied to the DC, only the Standard Profile. Is this
> expected
> behavior? Surely the Windows Firewall Domain Profile ought to be applied
> to
> the DC? The DC is fully working and has no current system issues. Thanks
> in
> advance for all correspondence.


.



Relevant Pages

  • Windows firewall for domain controllers
    ... Controllers Policy. ... Windows Firewall: Protect all network connections - Enabled ... Allow file and printer sharing exception - Enabled ... on our two domain controllers. ...
    (microsoft.public.windows.group_policy)
  • Re: Windows firewall for domain controllers
    ... So, if the Windows Firewall on the Domain Controllers is blocking the authentication requests, you will get the symptoms your users report. ... It is quite possible that the Firewall Policy you configured for the Domain has different settings for the Standard Profile than for the Domain Profile in the Windows Firewall part of the GPO. ...
    (microsoft.public.windows.group_policy)
  • Re: Windows 2003 SP1 Firewall on Domain Controller
    ... settings instead of 'domain'. ... > Unfortunately the Windows firewall is applying the non domain policy ... > Other servers have correctly assigned network names, ... > domain controllers suffer from this. ...
    (microsoft.public.windows.server.security)
  • Windows 2003 SP1 Firewall on Domain Controller
    ... I have installed SP1 on one of our Windows 2003 domain controllers. ... Unfortunately the Windows firewall is applying the non domain policy ... Other servers have correctly assigned network names, ...
    (microsoft.public.windows.server.security)
  • Re: Temporarily disabling Windows XP Firewall while on Domain
    ... > - While the rep. is on the road or connected to his home network, ... I believe that this is really already built in to the policies that SP2 ... Domain profile is automatically invoked when the computer is ... one level above the Windows Firewall node. ...
    (microsoft.public.windowsxp.general)

Loading