Why Does My Internet Work on Some Devices but Not Others?

One Device Is Online, Another Is Not

Your phone loads websites over Wi-Fi without a hitch. Your laptop sits on the same network and says “Connected, no internet.” Or the game console pulls updates over Ethernet while a tablet three feet away cannot open a single page. It’s frustrating because the connection works on one device but not the other.

The useful question here is not why the internet is broken. It plainly is not, at least not for every device. The question is why the same network behaves one way for one device and another way for the next. That gap is evidence, and it is worth more than any single fix you might try at random.

It also does not settle the matter on its own. A device that fails while others work is not automatically the broken one. The two devices may differ in several ways: connection type, Wi-Fi band, network settings, software, or hardware. Any one of those can explain the difference. This article is a practical way to find out which one is actually responsible. The method is to compare the devices carefully instead of changing five things at once.

What “It Doesn’t Work on This Device” Can Mean

Before comparing anything, it helps to be precise about the symptom. The phrase “the internet doesn’t work on this device” covers several different situations:

The device cannot find the Wi-Fi network in its list at all.
It sees the network but fails to join it.
Wi-Fi connects, but the device reports no internet access.
Some sites or apps load while others do not.
The connection holds, then drops repeatedly or performs poorly.
Ethernet works but Wi-Fi does not, or the reverse.

These are not the same problem. A device that will not join the wireless network has stumbled at one stage. A device that joins fine but cannot load a page has stumbled at another. The first is about getting onto the local network. The second is about reaching the wider internet once it is on. Treating them as one issue sends you checking the wrong things.

One habit is worth dropping early. A full Wi-Fi icon does not prove a device has working internet. The bars describe the wireless signal between the device and the router, and nothing beyond it. A device can show four strong bars and still be unable to reach anything past your own home. Keep that separation in mind and the rest of the process makes more sense.

A Controlled Way to Narrow It Down

The goal is to compare the working device against the failing one, changing a single variable at a time and watching what happens. Work through the steps in order and stop when a comparison points clearly at the cause. You will not need all of them.

Step 1: Confirm Both Devices Are on the Same Network

This sounds obvious, and it is the step people skip most. Start by checking that both devices are truly on the same Wi-Fi network, spelled the same way. Two networks with similar names are easy to confuse.

Phones complicate this. When Wi-Fi is weak or flaky, a phone will quietly fall back to mobile data without announcing it. The “working” device may not be using your Wi-Fi at all. To rule that out, turn off mobile data on the phone for a moment and see whether it still loads pages. If it does, it is genuinely working over Wi-Fi and the comparison is fair. If it stops, the phone was leaning on cellular and never really tested your network.

A few other things muddy the picture. Guest networks, a second network from the same router, range extenders, and mesh nodes all qualify. Each can put two devices on what looks like one Wi-Fi but is not quite. Many routers also broadcast separate 2.4 GHz and 6 GHz names. Different bands are not different internet connections, and being on one band rather than another does not mean a device is cut off. It can, though, matter for compatibility, which comes up later.

Step 2: Compare the Same Website on Both Devices

Once you know both devices share a network, load the exact same familiar site on each, something reliable you visit often. Comparing different apps or pages is where people draw wrong conclusions. One device opening a social app while the other tries a news site tells you very little.

If that one site fails on the problem device but others load fine, the trouble is narrower than “no internet.” It may involve that specific site, the device’s DNS settings, a browser configuration, a content filter, or the app itself. If every site fails on the problem device while the other browses normally, the trouble is more local. Look at that device’s own connection and configuration. And a single page loading is not proof that a device’s whole connection is healthy, so try two or three before deciding.

Sites that connect but cannot resolve names are a common and confusing case. If a device joins Wi-Fi but no web address will open, name resolution is worth a look. Our companion guide covers what “DNS server not responding” means and how to fix it in detail.

Step 3: When a Device Cannot Find or Join Wi-Fi

If the problem device never gets onto the network, the checks are different from a device that joins but cannot browse. Run through the basics first:

Wi-Fi is switched on and airplane mode is off.
You are selecting the right network and entering the correct password.
The device sits within reasonable range of the router or access point.
Its Wi-Fi band and security mode match what the network uses.
The router is not blocking that device or refusing new connections.
Nothing changed right after a router or device update.

The compatibility point deserves attention. An older phone, laptop, or smart-home gadget may not support every modern Wi-Fi setting. It might not see a 6 GHz network, or it might struggle with a security mode the router was recently switched to. The Wi-Fi Alliance, which certifies wireless devices, now treats WPA3 security as mandatory for newly certified equipment. Some routers can be set to require it. A device too old to speak WPA3 can then fail to join a network everything else uses without complaint.

