Wi-Fi Connected but No Internet? How to Diagnose and Fix It

Connected to Wi-Fi but No Internet Access? 9 Step-by-Step Fixes

Seeing a strong Wi-Fi signal does not necessarily mean that your device has Internet access. Your laptop, smartphone, tablet, or smart TV can be successfully connected to the wireless network while the router itself has lost its connection to the Internet.

When this happens, you may see messages such as "Connected, no internet," "No Internet access," or "Connected without Internet."

The important thing is to identify where the connection is failing. The problem could be limited to your device, or it could involve DHCP, DNS, the router's LAN, the WAN connection, or your Internet Service Provider (ISP).

This guide uses a systematic troubleshooting approach for Windows, macOS, Android, and iOS, starting with simple solutions and progressing to practical network diagnostics.

Quick Diagnostics by Operating System

Step 1: Restart Your Modem and Router

Before changing network settings, start with the simplest solution: restart your network equipment.

A temporary problem with the router, DHCP service, or WAN connection can sometimes be resolved by restarting the equipment and allowing its network services to initialize again.

1. Unplug the modem or ONT and Wi-Fi router from power.
2. Wait approximately 30 seconds.
3. Plug the modem or ONT back in first.
4. Wait until its connection and status indicators stabilize.
5. Turn the router back on.
6. Wait two or three minutes for the router to complete its startup process.
7. Reconnect your device to Wi-Fi and test the Internet.

If the problem comes back immediately, continue with the diagnostic steps below rather than repeatedly restarting the equipment.

Step 2: Check Whether Other Devices Have Internet Access

This is one of the most important troubleshooting steps because it helps determine whether the problem is local to one device or affects the entire network.

Connect another phone, computer, or tablet to the same Wi-Fi network and try opening a website.

If only one device is affected

The problem is more likely to be specific to that device. Possible causes include:

• Incorrect IP configuration
• DHCP problems
• A corrupted Wi-Fi profile
• DNS configuration
• VPN or proxy software
• Firewall or security software
• Wireless adapter or driver problems

If every device is affected

The problem is more likely to involve:

• The router
• The modem or ONT
• The WAN connection
• Upstream routing
• An ISP service outage

This simple test can prevent you from changing settings on a device that is actually working correctly.

Step 3: Forget the Wi-Fi Network and Reconnect

A damaged or outdated saved Wi-Fi profile can sometimes cause connection and configuration problems.

Forgetting the network removes the saved profile and allows the device to establish a fresh connection.

Windows

Go to:

Settings → Network & Internet → Wi-Fi → Manage known networks

Select your Wi-Fi network and click Forget.

Android

Open:

Settings → Network & internet → Internet

Select your Wi-Fi network, open its settings, and choose Forget.

The exact menu names can vary depending on the Android manufacturer and operating-system version.

iPhone or iPad

Go to:

Settings → Wi-Fi

Tap the Info (i) button next to your network and select Forget This Network.

macOS

Go to:

System Settings → Network → Wi-Fi

Open the saved network settings and remove the network from the list.

Reconnect afterward and enter the Wi-Fi password again.

Step 4: Reset the Windows Network Stack

If the problem occurs on a Windows computer, resetting the network stack can help resolve problems involving Winsock, TCP/IP configuration, DHCP, or the local DNS resolver cache.

Microsoft recommends these network commands as part of Windows connectivity troubleshooting. :contentReference[oaicite:1]{index=1}

Open Command Prompt as Administrator

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.

Run these commands one at a time and in this order:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Then restart your computer.

What do these commands do?

• netsh winsock reset — resets the Windows Winsock catalog.

• netsh int ip reset — resets TCP/IP configuration.

• ipconfig /release — releases the current DHCP lease.

• ipconfig /renew — requests a new IP configuration.

• ipconfig /flushdns — clears the local DNS resolver cache.

If the problem is caused by an inconsistent or corrupted network configuration, these commands can restore normal connectivity.

Step 5: Check or Change Your DNS Server

The Domain Name System (DNS) translates domain names such as google.com into IP addresses.

If your device has Internet connectivity but cannot communicate properly with its DNS resolver, websites may appear inaccessible even though the underlying network connection is still working.

Google Public DNS

• Primary: 8.8.8.8
• Secondary: 8.8.4.4

Cloudflare DNS

