Here's the scenario: high School with approximately 400 laptops. Windows 2008 R2 handling DHCP, Meru WAPs. We ghost the laptops with an image we use on all the laptops.
If you hand me a freshly ghosted laptop, I successfully login to the domain (scripts are processed, etc). This would seem to indicate a successful connection to the network and a good IP addy. Shortly after having a "working desktop (no more hourglass)", the spinning network icon shows up in the tray, and I am left with "Limited or No Connectivity" with the 169 IP addy.
rebooting the laptop, sometimes you connect successfully, other times, you get the No Connectivity thing. We have two batches of laptops, some older ones run XP, the newer runs run Win 7. this behavior shows up with both. the randomness of success and failure is bizarre.
We have overlapping WAPs, if that is an issue, even though they all send out the same SSID. So as you go down the hall WAP1 might have the strongest signal, but you can still pick up WAP2. I would imagine WAP1 would answer your request for a connection.
The server is set to offer 10.10.8.1 through 10.10.10.254 for IP addresses, so this seems like I have plenty of IPs available. Checking DHCP, I see 527 IPs have been handed out (IPhones and the like), so still plenty available.
I am at a bit of a loss here. Where would you look next?