Retail clients associate, pass PSK, receive a normal address, and can ping their gateway. Applications that use names fail, while an application opened by IP address works. What should be checked next?
Select an answer to reveal the explanation.
Short Explanation
They have an address, they can knock on the gateway, and they cannot turn a name into a number. That is DNS. Your passphrase already did its job, and the beacon is not where lookups go.
Full Explanation
Name resolution is DNS. Clients that have a normal address, can ping the gateway, and can open an application by IP address have finished association, authentication, and DHCP. The remaining break is the resolver address or the path to that resolver, so that is the next check. The PSK has already been accepted. A partial passphrase does not produce a working IP session that fails only by name. DHCP has also succeeded, because the clients have a normal address and can use the gateway. A link-local 169.254 address would be the clue for a DHCP failure, and that is not the address they have. Beacons advertise the BSS. They do not carry application DNS queries, and changing the beacon interval will not fix name lookup. Exam caveat: a DNS suffix or a captive-portal intercept can make some names fail while raw IP works. Check the resolver the client actually learned before you redesign the WLAN. Operational check: on a failed client, read the DNS server address and query it by IP for a known name. If that query fails, trace from the client VLAN to the resolver.