Hi all- new poster here.
I recently set up a new Meraki Org and WAP at one of our orgs' hub sites. I created new SSIDs, installed a demo Meraki MR36, setup a winServer 19 radius server (NPS) onsite, and have authentication against two of our AD groups working properly. For purposes of argument, I will call this SSID "NewNet-Emps".
I also have a legacy Meraki WiFi network onsite at the same hub site, housed in a different Meraki Org that was set up by my predecessors. It authenticates to a different radius server across a VPN tunnel to our parent site. For purposes of argument, I will call this SSID "OldNet-Emps".
When clients are connected to "OldNet-Emps", they are able to successfully redirect to our org's ADFS page. When clients are connect to "NewNet-Emps" however they are unable to redirect to the same ADFS page. Everything else appears to be working fine.
It appears that the connection attempt is timing out because the connection is not considered secure. When connecting to our ADFS site, clients on "OldNet-Emps" show a secure connection via TLS 1.3 while clients on "NewNet-Emps" show "connection not secure" and time out when trying to load the page.
Does anyone know why clients on the "OldNet-Emps" network would be able to make a secure connection with our ADFS page while clients on the other network "NewNet-Emps" cannot?
I would be glad to try any testing suggestions you might have that could help lead to a resolution of these issues.
Thanks for your kind help in advance 🙂