Meraki

Nadim · ‎Dec 2 2020

To clarify how my network is working, I have 2 meraki MX64 (warm spare enabled) connected to two MS switches each is used for a certain VLAN (attached image); meaning that I have a switch used for vlan x.x and another for xx.x to separate LAN from WLAN, I can see that under Security & SD Wan -> Addressing & VLANs I have no Group policy assigned to those VLANs. However, if I assign a policy this will neglect the role of my AD to assign users to their groups. Meaning that all users on vlan x.x will have a group policy applied (everyone on this vlan without exception)

Nadim · ‎Dec 1 2020

And the SSL certificate generated is identical to FQDN that of the active directory. I tried the ldp.exe tool it connects to both my ip address and fqdn using port 636 and ssl.

Nadim · ‎Dec 1 2020

Yes. only one active directory is running currently with global catalogue server enabled as well.

Nadim · ‎Dec 1 2020

Hi, I followed the documentation on Meraki in order to integrate MX with my Local Active Directory. I created an SSL certificate and did an ldp test which is successful whenever i use port 636 with SSL (checked/enabled). I was able to add AD under the Security & SD Wan where the connection was successful and when I refresh LDAP groups appear (as created on my AD i.e. Restricted Access Group, INternet Medium & internet full). However I have 2 issues: 1- Clients within their Groups (assigned to in AD) aren't applicable to any Group Policy from Meraki MX side 2- APs (when trying to enable Splash page) fail to connect (tried LDAP and ACtive Directory) it gives an error 249 (even though i am using the same username and password in Step 1- mentioned above) check below screenshots :

Meraki

Community

About Nadim

Nadim

Community Record

Re: Integrating Active Directory with Meraki Firewall MX64

Re: Integrating Active Directory with Meraki Firewall MX64

Re: Integrating Active Directory with Meraki Firewall MX64

Integrating Active Directory with Meraki Firewall MX64