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

31 Jul 2026

Your laptop says it is connected to Wi-Fi. The signal bars look strong. Windows reports Connected, and your phone may even show the same network name.

Yet websites do not open, email will not synchronise, Teams stays offline, and cloud applications refuse to connect.

This usually means the Wi-Fi connection itself is working, but the device has not received the correct network information needed to reach anything beyond the local wireless network.

Two of the most common causes are problems with DHCP and the default gateway.

Connected to Wi-Fi Does Not Always Mean Connected to the Internet

Wi-Fi only describes the wireless link between your device and an access point or router.

A successful Wi-Fi connection confirms that:

The wireless adapter is working
The device can detect the network
The security password was accepted
The device has associated with an access point

It does not guarantee that the device has:

A valid IP address
The correct subnet mask
A working default gateway
Usable DNS servers
Permission to access the internet
A functioning route through the router

This is why a computer can show full Wi-Fi signal while nothing loads.

What DHCP Does

DHCP stands for Dynamic Host Configuration Protocol.

It automatically provides devices with the network settings they need, including:

IP address
Subnet mask
Default gateway
DNS servers
Lease duration
Other network-specific options

Without DHCP, every laptop, phone, printer, and tablet would usually need to be configured manually.

When DHCP works correctly, a device joins the network and receives valid settings within seconds.

When it fails, the device may connect to Wi-Fi but remain unable to communicate properly.

What Is the Default Gateway?

The default gateway is normally the router or firewall that carries traffic from the local network to other networks, including the internet.

A typical home or small-office configuration might look like:

Device IP: 192.168.1.45
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.1
DNS server: 192.168.1.1

The exact numbers vary between networks.

If the gateway is missing, wrong, offline, or unreachable, the device may still communicate with local systems but will not be able to reach internet services.

Common Symptoms of DHCP or Gateway Problems

Typical signs include:

Wi-Fi shows as connected but websites do not open
Windows reports No internet
The device receives an address beginning with 169.254
Local printers or servers work, but internet services do not
Some devices work while one does not
Devices lose access after waking from sleep
The connection works temporarily after a restart
The router appears reachable, but external websites are not
The default gateway field is blank
The connection repeatedly changes between connected and no internet

These symptoms can also be caused by DNS, VPN, firewall, or internet-service problems, so test the connection step by step.

First, Check Whether Other Devices Work

Connect another device to the same Wi-Fi network.

Try a phone, tablet, or another computer.

If Every Device Is Affected

The likely causes include:

Router or firewall failure
Internet-service outage
DHCP server failure
Access-point uplink problem
Incorrect network configuration
Failed modem or fibre equipment
Network-wide DNS problem

If Only One Device Is Affected

The problem is more likely to involve:

A stale DHCP lease
Incorrect manual IP settings
A damaged network profile
VPN software
Security software
A network-driver issue
A duplicate IP address
A device-specific proxy setting

This simple comparison helps avoid resetting the entire network for a fault limited to one laptop.

Check the IP Address in Windows

Open Command Prompt and enter:

ipconfig

Find the active wireless adapter.

Look for:

IPv4 Address
Subnet Mask
Default Gateway

A normal private address often begins with:

192.168
10
172.16 through 172.31

The exact range depends on the network.

What a 169.254 Address Means

If the device shows an address such as:

169.254.87.24

it has probably failed to receive an address from DHCP.

Windows assigns itself an automatic private address so that basic local communication may still be possible, but the device will not normally have proper internet access.

Common causes include:

DHCP server unavailable
Router not responding
Access point isolated from the network
Wireless driver problem
VLAN configuration error
DHCP scope exhausted
Security controls blocking DHCP
A faulty network adapter

An address beginning with 169.254 is one of the clearest signs of a DHCP problem.

Check Whether the Default Gateway Is Missing

In the ipconfig output, find Default Gateway.

If the field is blank, the device does not know where to send traffic destined for the internet.

A missing gateway can result from:

Incomplete DHCP information
Manual IP settings
A damaged network profile
VPN or virtual-adapter interference
Incorrect VLAN configuration
A router fault
A failed DHCP relay

If the gateway is present but incorrect, traffic may be sent to the wrong device.

Renew the DHCP Lease

Windows can request fresh network settings from DHCP.

Open Command Prompt as administrator and enter:

ipconfig /release

ipconfig /renew

The first command releases the current address. The second requests a new one.

Afterwards, run:

ipconfig

Confirm that the device has received:

