«

We have several carts that are used as mobile computer labs. Each cart has 31
laptops, a printer, and either a Linksys wireless router or a Cisco WAP that
gets plugged into the network, and the laptops share the wireless connection.
Every once in a while, one of the laptops will lose it's access to the Domain
and we will have to remove the computers domain account and then rejoin the
machine to the Domain in order to get it to work again. Does anyone know why
this occurs and what we need to do to fix it?

samanderson123 via WindowsKB.com <u50227@uwe> wrote:
> Pete wrote:
>> We have several carts that are used as mobile computer labs. Each
>> cart has 31 laptops, a printer, and either a Linksys wireless router
>> or a Cisco WAP that gets plugged into the network, and the laptops
>> share the wireless connection. Every once in a while, one of the
>> laptops will lose it's access to the Domain and we will have to
>> remove the computers domain account and then rejoin the machine to
>> the Domain in order to get it to work again. Does anyone know why
>> this occurs and what we need to do to fix it?
>
>
> Might be problem with your user account please check it .

Hi - this isn't a user account issue; he's talking about computer accounts
in the domain.

We have the same problem also. If we connect the problem laptop onto the
wired network and reboot it, it will re-authenticate with the domain and
renew it's account so that wireless connectivety starts working again. Our
setup is Vista laptops, HP Wireless networking equipment and Windows 2003 Ad
Domain which is also providing IAS and radius authentication of the Wireless
clients.

"Pete" wrote:

> We have several carts that are used as mobile computer labs. Each cart has 31
> laptops, a printer, and either a Linksys wireless router or a Cisco WAP that
> gets plugged into the network, and the laptops share the wireless connection.
> Every once in a while, one of the laptops will lose it's access to the Domain
> and we will have to remove the computers domain account and then rejoin the
> machine to the Domain in order to get it to work again. Does anyone know why
> this occurs and what we need to do to fix it?