Wi-Fi Connected But No Internet? 30+ Fixes for Windows, Mac, iPhone & Android

You look at your laptop. The Wi-Fi icon says you're connected. You open a browser. Nothing. Your phone says Connected without internet. Windows might report No Internet, secured. Your Mac appears connected to Wi-Fi, but websites refuse to load.

So what's actually broken?

This is one of the most common — and most misunderstood — networking problems. The important thing to understand is:

Being connected to Wi-Fi does not necessarily mean you're connected to the internet.

Your device can successfully communicate with your router while the router itself has no working internet connection. Or your internet may actually be working while a DNS, VPN, DHCP, firewall, proxy or device configuration problem prevents you from using it normally.

In this week's Hashtag Electronics Tech Toolkit, we're going to troubleshoot the entire connection chain across Windows, macOS, iPhone and Android. And instead of randomly restarting things until something works, we're going to diagnose the problem properly.

Welcome to the Hashtag Electronics Tech Toolkit.

First: Understand How Your Internet Connection Actually Works

A simplified home or small-business network looks something like this:

Your Device → Wi-Fi → Router/Access Point → Fibre/ONT/Modem → ISP → Internet → Website or Service

Several different things have to work correctly.

Your device needs:

• a working Wi-Fi adapter
• the correct Wi-Fi password
• an IP address
• a default gateway
• DNS servers
• a route to the internet

Your router needs:

• power
• a functioning WAN connection
• a valid ISP connection
• working DHCP
• working DNS forwarding or configured DNS
• correct routing

Your ISP then needs to provide working connectivity beyond your premises. That means a Wi-Fi problem isn't necessarily a Wi-Fi problem.

Troubleshooting Rule #1: Find Out How Many Devices Are Affected

Before changing settings, ask one question:

Is the internet broken on one device or every device?

This immediately divides your investigation.

If every device has no internet — the likely problem is somewhere around the router, fibre ONT, modem, ISP, WAN configuration, DNS or an upstream outage.

If only one device is affected — the problem is more likely to involve that device's Wi-Fi adapter, IP configuration, DNS, VPN, proxy, firewall, network profile, operating system or driver.

This simple test can save enormous amounts of troubleshooting time.

1–4. Quick Tests First

1. Test Another Device

Suppose your laptop has no internet. Take your phone. Connect it to exactly the same Wi-Fi network. Open a few websites.

If the phone works perfectly, your internet connection and router are probably functioning. Your attention should now move toward the laptop.

But if your laptop, phone, tablet and smart TV all fail simultaneously, don't start reinstalling Windows network drivers. The problem probably isn't Windows.

2. Test More Than One Website

Don't assume your internet is down because one website doesn't open. Try several unrelated services — a search engine, a news website, another web service.

If everything works except one website, the problem may be with that website rather than your connection. Technicians should always distinguish between internet failure and application/service failure.

3. Check Your Router and Fibre Equipment

Look at your router. Then look at your fibre ONT or modem if you have separate equipment. Check for power, internet/WAN indicator, optical/PON status, LOS indicator and Ethernet link lights.

Fibre users: pay attention to LOS. On many fibre ONTs, LOS means Loss of Signal. If an LOS indicator suddenly appears red or begins flashing, that can indicate an optical connection problem. Restarting your laptop 14 times isn't going to repair a fibre signal failure. Contact your ISP or fibre network provider if appropriate.

4. Restart the Network Properly

Restarting equipment is legitimate troubleshooting — but do it methodically. For a typical home fibre setup:

1. Shut down or unplug the router.
2. Power-cycle the ONT/modem if appropriate.
3. Wait briefly.
4. Allow the ONT/modem to establish its connection.
5. Power the router back on.
6. Allow it to finish booting.
7. Reconnect your device and test again.

Don't repeatedly pull power every few seconds. Networking equipment needs time to initialise and establish upstream connections.

Windows Troubleshooting

5. Check Your Windows IP Configuration

Open Command Prompt and run:

