The topology is:
(2) redundant 3600 masters
(4) 3600 LMS
(1) 4600 N+1 backup LMS for any of the LMS 1-4
(408) AP-105 throughout (22) buildings
- SSID is using 802.1x authentication and we are doing both machine (computer) and user authentication.
- Active Directory servers as well as NPS are located at the core of the network where all the Aruba 3600's are located
Wireless laptop running XP boots up, authenticates as a machine (computer) and is sitting at the login prompt. Domain user logs into the laptop and authenticates and if successful gets placed in the "authenticated" role.
This all works for a period of time, maybe 2-3 weeks then for some reason the laptop can no longer authenticate as a machine (computer). Since the laptop can's authenticate it doesn't receive a DHCP address so users cannot log into the laptop either.
Customer connects the laptop into a wired network port, laptop obtains a DHCP address, user successfully logs in. Laptop can now authenticate once again on the wireless network as a machine (computer) and users can log in.
I've deployed many 802.1x authenticated networks this very same way but never run across this situation.
Hope this helps clarify the behavior we're seeing.
Thanks,
John