setting up Radius Authentication for our corp network.
followed the instruction in terms of NPS but when i test the radius server it fails to connect. it doesnt give out any other error.
i checked the radius server and i have added the AP and went through event logs but i cant find any failures under security logs.
NPS logs doesnt have any record.
i am able to ping the radius server from the subnet i am on.
any other pointers or location i need to check.
Solved! Go to Solution.
That typically happens when the RADIUS key does not match.
In NPS (at least in Server 2012R2 or better) you can assign a subnet that all clients are in (such as 10.0.0.0/8) and a common key. This makes it easy to leave Meraki devices configured to use DHCP (like access points).
i am running this on Server 2012.
but if its a bad key shouldnt i see it somewhere??
i am using radius only for corp network and the ip's will be forwarded via dhcp from our lan.
@PhilipDAth is likely correct, the most common issue is a mismatched shared secret between the AP and RADIUS server, but it could sometimes be fat-fingered IP address settings and a UDP port mismatch (make sure it's using 1812 and not some other port like 1645). Any of those things would likely cause radio silence from the RADIUS server.
its definitely 1812 and i have confirmed the password with 2 different people its definetly right.
i am using my account with and without domain prefix and confirmed the password.
my admin account has access to NPS server so i am not sure what else can be wrong.
this is is annoying the living daylights out of me.
Are you using an actual wireless client/supplicant or the "Test" button on the Access Control page in Dashboard? You already ran packet captures and/or ran it by Support to assist with some pcaps? Let's see what is or isn't traversing the AP.
I have had issues with NPS many times where it doesn't log anything to the event viewer, like it should. Enable the option to log to a TXT file. By default it writes it out to:
And the files begin with IN*. As long as the RADIUS secret is correct it will log success and failed responses there. They are a pain to read.
i did check that location but i dont see any files with IN. all i see are multiple subfolders but nothing says as radius server related.
Lets check some basics (I'm assuming you are using WPA2-Enterprise mode):
In NPS right click the NPS server and select "properties". Make sure you have ticked to logged accepted and rejected connections.
currently i have only added AP ip which is on different subnet compared to our corporate subnet.
so not sure if there is a point of adding the entire subnet
What connects these two subnets? Layer 3 switch, router, firewall?
Does the NPS server run antivirus that also contains a firewall?
Is Windows Firewall enabled on the NPS server? If so, has it got an exclusion for the 1812 and 1813 ports?
i might have to check the certificate its getting.
to my understanding all my settings are correct.
going through the certifcate requirement for this. let me see how i go.
For what it's worth, I was having this exact same issue with a Windows Server 2019 VM running NPS. Meraki could not connect to it, the key was right, the settings were right, everything was right. I rebooted the server and it suddenly started working.
Thank you! This helped as the AP was relocated from another location and assigned new IP. I had to remove the AP from NPS and re-add with new IP/manual generated password. WORKED!