Look for your active Wi-Fi or Ethernet adapter. You'll typically see IPv4 Address, Subnet Mask, Default Gateway, DHCP Server and DNS Servers. The important question is: did the computer receive a sensible IP address?

6. Watch Out for 169.254.x.x

Suppose your Windows PC shows an address like 169.254.47.18. That is an important clue. Windows may assign itself an Automatic Private IP Address when it cannot successfully obtain an IPv4 address through DHCP.

In practical terms: your computer may be connected at the physical/Wi-Fi level but isn't receiving proper network configuration from DHCP. Now your investigation can focus on DHCP, the router, VLAN/network configuration, the adapter, Wi-Fi authentication or network infrastructure. This is far more useful than simply saying "the Wi-Fi doesn't work."

7. Find Your Default Gateway

Run ipconfig and look for Default Gateway. A common home network might use 192.168.0.1 or 192.168.1.1. Now test it:

Replace that address with your actual gateway. If the gateway responds, your PC can communicate with the local router — excellent. If the gateway doesn't respond, investigate local connectivity first.

8. Ping an Internet IP Address

Try:

This isn't a complete internet diagnostic (some networks filter ICMP), but it can still provide useful information. Suppose ping 8.8.8.8 works but ping google.com doesn't. That immediately makes DNS suspicious. Your internet connection may be working perfectly — your computer simply can't translate domain names into IP addresses.

What Is DNS?

DNS stands for Domain Name System. Humans prefer names like example.com. Computers ultimately communicate using IP addresses. DNS performs the translation. Think of it loosely like the internet's directory service. If DNS fails, your connection can appear completely broken even though the underlying network is functioning.

9. Flush the Windows DNS Cache

You should receive a message indicating that the DNS resolver cache was successfully flushed. Then test again. This can help when Windows has cached outdated or problematic DNS information.

10. Test DNS With nslookup

Windows should query a DNS server and return address information. If DNS queries repeatedly fail while direct IP connectivity works, you've isolated the problem considerably. Technicians should become comfortable with nslookup — it tells you much more than "Chrome doesn't work."

11. Renew Your DHCP Lease

This tells Windows to release and request IPv4 DHCP configuration again.

12. Reset Winsock

Then restart Windows. This can help resolve certain network-stack problems. But don't turn it into a ritual that you run for every Wi-Fi problem. Diagnose first.

13. Reset TCP/IP

A restart is normally required afterward. This resets portions of the Windows TCP/IP configuration. Again: this is a troubleshooting tool, not the first command you should blindly execute.

14. Generate a Windows Wi-Fi Report

Open Command Prompt as Administrator and run:

Windows generates an HTML report containing information about recent wireless activity. It can be extremely useful when diagnosing intermittent Wi-Fi problems. Technicians should add this command to their toolkit.

15. View Saved Wi-Fi Profiles

You'll see Wi-Fi profiles stored on the computer. This can help when diagnosing old or incorrect wireless configurations.

16. Forget and Reconnect to the Wi-Fi Network

In Windows 11, go to your Wi-Fi/network settings and manage known networks. Forget the affected network. Then reconnect using the correct credentials. This recreates the profile. Don't do this unless you know the Wi-Fi password.

17. Check the Wi-Fi Adapter in Device Manager

Open Device Manager → Network adapters. Look for your wireless adapter. Warning signs include yellow warning symbols, a missing adapter, a disabled adapter or repeated driver errors. You can inspect Properties → Device status. If the wireless adapter disappeared after a Windows update, driver problems become a strong possibility.

18. Don't Install Random "Driver Updater" Software

If you need a network driver, get it from your laptop manufacturer, motherboard manufacturer, adapter manufacturer, or Windows Update where appropriate. Avoid random websites promising to "update all drivers automatically." Drivers operate deeply within the operating system. Treat them accordingly.

19. Check Whether a VPN Is Breaking Connectivity

If you're using a corporate VPN, privacy VPN, security VPN or work remote-access software, temporarily disconnect it for testing if your environment permits. If internet access immediately returns, investigate VPN configuration, DNS, routes, split tunnelling or firewall policies. For business users, don't simply uninstall company security software — escalate appropriately.