• Primary: 1.1.1.1
• Secondary: 1.0.0.1

Windows

Go to:

Control Panel → Network and Sharing Center → Change adapter settings

Right-click your active Wi-Fi adapter and select:

Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties

Choose Use the following DNS server addresses and enter the DNS servers you want to use.

Android

On Android devices that support Private DNS, go to:

Settings → Network & internet → Private DNS

Select Private DNS provider hostname and enter:

dns.google

for Google Public DNS, or:

1dot1dot1dot1.cloudflare-dns.com

for Cloudflare.

Android's exact settings can vary depending on the device manufacturer and Android version. Google recommends keeping Private DNS enabled on compatible Android devices. :contentReference[oaicite:2]{index=2}

macOS

Go to:

System Settings → Network → Wi-Fi → Details → DNS

Add your preferred DNS server.

Important: Changing DNS will not repair a failed WAN connection. If your router has completely lost its connection to the ISP, switching DNS providers will not restore Internet access.

Step 6: Temporarily Disable VPNs, Proxies, and Security Software

VPN applications, proxy configurations, and some security products can modify or filter network traffic.

For example, a VPN kill switch may intentionally block Internet traffic when the VPN tunnel is disconnected. In that situation, your computer can remain connected to the local Wi-Fi network while Internet traffic is blocked.

Temporarily check whether the problem persists after disabling:

• VPN applications
• Manual proxy settings
• Third-party firewall software
• Network security suites
• Browser proxy extensions

Then test the connection again.

If Internet access returns, identify which application or configuration was responsible and re-enable your security software afterward.

Apple also recommends investigating VPN and security software when Wi-Fi connectivity problems persist. :contentReference[oaicite:3]{index=3}

Step 7: Check Your Date and Time

An incorrect system clock can cause problems with secure HTTPS connections because TLS certificates have defined validity periods.

If the system date or time is significantly incorrect, browsers and applications may reject otherwise valid security certificates.

Make sure your device is configured to synchronize its date and time automatically.

Windows

Go to:

Settings → Time & language → Date & time

Enable:

Set time automatically

This is not normally the first cause to investigate when there is a complete loss of Internet connectivity, but it becomes relevant when basic connectivity works while secure websites or applications fail.

Step 8: Check Your IP Address and Default Gateway

Your device needs a valid IP address and a default gateway to communicate outside the local network.

Typical private IPv4 addresses include:

192.168.1.x
192.168.0.x
10.0.0.x

On Windows

Open Command Prompt and run:

ipconfig

Find your active Wi-Fi adapter and look for:

IPv4 Address

and:

Default Gateway

Check for a 169.254.x.x Address

If your device has an address such as:

169.254.25.18

it has assigned itself an Automatic Private IP Addressing (APIPA) address.

In a typical DHCP-based home network, seeing this type of address means the device did not obtain a normal IPv4 address from the DHCP server.

Potential causes include:

• DHCP problems
• Router configuration issues
• Wi-Fi connection problems
• Network adapter issues
• A temporarily unavailable DHCP server

What if the Default Gateway is blank?

A missing default gateway means the device does not have a configured route for traffic leaving the local network.

That can explain why the device appears connected to Wi-Fi but cannot reach the Internet.

Step 9: Diagnose the Connection Layer by Layer

If the previous steps did not solve the problem, stop guessing and test the network systematically.

The following tests help determine whether the problem exists inside the device, between the device and router, beyond the router, or at the DNS layer.

Test 1: Test the Local TCP/IP Stack

Open Command Prompt or Terminal and run:

ping 127.0.0.1

The address 127.0.0.1 is the local loopback address.

If this test fails, investigate the local TCP/IP stack or loopback interface before continuing with external connectivity tests.

Test 2: Test Your Router

First find the Default Gateway using:

ipconfig

For example, your gateway might be:

192.168.1.1

Then run:

ping 192.168.1.1

Replace the example address with your actual gateway.

If the gateway responds

Your device can communicate with the local router.

If the gateway does not respond

Investigate the local connection, including:

• Wi-Fi signal and connection
• Ethernet cable, if applicable
• Network adapter configuration
• Router LAN functionality
• Local firewall configuration

Test 3: Test External IP Connectivity

Next, test an external IP address without relying on DNS:

ping 8.8.8.8

