A Windows 11 Pro PC that connects to the local network but lacks internet access typically suffers from an incorrect IP configuration, specifically a DHCP-assigned address outside the router’s valid range. This mismatch prevents traffic from reaching the default gateway, isolating the device from external networks while keeping local LAN communication intact.
Understanding the DHCP Address Mismatch
The most common cause for this specific symptom is that the Dynamic Host Configuration Protocol (DHCP) server on your router has assigned an IPv4 address that does not align with the subnet mask or gateway settings required for internet routing. In many cases, the computer receives an APIPA address (Automatic Private IP Addressing), which falls within the
169.254.x.x range. These addresses are self-assigned when a DHCP request fails or times out, meaning the device cannot communicate with any router beyond the immediate physical link. Even if the address looks like a standard private IP (such as
192.168.1.x), it might be outside the pool of active leases defined by your router’s firmware, leading to a situation where you can ping other local devices but not the gateway itself.
To verify if this is the root cause, you must inspect the current network adapter status. Open the Command Prompt and run
ipconfig /all. Look for the
IPv4 Address line under your active Ethernet or Wi-Fi adapter. If the address begins with
169.254, the DHCP client failed entirely. If it starts with
10.,
172.16-172.31., or
192.168., check the
Default Gateway field. If the Default Gateway is blank or shows an address different from your router’s actual IP (often
192.168.1.1 or
192.168.0.1), your routing table is broken. This scenario often requires manual intervention to reset the lease or correct static settings. For broader context on general connectivity failures, you may find
Troubleshooting LAN Connection Issues on a Brand New Windows 11 Machine helpful, as it covers similar baseline diagnostics.
Resetting the Network Stack via Command Line
Before altering hardware settings, the most effective software fix is to clear the corrupted network state in Windows 11. This process forces the operating system to drop existing connections, flush DNS caches, and request fresh configurations from the DHCP server. Start by opening the Start menu, typing
cmd, right-clicking
Command Prompt, and selecting
Run as administrator.
Execute the following commands in order, pressing Enter after each one:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
The
netsh winsock reset command repairs the Windows Socket (Winsock) catalog, which handles network protocol bindings. The
netsh int ip reset command resets TCP/IP settings to their default state. Following these resets,
ipconfig /release tells the adapter to give up its current IP address, and
ipconfig /renew initiates a new handshake with the router. Finally,
ipconfig /flushdns clears stale DNS records that might be directing traffic to invalid servers. After running these commands, restart your computer. Upon reboot, Windows will attempt to obtain a new IP address automatically. Check if internet access is restored by pinging
8.8.8.8 (Google’s public DNS). If the ping succeeds but web browsing still fails, the issue may lie with DNS resolution rather than connectivity.
Configuring Static IP Settings Manually
If automatic DHCP renewal fails repeatedly, forcing a static IP configuration can bypass the router’s faulty assignment logic. This method ensures your PC uses a known-good address that matches your network’s subnet. First, determine your router’s IP address and subnet mask. You can find this by looking at the label on your router or by checking the
Default Gateway value from the
ipconfig /all output mentioned earlier.
Navigate to
Settings > Network & internet > Ethernet (or
Wi-Fi). Click on
Hardware properties or
IP assignment. Change the setting from
Automatic (DHCP) to
Manual. Toggle
IPv4 to
On. Fill in the fields as follows:
- IP address: Choose an address outside the router’s DHCP pool to avoid conflicts. If your router is
192.168.1.1, use 192.168.1.50.
- Subnet mask: Typically
255.255.255.0 for home networks.
- Gateway: Your router’s IP address (e.g.,
192.168.1.1).
- DNS Server: Use
8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) for reliability.
Click
Save. This manual entry bypasses the DHCP negotiation phase entirely. If internet access returns immediately, the problem was indeed a DHCP scope exhaustion or misconfiguration on the router side. Note that if you move this PC to a different network (like a coffee shop), you must switch back to Automatic (DHCP) to ensure compatibility. For users experiencing intermittent drops alongside this issue, reviewing driver stability is crucial, as seen in
Windows 11 (ASUS B550M-WIFi) Realtek NIC disconnects.
Frequently Asked Questions
Why can I ping local IPs but not websites?
This indicates that Layer 2 (data link) and Layer 3 (network) connectivity to the local subnet is working, but the default gateway route is missing or blocked. Your computer knows how to talk to neighbors but doesn’t know how to send data to the internet. Verify that the
Default Gateway in
ipconfig /all matches your router’s actual IP address.
What if my IP address is 169.254.x.x?
An address starting with
169.254 is an APIPA address, meaning the DHCP client timed out waiting for a response from the router. This usually happens due to a disabled DHCP service on the router, a faulty network cable, or a temporary router glitch. Restarting both the modem/router and the PC often resolves this by forcing a fresh DHCP discovery.
How do I check if my firewall is blocking internet?
While firewalls rarely block LAN traffic while allowing internet, they can sometimes corrupt routing tables. Temporarily disable third-party antivirus firewalls or Windows Defender Firewall to test connectivity. If internet returns, create an inbound/outbound rule exception for your browser or networking services in the firewall settings before re-enabling protection.
Should I update my network drivers?
Yes, outdated NIC drivers can cause DHCP renegotiation failures. Visit your motherboard or laptop manufacturer’s website and download the latest LAN/Wi-Fi drivers for Windows 11. Avoid using generic drivers from Windows Update if they are older than the vendor-specific versions, as they may lack proper power management features that keep the connection alive.
Can a bad subnet mask cause this issue?
Absolutely. If your subnet mask is set incorrectly (e.g.,
255.255.0.0 instead of
255.255.255.0), Windows may calculate that the gateway is on a different network segment. This causes it to send internet-bound traffic to the local broadcast instead of the router. Always ensure your subnet mask matches the majority of devices on your network, which is almost always
255.255.255.0 for home environments.