WiFi Connected but No Internet? Find the Broken Link

If WiFi is connected but there is no internet, test another device on the same network first. If only one device fails, restart it, forget and rejoin WiFi, then disable its VPN or proxy for a test. If every device fails, check the modem, ONT, router, and ISP. On hotel, airport, or cafe WiFi, open a browser and complete the network’s sign-in page.

Connected to WiFi does not mean connected to the internet

The WiFi icon confirms a wireless link between your device and a router or access point. It does not confirm that the router has a working path to the internet. The broken part might be one phone, the wireless network, the router’s internet connection, a DNS service, or the ISP.

1. Find out whether one device or every device is affected

Use a second phone, tablet, or computer on the same WiFi network. Open more than one familiar website. A single site can be offline even when your connection works.

• If the second device works, keep the router running and troubleshoot the first device.
• If no device works, move to the modem, ONT, router, and ISP checks.
• If one network name fails but another works, compare the main and guest networks.
• If Ethernet works while WiFi fails, concentrate on the wireless side.

When one device is the exception, the guide to WiFi not working on one device provides a longer device-specific path.

2. Complete the sign-in page on public WiFi

Hotels, airports, cafes, campuses, and guest networks often use a captive portal. You connect to WiFi first, then accept terms, enter a room number, or complete another sign-in step before internet access begins.

1. Open a regular browser window and visit a simple website.
2. Look for a notification that asks you to sign in to the network.
3. If no page appears, forget the public network and join it again.
4. Temporarily disconnect a VPN that might prevent the portal from loading.

Apple’s captive-network guidance follows this connect-then-login flow. Treat an unfamiliar public network carefully. Do not send banking, identity, or work credentials to a page unless you have confirmed who operates the network and why the information is required.

3. Fix the one-device branch

Restart the affected phone or computer. Turn WiFi off and back on, then forget the saved network and join it again with the correct password. This replaces a stale saved profile without changing the router for everyone else.

For one comparison, disable a VPN, proxy, privacy filter, or third-party security app that changes network traffic. Re-enable it after the test. If internet access returns, update or repair that app rather than leaving protection disabled.

Check that the device uses automatic IP and DNS settings unless your network administrator gave you fixed values. An old manual address from another network can connect to WiFi but fail to reach the correct router.

4. Restart the home network without resetting it

If every device is offline, restart the network equipment. A restart does not erase settings. A factory reset does.

1. Save work that depends on the network.
2. Turn off the router and modem or ONT. Some homes use one combined gateway.
3. Wait about 30 seconds.
4. Power the modem or ONT first and wait until its normal connection lights return.
5. Power the router and allow it to finish starting.
6. Reconnect one device and test again.

Do not press and hold a reset button. A factory reset can erase the WiFi name, admin password, ISP login, parental controls, port rules, and other settings. Use it only with a recovery plan and the provider or manufacturer instructions for your model.

5. Check cables, lights, and ISP status

Confirm that the internet cable has not come loose. Fiber service normally reaches an ONT. Cable service uses a coax connection to a modem or gateway. DSL uses a telephone-line connection. Do not move a fiber connector or open provider equipment if you are unsure how it is installed.

Look for a red, amber, or unusual internet, WAN, optical, or alarm light. Light names differ by device, so compare them with the ISP or manufacturer guide instead of guessing. Check the provider’s outage page or app using mobile data.

If the ISP reports an outage, local DNS changes and router replacements will not restore the service. Wait for the provider update, then restart only if its instructions ask you to.

6. Use Ethernet as a control

Connect a laptop to a LAN port on the main router and turn off WiFi on that laptop. If Ethernet reaches the internet, the modem or ISP path is working well enough for the test. Focus on the router’s wireless settings, access controls, and the affected WiFi devices.

If Ethernet and WiFi both fail, stay on the gateway and ISP branch. Do not buy a stronger wireless router based on signal bars when the wired connection has the same problem.

7. Check the Windows connection

Windows users should restart the PC, forget and rejoin the network, and install the network-adapter update offered by Windows Update or the hardware manufacturer. Microsoft’s WiFi troubleshooting guide also recommends comparing other devices, checking the router, and using Network reset only after earlier steps fail.

Network reset removes and reinstalls network adapters and returns their settings to defaults. Record VPN software, virtual adapters, fixed IP addresses, and other custom network settings before using it.

If Windows reports that the DNS server is not responding, use the separate Windows 11 DNS troubleshooting guide. Do not assume every “no internet” message is a DNS failure.

8. Test DNS only when the evidence points there

DNS translates a website name into an IP address. If the router and public internet path work but names do not resolve, DNS becomes a reasonable suspect. On Windows, open Command Prompt and compare:

ping -n 10 1.1.1.1
nslookup example.com

The first command tests a public IP address. The second asks the configured DNS service for the address of example.com. Some networks give ping traffic low priority, so treat the result as a clue. If both commands fail, changing DNS alone is unlikely to repair the connection.

If the public IP responds but nslookup repeatedly fails, return the device to automatic DNS or use a reputable DNS service according to its official setup guide. Change one device first. Do not change the router for the whole household until the smaller test works.

9. Check the router’s internet status

Open the router’s official app or local administration page and find its Internet or WAN status. Check whether it received an internet address and whether it reports disconnected, authentication failed, or another specific error. Menu names vary, so use the model’s manual.

If the problem began after adding a second router, make sure the internet cable reaches the correct WAN port and the new device uses the intended router or access-point mode. Two active routing layers can also complicate games, port forwarding, and remote access. The double NAT guide explains that separate issue, but double NAT is not a universal explanation for complete loss of internet.

Avoid fixes that erase useful evidence

• Do not factory-reset the router before recording its status and settings.
• Do not install a random “WiFi repair” app.
• Do not disable the firewall or security software permanently.
• Do not copy a fixed IP, gateway, or DNS address from a stranger’s network.
• Do not replace the router until a wired comparison shows where the failure begins.

What to tell the ISP

Contact the ISP when every device remains offline after a normal restart, especially when Ethernet also fails or the modem or ONT shows an unusual service light. Provide the start time, equipment model, light status, restart result, and whether the provider app reports an outage.

Ask the ISP to check the line, account provisioning, modem or ONT status, and known area incidents. Do not post your public IP address, account number, or private support logs in a public forum.

Choose the next action from the evidence

Start with the one-device versus every-device split. That comparison tells you whether to leave the router running or move to the gateway and ISP checks. Continue through public sign-in, restart, Ethernet, Windows, DNS, and ISP checks only as the evidence requires.

Sources

• Microsoft Support: fix WiFi connection issues in Windows
• Apple Support: use captive WiFi networks
• Google Home Help: troubleshoot slow internet and WiFi
• Microsoft Learn: nslookup command
• Cloudflare 1.1.1.1 setup guide