If your router responds but external connectivity fails across multiple devices, investigate:

• Router WAN connectivity
• Modem or ONT status
• Upstream routing
• Firewall rules
• ISP service problems

However, remember that ICMP traffic can be filtered. A failed ping alone does not conclusively prove that the Internet is unavailable.

Test 4: Test DNS Resolution

Finally, test DNS directly:

nslookup google.com

If the command returns an IP address, DNS resolution is working for that query.

If it times out or reports a DNS server failure, investigate the configured DNS server and the connectivity between your device and that DNS server.

A Useful Combination of Tests

Suppose:

ping 8.8.8.8

works, but:

nslookup google.com

fails.

In that situation, DNS resolution becomes a strong suspect.

This is more useful than changing DNS settings blindly because you have first identified which part of the connection is failing.

Network Diagnostic Decision Matrix

Test	Result	Likely Diagnostic Indication
ping 127.0.0.1	Fails	Local TCP/IP or loopback problem
ping Gateway	Fails	Local Wi-Fi/Ethernet or router LAN problem
ping 8.8.8.8	Fails on multiple devices	WAN, upstream routing, firewall, or ISP issue
ping 8.8.8.8	Succeeds	Basic external IP connectivity exists
nslookup google.com	Fails	DNS resolution problem is likely
IPv4 address	169.254.x.x	DHCP address acquisition problem; APIPA assigned

Frequently Asked Questions

Why does my phone say "Connected, no internet" while other devices work?

If other devices on the same Wi-Fi network have normal Internet access, the problem is probably specific to the affected phone or computer.

Possible causes include DHCP or IP configuration problems, a corrupted Wi-Fi profile, VPN or Private DNS settings, proxy configuration, or a local wireless issue.

Start by forgetting the Wi-Fi network and reconnecting to it.

What does a 169.254.x.x IP address mean?

A 169.254.x.x address is an IPv4 link-local address associated with APIPA.

In a typical DHCP-based home network, seeing this type of address means the device did not obtain a normal IPv4 address from the DHCP server.

Check the local Wi-Fi connection, router, and DHCP configuration.

Why can I connect to Wi-Fi but not the Internet?

Wi-Fi connectivity and Internet connectivity are two different stages of the network path.

Your device may successfully associate with the wireless access point while the router has no working WAN connection to the ISP.

Other possible causes include DHCP, DNS, routing, VPN, proxy, and firewall problems.

Should I change my DNS immediately?

Not necessarily.

First determine whether your device has basic external connectivity.

If an external IP address is reachable but DNS queries fail, changing DNS may be appropriate.

If the router has lost its WAN connection, changing DNS will not solve the underlying problem.

Should I factory-reset my router?

A factory reset should be considered a last resort.

Resetting a router can erase important configuration, including:

• Wi-Fi network name and password
• DHCP reservations
• Custom DNS settings
• Port forwarding rules
• Firewall configuration
• VLAN settings
• PPPoE credentials
• Other ISP-specific settings

Before performing a factory reset, check the router's WAN status and contact your ISP if necessary.

When Should You Contact Your ISP?

You should consider contacting your ISP when:

• Multiple devices cannot access the Internet.
• The router cannot establish a WAN connection.
• The modem or ONT reports a connection problem.
• External connectivity fails across multiple devices.
• The problem continues after restarting your network equipment.
• Your ISP confirms an outage in your area.

Apple also recommends testing the same Wi-Fi network on other devices and contacting the ISP when other devices cannot get online. 

Final Thoughts

A "Connected to Wi-Fi but no Internet" message does not necessarily mean that your Wi-Fi network is broken.

Your device may have a perfectly healthy wireless connection to the router while the actual failure occurs somewhere else in the network path.

The most effective approach is to troubleshoot the connection systematically.

Start with the basics: restart the modem and router, test another device, and reconnect to the Wi-Fi network. If the problem persists, check the device's IP address and default gateway.

On Windows, commands such as netsh int ip reset, ipconfig /renew, and ipconfig /flushdns can help repair local network configuration. If you need to go deeper, ping and nslookup can help identify whether the problem is occurring at the local network, WAN, or DNS level. Microsoft documents these network commands as part of its Windows connectivity troubleshooting process. 

The goal is not simply to try every possible fix. The goal is to identify where the connection breaks and then apply the appropriate solution.