Hi I am still having this issue. Some more testing I have done and logs I have seen.    From our RADIUS server I noticed while a client had been having issues connecting to this trouble AP, there was an event generated.   Event 13, NPS A RADIUS message was received from the invalid RADIUS client IP address 172.x.x.x.    After searching this event, it notes that the client in NPS may be using a hostname instead of IP. It was not, we set the Meraki APs all in NPS with their IP address. The IP is correct. I decided to completely remove from NPS and re-add. Today I am again having trouble with clients connecting to this AP.    3 of the last 5 requests did not receive responses. Req. ID Client MAC Server IP Request type Response type RTT (ms) Ago (s) 163 9c:30:5b:26:0c:17 x.x.x.x Access Request – – 393 164 9c:30:5b:26:0c:17 x.x.x.x Access Request Access Challenge 30 364 165 9c:30:5b:26:0c:17 x.x.x.x Access Request – – 364 166 9c:30:5b:26:0c:17 x.x.x.x Access Request Access Challenge 30 346 167 9c:30:5b:26:0c:17 x.x.x.x Access Request – – 346   This is intermittent. Yesterday this same laptop could not get connected. I rebooted the AP several times and made the changes in NPS and nothing worked. Today it is happening again, but I have one laptop that was connected successfully after 20 minutes of trying.   ... View more

Anybody have any other thoughts? ... View more

Another note, this particular AP is not mounted on a ceiling. It is sitting on a shelf.  ... View more

There are no logs from the RADIUS server except positive logs, where I can see audits for successful RADIUS requests from this particular laptop during this particular time frame I posted.    Yes we are using WPA2-Enterprise mode.    There are no rogue SSIDs reported in Wireless>Air Marshal for the last week. There are no Spoofs or Malicious Broadcasts reported for the last week. I work for several different banks. We take security very seriously. I would have known about anything like this ahead of time and/or been alerted already.    Power for the AP is PoE 802.3af. It is plugged directly into a brand new Cisco 2960-L switch. The issues were happening before that though when it was using a PoE injector to get power. It has not changed since removing that.          ... View more

Also this happens with pretty much any device that tries to connect to this AP.  ... View more

You can see for today it's happened many times already. But when this device goes back to where it normally resides it does not happen. SWDAP01 is the AP in questions with device GVLAP007. You can see "deauthentication" around the enterprise is very minimal for other APs.    3/15/2019 10:44 RCKAP02 FFG_CORP NWBTAB01 802.1X deauthentication "radio: 1, vap: 2, client_mac: 98:5F:D3:54:A8:F4" 3/15/2019 8:32 PHPAP01 FFG_CORP NWBTAB041 802.1X deauthentication "radio: 0, vap: 2, client_mac: F0:6E:0B:CF:95:DA" 3/15/2019 8:30 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:30 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:28 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:28 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:27 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:27 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:27 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:27 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:26 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:26 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:26 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:24 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:24 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:23 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:23 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:23 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:23 SBHAP01 FFG_CORP SBHLAP008 802.1X deauthentication "radio: 1, vap: 2, client_mac: 7C:5C:F8:A6:ED:43" 3/15/2019 8:23 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:22 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:22 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:21 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:21 LSTAP01 FFG_CORP SBHLAP009 802.1X deauthentication "radio: 0, vap: 2, client_mac: 80:00:0B:B7:AB:FB" 3/15/2019 8:20 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:20 SWDAP01 FFG_CORP FFGLAP040 802.1X deauthentication "radio: 1, vap: 2, client_mac: 2C:6F:C9:03:88:F9" 3/15/2019 8:20 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:19 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:19 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" 3/15/2019 8:19 SWDAP01 FFG_CORP GVLAP007 802.1X deauthentication "radio: 1, vap: 2, client_mac: E4:42:A6:D3:92:35" ... View more

Firmware on the AP is 25.13 currently up to date.    Yes these are intel NICs but this is only happening on this particular AP. If it was a NIC issue on the laptop it should be happening at other locations in our enterprise.    Our radius server is a 2012r2 server.    ... View more