A valid IPv4 address
A subnet mask
A default gateway
DNS servers

If the renewal command times out or reports that it cannot contact the DHCP server, investigate the router, wireless network, VLAN, or adapter.

Disconnect and Reconnect to Wi-Fi

A simple reconnection can trigger a fresh DHCP request.

Select the Wi-Fi icon
Disconnect from the network
Wait a few seconds
Reconnect
Test again

You can also turn Wi-Fi off and back on.

If the fault returns frequently, do not rely on this as the permanent solution. Identify why DHCP information is becoming stale or unavailable.

Forget and Rejoin the Network

A saved Wi-Fi profile can contain damaged or outdated settings.

In Windows 11:

Open Settings
Select Network & internet
Select Wi-Fi
Open Manage known networks
Select the affected network
Choose Forget
Reconnect and enter the wireless password

This creates a fresh network profile.

Be cautious on business devices where wireless settings are managed through Intune, Group Policy, or another management platform.

Restart the Network Adapter

Disable and re-enable the wireless adapter.

Press Windows key + R
Enter:

ncpa.cpl

Right-click the Wi-Fi adapter
Select Disable
Wait several seconds
Select Enable

This restarts the adapter without rebooting the whole computer.

Restart the Router Carefully

For a home or very small office, restarting the router may restore DHCP and gateway services.

Disconnect the router’s power, wait approximately 30 seconds, and reconnect it.

Allow several minutes for:

Broadband connection
Wi-Fi
DHCP
DNS forwarding
Firewall services

to become available again.

In a business environment, do not restart routers, firewalls, switches, or access points without checking the impact. A restart could interrupt phones, servers, VPNs, payment systems, and other users.

Test the Default Gateway

From Command Prompt, ping the gateway address shown by ipconfig.

For example:

ping 192.168.1.1

Use the actual gateway address from your network.

If the Gateway Replies

The device can communicate with the router locally.

The remaining issue may involve:

Internet connection
DNS
Firewall rules
Routing
VPN software
Upstream provider

If the Gateway Does Not Reply

Possible causes include:

Incorrect IP settings
Wrong subnet
Wireless isolation
Access-point uplink failure
Router offline
Firewall blocking local traffic
Duplicate IP address
Driver or adapter fault

Some gateways block ping, so also try opening the router’s management page or testing another known local device.

Test an External IP Address

Try pinging a public IP address:

ping 1.1.1.1

If the gateway responds but the external IP does not, the router may not have a working internet route.

Possible causes include:

Broadband outage
Modem or fibre termination fault
Router WAN problem
Incorrect default route
Firewall rule
Provider authentication failure

If the external IP replies but websites still do not load, DNS is a strong suspect.

Test DNS Separately

Try:

nslookup example.com

This checks whether the device can translate a domain name into an IP address.

If external IP addresses respond but domain names do not, review the DNS settings supplied by DHCP.

The device may have received:

A missing DNS server
An invalid DNS address
An unreachable internal DNS server
An old server address
A DNS server accessible only through a VPN

DHCP and DNS faults often appear together because DHCP is responsible for delivering DNS information.

Check for Manual IP Settings

A device may have been configured with a manual address that no longer matches the network.

In Windows 11:

Open Settings
Select Network & internet
Select Wi-Fi
Open the connected network’s properties
Find IP assignment
Check whether it is set to Automatic (DHCP) or Manual

For most laptops that move between networks, automatic DHCP is the correct setting.

A manual address may fail when:

The router is replaced
The network range changes
The device moves to another office
The gateway address changes
DNS servers are replaced
The address conflicts with another device

Do not change managed business network settings without approval.

Duplicate IP Addresses

Two devices using the same IP address can cause intermittent connectivity.

Symptoms may include:

Internet access appearing and disappearing
The gateway working only occasionally
Windows reporting an address conflict
One device disconnecting when another joins
Connections switching between devices
Remote access reaching the wrong machine

Duplicate addresses are often caused by manually assigned IPs inside the DHCP allocation range.

DHCP reservations should be used where fixed addresses are needed.

DHCP Scope Exhaustion

A DHCP server has a defined pool of addresses available to clients.

For example, it may be configured to provide addresses from:

192.168.1.100 to 192.168.1.200

If every address is already leased, new devices may connect to Wi-Fi but fail to receive usable network settings.

This can happen in:

Busy offices
Guest networks
Events
Schools
Hotels
Networks with very long lease durations
Environments with many personal devices
Networks where old leases are not being cleared