20. Check Windows Proxy Settings

A misconfigured proxy can make the internet appear broken. Look under Settings → Network & Internet → Proxy. If a proxy is configured unexpectedly, investigate why. Business environments may legitimately use proxies. Don't disable corporate configuration without understanding the environment.

21. Use tracert to See Where Traffic Stops

or, for a direct IP test:

tracert attempts to show the path traffic follows toward its destination. It's useful when connectivity exists but traffic fails somewhere further upstream. Timeouts don't automatically prove a router is broken because some infrastructure doesn't respond to these probes. Interpret results rather than blindly reading them.

22. PowerShell: Test-NetConnection

You can also test a specific TCP port:

This is particularly useful for technicians. A server may respond to certain network tests while a required application port is unavailable.

macOS Troubleshooting

Mac users can apply the same diagnostic logic. The commands change. The principles don't.

23. Forget and Rejoin Wi-Fi on Mac

Open Wi-Fi settings and review the known network. Forget the problematic network if appropriate and reconnect. Again, make sure you know the password first.

24. Check the Mac's IP Address

macOS provides network information through System Settings, but Terminal gives technicians additional visibility. One useful command is:

It displays network-interface information. The output can look intimidating because macOS may show numerous interfaces. You're looking for the active interface and its addressing information.

25. Find the Default Route on macOS

This can reveal information about the default network route, including the gateway. Once you know the gateway, test it.

26. Test Connectivity From Terminal

Stop the continuous ping with Control + C. You can also test an IP address directly:

The same diagnostic principle applies: IP works + domain fails = investigate DNS.

27. Check DNS Configuration on macOS

This provides information about the DNS resolver configuration macOS is using. Particularly useful for technicians diagnosing VPN DNS, multiple interfaces, enterprise configurations or unusual resolver behaviour.

28. Renew DHCP on Mac

Ordinary users can often renew DHCP through the network interface's TCP/IP configuration in macOS System Settings. If the Mac has an obviously incorrect IP configuration, renewing the lease is a reasonable troubleshooting step.

iPhone Wi-Fi Troubleshooting

29. Turn Wi-Fi Off and Back On

Simple? Yes. Useful? Also yes. If your iPhone has become stuck in an unusual network state, toggling Wi-Fi can force it to reconnect. But if the problem immediately returns, don't keep toggling forever — move deeper.

30. Forget the Wi-Fi Network on iPhone

Go to Settings → Wi-Fi. Tap the information button beside the network and choose Forget This Network. Then reconnect. This is particularly useful if the password changed, authentication changed, or the saved network configuration is problematic. Make sure you know the password first.

31. Check iPhone IP and Router Information

Under the Wi-Fi network's information page, inspect details such as IP Address, Subnet Mask, Router and DNS. This information can immediately tell a technician whether the iPhone has received sensible network configuration.

32. Test Wi-Fi Against Mobile Data

This is one of the best smartphone troubleshooting techniques. Disable Wi-Fi. Test using cellular data. If mobile data works, the problem probably relates to the Wi-Fi network rather than the entire phone. If neither works, your investigation becomes broader. This technique applies equally to Android.

33. Check VPN Configuration on iPhone

If a VPN is active, temporarily disconnect it as a diagnostic test when appropriate. If connectivity immediately returns, investigate the VPN rather than repeatedly resetting Wi-Fi.

34. Reset Network Settings — But Understand What It Does

iPhone provides a network-settings reset option. This can be useful when persistent networking problems survive ordinary troubleshooting. But don't treat it casually. Resetting network settings can remove saved network-related configuration, including remembered Wi-Fi networks. Make sure you understand the consequences before proceeding. It should be a later troubleshooting step, not step one.

Android Wi-Fi Troubleshooting

Android menus differ between Samsung, Google Pixel, Xiaomi, HONOR, OPPO, Huawei and other manufacturers, but the troubleshooting logic remains consistent.

35. Check Whether Android Says "Connected Without Internet"

Android can sometimes explicitly indicate that the Wi-Fi connection itself exists but internet validation has failed. That's an important distinction. The phone can see and communicate with the access point. Now investigate the router internet connection, DHCP, DNS, captive portal, VPN or upstream network.

