A device can stay connected to a router while losing access to the internet. These steps show how to identify whether the fault lies with the network, device, DNS or a captive portal.
When a device shows that it is connected to Wi-Fi but cannot reach the internet, the problem usually lies at one of two points: the link from the device to the router, or the link from the router to the wider network. A useful first step is to identify which side has failed. If every device in the home is affected, the modem, router or internet service provider is the more likely cause. If only one phone or laptop is offline, the fault is usually local to that device, its settings or its network profile.
The fastest practical test is to try another device on the same network, then test the affected device on a different connection, such as a mobile hotspot. If other devices also fail, attention should turn to the modem and router. A modem status light that is off, red or behaving unusually often points to a provider-side problem. In that case, a power cycle is worth trying before contacting the ISP. If the problem appears only on one device, the next checks should focus on the device itself rather than the network hardware.
Restarting the modem and router remains one of the most reliable fixes. The correct sequence matters. The modem should be unplugged first, then the router, with at least 30 seconds left before power is restored. The modem should come back online before the router is reconnected. That process clears many temporary faults, including frozen network sessions and failed handshakes with the provider. If the equipment is several years old, repeated dropouts may also justify a firmware check or a hardware upgrade.
On Windows 11, the most common software-side remedies are straightforward. Start with the built-in network troubleshooter, then check that airplane mode, proxy settings and any VPN are not interfering with traffic. If those steps do not help, forgetting the Wi-Fi network and reconnecting can clear a corrupted profile. Renewing the IP address and flushing DNS are also standard repairs when the PC can talk to the router but not to web servers. If the issue began after a driver or system update, the wireless adapter driver may need to be updated, rolled back or reinstalled. A full network reset should be left for the end, because it returns network settings to default and may remove saved VPN and Wi-Fi details.
iPhone users should follow a similar order, beginning with the router and modem. Apple recommends checking the network equipment first, then removing any security or VPN software that may be filtering traffic. Forgetting the wireless network and joining it again can clear a bad profile. If nothing else works, Reset Network Settings is the last resort, but it also clears saved Wi-Fi passwords, cellular settings and VPN and APN configurations. In most cases, that is unnecessary unless the connection problem is persistent or the device has developed a deeper configuration fault.
Android devices use slightly different menu paths, but the logic is the same. Resetting the internet connection, forgetting the saved network and checking Private DNS are the main fixes when the phone remains attached to Wi-Fi but cannot browse. A stale custom Private DNS hostname can block websites even when the Wi-Fi link itself looks healthy. On some Pixel phones, Google also provides a reset option that clears Bluetooth and Wi-Fi settings together, although this should be treated as a final step because it removes saved wireless connections.
Public Wi-Fi introduces a different category of problem: the captive portal. In hotels, airports and cafés, a device may appear connected while access is still blocked until the terms page or login screen has been completed. Opening a browser and visiting a plain web page often triggers the sign-in screen. If it does not appear, temporary changes to DNS or VPN settings may be preventing the portal from loading. On public networks, it is sensible to sign in first and only then restore any VPN connection if needed.
If the problem persists after all of these checks, the ISP should be contacted with specific information: when the failure began, what the modem lights show, whether multiple devices are affected and whether a device connected by Ethernet can get online. That final detail is especially helpful. If wired internet works but Wi-Fi does not, the issue is likely in the router’s wireless function rather than the provider’s line. In business environments, repeated disconnects can also indicate a deeper problem with cabling, router placement or DNS configuration, which may need a more structured review.
For readers planning ahead, the core troubleshooting approach is unlikely to change, because the basics of IP addressing, DNS and router handshakes remain the same. The hardware landscape, however, continues to move forward. Reports from industry coverage suggest that Wi-Fi 8 equipment is beginning to appear in preview form, even though the standard is not expected to be finalised until 2028. For most households and small offices, there is little reason to rush into new hardware if a current Wi-Fi 6 or Wi-Fi 7 router is stable and properly configured.
Disclaimer: This content is intended for informational purposes only. Readers are advised to exercise their own judgement, conduct due diligence, or consult a qualified expert before acting on any information provided.
