A laptop on a branch WLAN can ping its gateway and cannot reach the internet. Other destinations on the gateway's own subnet work. Association and the address are fine. Where is the fault?
Select an answer to reveal the explanation.
Short Explanation
Your laptop is joined to the WLAN and can reach its gateway and nearby devices. The fault begins beyond the gateway, while the radio has already carried the local traffic. Look past the gateway rather than at association, the key, or the radio.
Full Explanation
A laptop that can ping its gateway and other hosts on the same subnet has associated, received an address, and passed traffic as far as the gateway. Since internet destinations fail beyond that point, the fault is past the gateway, such as in routing, NAT, or a firewall. An association failure does not fit: the laptop is already communicating on the WLAN. A pre-shared-key failure does not fit either; a successful gateway ping shows that the key was accepted, not skipped. An access-point radio fault is also inconsistent with the evidence: local subnet packets use the radio, and those packets are getting through. The local and internet paths share the WLAN up to the point where traffic leaves the gateway. Exam caveat: DNS failure can resemble an internet outage when the test uses a name, but this question is about reachability beyond the gateway. Confirm with an IP address so you do not chase the resolver. For a practical check, ping the gateway from the laptop, then test the next hop beyond it and investigate the first hop that does not answer. After a change, verify the result on one live client before making broader changes.