Good Afternoon,

I'm running WinXPSP2 on a Windows Server 2003 (SBS) domain. I used the
servername/connectcomputer link and now the WinXP machine is connected to
the domain. It is a member of the domain.
I'd like for Windows firewall to use the domain policy instead of the
standard policy.
When I go into Windows firewall it states:
Windows Firewall is using your non-domain settings

I don't know how to make it permanently stay on domain settings. Can
someone tell me what I'm missing on this WinXPSP2 machine? It was once a
member of a workgroup and has now been switched to be a member of a domain.

Thanks!

Sincerely,
Anthony Smith
In God We Trust!

On any workstation where the firewall is showing as using the non-domain
settings, go into Services and set the Network Location Awareness service to
start automatically, and then restart the workstation or do gpupdate /force.
Setting NLA to automatic startup should fix it permanently. The issue is
that with NLA set to manual, it starts too slowly to get the firewall to use
the correct (domain) settings.

As far as I know, MS never documented this, but you'll notice that NLA is
set to automatic by default in Vista.

"Anthony Smith" <anthony@peconet.com> wrote in message
news:u2EUi0qCIHA.5980@TK2MSFTNGP04.phx.gbl...
> Good Afternoon,
>
> I'm running WinXPSP2 on a Windows Server 2003 (SBS) domain. I used the
> servername/connectcomputer link and now the WinXP machine is connected to
> the domain. It is a member of the domain.
> I'd like for Windows firewall to use the domain policy instead of the
> standard policy.
> When I go into Windows firewall it states:
> Windows Firewall is using your non-domain settings
>
> I don't know how to make it permanently stay on domain settings. Can
> someone tell me what I'm missing on this WinXPSP2 machine? It was once a
> member of a workgroup and has now been switched to be a member of a
> domain.
>
> Thanks!
>
> Sincerely,
> Anthony Smith
> In God We Trust!
>
>

Yep that fixed it Dave. Thanks for your help, have a blessed evening!
"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:ONBv4JrCIHA.3916@TK2MSFTNGP02.phx.gbl...
> On any workstation where the firewall is showing as using the non-domain
> settings, go into Services and set the Network Location Awareness service
> to start automatically, and then restart the workstation or do gpupdate
> /force. Setting NLA to automatic startup should fix it permanently. The
> issue is that with NLA set to manual, it starts too slowly to get the
> firewall to use the correct (domain) settings.
>
> As far as I know, MS never documented this, but you'll notice that NLA is
> set to automatic by default in Vista.
>
> "Anthony Smith" <anthony@peconet.com> wrote in message
> news:u2EUi0qCIHA.5980@TK2MSFTNGP04.phx.gbl...
>> Good Afternoon,
>>
>> I'm running WinXPSP2 on a Windows Server 2003 (SBS) domain. I used the
>> servername/connectcomputer link and now the WinXP machine is connected to
>> the domain. It is a member of the domain.
>> I'd like for Windows firewall to use the domain policy instead of the
>> standard policy.
>> When I go into Windows firewall it states:
>> Windows Firewall is using your non-domain settings
>>
>> I don't know how to make it permanently stay on domain settings. Can
>> someone tell me what I'm missing on this WinXPSP2 machine? It was once a
>> member of a workgroup and has now been switched to be a member of a
>> domain.
>>
>> Thanks!
>>
>> Sincerely,
>> Anthony Smith
>> In God We Trust!
>>
>>
>
>