Devices connect to Wi-Fi but have no internet access

Troubleshoot Wi-Fi connections that appear successful but cannot reach the internet, from DNS errors to gateway failures.

Introduction

Reliable networking underpins modern work, streaming, and smart home services, yet issues like wireless devices connect but cannot access online services can disrupt everyday use. When a network behaves unpredictably, troubleshooting often feels like guesswork because many symptoms look similar on the surface. A clear, methodical approach makes it possible to narrow the cause and restore stable performance without unnecessary changes. This guide focuses on practical diagnosis and remediation that applies to typical homes and small offices.

Connectivity issues are rarely caused by a single factor; they are often the result of overlapping conditions such as congestion, configuration drift, or physical interference. Understanding how devices, access points, routers, and ISP links interact makes it easier to interpret symptoms correctly. The same symptom can have multiple causes, so the best results come from isolating variables rather than changing many settings at once.

The sections below explain what the issue really means, why it happens, and which steps provide the highest likelihood of a durable fix. Each section emphasizes repeatable actions and safe adjustments that preserve security while improving stability. The goal is not just a quick fix, but a stable network that continues to perform under everyday load.

A red light, slow link, or unstable connection usually reflects a breakdown in the path between the device, the router, and the ISP edge. The goal is to isolate where the failure starts by comparing wired versus wireless behavior, checking known-good devices, and verifying whether the problem is consistent across times of day. Clear isolation keeps the focus on practical fixes instead of random resets.

What this actually means

The phrase “devices connect to wi-fi but have no internet access” describes wireless devices connect but cannot access online services, which indicates the network is failing to maintain consistent connectivity across sessions. This is different from a complete outage because some traffic may still pass, and devices might reconnect automatically. The most important step is determining where the disruption starts: device, Wi-Fi link, router, modem, or ISP path.

Because modern devices retry connections quickly, small disruptions can appear as brief freezes, slow page loads, or temporary offline messages. These micro-outages can be more disruptive than a full outage because they are harder to diagnose and can affect real-time services like calls or gaming. A solid understanding of the network layers helps narrow the source and avoid unnecessary changes.

Key signs often include:

• Wi-Fi shows connected with full signal.
• browsers display DNS or gateway errors.
• wired devices may still work.
• mobile data works, Wi-Fi does not.
• connections work briefly after reboot.
• some devices are affected while others are not.

Common causes / reasons

• DHCP issues assigning incorrect gateway or DNS. This often appears when network load or environmental conditions expose a weak link, and it can be confirmed by checking logs, signal levels, or device behavior.
• router WAN outages or ISP maintenance. This often appears when network load or environmental conditions expose a weak link, and it can be confirmed by checking logs, signal levels, or device behavior.
• MAC filtering or access control lists blocking devices. This often appears when network load or environmental conditions expose a weak link, and it can be confirmed by checking logs, signal levels, or device behavior.
• IP address conflicts on the local network. This often appears when network load or environmental conditions expose a weak link, and it can be confirmed by checking logs, signal levels, or device behavior.
• VPN or security software blocking traffic. This often appears when network load or environmental conditions expose a weak link, and it can be confirmed by checking logs, signal levels, or device behavior.
• captive portal not completed. This often appears when network load or environmental conditions expose a weak link, and it can be confirmed by checking logs, signal levels, or device behavior.

Step-by-step guidance

1. Forget and reconnect to the Wi-Fi network to refresh credentials. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
2. Check the device’s IP, gateway, and DNS settings for correctness. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
3. Test access to a public IP to isolate DNS issues. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
4. Restart the router and verify WAN status. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
5. Disable VPNs or security filters on the device for testing. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
6. Confirm the device is not blocked by MAC filtering or parental controls. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
7. If needed, reset network settings on the device. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.

Common mistakes (what NOT to do)

• ignoring IP conflicts from static assignments.
• changing DNS without clearing caches.
• assuming the Wi-Fi password is the issue.
• resetting the router without saving configuration.
• leaving captive portal pages unacknowledged.

Avoiding these mistakes keeps the troubleshooting process reliable and prevents the loss of useful diagnostic evidence. If changes are required, capture the original settings first so a stable baseline can be restored quickly.

When this cannot be fixed / limitations

Some network problems have causes outside the home, such as upstream line faults, regional congestion, or physical building constraints. In these cases, local troubleshooting can improve stability but may not fully eliminate the issue. Documenting clear evidence helps accelerate the resolution process with a provider or building manager.

Isp outages will block access even if wi-fi is strong. Some corporate or school devices may require specific dns or proxy settings. When these limitations apply, the best path is to focus on mitigation, such as using wired links, scheduling heavy usage, or requesting ISP escalation.

When to seek professional help

• multiple devices fail despite correct IP settings. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.
• router logs show repeated DHCP or authentication errors. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.
• the issue persists across different routers. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.
• the ISP reports upstream maintenance. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.

Prevention tips

• keep DHCP ranges consistent and avoid overlapping static IPs. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• document access control rules and device MAC addresses. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• use stable DNS resolvers and monitor for failures. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• update device OS and Wi-Fi drivers. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• avoid unnecessary VPN use on local networks. Small, routine adjustments often prevent larger disruptions and keep performance predictable.

FAQs (6–8 real questions)

Why does Wi-Fi say connected but no internet?

Wi-Fi only confirms a local wireless link. Internet access requires a working gateway, DNS, and upstream connection. When testing, compare wired and wireless results so the underlying cause is clearer. Consistent documentation of timing, device, and location makes follow-up support more effective.

Should the router be rebooted first?

Rebooting helps clear transient issues, but checking device IP settings can reveal quicker fixes. When testing, compare wired and wireless results so the underlying cause is clearer. Consistent documentation of timing, device, and location makes follow-up support more effective.

Can a wrong time setting affect access?

Yes. Incorrect device time can break TLS certificates and make websites appear offline. When testing, compare wired and wireless results so the underlying cause is clearer. Consistent documentation of timing, device, and location makes follow-up support more effective.

Does airplane mode help?

Toggling airplane mode can reset the Wi-Fi radio and clear stale network states. When testing, compare wired and wireless results so the underlying cause is clearer. Consistent documentation of timing, device, and location makes follow-up support more effective.

Are IP conflicts common?

They can occur when static IPs overlap with DHCP ranges or multiple routers hand out addresses. When testing, compare wired and wireless results so the underlying cause is clearer. Consistent documentation of timing, device, and location makes follow-up support more effective.

Why does it work on mobile data?

Mobile data bypasses the local network and ISP path, indicating the issue is on the Wi-Fi network or ISP line. When testing, compare wired and wireless results so the underlying cause is clearer. Consistent documentation of timing, device, and location makes follow-up support more effective.

For related guidance, review Ethernet connection slower than expected, Internet disconnects randomly during normal use, and Internet stops working after router restart or power outage.

Summary and key takeaways

• Devices connect to Wi-Fi but have no internet access is usually a stability or configuration issue rather than a single permanent outage.
• Separating local network causes from ISP causes speeds up troubleshooting and avoids unnecessary changes.
• Focused checks of cabling, firmware, and device settings resolve many cases without major upgrades.
• Documented testing results make it easier to escalate to professional support when needed.

Disclaimer

This article provides general information for educational purposes and does not replace guidance from a qualified networking professional or service provider. Always follow vendor instructions and safety guidelines when handling networking equipment.

Last updated date

2026-01-11