Complete these steps in order to troubleshoot your configuration.

1. In the client-side utility or software, create a new profile or connection with the same or similar parameters in order to ensure that nothing has become corrupted in the configuration of the client.

2. In order to eliminate the possibility of RF issues that prevent successful authentication, temporarily disable authentication as shown in these steps:

o From the CLI, use the commands no authentication open eap eap_methods, no authentication network-eap eap_methods and authentication open.

o From the GUI, on the SSID Manager page, un-check Network-EAP, check Open, and set the dropdown list back to No Addition.

If the client successfully associates, then RF does not contribute to the association problem.

3. Verify that shared secret passwords are synchronized between the access point and the authentication server. Otherwise, you can receive this error message:

Invalid message authenticator in EAP request

o From the CLI, check the line radius-server host x.x.x.x auth-port x acct-port x key .

o From the GUI, on the Server Manager page, re-enter the shared secret for the appropriate server in the box labelled "Shared Secret."

The shared secret entry for the access point on the RADIUS server must contain the same shared secret password as those previously mentioned.

4. Remove any user groups from the RADIUS server. Sometimes conflicts can occur between user groups defined by the RADIUS server, and user groups in the underlying domain. Check the logs of the RADIUS server for failed attempts, and the reasons those attempts failed.