Re: XP SP3 Clients don't abide by Group Policy Firewall Exceptions by docasion
docasion
Mon Sep 22 05:19:43 PDT 2008
Well, when the client is running SP2 you can go into control panel,
firewall and see the port exceptions listed there. On SP3 clients
those port exception never show up in the list. This has also just
presented intself on a new network installation of an SBS 2003 R2
server with new XP Pro clients. Straight up stock installations with
no group policy items defined other than these firewall exceptions.
Perhaps I'm defining them under the wrong section in group policy?
On Sep 20, 4:12=A0pm, "Cliff Galiher" <cgali...@gmail.com> wrote:
> How have you verified that the group policy is being ignored? =A0Have you=
run
> RSoP? =A0It is entirely possible that the firewall is set properly but th=
at
> something else has changed that is still causing communications to fail.
>
> I've upgraded literally thousands of clients to XP SP3 in SBS and enterpr=
ise
> environments and have not had them suddenly start ignoring group policies=
.
> I've had plenty break...just not in the way you describe.
>
> -Cliff
>
> "docasion" <funn...@doaks.net> wrote in message
>
> news:8d8c092f-51f9-42f5-99e4-ea0522893aaa@m73g2000hsh.googlegroups.com...
>
>
>
> > On all my SBS 2003 clients I define a group policy that opens secific
> > firewall ports for remote installation and monitoring of antivirus
> > software. =A0This worked great under XP Pro SP2 but once a computer get=
s
> > SP3 it ignored the group policy. =A0This is also on new installations a=
s
> > well.
>
> > This is under SBS Client computer >> Admin Templates >> network >>
> > network connections >> windows firewall
>
> > I enable the one to define port exceptions and set them up in the
> > following format as an example...
>
> > 4156:TCP:*:enabled:Antivirus
>
> > Any ideas on this would be great.
>
> > Thanks.- Hide quoted text -
>
> - Show quoted text -