Wi-Fi & Network
Internet works on phone but not laptop
Separate laptop Wi-Fi, VPN, DNS, browser, and work-management problems when other devices are online and the internet service is not the first suspect.
Problem summary
If a phone works on the same Wi-Fi while the laptop does not, the internet service is probably not the first suspect.
Confirm phone and laptop are on the same SSID and not guest or hotspot networks.
ipconfig /all (macOS/Linux: ifconfig)
Both devices are on the trusted home Wi-Fi.
Stop if policy, VPN, or security controls are managed by work or school.
Layer path
Step-by-step runbook
Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.
Make the comparison valid
Check: Put phone and laptop on the same trusted SSID, then pause large transfers.
Expected result: The phone remains a useful control device.
If not: If they are on different networks, fix that before further testing.
Check laptop IP details
Check: Run ipconfig /all or the OS network details screen.
Expected result: The laptop has a valid IP, gateway, and DNS.
If not: If not, forget/rejoin only the laptop Wi-Fi.
Test local before internet
Check: Open the router IP in a browser or ping the gateway.
Expected result: The laptop reaches the local router.
If not: If not, stop changing DNS or browser settings.
Separate DNS, VPN, and browser
Check: Test nslookup, a private browser window, and VPN-off only if personally managed.
Expected result: The failing layer is visible.
If not: If VPN or work security is involved, stop and follow owner policy.
Apply the narrow fix
Check: Fix the laptop adapter, browser, VPN, or DNS path identified by evidence.
Expected result: The laptop works without changing the whole home network.
If not: If several trusted networks fail, escalate laptop support.
Decision tree
If: Laptop has no valid local IP.
Then: Wi-Fi attachment or DHCP is failing.
Action: Forget/rejoin the home Wi-Fi and check router lease.
If: Laptop reaches router IP but not websites.
Then: DNS, VPN, proxy, or WAN routing is suspect.
Action: Check DNS/VPN/proxy before router reset.
If: Browser fails but another app works.
Then: Browser profile, extension, cache, or proxy is likely.
Action: Test private window or another browser.
If: VPN off fixes it on a personal laptop.
Then: VPN routing or DNS is the active layer.
Action: Adjust the VPN's local/internet routing only if you control it.
If: The laptop is work-managed.
Then: Policy may intentionally control network, VPN, DNS, and proxy.
Action: Stop before disabling security software.
Safe stop: Stop if policy, VPN, or security controls are managed by work or school.
Evidence table
| Symptom | Evidence to collect | Likely layer | Next action |
|---|---|---|---|
| Phone works, laptop no internet. | Same SSID comparison and laptop IP details. | Laptop network stack | Fix laptop Wi-Fi/DHCP first. |
| Laptop connected but no sites load. | Ping/router page versus website behavior. | DNS/proxy/VPN | Check VPN/proxy/DNS before router reset. |
| Only browser fails. | Private window or second browser test. | Browser/app | Fix browser profile or extension. |
| Problem starts after VPN connects. | Before/after VPN test and policy message. | VPN routing/policy | Follow VPN owner rules. |
Commands and settings paths
Laptop IP state
ipconfig /all (macOS/Linux: ifconfig)
Where: PowerShell or Command Prompt on the laptop.
Expected: The Wi-Fi adapter has a valid private IP, gateway, and DNS on the home network.
Failure means: Missing gateway, APIPA, or wrong subnet points to local Wi-Fi/DHCP.
Safe next step: Forget/rejoin the home Wi-Fi only on the laptop.
Gateway reachability
ping <router-ip>
Where: PowerShell or Command Prompt on the laptop.
Expected: The laptop reaches the router with low local latency.
Failure means: Failure means local network path is broken before DNS or web troubleshooting.
Safe next step: Reconnect Wi-Fi and check adapter state.
DNS comparison
nslookup hometechops.com
Where: PowerShell or Command Prompt on the laptop.
Expected: DNS resolves while connected to the home network.
Failure means: DNS failure with router reachability points to DNS/VPN/proxy.
Safe next step: Check VPN/proxy and router DNS settings only after IP is valid.
Hardware and platform boundary
Change only when
- Replace laptop Wi-Fi hardware only after same-SSID, IP, gateway, DNS, VPN/proxy, and other-network tests isolate the adapter.
Evidence that matters
- Driver support, adapter reliability, antenna condition, and managed-policy compatibility matter.
Evidence that does not matter
- A new router or faster plan does not fix one laptop's VPN, DNS, browser, or adapter state.
Avoid
- Avoid disabling work security software or changing router DNS for the whole home before laptop evidence supports it.
Related tool/checklist
Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.
Device setup troubleshooterRelated problems
Last reviewed
2026-05-06 · Reviewed by HomeTechOps. Reviewed for laptop-only internet failures across SSID, DHCP, gateway, DNS, VPN/proxy, browser, and work-management boundaries.
Sources/assumptions
- Assumes the phone and laptop are using the same trusted home Wi-Fi.
- Work-managed devices may enforce VPN, proxy, firewall, or DNS policy.
Source-backed checks
HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.