In news:1E1B229D-7505-4D2C-9794-(E-Mail Removed),
ThatsIT.net.au <me@work> typed:
> I have done so,
> it either says that if could not find DC and gives a red error icon
> or it gives a yellow warning icon saying that it needs to reboot in
> order to appy software installations, but never seems to do so
>
There maybe one or two issues going on. If the wireless are using the
incorrect DNS addresses such as mixing them with ISP's DNS IP addresses, it
would never be able to 'find' the DC(s).You haven't posted any configuration
information, but just to remind you, the cardinal rule is to only use the
internal DNS on all AD members and servers. Configure forwarding on your
internal DNS servers to the ISP's. Otherwise, if using the ISP's in ip
properties, expect problems.
If everything is configured correctly, then I would look at the speed of the
wireless connection. If weak, the GPOs may not apply. By default, everything
expect security and password policies will not apply under 500k.
For better assistance to get to the root of it, please supply the following
information:
1. Unedited "ipconfig /all" of one of your DCs and of a wireless laptop.
2. AD DNS domain name.
3. What type of wireless AP are you using? How is it giving the clients
their IP addresses?
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
Infinite Diversities in Infinite Combinations