- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to connect to Meraki wireless network using network profile pushed from GPO
Hi All
We have an existing wireless setup with Cisco WLC and Aironet access points which work with enterprise radius authentication. We are now working to migrate the setup to Meraki access points
Below is the detail on the issue
There is a GPO wireless profile being pushed out to the clients which has the Cisco Aironet SSID added in it, this is the one running in production
We did a test where we turned off the Cisco Aironet SSIDs and broadcasted the Meraki SSID with the same name that is used by cisco, as we wanted the client side to have minimal changes when doing a cutover
When testing this, the client machine is not able to connect to the Meraki network. The dashboard continues to show EAP authentication failure messages. If we rename the Meraki SSID name to a different name and directly connect from the client machine, it works fine
Could you please suggest on what steps could be taken to diagnose and resolve this issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Create group policy using the filter-id attribute and this is the policy that get referenced with ISE make sure that the filter id name matches exactly
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi - Thanks for your help. We want to move away from auronet plus ISE authentication to Meraki
so in the meraki we used the same SSID as used in airlonet turned off aironet and tested and it was not connecting with the GPO profile but connects fine directly with the same meraki SSID
So not sure what in the GPO profile differs from not allowing to connect to meraki even though SSID name is retained same
