Any ideas what's happening here?
We have a MacOS computer that refuses to connect to the RADIUS (email and PW credentials) via an AP (1 of 4). EAPoL timeout error.
EAPoL timeout indicates an 802.1X issue. How is the SSID configuration? Are 802.11w and 802.11r enabled?
Those are both disabled on the SSID.
Does the RADIUS server say it gave permission (sent an ACCESS_ACCEPT)? If it denied permission, why?
Does the Mac have the CA certificate loaded that was used to create the certificate that is being used by the RADIUS server?
This is what I see in the dashboard:
auth_mode='wpa2-802.1x' vlan_id='xx' radius_proto='ipv4' radius_ip='x.x.x.x' reason='eapol_timeout' radio='1' vap='2' channel='157' rssi='44'
No certificate. Connects with email and PW (WPA2).
@PhilipDAth I think the Meraki Radius is being used, correct @larsdueck ?
That is correct.
So you have 1 MacOS, which cannot connect to a 802.1x SSID with EAP-PEAP using Local Authentication on 1 AP, but it works on the other 3?
And you have other MacOS pcs that do work on all four APs?
I'd try to look into the settings on the one MacOS pc, and perhaps factory reset that one AP; and see if that does the trick.
Does not work with any AP at the point after further testing. Other Macs/PC's can connect. Can't see what would be wrong with the Mac at this point.