!! Firewall incorrectly determining DOMAIN/Standard - since last WU?

[RJ]

Since XPsp2 we have been configuring the Windows Firewall via Group
Policy.

On Standard: Protect All network Connections
Do not allow exceptions
On Domain: Protect All network Connections (disabled)

So - when laptop on LAN - firewall disabled, on any other network -
firewall enabled.

This worked perfectly in tests and for as long as we can remember.

However - it now does not work - and the firewall turns off (thinks it
is in Domain) when connected to any LAN hub (even if it is the only
device on there).

Group Policy hasn't changed.

Only change we can think of is the December Windows Updates which
included a Firewall patch.

Can anyone else confirm this to be a global problem, and advise of any
solution?



PS - can confirm Group Policy Modelling shows correct settings on
laptops. This affects multiple laptops. (All did work, all now have
this XP "update")

PPS - is it me or is this worrying - as we were just about to roll out
VPN access as the laptops would firewall themselves "at home". If we
were 2 months ahead we'd have users now putting their work laptops on
their home Internet with the firewall disabling itself!

 

[Torgeir Bakken \(MVP\)]

Since XPsp2 we have been configuring the Windows Firewall via Group
Policy.

On Standard: Protect All network Connections
Do not allow exceptions
On Domain: Protect All network Connections (disabled)

So - when laptop on LAN - firewall disabled, on any other network -
firewall enabled.

This worked perfectly in tests and for as long as we can remember.

However - it now does not work - and the firewall turns off (thinks it
is in Domain) when connected to any LAN hub (even if it is the only
device on there).

Group Policy hasn't changed.

Only change we can think of is the December Windows Updates which
included a Firewall patch.

Can anyone else confirm this to be a global problem, and advise of any
solution?

Hi

If you uninstall this Firewall patch, does it start to work OK again?