Any update on this? ... View more

One way is to view the txt file that is created and shows the APs that were rebooted. I also verified if an AP was rebooted by running the script and going to a different office where the AP should have rebooted, but didn't. ... View more

Thanks for the quick response. I do use "-AP" since that should match every APs name, but it doesn't. I changed it to just "AP", but that actually rebooted less than using "-AP". I then changed it to "Room" since where I see most problems are in the APs that have "Room" in the name, but again, that didn't reboot every AP that had "Room" in their name.   What I also noticed when I used "-AP", it was always the same APs that were rebooted. I just have one network, all the APs are in it.     ... View more

Thanks for the script, but when I use it, not all the APs get rebooted. All my APs name end with "-AP" but about a third get rebooted. Is there a way to just say reboot all APs? ... View more

Users are authenticating via on prem AD.   ... View more

There are no other APs.  Also in the client view, I can see the device connected to the AP. I had a couple of people look at the situation, and it seems the DNS/DHCP servers are acting as they should, but the ACK responses are not getting back to the client.  So the client doesn't get an IP or resolve dns queries.  What's even odder is that this was only happening on one vlan, the rest were fine, even on the same AP. I'm going to have Cisco take a look at our core switches, which does the vlan routing. ... View more

Reviving this oldish thread. I'm having this issue as well. Meraki support hasn't been able to tell me anything. I've called on CDW to help me out with this issue.   Anyone else seeing this kind of issue?  Any resolution? ... View more