10-19-2006 07:23 AM - edited 02-21-2020 01:15 AM
Using CTA 4.0.2, ACS SE 4.x, and Windows AD the following occurs:
1. When login to WindowsXP using Local Account, then CTA prompts its login. I can then put the AD account. This process works!
2. When login to WindowsXP using AD Account, the error msg "domain xyz is not available", so the CTA prompt never come-up
3. When login to WindowsXP using "CACHED" AD Account, then CTA prompts its login. I can then put the AD account. This process works also!
4. Using Single Sign-on with "Never Validate Server", #2 and #3 occured.
Any input is very appreciated. Cisco TAC has been notified.
thanks,
Audie
703-292-5316
10-20-2006 09:30 AM
We were told to start testing the CTA 2.1 SA (Selective Availability) version.
Audie
01-03-2007 12:56 AM
I Have the same issue.
Whenever a user is new to a machine wich uses NAC/CTA, he cannot log onto the AD network since he is not cached locally on that PC.
Did you find a solution to this ?
Kind regards
KelvinDam
01-04-2007 04:29 AM
Yes, we upgraded the ACS to 4.1! It is working like a champ now.
Audie
01-16-2007 04:48 AM
Hi all,
I have the exact same problem.
I have just upgraded my ACS to 4.1 but that didnt help on the problem.
You write "CTA 4.0.2"....I suppose you mean 2.0.x ?
Did you guys do anything extra on the ACS to get this to work ?
Kind regards
KDam
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