Client devise keep failing to access AP with error_code=77

[Jay131]

hello,

I am having a trouble with my Meraki MR44.

there has been no issue till yesterday.

but our one client marchine can not access to MR44 from today.

error code is as below.

Feb 17 16:04:30		802.11 disassociation	802.11_reason_code = undefined
Feb 17 16:04:30		802.11 disassociation	unspecified reason
Feb 17 16:03:44		802.11 association	band: 5, channel: 36, rssi: 45
Feb 17 16:03:43		802.11 disassociation	802.11_reason_code = undefined
Feb 17 16:03:43		802.11 disassociation	802.11_reason_code = 77
Feb 17 16:03:43		802.11 disassociation	802.11_reason_code = undefined
Feb 17 16:03:43		802.11 disassociation	802.11_reason_code = 77
Feb 17 16:03:43		RADIUS response	radio: 1, vap: 1, group: more »
Feb 17 16:03:43		802.11 association	band: 5, channel: 36, rssi: 45

there were no changes but this issue happend suddenly.

is there anyone who experienced similar issue?

[RWelch-USA]

Common Wireless Event Log Messages and Issues

[sinelnyyk1]

Hi @Jay131,

I did some digging, and here is what I found: reason code 77 (UNSUPPORTED_FINITE_CYCLIC_GROUP) - Authentication is rejected because the offered finite cyclic group is not supported; check the RSN Information Element in the Association Request/Response frames.

I would suggest to try and scope the issue to see what SSIDs are affected. I'm not sure what authentication you're using, but I'd recommend to try different (including open SSID) to see which are affected.

Monitor Mode (or Over the Air) captures would also help here - you would need to look at the beacon and association request frames to see and compare "RSN Capabilities" header. I think on MR44 you can also collect bidirectional over the air captures from the Wireless interface of the AP in the Dashboard from the Network-Wide > Packet Capture page.

[Philip D'Ath]

I would start by seeing if there is a WiFi driver update for the client. Don't just check the OEM web site, but check the manufacturer of the Wifi ship set (e,g. Intel, Marvel, etc).

I'll put the odds on 75% that a driver update will resolve it.