That does not mean you should strip your Wi-Fi security back to accommodate one device. Many routers offer a mixed or transitional mode that supports older and newer devices at once. That is a safer path than turning protection off. And resist the urge to factory-reset the device this early. It rarely helps at this stage and costs you all its settings.

Step 4: When a Device Joins Wi-Fi but Has No Internet

This is the “Connected, no internet” case, and it means the device got onto the local wireless network but cannot reach past it. Joining Wi-Fi and reaching the internet are two separate achievements, and this device managed the first but not the second.

A handful of checks usually locate it:

Whether the device received a valid local IP address rather than a self-assigned fallback.
Its gateway and DNS entries, which should look reasonable rather than blank or odd.
A leftover static IP that no longer fits the current network.
A VPN, proxy, firewall, or filter on the device that is blocking traffic.
Whether a public or guest network is holding it at a sign-in page that never appeared.

You do not need to understand subnetting to make progress here. The common culprit is a manual setting left over from another network. A device set up with a fixed IP or a specific DNS server from another router shows this exactly. It joins Wi-Fi, then fails to reach anything. Switching those back to automatic is frequently the fix.

Both Microsoft and Apple document how to view and adjust these settings for their current systems. Microsoft’s guide to fixing Wi-Fi connection issues in Windows walks through checking the connection, IP configuration, and network reset. Apple’s guide for a Mac that is not connecting to the internet over Wi-Fi covers the equivalent steps, including its built-in wireless diagnostics. Before you change any manual entry, write down the current values exactly, so you can restore them if the change does not help.

Step 5: Compare Wi-Fi, Ethernet, and Another Network

Swapping the connection type is one of the most revealing comparisons available. If the problem device has an Ethernet port, plug it into the router with a cable and test again. A device that works over Ethernet but fails over Wi-Fi points you toward something wireless. The cause is more likely a band or security-mode mismatch, a driver, or interference than a dead connection.

You can also carry the failing device to a different network. A phone hotspot works well for this, as long as the phone has signal and data to spare. Suppose the device reaches the internet on a hotspot but not your home Wi-Fi. That points to a setting or compatibility issue with your own network, not a fault in the device. Success elsewhere does not prove your router is broken, though. It only tells you the device and the wider internet can work together under the right conditions.

Not every device offers these options. Phones and most tablets have no Ethernet port, and a console may not connect to a hotspot easily. Use whichever comparison the hardware allows. Even one of them tells you a lot.

Step 6: Check Device-Specific Settings and Software

Some things live on a single device and affect only that device. That is exactly why one machine fails while the rest carry on. Worth reviewing:

A DNS server entered manually in the device’s network settings.
A VPN or proxy that is on and routing or blocking traffic.
Security software or a web filter that is intercepting connections.
A network adapter driver that is outdated or misbehaving.
A recent operating-system update that changed network behavior.
Power-saving settings that put the wireless adapter to sleep.
Any device-specific network restriction, such as a screen-time or content control.

Favor checks that are safe and easy to undo. If you suspect a VPN or filter, disconnect it briefly, test, and turn it back on afterward. A change in behavior tells you where to look, though it does not always reveal the deeper cause. Leaving a firewall or security suite switched off is not a routine fix. Do not treat that as a solution.

Drivers deserve a note. If a Windows adapter looks like the problem, update it through Windows Update or the manufacturer’s official support site. Avoid a random driver-updater tool from a search result. Those utilities cause more trouble than they solve. For Android and iPhone, keeping the system itself current through the built-in update process is usually enough.

Step 7: Check Router Settings That Treat Devices Differently

A router can hand out internet to most devices while quietly holding back one. That is not a contradiction; it is often a setting. Possibilities include:

Access controls or a blocked-device list that names the failing device.
Parental controls scheduled or scoped to certain devices.
Guest network rules that isolate a device from the rest.
A DHCP problem where the router runs out of addresses to assign.
Band or security modes the failing device cannot use.
Device limits on the router or a mesh node, where the equipment enforces them.
A mesh or extender node that a device connects to but that is misconfigured.

Router menus differ so much between brands and models. Look up the exact path in your own router’s documentation rather than following generic steps. When you do change something, change one setting at a time and retest, so you know what made the difference. Avoid disabling security features across the board to see if it helps. Do not factory-reset the router unless you have a specific reason and are ready to set it up again.

Step 8: Decide When Restarting or Resetting Makes Sense

Restarting has its place, but timing matters. For a single misbehaving device, reconnecting it is the gentlest move. Toggle its Wi-Fi off and on, or disable and re-enable the network adapter. That can clear a stuck state without touching anyone else’s connection.

