You open your laptop, the WiFi icon looks perfectly normal, the network name is there, the signal bars are full, and yet every browser tab gives you the same dead-end: no internet. It is one of the most frustrating tech problems precisely because the symptoms seem contradictory. The device says it is connected. The internet says otherwise.
After years working in IT support, I have seen this issue hundreds of times across home networks, small offices, and corporate environments. The good news is that in the vast majority of cases, the cause is one of a handful of well-understood problems and can be resolved without calling your ISP or buying new hardware. This guide walks you through every meaningful fix, in the order that actually saves time.
There is an important distinction your device draws between two things: being connected to a router and having a working path to the internet. When your laptop or phone shows "connected," it means it has successfully joined the local network created by your router. That is just the first leg of the journey. From there, your router still needs to communicate with your Internet Service Provider's infrastructure to actually reach the outside world.
When that second leg breaks, you get the exact symptom described above: connected to the router, but no internet access. The yellow warning triangle or the "No Internet" message next to your WiFi connection is your operating system telling you precisely this. It ran a quick check, could not reach a known external address, and flagged the problem.
Common root causes include:
Knowing exactly what you are looking at helps narrow down the fix faster. Here is what users typically report:
That last distinction is critical. If every device on your network has no internet, the problem is almost certainly in the router or with your ISP. If only one device is affected, the fault is specific to that device, its drivers, its IP configuration, or its software.
This is not just an old IT joke. A proper restart resolves the majority of these cases. Routers are running a full embedded operating system, and like any OS, they can hit memory issues, get stuck in a failed state, or lose their connection to the ISP without automatically recovering.
The right way to do it matters. Do not just press the reset button on the back, which restores factory settings. Instead:
The waiting period is important. Capacitors in the devices need to fully discharge, and the modem needs time to re-establish its connection with the ISP before the router starts sending traffic through it.
If the router restart did not help and only your Windows machine is affected, there is a good chance it has received an invalid IP address or its IP lease has expired. This is a common DHCP issue and takes about two minutes to fix.
ipconfig /release and press Enteripconfig /renew and press Enteripconfig /flushdns and press EnterWhile you are in the command prompt, it is also worth running the network reset commands. Type netsh winsock reset, press Enter, then netsh int ip reset, press Enter, and restart your machine. These two commands clear out corrupted network stack entries that can silently break connectivity while everything appears normal on the surface.
DNS is the system that translates domain names like google.com into the numeric IP addresses computers actually use. If your DNS server is down or returning incorrect results, websites will not load even though the underlying internet connection is perfectly fine. This is more common than most people realize, particularly with ISP-provided DNS servers during outages or maintenance windows.
Switching to a public DNS server takes under two minutes:
On Windows:
8.8.8.8 as the preferred DNS and 8.8.4.4 as the alternate (these are Google's public DNS servers)On Mac:
8.8.8.8 and 1.1.1.1Cloudflare's DNS at 1.1.1.1 is an excellent alternative to Google's. Both are fast, reliable, and privacy-respecting compared to most ISP DNS servers.
On mobile devices especially, this is often the fastest fix. The saved network profile can store outdated authentication data or incorrect settings that prevent a proper connection from being established.
On iPhone or iPad: Go to Settings, then WiFi, tap the information icon next to your network name, and select "Forget This Network." Reconnect by tapping the network name and entering your password.
On Android: Go to Settings, then WiFi, long-press your network name and select "Forget." Reconnect fresh.
On Windows: Click the WiFi icon in the taskbar, click the arrow next to your network name, select "Forget," then reconnect.
Before spending more time troubleshooting your own equipment, check whether your ISP is having a wider outage. This is quick to verify and can save you a lot of pointless effort.
Visit your ISP's website on mobile data (not WiFi) and look for a service status page. Alternatively, sites like Downdetector.com aggregate real-time outage reports by ISP and region. If your neighbors are also affected, the problem is almost certainly upstream and you simply need to wait it out.
Windows Update occasionally pushes driver updates that break WiFi adapter behavior. Conversely, an old driver that has never been updated can fail on newer router firmware. Either direction can cause this exact symptom.
If the standard fixes above have not resolved the issue, the following scenarios cover less obvious but real causes that come up regularly in support work.
Check for IP address conflicts. If two devices on the network have been assigned the same IP address, both can experience intermittent or complete connectivity failures. Open a command prompt and run arp -a to see the ARP table. Duplicate entries pointing to different MAC addresses indicate a conflict. Restarting the router usually resolves this by redistributing IP assignments.
Disable IPv6 temporarily. Some ISPs and routers handle the transition between IPv4 and IPv6 poorly, and the result can be that IPv6 fails silently while confusing the operating system. You can disable IPv6 in your adapter properties under Network and Sharing Center in Windows. If connectivity restores, you have found the issue and can investigate your router's IPv6 settings more carefully.
Check your VPN software. If you run a VPN client, it can interfere with normal routing even when it appears to be disconnected. Fully quit the VPN application, not just minimize it, and test whether internet access returns. Some VPN clients install virtual network adapters that continue intercepting traffic after the session has ended.
Look at the router's WAN status. Log into your router admin panel, typically at 192.168.1.1 or 192.168.0.1 in a browser. Look for a WAN or Internet status page. If it shows "Disconnected" or an invalid IP like 0.0.0.0, the router itself has no connection to your ISP. This points to either a physical line fault, a modem issue, or an account-level problem with your ISP.
| Symptom | Likely Cause | Where to Start |
|---|---|---|
| Only one device affected | IP conflict, bad DNS, driver issue, VPN, corrupted network stack | Fix 2, 3, 4, or 6 above |
| All devices affected | Router crash, ISP outage, modem failure, WAN disconnection | Fix 1 first, then check ISP status |
| Intermittent on all devices | Overheating router, ISP line quality, router firmware bug | Check router temperature, update firmware |
| Works on phone, not laptop | OS-level misconfiguration or driver problem on laptop | Fix 2 and 6, then check firewall/VPN |
| Works on some sites, not others | DNS failure (resolving some cached names but not new ones) | Fix 3, flush DNS cache |
Most WiFi connectivity problems are not random. A few habits significantly reduce how often you will encounter this issue.
Restart your router regularly. This does not mean every day, but a monthly restart keeps the firmware running cleanly and clears stale connection tables. Many modern routers have a scheduled restart option in their admin panels. Use it.
Keep router firmware updated. Router manufacturers push firmware updates to fix bugs, patch security vulnerabilities, and improve compatibility with ISP infrastructure. Most modern routers can check for updates from within the admin panel. Budget routers from lesser-known brands sometimes stop receiving updates after a year, which is worth keeping in mind when purchasing.
Position your router away from interference sources. Cordless phones, microwaves, and neighboring WiFi networks on the same channel can degrade signal quality to the point where a device stays connected at the network level but cannot maintain a reliable data stream. If you are on a 2.4 GHz band, try switching to 5 GHz for nearby devices, or use your router's admin panel to manually select a less congested channel.
Use a UPS for your networking equipment. Power fluctuations and brief outages are a surprisingly common cause of router and modem instability. An inexpensive uninterruptible power supply smooths out these fluctuations and lets the router shut down cleanly during extended outages rather than being cut mid-operation.
Check for overheating. Routers are often tucked in cabinets or closets with poor airflow. Sustained high temperatures cause firmware instability that manifests exactly as described in this article: seemingly connected but no working internet. Keep your router in an open, ventilated spot, not in a closed drawer.
WiFi connected but no internet is a genuinely fixable problem in almost every situation you are likely to encounter. The key is not to assume the worst immediately. Work through the issue methodically: restart the networking hardware, renew the IP configuration, check DNS, verify whether the issue is isolated to one device or affecting everything, and check your ISP's service status before spending time on device-level fixes.
The comparison table in this guide is worth bookmarking for future reference. Knowing at the outset whether you are dealing with a single-device problem or a network-wide failure cuts troubleshooting time in half by pointing you directly at the right fix category.
If you have worked through every step here and the problem persists, the most likely remaining culprits are a hardware fault in the router or modem, a physical line issue requiring an ISP engineer visit, or a corrupted network stack that may benefit from a full Windows repair or reinstall. That said, the fixes in this guide resolve the issue for the overwhelming majority of users who reach for them.
The most common sudden-onset causes are a router that has silently lost its upstream connection, an IP address lease that expired and was not properly renewed, or an ISP-side issue. Start with a proper router and modem restart, then check your ISP's service status page before doing anything else on your device.
This is almost always a device-specific issue. On the phone, try forgetting the network and reconnecting fresh. Also check whether a VPN app is active. On iPhone, go to Settings, WiFi, tap your network, and make sure "Private WiFi Address" is not causing an authentication issue with your router's access controls.
If you can ping an IP address but cannot load a domain name, DNS is the culprit. Your device can reach the internet numerically but cannot resolve human-readable addresses. Follow Fix 3 above to change your DNS server to Google or Cloudflare, then flush your DNS cache with ipconfig /flushdns on Windows.
It can, but it is a last resort and comes with significant downsides. A factory reset wipes all your settings, including your WiFi name, password, port forwarding rules, and any custom configuration. In most cases the issue can be resolved without going that far. Only consider it if you suspect the router configuration itself has become corrupted and a normal restart does not help.
Recurring connectivity drops often point to an overheating router, a slow firmware bug, or an ISP line quality problem. Log into your router's admin panel and look for any error logs. Also note whether the problem correlates with specific times of day, which can indicate network congestion on your ISP's end. If the router is more than four or five years old, hardware degradation is also worth considering.
Corporate and institutional networks often use captive portals or MAC address filtering. Your personal device may not have been registered on the allowed device list, or a browser-based login page may need to be completed first. Open a browser and try navigating to any HTTP (not HTTPS) site, which often triggers the portal login page. If that does not appear, speak to your IT department about registering your device.
Yes, if the problem is on their end or in the equipment they provided. Before calling, run through the fixes in this guide so you can report what you have already tried. ISPs can remotely check line signal levels and the status of your modem if they supplied it, which can quickly confirm whether the issue is in their infrastructure or on your side of the connection.