03-09-2016 10:52 AM - edited 03-10-2019 11:33 PM
I have a WLC that has two identical ACS 5.5 used as RADIUS for authentication. The primary works fine without any issues. The secondary (relative to the WLC) is having authentication issues. There is no path issue between the WLC and the two ACSs. I do see that the secondary has not kept synchronization with the NTP clock. I see documents where this can be an issue with machine authentication but none that address user authentication. Can anyone provide information about whether this can be an issue and the documentation to support. Users are using PEAP (no certificate) to authenticate. The time difference is ~ 4 minutes in drift at this time.
03-09-2016 11:14 AM
If ACS is configured to use AD as the back-end user database, the maximum clock drift allowed is five minutes. This would affect both machine and user authentications.
What reason is ACS giving to reject the authentication attempts?
Javier Henderson
Cisco Systems
03-09-2016 11:29 AM
In my case the users are all within the Local ACS database. AD is not being used.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide