Wi-Fi Works but Nothing Loads? DHCP and Gateway Issues Explained

Your laptop shows:

Connected

The Wi-Fi bars look strong.

You are definitely joined to the correct wireless network.

But:

websites do not load

Outlook stays disconnected

Teams cannot connect

OneDrive stops syncing

cloud applications refuse to open

That can feel contradictory.

It is not.

A successful Wi-Fi connection only proves that your device has established a wireless link to the access point.

You still need several other things to work:

Wi-Fi → IP address → default gateway → DNS → internet

If any one of those breaks, Windows can still look “connected” while nothing useful works.

First: Check Whether the Problem Affects One Device or Everyone

This is the fastest diagnostic split.

Only one laptop is affected

Investigate:

DHCP on that device

network adapter

driver

VPN

static IP settings

Windows networking

Every device is affected

Investigate:

router

DHCP server

access point/uplink

broadband/ISP

wider network outage

Microsoft similarly recommends testing another device because it helps distinguish a problem on the Windows PC from a problem in the wider network.

Step 1: Check Your IP Configuration

Open:

Command Prompt

and run:

ipconfig

Microsoft documents ipconfig as the built-in command for displaying IPv4/IPv6 address information, subnet mask and default gateway.

Look under your Wi-Fi adapter.

A healthy home or small-business connection might show something like:

IPv4 Address. . . . . . : 192.168.1.84
Subnet Mask . . . . . . : 255.255.255.0
Default Gateway . . . . : 192.168.1.1

The exact numbers will vary.

What matters is whether Windows has received a sensible address and gateway.

What Is DHCP?

DHCP stands for:

Dynamic Host Configuration Protocol

Its job is to automatically give devices the network information they need.

That usually includes:

IP address

subnet mask

default gateway

DNS servers

Microsoft’s DHCP troubleshooting guidance describes automatic IP assignment as the job of the DHCP service.

Without a usable DHCP lease, your PC may successfully join Wi-Fi but still have nowhere useful to send network traffic.

The 169.254.x.x Clue

If ipconfig shows an address beginning with:

169.254.

that is a strong clue that normal DHCP assignment failed.

Windows can assign itself an automatic local address when it cannot obtain one from DHCP.

That can allow limited same-link communication in some situations, but it normally will not provide ordinary access to your router and internet.

In practical terms:

Wi-Fi connected + 169.254.x.x = investigate DHCP first.

Step 2: Renew the DHCP Lease

If the address looks wrong or DHCP may have failed, try:

ipconfig /release

then:

ipconfig /renew

The ipconfig command supports both releasing and renewing DHCP configuration.

Then run:

ipconfig

again.

You now receive a normal local address

Good.

Retry browsing.

You still receive no useful address

Now investigate:

DHCP server/router

Wi-Fi adapter

VLAN/network configuration

DHCP scope exhaustion

security controls

Repeatedly renewing will not fix a DHCP server that cannot answer.

Step 3: Check the Default Gateway

The default gateway is usually the router or firewall that carries traffic from your local network towards other networks.

In many simple networks it might be:

192.168.1.1

or:

192.168.0.1

The exact address depends on your network.

If ipconfig shows no default gateway, the PC may have a local IP address but still lack the route it needs to reach the internet.

That is why:

valid-looking IP address ≠ complete network configuration.

Step 4: Ping the Gateway

Microsoft specifically recommends identifying the default gateway with ipconfig and then pinging it when troubleshooting Windows Wi-Fi connectivity.

Run:

ping 192.168.1.1

Replace the address with your actual gateway.

You receive replies

That tells you:

PC → Wi-Fi → local network → gateway

is functioning at least at a basic IP level.

Move outward.

The gateway does not reply

Investigate the local network before blaming DNS or the ISP.

Possible causes include:

wrong subnet

wrong gateway

Wi-Fi isolation

router problem

access-point/uplink issue

local firewall/policy

Do not start changing public DNS servers if you cannot even reach your own gateway.

Step 5: Test Internet Reachability Separately From DNS

This is where troubleshooting often becomes muddled.

There are two different questions:

Can I reach the internet by IP?

and:

Can I resolve domain names?

If the gateway works but websites do not, DNS becomes more interesting.

Run:

nslookup microsoft.com

If the lookup fails, investigate DNS.

If it returns addresses normally but applications still cannot connect, the fault lies somewhere else.

This prevents every “internet not working” problem turning into another random DNS change.

DNS Is Not the Same as DHCP

DHCP often supplies the DNS server address to the PC.

But DHCP and DNS perform different jobs.

DHCP

Gives the computer its network configuration.

DNS

Translates names such as:

microsoft.com

into IP addresses.

So:

no valid IP/gateway
→ investigate DHCP/networking.

valid IP/gateway, but names fail
→ investigate DNS.

That distinction is crucial.

Step 6: Forget and Reconnect to the Wi-Fi Network

If one device is affected, remove the saved Wi-Fi profile.

Go to:

Settings > Network & internet > Wi-Fi > Manage known networks

Select the network and choose:

Forget

Then reconnect and re-enter the password.

Microsoft includes forgetting and reconnecting to a Wi-Fi network among its supported connection troubleshooting steps.

This can clear damaged wireless profile configuration.

It will not repair a DHCP server that is broken for every device.

Step 7: Check IP Assignment in Windows

Windows 11 lets you configure IP assignment under its network settings. Microsoft documents changing IP assignment from the Wi-Fi or Ethernet configuration pages.

For most ordinary networks, the PC should use:

Automatic (DHCP)

unless there is a deliberate reason for static configuration.

If somebody manually entered:

IP address

subnet

gateway

DNS

those settings may now be wrong.

For example, a laptop configured for:

192.168.0.50

will have problems if the current network uses:

192.168.1.x

Do not assume a static IP is more reliable simply because it is static.

Step 8: Watch for Static IP Problems

Static addressing can cause:

wrong subnet

wrong gateway

duplicate IP address

stale DNS

settings copied from another network

If a laptop travels between offices, manually configured addressing becomes particularly easy to get wrong.

Unless a device genuinely needs a fixed address, DHCP is usually the cleaner client configuration.

For devices that do need predictable addressing, such as printers or infrastructure, a DHCP reservation is often easier to manage centrally.

Step 9: Check Whether the DHCP Scope Is Full

This is more relevant to business networks.

A DHCP server has a pool of addresses it can allocate.

For example:

192.168.1.50 - 192.168.1.200

If all available leases are consumed, new devices may join Wi-Fi successfully but fail to obtain usable addressing.

Microsoft’s DHCP guidance specifically centres on whether clients can obtain addresses from the DHCP server and recommends investigating DHCP server/client behaviour when they cannot.

An administrator should check:

available leases

scope utilisation

exclusions

reservations

lease duration

Do not simply increase the range before understanding why it became exhausted.

Step 10: Business Networks May Have VLAN Problems

In a managed office, the access point and DHCP server may not sit on the same network segment.

DHCP requests may need to cross:

VLANs

switches

routers

DHCP relay/IP helper

A configuration failure can create a very characteristic symptom:

Wi-Fi association succeeds

but:

no DHCP address arrives.

If an entire SSID or department is affected while another network works, investigate:

VLAN assignment

trunk configuration

DHCP relay

firewall rules

rather than individual laptops.

Step 11: Captive Portals Can Look Similar

Hotels, cafés and guest networks add another possibility.

You join Wi-Fi successfully.

The device gets:

valid IP

valid gateway

DNS

but websites still seem blocked until you accept a login or terms page.

Try opening a normal browser.

Look for a captive-portal sign-in prompt.

This is not a DHCP fault if the IP configuration is already healthy.

It is an access-control step imposed by the network.

Step 12: VPN Can Break Routing or DNS

If everything works until the VPN connects, compare:

VPN disconnected

and:

VPN connected

A VPN can change:

routes

DNS servers

default gateway behaviour

split-tunnel rules

If the fault only exists when connected to VPN, investigate the VPN configuration rather than resetting the home router.

On business devices, do not permanently disable a required VPN merely because internet access works without it.

Step 13: Run the Windows Network Troubleshooter

For current Windows 11 systems, Microsoft recommends starting the automated Network and Internet troubleshooter in the Get Help app.

It can identify and repair some:

adapter issues

IP configuration problems

connectivity faults

This is worth trying.

But still inspect ipconfig.

Understanding whether the PC lacks an address, gateway or DNS entry gives you much better evidence when the automated repair does not work.

Don't Reset the Network Stack First

You will find lots of guides immediately recommending:

netsh winsock reset

or a full Windows network reset.

Those can be useful later.

But they should not be step one.

If ipconfig clearly shows:

169.254.x.x

because the router's DHCP service is down, resetting Winsock does not fix the router.

Likewise, if every device in the office cannot obtain DHCP, repeatedly resetting Windows PCs wastes time.

Diagnose the layer first.

Router Restart: Useful, but Not a Diagnosis

In a small home network, restarting the router can clear:

stuck DHCP service

temporary routing issue

firmware glitch

But if the problem keeps returning, investigate the root cause.

For a business firewall/router, avoid unnecessary restarts during working hours without understanding the impact.

A reboot is a recovery action.

It is not evidence of why the fault happened.

A Useful Diagnostic Example

Suppose:

Wi-Fi signal = excellent

but nothing loads.

You run:

ipconfig

and see:

IPv4: 169.254.83.12
Default Gateway:

Now you know:

Wi-Fi association succeeded

DHCP did not provide normal network settings

no default gateway exists

Changing Chrome.

Changing DNS.

Reinstalling Teams.

None of those is where I would start.

Investigate DHCP.

Another Example

You see:

IPv4: 192.168.1.72
Gateway: 192.168.1.1

You run:

ping 192.168.1.1

and receive replies.

But:

nslookup microsoft.com

fails.

Now the evidence points towards:

DNS

rather than DHCP or Wi-Fi.

That is proper fault isolation.

The Fastest Troubleshooting Order

If Wi-Fi says connected but nothing loads:

1. Check whether one device or all devices are affected.

2. Run ipconfig.

3. Check for a sensible IPv4 address.

4. Check the default gateway.

5. If you see 169.254.x.x, investigate DHCP.

6. Renew the DHCP lease.

7. Ping the default gateway.

8. If the gateway works, test DNS.

9. Forget and reconnect to the Wi-Fi network if only one PC is affected.

10. Confirm IP assignment is set correctly.

11. Check VPN/captive portal where relevant.

12. On business networks, investigate DHCP scopes, VLANs and relay configuration.

13. Use full network reset only after simpler evidence points back to the Windows networking stack.

The key principle is:

Strong Wi-Fi only proves the radio connection. It does not prove the PC has a valid route to the internet.

How Hamilton Group Can Help

“Wi-Fi connected but no internet” can be caused by several completely different network layers.

Hamilton Group can help diagnose:

Windows 11 Wi-Fi

DHCP

default gateway issues

DNS

routers and firewalls

VLANs

DHCP scopes

VPN connectivity

business wireless networks

internet outages

For business environments, we can also determine whether the fault sits with one laptop, one wireless network or the wider DHCP/network infrastructure rather than applying the same Windows reset to every user.

Visit hgmssp.com or call 0330 043 0069 to discuss business networking and IT support.