Wireless association after logging into windows

Because the machines don't associate with the access point and connect to
the Wireless LAN until the machine logs onto the domain, apart from other
issues login scripts don't run.



If would appreciate any comments on this.



Many thanks.

corb wrote:

>Because the machines don't associate with the access point and connect to
>the Wireless LAN until the machine logs onto the domain, apart from other
>issues login scripts don't run.
>
>
>
>If would appreciate any comments on this.
>
>
>
>Many thanks.
>
>
>
>
That is a problem with Windows. Some client utilities do address this.
Atheros' client utility has an option to make the wireless run as a
service. I believe some broadcom utilities also address this.

Thanks for the info, I will investigate.

"Jerry Park" <(E-Mail Removed)> wrote in message
news:qQDpf.12375$(E-Mail Removed).. .
> corb wrote:
>
>>Because the machines don't associate with the access point and connect to
>>the Wireless LAN until the machine logs onto the domain, apart from other
>>issues login scripts don't run.
>>
>>
>>
>>If would appreciate any comments on this.
>>
>>
>>
>>Many thanks.
>>
>>
>>
> That is a problem with Windows. Some client utilities do address this.
> Atheros' client utility has an option to make the wireless run as a
> service. I believe some broadcom utilities also address this.