Internet works on some devices but not others

Identify why certain devices lose internet while others work, including device settings, DNS, and compatibility factors.

Introduction

Reliable networking underpins modern work, streaming, and smart home services, yet issues like inconsistent connectivity across devices on the same network 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 “internet works on some devices but not others” describes inconsistent connectivity across devices on the same network, 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:

• one laptop works while another cannot load pages.
• smart TVs stream while phones fail.
• only older devices have issues.
• problems follow a specific device across networks.
• VPN or security apps affect only some devices.
• devices show connected but no internet status.

Common causes / reasons

• device-specific DNS or proxy settings. 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.
• outdated Wi-Fi drivers or OS versions. 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.
• incompatible Wi-Fi security modes. 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 parental controls. 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.
• corrupt network profiles or saved passwords. 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.
• malware 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.

Step-by-step guidance

1. Compare the affected device’s IP, gateway, and DNS settings to a working device. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
2. Remove and re-add the Wi-Fi network profile on the affected device. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
3. Update the device’s OS and Wi-Fi drivers. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
4. Disable VPN, proxy, or security filters temporarily to test. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
5. Check router access controls and ensure the device is allowed. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
6. Test the device on a different network to see if the issue follows it. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.
7. Reset the network settings if configuration corruption is suspected. This step helps isolate whether the problem is local, device-specific, or upstream and reduces unnecessary configuration changes.

Common mistakes (what NOT to do)

• assuming all devices share the same network settings.
• changing router settings without confirming device-specific issues.
• forgetting about saved proxy or VPN profiles.
• ignoring device time and certificate errors.
• keeping outdated firmware on older devices.

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.

Legacy devices may not support wpa3 or modern encryption. Corporate-managed devices may enforce restrictive security policies. 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

• device settings appear correct but issues persist. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.
• router logs show authentication failures for the specific device. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.
• the device fails on multiple networks. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.
• security policies restrict changes. A professional can validate line quality, run certified tests, or verify equipment health beyond what consumer tools provide.

Prevention tips

• keep device software updated and supported. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• use consistent security modes across the network. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• document custom proxy or DNS settings. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• review access control lists when adding devices. Small, routine adjustments often prevent larger disruptions and keep performance predictable.
• replace devices that cannot meet modern security standards. Small, routine adjustments often prevent larger disruptions and keep performance predictable.

FAQs (6–8 real questions)

Why would only one phone fail?

Phones may use custom DNS, VPN apps, or aggressive battery optimization that interferes with connectivity. 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 forgetting the network help?

Yes. It clears saved credentials and profiles that may be corrupt or outdated. 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 outdated drivers stop internet access?

Yes. Old drivers can mishandle encryption or roaming, causing failed connections. 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.

Is it a router problem if only one device fails?

Not usually. The issue is likely on the device or its settings, though access controls could be blocking it. 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 MAC randomization be disabled?

If access controls are enabled, randomized MAC addresses can cause blocks. Disabling randomization for that network can help. 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 security apps block traffic?

Yes. Some security or parental control apps can block network access or require reconfiguration. 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 Devices connect to Wi-Fi but have no internet access, Ethernet connection slower than expected, and Internet disconnects randomly during normal use.

Summary and key takeaways

• Internet works on some devices but not others 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