Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Nadim
Nadim
Comes here often
Member since Nov 30, 2020
Dec 15 2020
Community Record
4
Posts
0
Kudos
0
Solutions
Dec 2 2020
7:12 AM
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)
... View more
Dec 1 2020
11:57 PM
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.
... View more
Dec 1 2020
11:54 PM
Yes. only one active directory is running currently with global catalogue server enabled as well.
... View more
Dec 1 2020
12:15 AM
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 :
... View more
© 2024 Cisco Systems, Inc.