An administrator should check the DHCP scope, active leases, exclusions, and lease duration.

Do not simply widen the range without confirming the subnet and network design.

DHCP Server Failure

In a home network, the router normally provides DHCP.

In a business, DHCP may be provided by:

Windows Server
Firewall
Router
Layer 3 switch
Cloud-managed gateway
Dedicated DHCP appliance

If the DHCP service stops, devices with existing leases may continue working temporarily while new or reconnecting devices fail.

This can create a confusing situation where some staff have internet access and others do not.

Check:

DHCP service status
Available leases
Server event logs
Scope configuration
Authorised DHCP servers
Network relay settings
Firewall rules

DHCP Relay and VLAN Issues

Larger networks often separate devices into VLANs.

The DHCP server may sit on another network, so routers or switches use a DHCP relay to forward requests.

A relay fault can cause devices to:

Connect to the access point
Receive strong Wi-Fi signal
Fail to obtain an IP address
Receive settings from the wrong subnet
Lose access after moving between access points

Possible causes include:

Missing helper address
Wrong VLAN assignment
Incorrect switch-port tagging
Access point using the wrong network profile
Firewall blocking DHCP traffic
Relay pointing to an old server

This requires investigation of the network infrastructure rather than the laptop alone.

Incorrect Gateway Supplied by DHCP

A DHCP server can be working but distributing the wrong gateway.

This may happen after:

Router replacement
Firewall migration
Network redesign
Scope duplication
Configuration restore
Typographical error
An old DHCP server remaining active

Devices may receive valid-looking IP addresses but send all external traffic to a gateway that does not exist.

Compare the gateway received by working and non-working devices.

Rogue DHCP Servers

A rogue DHCP server is an unauthorised device supplying network settings.

It may be:

An incorrectly connected home router
A misconfigured wireless extender
A test device
A virtual machine
A malicious system
A second DHCP server accidentally enabled

Affected devices may receive:

Wrong IP range
Wrong gateway
Wrong DNS server
Short lease times
No internet route

If different devices receive completely different network ranges on the same Wi-Fi network, investigate for multiple DHCP servers.

Business switches and security platforms may support DHCP snooping to help prevent this.

Access Point Connected but Uplink Failed

A wireless access point can continue broadcasting its network name even when its wired connection to the main network has failed.

Devices connect with full signal but cannot reach:

DHCP server
Default gateway
DNS
Internet
Local servers

Check:

Ethernet cable to the access point
Switch port
Power over Ethernet
VLAN configuration
Mesh backhaul
Access-point status
Controller alerts

A strong signal only proves that the device is close to the access point.

Guest Wi-Fi and Captive Portals

Some guest networks require users to accept terms, enter a code, or sign in through a web portal.

Until that process is complete, the device may show as connected while normal websites fail.

Open a browser and try visiting a simple non-encrypted page to trigger the login screen.

Problems can occur when:

The portal does not open automatically
The session has expired
DNS is blocked before authentication
Private address features confuse registration
The device was previously registered with another MAC address
The user has reached a time or data limit

Business guest networks may also block access to local printers and servers by design.

VPN Problems

A VPN can change:

Default gateway
DNS servers
Routing table
Firewall rules
Proxy settings

If the VPN disconnects badly, the computer may remain unable to route traffic normally.

Temporarily disconnect the VPN and test again.

Some VPN clients include a kill switch that deliberately blocks internet access whenever the secure tunnel is unavailable.

Do not disable business security controls permanently. Report repeat VPN routing problems to the IT provider.

Check Proxy Settings

An incorrect proxy can make browsers appear offline even when the network itself is working.

Open:

Settings > Network & internet > Proxy

Unless your organisation intentionally uses one, manually configured proxy settings would normally be disabled.

Malware, unwanted software, old VPN clients, and previous workplace configurations can leave incorrect proxy details behind.

Windows Network Reset

Windows includes a network-reset option that removes and reinstalls network adapters.

Open:

Settings > Network & internet > Advanced network settings > Network reset

This can repair damaged networking components, but it also removes:

Saved adapter settings
Some VPN adapters
Virtual switches
Custom DNS settings
Network profiles

The computer will restart.

Use this after simpler DHCP and adapter steps have failed, not as the first response.

Reset the TCP/IP Stack

Open Command Prompt as administrator and run:

netsh int ip reset

netsh winsock reset

ipconfig /flushdns

Restart the computer afterwards.

These commands can repair damaged TCP/IP and Winsock configuration.