36. Forget and Reconnect to Wi-Fi on Android

Usually: Settings → Wi-Fi / Connections → Select Network → Forget. Then reconnect. Menu names vary by manufacturer.

37. Check Android IP Settings

Open the connected Wi-Fi network's details. Depending on your phone, you may be able to view IP address, gateway, DNS, MAC address, link speed and security type. Technicians should get into the habit of inspecting this information before resetting anything.

38. Private DNS Can Break Internet Access

Modern Android provides Private DNS functionality. It's useful for privacy and security. But a misconfigured Private DNS hostname can cause websites and applications to stop resolving. If Android suddenly has strange DNS problems, inspect Settings → Network & Internet / Connections → Private DNS. The exact path varies. If someone manually configured a DNS provider incorrectly, this can explain the problem.

39. Randomised MAC Addresses Can Matter on Managed Networks

Modern smartphones use privacy features that can randomise the MAC address presented to Wi-Fi networks. This is generally a good privacy feature. But in certain business, hotel, campus or access-controlled networks, MAC-based authentication or registration may interact poorly with private/randomised addresses. Don't disable privacy features by default — but technicians should know they exist when troubleshooting managed networks.

40. Captive Portals: The Hotel Wi-Fi Problem

Ever connected to hotel Wi-Fi, airport Wi-Fi, shopping-centre Wi-Fi or university Wi-Fi and had full Wi-Fi signal but no internet? You may need to complete a captive portal — the webpage asking you to accept terms, enter room details, provide an email, enter a voucher or authenticate.

If the portal doesn't automatically appear, open a browser and attempt to visit a normal webpage. The network may redirect you to its login page.

41–50. Extra Practical Guidance

41. "Connected, No Internet" After a Power Failure?

South African homes and businesses experience another common scenario. Power returns. The router starts. Wi-Fi becomes visible. Everyone connects. But there's no internet.

Why? Because the Wi-Fi access point can become operational before the fibre ONT finishes synchronising, the modem reconnects, the WAN session establishes, or upstream infrastructure recovers. Give the network equipment time to initialise. Check the ONT and WAN indicators before resetting every device.

42. Router Placement Matters

Poor Wi-Fi performance isn't always an ISP speed problem. Your router might be inside a cabinet, behind a television, on the floor, surrounded by metal, at one end of a large house, or several concrete walls away. Wi-Fi is radio. Physical environment matters.

Try positioning the router centrally, elevated, unobstructed and away from unnecessary interference. For larger homes and offices, consider properly designed additional access points, mesh Wi-Fi or wired Ethernet backhaul rather than simply purchasing the router with the largest number of antennas on the box.

43. 2.4 GHz vs 5 GHz vs 6 GHz

• 2.4 GHz — generally offers better range and wall penetration but is often more congested and provides lower performance.
• 5 GHz — usually provides higher performance with shorter practical range than 2.4 GHz.
• 6 GHz — available with newer Wi-Fi generations and compatible devices, providing additional spectrum but requiring compatible hardware and having propagation characteristics that make network design important.

The "fastest" band isn't always the best connection from every room.

44. Ethernet Is Still Extremely Useful

Wi-Fi is convenient. Ethernet is predictable. For desktops, servers, NAS devices, workstations, gaming PCs, business VoIP infrastructure and access points, wired Ethernet often provides lower latency, greater consistency, reduced wireless congestion and easier diagnostics. A properly designed network uses the right technology for the right endpoint.

45. Slow Internet? Measure It Correctly

Before complaining that you're not getting your advertised internet speed, consider Wi-Fi signal strength, device capability, router capability, Ethernet port speed, Wi-Fi standard, interference, server location, network congestion, VPN and background downloads. For a more meaningful ISP test, technicians often connect a capable computer directly via Ethernet where possible. This removes Wi-Fi as a variable.

46. Understand Mbps vs MB/s

