I've encountered a similar issue although its complicated slightly by some changes within my organisation.    We had 20 Meraki AP's running perfectly happy across a large site. We've recently closed the site and kept two of the MR46's to use in our new much smaller office suite.    I've now setup the two MR46's with cabling direct to a Cisco Catalyst 9200 switch and they were running without issue for a couple of weeks and then on November 19th (i think) they started to complain about the link speed. I've checked the cabling, reset the AP's, forced the speed on the port. Nothing seemed to fix it.  I haven't been able to bounce the switch but I'll need to wait for an opportunity to do that. ... View more

Another potentially easy option not mentioned yet - you could expand your DHCP pool.   Another option not mentioned yet - you could consider using iPSK - where you give each user their own individual PSK.  If you don't have it, they can't connect.  As a bonus, when you use this method you can add a column to the dashboard to display the name of the iPSK - so you can determine the name of each user connecting. You can also create a "default" iPSK which is the same as the current PSK, which means you can keep the current WiFi working "as is" while you migrate to iPSK, and then once done, delete the existing default iPSK. https://documentation.meraki.com/MR/Encryption_and_Authentication/IPSK_Authentication_without_RADIUS    As a bonus, both of the above two methods are "free" and once setup they have a very low management overhead (you won't have to do anything to look after it!). ... View more

Yes.  Most WiFi networks shouldn't have clients with static IP addresses, and this reduces a whole lot of potential problems by not allowing machines with a manually configured address. ... View more