Overview
Windows can show a computer as connected to Wi-Fi even when it cannot reach the internet. The wireless connection only proves that the computer joined an access point. Internet access still depends on valid IP addressing, a default gateway, DNS, upstream connectivity, and any security controls between the computer and the internet.
Why this happens
Common causes include joining the wrong SSID, an expired DHCP lease, a 169.254 self-assigned address, a missing gateway, DNS failure, captive portal, VPN or proxy problems, weak wireless signal, or an upstream internet outage.
Before you begin
- Check whether another device on the same Wi-Fi can reach the internet.
- Record the Wi-Fi network name and Windows connection status.
- Save open work before restarting the computer.
- Do not factory-reset access points, routers, or firewalls.
Click-by-click troubleshooting
Step 1: Confirm the correct Wi-Fi network
Action: Select the network icon on the Windows taskbar. Verify that Wi-Fi is on and that the connected network is the approved business SSID.
Why this matters: A guest, isolated, or neighboring network may show Connected while not providing the required internet or business access.
What to look for: Look for the correct SSID, normal signal strength, and whether Windows shows No internet or Action needed.
Expected result: The computer should be connected to the intended business Wi-Fi network.
Step 2: Compare with another device on the same Wi-Fi
Action: On another approved device connected to the same SSID, open two unrelated websites.
Why this matters: If other devices also fail, the issue is probably shared and should not be treated as a single-computer problem.
What to look for: Determine whether the failure affects one device, one access point area, or all wireless users.
Expected result: You should know the scope before making local changes.
Step 3: Review the computer's IP configuration
Action: Open Command Prompt and run ipconfig. Review the IPv4 address and Default Gateway for the active wireless adapter.
Why this matters: Wi-Fi can be associated with an access point while the computer still lacks a usable IP configuration.
What to look for: Look for an address beginning with 169.254, a blank default gateway, or addressing that differs unexpectedly from working devices.
Expected result: The computer should have a normal address in the expected network range and a default gateway.
Step 4: Test local gateway reachability
Action: In Command Prompt, run ping followed by the default gateway address from ipconfig.
Why this matters: This tests whether the computer can communicate beyond the Wi-Fi association and reach the local router or gateway.
What to look for: A failure can indicate a local wireless, VLAN, adapter, or access-point problem. A response means the local path is working.
Expected result: The gateway should normally be reachable unless ping is intentionally blocked.
Step 5: Separate internet reachability from DNS
Action: Run ping 1.1.1.1, then run nslookup www.microsoft.com.
Why this matters: If an external IP is reachable but a hostname is not, the failure is more likely DNS than Wi-Fi itself.
What to look for: Compare external-IP reachability with the DNS lookup response.
Expected result: A healthy connection should have both upstream reachability and working name resolution.
Step 6: Reconnect only the affected computer
Action: Select the taskbar network icon, disconnect from the Wi-Fi network, wait a few seconds, and reconnect. If authorized and the credentials are known, Forget and reconnect only when a simple disconnect does not help.
Why this matters: Reconnecting can renew the local wireless session without interrupting other users.
What to look for: Check whether the computer receives a normal IP address and loses the No internet status.
Expected result: The computer should reconnect with a valid network configuration.
Step 7: Check VPN and proxy state
Action: Open Settings > Network & internet > VPN and Settings > Network & internet > Proxy. Confirm that only approved settings are active.
Why this matters: A failed VPN tunnel or incorrect proxy can prevent browsing even when Wi-Fi and the gateway are healthy.
What to look for: Look for a VPN stuck connecting, an unexpected manual proxy, or an organizational policy message.
Expected result: Network traffic should use the organization's intended VPN and proxy configuration.
What to look for
- Multiple devices fail on the same SSID: likely shared wireless or upstream problem.
- 169.254 address: DHCP or local network configuration problem.
- Gateway fails: local Wi-Fi, access point, VLAN, or adapter problem.
- External IP works but DNS fails: DNS problem.
- Only the affected device fails with valid network tests: inspect VPN, proxy, endpoint, and browser layers.
When to stop
When to contact IT
Contact IT when multiple devices are affected, the computer receives a 169.254 address repeatedly, cannot reach the gateway, DNS fails consistently, or managed VPN/proxy/security controls appear involved. Provide the SSID, scope, ipconfig results, gateway test, and DNS test.
Need help with this issue?
J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.
Contact J3 Systems GroupAuthoritative references
Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.