by Tommy N. Updated Apr 12, 2026
Few things are more frustrating than seeing your device show "Connected" to WiFi while displaying "No Internet" or "No Internet Access" at the same time. This connected but no internet error means your device has successfully authenticated with your router and received an IP address, but it cannot reach anything beyond your local network. The problem affects Windows PCs, Macs, iPhones, Android phones, and every other WiFi device equally.
The causes range from simple (your ISP is down) to more technical (DHCP conflicts, DNS failures, or incorrect gateway settings). This guide provides systematic fixes for every platform, starting with the quickest solutions and progressing to more advanced troubleshooting.
Understanding the root cause helps you fix the problem faster. When your device connects to WiFi, several things must happen for internet access to work: your device must receive a valid IP address from the router via DHCP, the router's DNS settings must correctly resolve domain names, the router's gateway must have a working connection to your ISP, and there must be no IP address conflicts with other devices on the network.
When any of these steps fails, you get the characteristic "connected but no internet" status. The most common causes include:
| Cause | Description | Frequency |
|---|---|---|
| ISP outage | Your internet provider is experiencing a service disruption | Very common |
| DNS failure | DNS server is unreachable or returning errors | Very common |
| DHCP issue | Router failed to assign a valid IP address or lease expired | Common |
| IP address conflict | Two devices on the network have the same IP address | Common |
| Wrong gateway/subnet | Device has incorrect network configuration | Occasional |
| Router WAN failure | Router's connection to modem is interrupted | Occasional |
| MAC filtering | Router is blocking your device's MAC address from internet access | Rare |
| Captive portal | Network requires login (hotel, cafe) that hasn't been completed | Situational |
Before diving into platform-specific solutions, try these universal fixes that resolve the majority of "connected but no internet" issues. They take less than five minutes total.
1. Restart your router and modem. Unplug your modem first, wait 30 seconds, plug it back in, and wait for all lights to stabilize (usually 1–2 minutes). Then unplug your router, wait 30 seconds, and plug it back in. This clears cached DNS entries, resets DHCP leases, and re-establishes the WAN connection. This single step fixes the problem roughly 50 percent of the time.
2. Toggle WiFi off and on. On your device, turn WiFi off, wait 10 seconds, and turn it back on. This forces your device to request a fresh IP address from the router and re-establish the connection from scratch.
3. Forget and reconnect to the network. Go to your device's WiFi settings, select your network, choose "Forget" or "Remove," then reconnect by entering your password again. This clears any corrupted connection data stored on your device.
4. Check if it's an ISP outage. Try connecting to the internet using your mobile data (turn off WiFi on your phone). If websites load on mobile data, your home internet is the problem. Check your ISP's status page or social media accounts for outage reports in your area.
Pro Tip: If only one device shows "connected but no internet" while other devices work fine, the problem is with that specific device. If all devices are affected, the issue is with your router, modem, or ISP. This distinction dramatically narrows down the troubleshooting path.
Windows provides built-in tools and commands that can diagnose and fix most connectivity issues. Open Command Prompt as Administrator (search for "cmd," right-click, "Run as administrator") and run these commands in order.
Open Settings, navigate to Network & Internet, and click "Network troubleshooter" (Windows 11) or go to Troubleshoot > Additional troubleshooters > Internet Connections (Windows 10). The built-in diagnostics can automatically detect and fix common configuration problems like incorrect DNS settings or disabled network adapters.
Open Command Prompt as Administrator and run these commands in sequence:
ipconfig /release ipconfig /renew
This tells your computer to release its current IP address and request a new one from the router via DHCP. If the problem was a stale or conflicting IP lease, this resolves it immediately.
Corrupted DNS cache entries are a frequent cause of "connected but no internet." Clear them with:
ipconfig /flushdns
You should see the message "Successfully flushed the DNS Resolver Cache." After flushing, try loading a website. If this alone fixes the problem, your device had cached a bad DNS entry.
If the previous steps didn't help, reset the entire networking stack:
netsh winsock reset netsh int ip reset
Restart your computer after running these commands. This resets all networking protocols to their default state, fixing corruption that simple flushing can't address.
| Command | Purpose | Requires Restart |
|---|---|---|
ipconfig /release | Release current IP address lease | No |
ipconfig /renew | Request new IP from DHCP server | No |
ipconfig /flushdns | Clear cached DNS entries | No |
netsh winsock reset | Reset Winsock catalog to clean state | Yes |
netsh int ip reset | Reset TCP/IP stack to default | Yes |
netsh int ip reset resetlog.txt | Reset TCP/IP with log file | Yes |
If your ISP's DNS server is the problem, switching to a public DNS provider can restore access immediately. Open Network & Internet settings, click your WiFi connection, choose "Edit" next to DNS server assignment, and switch from Automatic to Manual. Enter 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) as the preferred DNS, and 1.0.0.1 or 8.8.4.4 as the alternate. For a permanent fix at the network level, change the DNS on your router directly.
macOS handles network configuration differently than Windows, but the troubleshooting principles are the same. Open Terminal (Applications > Utilities > Terminal) for command-line fixes.
Renew DHCP Lease: Go to System Settings > Network > WiFi > Details > TCP/IP, and click "Renew DHCP Lease." This is the macOS equivalent of ipconfig /renew on Windows. Alternatively, from Terminal run:
sudo ipconfig set en0 DHCP
Flush DNS Cache: Run the following command in Terminal:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Change DNS: In System Settings > Network > WiFi > Details > DNS, remove existing entries and add 1.1.1.1 and 1.0.0.1. Click OK and Apply.
If none of these work, try creating a new Network Location (System Settings > Network > the three-dot menu > Locations > Edit Locations > Add). This creates a fresh network configuration without any cached settings from the old one.
On iPhone, go to Settings > WiFi, tap the (i) icon next to your connected network, and try these in order: tap "Renew Lease" to get a fresh IP address. If that doesn't work, scroll down to "Configure DNS," switch from Automatic to Manual, and add 1.1.1.1 and 8.8.8.8 as your DNS servers. As a last resort, go to Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. This erases all saved WiFi passwords and network configurations, so make sure you have your WiFi passwords available before proceeding.
On Android, go to Settings > Network & Internet > WiFi, long-press your connected network, tap "Modify network" or the gear icon, then select "Advanced" or "IP settings." Change from DHCP to Static, enter your router's IP address as the gateway (usually 192.168.1.1 or 192.168.0.1), set DNS 1 to 1.1.1.1 and DNS 2 to 8.8.8.8, then save. If this doesn't work, try Settings > System > Reset options > Reset WiFi, mobile & Bluetooth.
Warning: Resetting network settings on any device (Windows, Mac, iPhone, or Android) will erase all saved WiFi passwords, VPN configurations, and paired Bluetooth devices. Only use network reset as a last resort, and make sure you have your WiFi password written down before proceeding.
If the problem affects all devices on your network, the issue is likely with the router or modem rather than individual devices. Log into your router's admin panel at 192.168.1.1 or 10.0.0.1 and check the following settings.
Check WAN Status: Look for the WAN or Internet status page. It should show a valid IP address assigned by your ISP. If it shows 0.0.0.0 or no IP, the connection between your router and modem (or ISP) is broken. Try rebooting the modem and checking the Ethernet cable between modem and router.
Verify DHCP is Enabled: Your router's DHCP server should be enabled with a range like 192.168.1.100 to 192.168.1.254. If DHCP is disabled, devices won't receive IP addresses automatically and will show "connected but no internet" unless manually configured with a static IP address.
Check MAC Filtering: If MAC address filtering is enabled on your router, make sure your device's MAC address is on the allowed list. An incorrectly configured filter can block internet access while still allowing the WiFi connection itself.
Factory Reset (Last Resort): If nothing else works at the router level, a factory reset restores all settings to defaults. You'll need to reconfigure your WiFi name, password, and any custom settings afterward.
Contact your Internet Service Provider when: all devices show "connected but no internet" and router reboot doesn't fix it; your modem's internet light is off or blinking (indicating no signal from the ISP); wired connections directly through the modem also have no internet; the problem persists for more than 30 minutes after a full modem and router restart; or your ISP's status page shows an outage in your area. When calling, have your account number ready and be prepared to report the troubleshooting steps you've already taken. Ask the ISP to check the signal levels to your modem remotely—they can often diagnose line problems and send a technician if needed.
Refer to Microsoft's official WiFi troubleshooting guide for additional Windows-specific diagnostics and tools that may help resolve persistent connectivity issues.
Pro Tip: Keep a record of your network settings—router IP, DNS servers, WiFi passwords, and ISP account number—stored somewhere accessible even without internet (like a note on your phone or a printed sheet). When connectivity problems strike, having this information on hand saves significant troubleshooting time.
Key Takeaways:
ipconfig /release, ipconfig /renew, and ipconfig /flushdns to resolve most device-side problems.Your phone has successfully connected to the WiFi router but the router itself has lost internet access, or your phone has received incorrect network configuration (wrong DNS or gateway). Try toggling WiFi off and on, forgetting and reconnecting to the network, or manually setting DNS to 1.1.1.1 in your WiFi settings.
Yes, a damaged or loose Ethernet cable between your modem and router can cause the router to broadcast WiFi normally while having no actual internet connection. Check that the cable connecting your modem to your router's WAN port is firmly seated and undamaged. Try replacing it with a known good cable.
After a power outage, your modem and router may boot up in the wrong order, or your ISP's network equipment may still be recovering. Your modem needs to fully synchronize with the ISP before the router can establish a WAN connection. Wait 5 minutes after power restoration, then reboot your modem followed by your router.
Almost certainly not. While unauthorized access could theoretically cause connectivity issues, it's extremely unlikely. The vast majority of "connected but no internet" cases are caused by routine issues like DNS failures, DHCP problems, or ISP outages. However, it's always good practice to ensure your router has a strong admin password.
Open Command Prompt as administrator and run these commands in order: ipconfig /release, ipconfig /renew, ipconfig /flushdns. If that doesn't work, run netsh winsock reset and netsh int ip reset, then restart your computer. Finally, try changing your DNS to 1.1.1.1 in Network settings.
When only one device is affected, the problem is device-specific. Common causes include a corrupted DNS cache, expired DHCP lease, VPN software interfering with the connection, or a firewall blocking internet access. Start by flushing DNS and renewing your IP lease on that specific device.
Yes, VPN software can cause this issue if the VPN server is unreachable, the VPN client has a bug, or the VPN's DNS settings conflict with your network. Try disconnecting the VPN and testing your connection. If internet works without the VPN, the VPN configuration or server is the problem.
 |
 |
 |
 |
About Tommy N.
Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
|
|
|
|
