Published August 31, 2026
When My Wi-Fi Worked on My Phone but Not on My Computer
I was sitting on my couch, phone in one hand streaming a video without a single hiccup, laptop open on my knees telling me, quite confidently, that I had no internet connection at all. Same room. Same router, a few feet away. Same network name, selected on both devices. And somehow one of them was completely fine while the other insisted the internet simply didn't exist.
The Problem
My laptop showed the Wi-Fi icon connected, full signal bars, everything that should have meant it was online — right up until I actually tried to load anything, at which point every page just sat there, spinning, going nowhere. My phone, sitting a few inches away on the same couch cushion, loaded pages instantly, streamed video without buffering, behaved exactly the way a normal internet connection should. It genuinely didn't make sense to me at first, in the way things don't make sense when the obvious explanation — "the internet is down" — is directly contradicted by a device sitting right next to the one having the problem.
I tried closing and reopening my browser, which felt like the equivalent of jiggling a door handle rather than an actual troubleshooting step, and got the same spinning nothing. I checked that I was actually on the right network, not some neighbor's open connection with a similar name, and confirmed I was exactly where I thought I was. The signal bars stayed full the entire time, which somehow made it more frustrating rather than less — a strong signal to nowhere useful.
What I Initially Thought
My first assumption was that this had to be the router's fault, some kind of temporary hiccup affecting just my laptop's connection to it. I unplugged the router and plugged it back in, the classic first move, mostly out of habit rather than any real theory about why that would help. It didn't help. My laptop still showed the exact same problem, connected in name only, unable to actually reach anything, while my phone continued along completely unaffected the entire time, an unhelpful reminder that whatever this was, it clearly wasn't the router itself.
What I Tried
Once the router restart didn't change anything, I stopped assuming the problem was on the network's end and started actually treating my laptop as the more likely suspect, given that literally every other device in the house — my phone, my partner's tablet — was working completely normally on the same network the entire time. I ran the built-in Windows network troubleshooter, mostly expecting it to tell me nothing useful, since that had been my experience with it in the past.
This time it actually flagged something specific: an IP address conflict, a phrase I recognized but couldn't have explained if you'd asked me to. I also opened an admin Command Prompt and tried releasing and renewing my laptop's IP address manually, since that came up repeatedly while I was looking into what the troubleshooter's message actually meant.
What I Discovered
An IP address conflict, it turned out, happens when two devices on the same network end up trying to use the same address at the same time — something the router is supposed to prevent automatically, but occasionally doesn't, especially after a device has been asleep or disconnected for a while and reconnects into a slot the network thinks is still assigned to someone else. My laptop had apparently been assigned an address that another device — possibly even a previous, disconnected session of itself — was still technically holding onto from the network's perspective, a kind of digital case of mistaken identity nobody had actually resolved.
That explained the contradiction perfectly, once I actually understood it. My phone had a completely different, non-conflicting address and so it worked without any issue whatsoever, blissfully unaware anything was wrong anywhere on the network. My laptop was stuck fighting over an address the network had gotten confused about, which meant it could technically show as "connected" — associated with the Wi-Fi network itself, authenticated, sitting there with full bars — while still being unable to actually send or receive anything useful over that connection. Connected and functional turned out to be two different claims entirely, and I'd never had a reason to separate them in my head before this happened.
Manually releasing and renewing the IP address forced my laptop to request a completely fresh address from the router, and the moment it got one that wasn't in conflict with anything else, pages started loading normally again, instantly, as if nothing had ever been wrong. The whole fix, once I understood what to actually type, took under a minute — a strange contrast to the confused half hour that came before it.
What I Changed
I stopped assuming that "Wi-Fi shows connected" and "internet actually works" were the same thing, since this whole experience proved fairly conclusively that they aren't. Now, if a device shows connected but nothing actually loads, I check other devices on the same network immediately, specifically because that single comparison — does this same problem affect everything, or just this one device — tells me almost immediately whether to keep troubleshooting the router or start looking at the specific device instead.
I also got more comfortable with the release-and-renew commands, which took a genuinely tiny amount of effort once I knew they existed, compared to how mysterious and technical they'd sounded to me before I'd ever actually needed them.
The Lesson
The contradiction — one device working, one device not, on the exact same network — wasn't a distraction from the real problem. It was the actual clue the whole time, and I nearly talked myself out of paying attention to it because "the internet is down" felt like a simpler, more familiar explanation than "my laptop specifically has a conflicting address." The simpler-sounding explanation isn't always the correct one, and the detail that doesn't fit the story you're telling yourself is often the detail worth following.
Practical Takeaway
- If one device can't get online, check whether other devices on the same network can — that comparison tells you whether to focus on the router or the specific device.
- Don't assume "shows connected" means "internet actually works" — a device can be associated with a Wi-Fi network while still being unable to send or receive data properly.
- Run the built-in Windows network troubleshooter — it can specifically flag an IP address conflict, which isn't always obvious from the symptoms alone.
- Try releasing and renewing your IP address (via an admin Command Prompt) before assuming a deeper network or driver problem.
- Restarting the router is worth trying first, but if it doesn't help and other devices are unaffected, stop troubleshooting the router and start troubleshooting the one device that's actually having the problem.
- Pay attention to contradictions rather than explaining them away — a detail that doesn't fit your assumption is often more informative than one that does.
A Personal Ending
I think about how long I might have kept blaming the router if my phone hadn't been sitting right there, working perfectly, contradicting the story I wanted to believe. Since then, when something seems broken, I always check whether it's broken everywhere or just in the one place I happen to be looking.
Had one device fail while everything else on the same network worked fine? I'd like to hear about it.