They will not fix a failed DHCP server, broken access-point uplink, or incorrect gateway being supplied by the network.

Update the Wireless Driver

A damaged or incompatible wireless driver can interrupt DHCP communication.

Obtain the appropriate driver from:

Laptop manufacturer
Computer manufacturer
Wireless-adapter manufacturer
Approved Windows Update channel

Avoid unofficial driver-update utilities.

If the problem began immediately after a driver update, use Device Manager to roll back the driver where possible.

Power Management and Sleep Issues

Some laptops lose valid network settings after waking from sleep.

In Device Manager:

Expand Network adapters
Open the wireless adapter’s properties
Select Power Management
Temporarily clear Allow the computer to turn off this device to save power

Also review advanced settings such as:

Minimum power consumption
U-APSD
Roaming aggressiveness
Preferred band
Sleep on WoWLAN disconnect

The available options vary by adapter.

If reconnecting restores access every time, driver or power-management behaviour may be involved.

Check the System Date and Time

A significantly incorrect date or time can prevent secure websites and cloud services from loading.

The network may be functioning, but certificate validation fails.

Confirm that:

Date is correct
Time is correct
Time zone is correct
Automatic time synchronisation is enabled

This is less likely when raw IP tests also fail, but it can explain why some applications work and secure websites do not.

IPv4 and IPv6 Problems

Some networks use both IPv4 and IPv6.

A device may receive incomplete or broken settings for one protocol.

Symptoms can include:

Some websites loading while others fail
Long delays before pages open
Applications behaving inconsistently
Gateway tests working only for one protocol

Do not disable IPv6 permanently as a routine fix.

Instead, compare results, review router advertisements, DHCPv6, DNS, and upstream connectivity.

Business networks should correct the protocol configuration rather than relying on broad workarounds.

Router Has Wi-Fi but No Internet Connection

The router may continue providing Wi-Fi and DHCP even when its external connection has failed.

Devices may receive valid settings and reach the gateway, but nothing beyond it.

Check the router or firewall for:

WAN status
Public IP address
Authentication
Modem synchronisation
Fibre terminal status
Default route
Provider outage
Failed failover connection

Restarting the router may help temporarily, but repeated failures require investigation.

Do Not Use Random Static IP Settings

Entering a manual IP address found in an online guide can create more problems.

A static address must match:

Network range
Subnet mask
Default gateway
DNS configuration
DHCP exclusions
VLAN

An incorrect static address can make the device completely unreachable or create a conflict with another system.

Use manual settings only when you know the approved network configuration.

A Practical Troubleshooting Order

Use this sequence when Wi-Fi is connected but nothing loads:

Test another device on the same Wi-Fi network
Check the computer’s IP address with ipconfig
Look for a 169.254 address
Confirm that a default gateway is present
Disconnect and reconnect to Wi-Fi
Renew the DHCP lease
Ping the default gateway
Test an external IP address
Test DNS resolution
Check for manual IP and proxy settings
Disconnect VPN software temporarily
Forget and rejoin the Wi-Fi network
Restart the network adapter
Check the router or DHCP server
Investigate DHCP scope, relay, VLAN, and gateway settings
Update the wireless driver
Use network reset only after simpler fixes fail

This order helps identify whether the fault is local to the device or belongs to the wider network.

When to Contact an IT Professional

Professional assistance is recommended when:

Several users cannot obtain an IP address
Devices receive addresses from the wrong subnet
The default gateway is missing or incorrect
DHCP leases are exhausted
Multiple DHCP servers may be active
The network uses VLANs or DHCP relay
Access points remain online but have lost their uplink
VPN or firewall changes affect routing
The problem repeatedly returns
Business-critical systems are offline

An IT technician can inspect DHCP leases, scope settings, gateway routes, VLAN assignments, wireless-controller alerts, DNS, firewall policies, and network logs to identify the underlying cause.

Connected to Wi-Fi but Still Offline?

A strong Wi-Fi signal only confirms that your device can communicate with the wireless access point.

For internet access, it also needs a valid IP address, subnet, default gateway, DNS configuration, and a working route beyond the router.

When nothing loads, check the IP information first. A 169.254 address, missing gateway, or failed DHCP renewal can quickly reveal where the problem lies.

Hamilton Group can diagnose DHCP and gateway issues, repair unreliable wireless networks, configure routers and firewalls, investigate VLAN problems, and restore dependable business connectivity.

Call 0330 043 0069 or visit hgmssp.com to book a meeting with one of our networking experts.

Previous Next