This causes endless confusion. Internet providers usually advertise speed in Mbps (megabits per second). File transfers are frequently displayed in MB/s (megabytes per second). There are eight bits in a byte. So a nominal 100 Mbps connection does not mean you'll download files at 100 MB/s. The theoretical conversion before overhead is approximately 12.5 MB/s. Understanding units prevents a lot of false troubleshooting.

47. Don't Ignore the Cable

If you're troubleshooting wired networking, inspect the Ethernet cable, connectors, wall jack, patch panel, switch port and router port. A damaged cable can produce no link, intermittent connectivity, reduced negotiated speed or packet loss. Technicians shouldn't spend an hour rebuilding TCP/IP when swapping one known-good patch cable can isolate the problem in 30 seconds.

48. Check the Link Speed

Suppose you expect gigabit Ethernet but the connection negotiates at 100 Mbps. Investigate the cable, termination, switch port, NIC, router, power-saving features or configuration. One damaged pair can create strange Ethernet behaviour. Physical layer first. Software layer second.

49. Business Networks: Check VLANs

In business environments, the device can have a valid IP, good Wi-Fi signal and a working adapter — and still be on the wrong network. Check VLAN assignment, switch port configuration, SSID-to-VLAN mapping, DHCP scope, firewall policy, NAC and access-control rules. This is why enterprise troubleshooting differs from resetting a home router.

50. Don't Forget DHCP Exhaustion

Suppose a business network has a DHCP scope that can only provide a limited number of addresses. Eventually all leases may be consumed. New devices connect to Wi-Fi but can't obtain usable network configuration. This can look like random Wi-Fi failure. Technicians should inspect the DHCP scope rather than restarting every access point.

A Better Technician Troubleshooting Sequence

When someone says "The internet isn't working," don't immediately restart the router. Use a structured approach:

1. Define the scope — One device or everyone?
2. Identify the connection — Wi-Fi or Ethernet?
3. Check physical/link status — Connected? Signal? Cable?
4. Inspect IP configuration — Valid IP? Gateway? DNS?
5. Test the gateway — Can you reach the router?
6. Test an external IP — Can you reach beyond the LAN?
7. Test DNS — Can domain names resolve?
8. Test applications — Browser? Email? VPN? Specific service?
9. Inspect security/network services — Firewall? Proxy? VPN? Private DNS?
10. Escalate outward — Router → ONT/modem → ISP → upstream service.

This is considerably more efficient than "Restart everything and hope."

Quick Command Cheat Sheets

Windows

• ipconfig — View basic IP configuration
• ipconfig /all — View detailed network configuration
• ipconfig /flushdns — Clear the DNS resolver cache
• ipconfig /release then ipconfig /renew — Request fresh DHCP configuration
• ping 192.168.1.1 — Test your gateway (replace with your actual gateway)
• ping 8.8.8.8 — Test basic external IP connectivity
• ping google.com — Test connectivity plus DNS resolution
• nslookup google.com — Query DNS
• tracert google.com — Inspect the network path
• netsh wlan show profiles — View saved Wi-Fi profiles
• netsh wlan show wlanreport — Generate a Windows wireless report
• netsh winsock reset — Reset Winsock when appropriate

macOS Terminal

• ifconfig — View network interfaces
• route -n get default — Inspect the default route
• ping google.com — Test connectivity and name resolution
• ping 8.8.8.8 — Test IP connectivity
• scutil --dns — Inspect DNS configuration

Frequently Asked Questions

Don't Just Restart It — Understand It

There's nothing wrong with restarting a router. There's nothing wrong with restarting a laptop. The problem is when restarting becomes your entire troubleshooting strategy.

A good technician asks: Where does communication stop? Can the device reach the access point? Can it obtain an IP address? Can it reach its gateway? Can it reach an external IP? Can it resolve DNS? Can it reach the required service?

Every successful test eliminates possibilities. And that's the difference between guessing and diagnosing.

Technical note: Commands and settings in this guide can vary according to operating-system version, device manufacturer and network configuration. Business users should consult their IT administrator before resetting corporate network, VPN, security, DNS or proxy configurations. This guide is intended for educational and troubleshooting purposes.