02-13-2013 12:30 AM - edited 03-10-2019 08:05 PM
Hi all experts.
I recently have experienced this issue.
I have been using ISE1.1.2.145 and joined to AD since the ISE was released, but never seen this error before.
I did not touch any configuration and I was trying to test CWA with multiple WLCs.
I finished all configuration about CWA, and I was verifing if it is working.
while I was trying to login as user on AD, I could not. so I looked up on External Identity Source and it apears.
does anyone know why it is giving me that error ?
the ISE and AD both see the same NTP and time difference between them is only 1 minute, timezone is same.
even though they are looking at the same NTP, it's outside of private network and it is isolated.
also, I am able to ping each other. DNS is working. I don't see why it is not working......
can anyone help me with this problem ?
02-14-2013 07:31 PM
NTP and timezones are very important for ISE. If both the AD and ISE are using the same NTP server then they should not be any variance between the two clocks. Can you:
1. Run "show ntp" from CLI and see if the association with the NTP server is correct
2. What happens when you try to connect to AD? (Make sure that the AD account has the proper permissions)
Thank you for rating!
07-09-2013 09:28 PM
Hello,
I went through your query and I guess there Can be several things for the issue to persist.
Just want to know if you had run a detailed test connection from the GUI to see if any issues come up?
Without any other data, first guess would be the DNS name server setting on the Cli. IF AD is used, the CLI should be containing only Dns that know about AD.
For example, having a mix of DNS name servers, some of which don't include AD info can cause this.
Next steps would be:
07-10-2013 04:36 PM
If you perform a Leave, wait for few minutes and Join to the domain, does it correct the issue? To identify the cause of this issue, you would really need to capture the ad_agent logs and try to pinpoint what failed with the AD communication. That's the only way to get to the bottom of this.
~BR
Jatin Katyal
**Do rate helpful posts**
If you perform a Leave/Join of the domain, does it correct the issue?
11-15-2013 06:07 AM
I had this issue as well but my NTP settings were correct and the time was not slipped at all.
I logged into the cli and ran this: #sh logging application ad_agent.log tail
which led me to this error:
2013-11-15T07:55:57.177566-06:00 host-psn1 adclient[10469]: INFO
2013-11-15T07:55:57.282448-06:00 host-psn1 adclient[10469]: ERROR
Go into Active Directory Users and Computers and right click on the computer account object and click reset account.
Which resulted in these log entries:
2013-11-15T07:57:57.473370-06:00 host-psn1 adclient[10469]: INFO
2013-11-15T07:57:58.266485-06:00 host-psn1 adclient[10469]: INFO
mode.
2013-11-15T07:58:25.006230-06:00 host-psn1 adclient[10469]: INFO
2013-11-15T07:58:25.058151-06:00 host-psn1 adclient[10469]: INFO
2013-11-15T07:58:25.058189-06:00 host-psn1 adclient[10469]: INFO
2013-11-15T07:58:25.100676-06:00 host-psn1 adclient[10469]: INFO
That fixed me up. Hope this helps someone else out there.
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