Restarting the router is a bigger lever, since it drops every device for a minute or two. Save it for when several devices show related trouble, not when one device alone is affected. A restart can clear a temporary glitch, but it does not tell you what caused it. A problem that returns quickly was only masked. If you decide to forget and rejoin a Wi-Fi network, have the password ready. You will need it again, and you may lose other saved settings for that network. Treat a full network-settings reset as a later resort rather than a first move, and skip factory-resetting hardware as a general-purpose fix.

Step 9: When to Contact Your ISP, Admin, or Manufacturer

If the comparisons point somewhere but you cannot resolve it, gather what you have observed before reaching out. A clear account gets you a faster answer than “the internet is broken.” Useful details include:

Which devices work and which do not.
Whether the devices are on the same Wi-Fi network.
Whether the failing device can even join Wi-Fi.
How it behaves over Ethernet or on another network like a hotspot.
Whether all sites fail or only certain ones.
When the trouble began, and whether it followed a setting or software change.
Which steps you have already tried.

Where you turn depends on what you saw. If only one device fails while everything else works normally, the internet provider is unlikely to be the cause. The device’s manufacturer or your network administrator is a better first call. Google’s guide to fixing connection problems on Android devices is a reasonable reference for a single Android phone that will not connect. If many devices struggle at once, the router or the line into your home becomes the more likely suspect. That is when to contact the ISP.

When Both Devices Work but One Is Just Worse

Not every version of this problem is a hard failure. Sometimes two devices both reach the internet, yet one feels noticeably worse. Calls stutter on the laptop but not the phone, or a game lags while streaming stays fine. That is a difference in connection quality rather than a yes-or-no outage, and it is harder to judge by eye.

Comparing the two directly helps. Running a stability test on each device gives you something concrete to set side by side. StabilityTest is a free, browser-based tool that watches a connection over time. It reports ping, jitter, packet loss, failed probes, drops, and an overall Stability Score. Because it observes behavior across a stretch of time, it can surface intermittent trouble that a single quick check misses.

It has limits worth stating plainly. StabilityTest measures how a connection behaves, not why. It does not diagnose DNS errors, Wi-Fi authentication failures, router incompatibilities, or a hardware fault. No single run identifies the failing component on its own. It also cannot run on a device that has no internet access. So it fits the “both connect but one is worse” case, not a device that is fully offline. Used that way, though, it documents a difference that is otherwise easy to argue about. If one device shows far worse ping under load or more frequent drops, you have something concrete to act on.

Frequently Asked Questions

Why does Wi-Fi work on my phone but not my laptop?

Usually because the two devices differ in some way that matters on your network. The laptop may use a different band, a manual DNS or IP address, or a VPN or firewall. An adapter driver that needs attention can also be the cause, while the phone avoids all of it. Confirm both are really on the same Wi-Fi first, since a phone can quietly use mobile data. Then compare the same website on each and check the laptop’s own network settings.

Why does one device say “Connected, no internet”?

That message means the device joined your local Wi-Fi but cannot reach the wider internet beyond it. Joining the network and reaching the internet are separate steps, and the device cleared the first but not the second. Common causes are a leftover static IP or DNS setting, or a VPN or filter on the device. A captive portal on a guest network that never loaded can also do it. Setting the device’s IP and DNS back to automatic resolves many of these.

Why does my device work on another Wi-Fi network but not mine?

It suggests the device and the wider internet can work together, so the mismatch is between that device and your specific network. That often points to a router setting the device cannot use, such as a band or security mode. An access control or a compatibility gap can also explain it. It does not prove your router is faulty. It narrows the search to how your network is configured for that particular device.

Can DNS cause internet problems on only one device?

Yes. A single device can have a DNS server entered manually in its settings. If that server is wrong or unreachable, the device joins Wi-Fi but fails to open websites. Other devices, using the network’s normal DNS, keep working fine. Setting that device back to automatic DNS is a good first test. The distinction between joining a network and resolving names is covered more fully in our DNS guide.

Should I reset my router if only one device has a problem?

Generally no, not as a first step. Restarting the router affects every device and makes the most sense when several devices show trouble together. When just one device fails, start with that device. Reconnect its Wi-Fi, check its settings, and compare it against a working one. A full factory reset of the router is a last resort that erases your configuration. Keep it well down the list.

What if both devices connect but one is much slower?

That is a quality difference rather than an outage, and it is worth measuring instead of guessing. Run a stability test on each device and compare the results for ping, jitter, packet loss, and drops over time. A device on a weaker band, farther from the router, or burdened by background software can perform noticeably worse while staying online. The measurement tells you how large the gap is and whether it lines up with a change you can make.