Wireless laptops and Group Policy

I have Win2k Pro laptops connecting to Win 2k3 server via a Netgear WG302
wireless access point. When the users logon they are not getting the Group
Policies applied and batch files are not executing. If I connect the wired
they all works ok. Can anyone tell me why and how to fix?

There was recently a long discussion about such in the
win2000.public.networking newsgroup if you want to check the posts there and
also you may want to post in the Microsoft.public.networking.wireless. What
more than likely is happening is that users are being logged on with cached
credentials and then when the network becomes available they are then being
authenticated to the domain, but too late to have initial logon Group Policy
applied to them and of course that is the only time that logon/startup
scripts will be applied. You could try to disable logging on with cached
credentials to see if that makes a difference [try one computer for a test]
.. That can be done in the appropriate security policy such as at the
domain/OU/local level. For example for Local Security Policy go to security
settings/local policies/security options and for the option number of
previous logons to cache - set to zero. However if it takes too long for the
wireless network to respond the user may get a message that they can not
logon because a domain controller can not be contacted. --- Steve



"Daniel" <(E-Mail Removed)> wrote in message
news:8B60CB19-85CC-4345-8F73-(E-Mail Removed)...
>I have Win2k Pro laptops connecting to Win 2k3 server via a Netgear WG302
> wireless access point. When the users logon they are not getting the Group
> Policies applied and batch files are not executing. If I connect the wired
> they all works ok. Can anyone tell me why and how to fix?

I now get a message saying the domain is not available, when trying to logon??

"Steven L Umbach" wrote:

> There was recently a long discussion about such in the
> win2000.public.networking newsgroup if you want to check the posts there and
> also you may want to post in the Microsoft.public.networking.wireless. What
> more than likely is happening is that users are being logged on with cached
> credentials and then when the network becomes available they are then being
> authenticated to the domain, but too late to have initial logon Group Policy
> applied to them and of course that is the only time that logon/startup
> scripts will be applied. You could try to disable logging on with cached
> credentials to see if that makes a difference [try one computer for a test]
> .. That can be done in the appropriate security policy such as at the
> domain/OU/local level. For example for Local Security Policy go to security
> settings/local policies/security options and for the option number of
> previous logons to cache - set to zero. However if it takes too long for the
> wireless network to respond the user may get a message that they can not
> logon because a domain controller can not be contacted. --- Steve
>
>
>
> "Daniel" <(E-Mail Removed)> wrote in message
> news:8B60CB19-85CC-4345-8F73-(E-Mail Removed)...
> >I have Win2k Pro laptops connecting to Win 2k3 server via a Netgear WG302
> > wireless access point. When the users logon they are not getting the Group
> > Policies applied and batch files are not executing. If I connect the wired
> > they all works ok. Can anyone tell me why and how to fix?
>
>
>

If you disabled domain cached logons and now get that error, then your
wireless network is not being enabled in time for a domain logon. Your
option would be to go back and allow cached domain logons, though you still
would not receive initial logon Group Policy. The users in the
Microsoft.public.networking.wireless newsgroup may have more words of wisdom
on this subject. --- Steve


"Daniel" <(E-Mail Removed)> wrote in message
news:A32A3C54-9C65-49BE-951C-(E-Mail Removed)...
>I now get a message saying the domain is not available, when trying to
>logon??
>
> "Steven L Umbach" wrote:
>
>> There was recently a long discussion about such in the
>> win2000.public.networking newsgroup if you want to check the posts there
>> and
>> also you may want to post in the Microsoft.public.networking.wireless.
>> What
>> more than likely is happening is that users are being logged on with
>> cached
>> credentials and then when the network becomes available they are then
>> being
>> authenticated to the domain, but too late to have initial logon Group
>> Policy
>> applied to them and of course that is the only time that logon/startup
>> scripts will be applied. You could try to disable logging on with cached
>> credentials to see if that makes a difference [try one computer for a
>> test]
>> .. That can be done in the appropriate security policy such as at the
>> domain/OU/local level. For example for Local Security Policy go to
>> security
>> settings/local policies/security options and for the option number of
>> previous logons to cache - set to zero. However if it takes too long for
>> the
>> wireless network to respond the user may get a message that they can not
>> logon because a domain controller can not be contacted. --- Steve
>>
>>
>>
>> "Daniel" <(E-Mail Removed)> wrote in message
>> news:8B60CB19-85CC-4345-8F73-(E-Mail Removed)...
>> >I have Win2k Pro laptops connecting to Win 2k3 server via a Netgear
>> >WG302
>> > wireless access point. When the users logon they are not getting the
>> > Group
>> > Policies applied and batch files are not executing. If I connect the
>> > wired
>> > they all works ok. Can anyone tell me why and how to fix?
>>
>>
>>