07-15-2009 09:25 AM - edited 07-03-2021 05:49 PM
I currently am running a primary/backup ACS server to authenticate my wireless users. PEAP is the authentication method. I generated a self-sign certificate on both the primary and backup ACS servers and primary works fine. When I stop services on the primary I see users fail to the backup but on my test machine which has the secondary certificate loaded it will not authenticate.
I submitted a package.cab file to TAC and they couldn't even see my machine hit the ACS server.
Has anyone seen this issue?
Darcy
07-15-2009 12:51 PM
Perhaps you should eliminate the certificate as being a potential part of the problem. On your wireless client, disable the server certificate check.
You might also want to try setting your secondary server as the PRIMARY server to see if it is authenticating properly. You should also check the ACS logs to ensure that things like mis-configured shared secrets aren't the real cause of your problem.
Also - is the wireless client timing out before your wireless network/ACS combo have figured out that the primary ACS server is offline?
07-17-2009 10:29 AM
I will give your suggestions a try this weekend.
Thank you
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: