Home > Wireless LAN > Encryption and Authentication > "Timeout" error on the 802.1x test in Dashboard

"Timeout" error on the 802.1x test in Dashboard

Table of contents
No headers
A "timeout" error can indicate one of the following:
  1. The Access-Request message from the Meraki AP never reached the RADIUS server, or 
  2. The reply (Access-Accept or Access-Reject) from the RADIUS server never reached the AP

Recommended Steps:

- Check the RADIUS logs to see if the Access-Request ever came in from the Meraki AP and/or whether there are any errors
- Perform wired packet captures to see where the request and reply packets are going (or not going).

You must to post a comment.
Last modified
21:28, 2 Feb 2015


This page has no custom tags.


This page has no classifications.

Article ID

ID: 1631

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case