Specific AP having radius server did not respond issue

[keithli]

Dear All,

Would like to seek for help on the following, one of our customer are using Meraki MR44 AP, and with 2 ssid created call "Internal" & "Visitor", ssid internal are authenticated with Radius server, and ssid visitor are authenticated via PSK, and it was working fine with both ssid, and in recent day our customer reported there is one AP having authenticated issue on the ssid "Internal", and below is the logs i found, i have tried to ping the radius server ip from the problem AP, and it could reach the radius server, but below logs are still appearing, just wonder is there anything i can do to fix such issue ? any help would be appreicated

Client failed during the authentication step.
reason='reserved' radio='1' vap='0' channel='40' rssi='49'

Client made an 802.1X authentication request to the RADIUS server, but it did not respond.
radius_ip='188.3.8.201' reason='radius_timeout' radio='1' vap='0' channel='40' rssi='28'

Keith

[joey.debra · Accepted solution]

You didn't need the host , only radius communicates on that port.
If your AP does not send anything when the client connects to it (so be sure it is a new session, not a roam) then the AP is not doing anything towards the radius servers.

Another important note though: Dashboard captures can be a bit finnicky and it is possible your capture stopped capturing packets a long time ago. It is best if you use dashboard captures that you keep to the 30 seconds to 60 seconds mark and immediately try to connect.