Hi Everyone, Kinda new to this community, I want to share and ask for help to solve a very strange case in our office. In our three-story building, 2nd floor works fine, however 3 out of 11 MR 56s on the first floor report DHCP failures, same as our third floor, 3 out of 9 MR 56s do not work as expected. The APs cannot to Aruba switch on a trunked port in the default vlan allows vlan 31 and vlan 100(management). APs' ip address is on management vlan network. We have three SSIDs: SSID Private requires 802.11x authentication and uses vlan tagging. SSID Public uses meraki dhcp SSID GP uses Pre-shared key, local LAN but no vlan tagging (untagged). After some troubleshooting here are our findings: PC1 fails to connect to Private SSID with nearby AP24, while PC2 and PC3 can connect AP24. Shows connecting..... PC1 can connect to Private SSID from AP 26 and roam to AP24 without disconnecting. PC1 can connect GP and Public SSID from AP 24. After PC1 releases ip address and then fails in connecting to Private SSID from AP24. However, it works for PC2 and PC3 when we do the same test. 4. We check the cable, which it is good. We relocate AP24 to AP26's location and directly connect to Switch. This works for PC2 and PC3 but same issue for PC1. We use 802.11aw and WPA2 only. When checking the dashboard and pcap file, dhcp fails as no response from dhcp server. We have two windows dhcp servers for wireless client. If we use switch as dhcp server, would that be a better choice?
... View more
