Figured it out, Meraki Layer 3 firewall we use to "allow" specific IPs such as Radius servers/DNS/Gateway and "deny" any by default. the error in configuration that the broadcast IP 255.255.255.255/32 is not allowed, nor Ports 67/68. adding these to the allow list in the firewall policy will solve the issue. If we go back and check Meraki's recommendation is to "Deny" any unwanted subnets, and keep the Allow as default. But this does not work for me, as we need to also block public IPs before .1x authorization response. Thanks ... View more

Let us think in a different way, perhaps the issue isn't from Meraki, may be its a Windows/NICs related issues, I have seen multiple posts regarding Intel's new AX wireless NICs that only have DHCP issue with RADIUS networks. In my environment, we have AC8xxx / AC9xxx / AX201 / AX210 We had in hands a machine that is unable to obtain IP, we tried to connect using an external USB TP-Link adapter, it worked instantly, under the same SSID, and same AP. Unplugging the USB and reuse the internal NIC, the machine is unable to obtain IP address. Dears, please share your environment used NICs, are they all Intel's, what model?  ... View more

Hi guys, We have been suffering with this issue for more than ten months; we have three separate environments in various locations, each running the Meraki solution, all connected to the same radius server via LAN, and each using a different brand of DHCP server and routers. This problem only affects one place for prolonged time, and it happened only once on another location but only for 1 day. This issue affects users in a complete random manner, no specific details nor device type/NIC make was detected. we have 1500+ user in the environment with more than 15 different devices, NIC and drivers. Following a thorough study and checks, we have discovered the following:   According to pcaps from clients and (AP's wireless); discover requests are sent, however they are never shown on the switch nor (AP Wired) captures.. Before the discover packets can reach the (AP Wired) pcaps, they are lost. The DHCP server's packet captures indicate that the client has not sent any packets, but any successful connection does indicate a full DHCP DORA. 4 or more clients may successfully connect to and finish the DORA on the same AP where a client fails to do so. We attempted to restart all of the devices in production,, also we upgraded the Meraki APs and switches to the most recent firmware release but without success.   The workaround we have thus far involved is moving the problematic machine to another AP (Roam), trying to connect again and it succeed, then returning to the same location while still being connected, even when reconnecting will be successful.   The device connects and complete the DORA when roamed. Please let us know if this was useful and if anyone had a solution for this problem. Support from Meraki was of no assistance at all. A big thank you! Regards, Waseem -  ... View more