Hi there,   We are having an odd issue with users who are running the Cisco Secure Access Client on their laptops.   Users who connected to any of our SSID's have trouble getting out to the internet when the cisco secure access client is installed and active.   Example dns msg: "failed connection to SSID XXXX on access point aa:bb:cc:dd:ee:ff because the DNS server did not respond."   The thing is though that the public dns servers ARE in fact reachable via users who have the cisco secure access client installed/uninstalled or users who have the client installed but are wired in directly to the switches.  I.E. they can ping the public dns servers from their devices.  We can ping/trace to the dns servers from the ap's themselves and from the switches as well as from our firewall.  The firewall isn't blocking any outbound traffic and logs show that the traffic to the various public dns servers and to the CIsco opendns servers that the secure client uses is allowed.   The issue is intermittent and doesn't affect everyone either.  For example, today there were 20 people in the office but only 2 of them had the issue.  Other days, it's a bunch of people having the issue.  It's very random.   To reiterate, when the user gets wired into the switches directly, they do not have the same issue and can reach the internet without any issue (even with the cisco secure access client active).   Is there anything on the MR52 access points that can cause issues with DNS and Cisco Secure Access clients on end user devices? I've reached out to meraki support but they say there are no known issues btw MR52 ap's and the cisco secure client.   Anyone else run into something like this?  If yes, how did you fix? ... View more