topic Re: Failed EAP-Authentication after ACS 3.0 upgrade in Wireless

Failed EAP-Authentication after ACS 3.0 upgrade

lyeyong1 — Sun, 04 Jul 2021 16:20:29 GMT

All clients are unable to do LEAP authentication after a ACS 3.0 upgrade.

On the ACS error message is Radius Extension DLL Rejected user

On the AP error messgae is Failed EAP-Authentication

Using External Database to WIN2K Domain.

Re: Failed EAP-Authentication after ACS 3.0 upgrade

b.hsu — Wed, 11 Feb 2004 15:09:10 GMT

Seems like you hit upon a bug, CSCdy81816 - When using AD and ACS on the different machine, LEAP authentication fails. The given work around is to run both the services from the same server.

Re: Failed EAP-Authentication after ACS 3.0 upgrade

steve.deal — Thu, 12 Feb 2004 21:41:27 GMT

I would upgrade to the latest ACS which is 3.2. I was having EAP problems until I upgraded.

Re: Failed EAP-Authentication after ACS 3.0 upgrade

pallette — Sun, 14 Mar 2004 08:24:52 GMT

or take a look at this link and make sure you have met all the requirements. This is for running ACS 3.0 on a member server in a domain.

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacsapp/raig/rawi.htm#642349

This is for a remote agent confgiration, but look at the "Windows Authentication from a member server" section