Meraki

KBLatColonial · ‎Sep 9 2022

Hi, thanks for the reply. You're right, it's a Windows NPS server. You're right, it's almost certainly a misconfiguration of the Radius server. where the errors are is the big question. However, I'm implementing Radius through the Spash Page, not the WPA2 enterprise route. I will review that doc just to see if there are any clues there for why it's not working.

KBLatColonial · ‎Sep 8 2022

I have MR46 APs. I'm trying to set up Radius Authentication in the Splash page. I followed the steps in https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Configuring_RADIUS_Authentication_with_a_Sign-on_Splash_Page but every time I test, it fails. I usually get reason code 22, The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server. or reason code 66, The user attempted to use an authentication method that is not enabled on the matching network policy. I also get "A RADIUS message was received from the invalid RADIUS client IP address xxx.xxx.xxx.xxx." (IP obfuscated) Windows event id 13 messages I'm pulling what little hair I have left out trying to figure this one out! bottom line, why is this not working?

KBLatColonial · ‎Sep 1 2022

I really appreiciate you taking time to share your experience and advice! I've already skimmed your first link, and I'm checking out the one from Meraki now. According to the Meraki docs, there's a way to scope AD to only allow authentication from a particular OU, but that's not a very practical method when you'd have to set a "deny" for the admin account on all the OUs except the one you're using. We have way too many OUs for that to work... thanks again for your time and effort!

KBLatColonial · ‎Sep 1 2022

Hi, thanks for the response! while we do have a radius server, I'd prefer the simpler solution of AD, or LDAP, even. if I can't make that work, I'll give the Radius thing a try thanks, Kim

KBLatColonial · ‎Aug 31 2022

I want to use AD authentication in the Splash page, but want to limit the access to a specific AD group rather that the cumbersome AD scoping mentioned in the documentation. How can that be accomplished? I can use LDAP in the Splash page if that is what needs to happen to do what I want. TIA for any responses/suggestions

Meraki

Community

About KBLatColonial

KBLatColonial

Community Record

Badges

Re: Radius authentication in Splash page not working

Radius authentication in Splash page not working

Re: how to set up splash page AD authentication based on AD group membershi...

Re: how to set up splash page AD authentication based on AD group membershi...

how to set up splash page AD authentication based on AD group membership