Resolved Exact fix not confirmed

Wi-Fi connected. Internet unavailable.

A Windows 11 work laptop could associate with Wi-Fi but had no internet access. The adapter was found with static IPv4, gateway, and DNS settings. Connectivity returned during troubleshooting, although the precise recovery trigger could not be confirmed.

Category: Windows IPv4 / DHCP
Device: Windows work laptop
Network: Wi-Fi · GalaOffice
Impact: No internet access

What we found

Wireless association and authentication were working. The failure was above the Wi-Fi link layer: the adapter initially had DHCP disabled and retained a static IPv4 address, gateway, and DNS configuration.

Root cause remains unconfirmed.

The static configuration was a credible contributor and was corrected. After the change, Windows initially failed to obtain a DHCP lease and assigned an APIPA address in the 169.254.x.x range. Internet access later returned, but the action that caused recovery was not isolated.

Wi-Fi adapter: MediaTek Wi-Fi 7 MT7925 Wireless LAN Card.
Tailscale and Npcap virtual adapters were present.
The Realtek PCIe GbE Ethernet adapter was disconnected.
No passwords, authentication secrets, or public IP addresses were shared.

Troubleshooting timeline

Completed

Collected the full network configuration.
ipconfig /all
The Wi-Fi adapter showed DHCP disabled with a static IPv4 address, default gateway, and DNS servers.

Interpretation: the retained static configuration could prevent the laptop from operating on other networks.
Completed

Verified the IPv4 interface configuration.
netsh interface ipv4 show config name="Wi-Fi"
Confirmed static IPv4, gateway, and DNS settings with DHCP disabled.

Interpretation: the adapter was not requesting addresses dynamically.
Completed

Changed IPv4 addressing to DHCP.
netsh interface ipv4 set address name="Wi-Fi" source=dhcp
The command completed with no output.

Interpretation: Windows accepted the configuration change.
Completed

Changed DNS configuration to DHCP.
netsh interface ipv4 set dnsservers name="Wi-Fi" source=dhcp
The command completed with no output.

Interpretation: the static DNS configuration was removed.
Did not complete

Attempted DHCP lease renewal.
ipconfig /release · ipconfig /renew
The renewal operation stalled for several minutes.

Interpretation: DHCP negotiation was not completing.
Completed

Collected the updated network configuration.
ipconfig /all
DHCP was enabled, but the Wi-Fi adapter had an APIPA address in the 169.254.x.x range.

Interpretation: Windows attempted DHCP but did not receive a lease.
Completed

Verified wireless connection status.
netsh wlan show interfaces
The adapter was connected to GalaOffice with good signal and successful authentication.

Interpretation: wireless association worked; the failure existed above the link layer.
Failed

Tested the previously configured gateway.
ping [redacted private gateway]
The ping failed with “General failure.”

Interpretation: packets could not be transmitted without a usable IPv4 configuration.
Completed

Verified interface operational state.
netsh interface ipv4 show interfaces
The Wi-Fi interface reported as connected.

Interpretation: the adapter itself appeared operational.
Mostly completed

Reset the Windows IP stack.
netsh int ip reset
Most operations succeeded. One component returned “Access is denied,” and Windows requested a restart.

Interpretation: the reset largely succeeded; the denied component may have been protected or managed, but no definitive conclusion was reached.
Resolved

Observed the system after additional troubleshooting.

The user reported that network connectivity was restored.

Interpretation: the issue resolved during troubleshooting, but the triggering event could not be confirmed.

Resolution and verification

Actions taken

Reviewed the existing IPv4 configuration.
Returned IPv4 addressing and DNS to DHCP.
Attempted DHCP release and renewal.
Verified Wi-Fi association and interface state.
Reset the Windows IP stack.

Final working state

Internet connectivity restored, confirmed by the user.

The exact corrective action remains unknown.

Lessons for the next occurrence

A static IPv4 configuration can fail when a Windows laptop moves between networks.
An APIPA address indicates that DHCP did not provide a lease.
Successful Wi-Fi association does not guarantee a valid IP configuration.
An IP stack reset may require a restart before taking full effect.
Verify connectivity after each major change so the effective fix can be identified.

Recommended procedure

Collect ipconfig /all before making changes.
Verify whether DHCP is enabled.
If static addressing is unnecessary, return both IPv4 addressing and DNS to DHCP.
If APIPA is assigned, investigate DHCP availability before assuming an internet outage.
If needed, reset the Windows IP stack and restart the device.
Test connectivity after every major change.

Commands used

ipconfig /all
netsh interface ipv4 show config name="Wi-Fi"
netsh interface ipv4 set address name="Wi-Fi" source=dhcp
netsh interface ipv4 set dnsservers name="Wi-Fi" source=dhcp
ipconfig /release
ipconfig /renew
netsh wlan show interfaces
ping [redacted private gateway]
netsh interface ipv4 show interfaces
netsh int ip reset

Follow-up

Confirm the Wi-Fi adapter remains configured for DHCP.
Document whether this device requires static addressing in the future.
If the issue recurs, investigate DHCP availability, endpoint security software, VPN filter drivers, and wireless driver health.

What we found

Troubleshooting timeline

Collected the full network configuration.

Verified the IPv4 interface configuration.

Changed IPv4 addressing to DHCP.

Changed DNS configuration to DHCP.

Attempted DHCP lease renewal.

Collected the updated network configuration.

Verified wireless connection status.

Tested the previously configured gateway.

Verified interface operational state.

Reset the Windows IP stack.