Why Your Wi-Fi Device Has an IP Address but No Internet

Seeing an IP address on your phone, laptop, or streaming device can make a connection problem seem contradictory. If the device has an IP address, it has connected to the local network—but that doesn't prove the router can reach the wider internet, resolve website names, or authorize your access.

The useful distinction is between joining your home network and using the internet through that network. Once you separate those stages, the error becomes easier to diagnose without immediately resetting every device in the house.

What an IP address actually proves

Your router normally gives each connected device a private IP address through a service called DHCP. Addresses such as 192.168.1.24, 192.168.0.18, or 10.0.0.35 usually identify devices inside your home network. Receiving one means the device successfully communicated with the router and obtained local network settings.

That exchange doesn't confirm that the router has a working connection to your internet provider. Think of the router as a building with an internal address system and an outside connection. Your device can be assigned a room number even if the building's exit is blocked.

A device usually receives several related settings, not just an IP address:

• IP address: The device's local identity.
• Subnet mask or prefix: Which other addresses count as local.
• Default gateway: Usually the router; the path for traffic leaving the local network.
• DNS server: The service that turns names such as example.com into numerical addresses.

An IP address by itself tells you only that one part of this arrangement worked.

The four common points of failure

The router has no working upstream connection

Your device may communicate with the router normally while the router's connection to the modem, fiber terminal, or internet provider has failed. A loose cable, a provider outage, a modem problem, or an expired connection session can all produce this result.

In this situation, several devices usually lose internet access at once. They may still appear connected to Wi-Fi, and they may still be able to open the router's settings page. That local access isn't the same as internet access.

The default gateway is unavailable

The default gateway is normally your router's local IP address. When your device tries to reach a website outside your home network, it sends the traffic to that gateway. If the router is frozen, overloaded, misconfigured, or unreachable over Wi-Fi, the device can retain an IP address while outside traffic fails.

You can often test this by opening the router's administration address, if you know it. A page that loads from the router confirms local communication, not internet service. It does, however, help distinguish a Wi-Fi link problem from an upstream problem.

DNS is failing

DNS is the internet's naming system. Your browser asks a DNS server for the numerical address associated with a domain name before it can connect to most websites. If DNS is unavailable or incorrectly configured, the internet connection may exist even though normal web browsing produces messages such as “server not found.”

DNS failures can affect many websites at once, while some apps or services may continue working if they already know an address or use their own resolution method. Restarting the device may temporarily clear a bad DNS state, but it won't repair a DNS problem affecting the router or provider.

Access requires a sign-in or approval

Public Wi-Fi in hotels, airports, libraries, cafés, schools, and workplaces may assign an IP address before requiring you to accept terms, enter a room number, or sign in through a captive portal. Until that step is complete, the network may deliberately restrict internet traffic.

The sign-in page doesn't always appear automatically. Try opening a normal, non-secure web address in a browser, then look for the network's welcome or authentication page. Avoid entering sensitive information into a page that looks suspicious or has an unexpected domain; ask the venue for the correct network name and sign-in process.

Check the network’s access step: If you’re on public or managed Wi-Fi, open a browser and look for a legitimate sign-in, terms-of-use, or approval page before changing DNS or resetting network settings.

A sensible troubleshooting order

Start by checking whether the problem affects one device or the whole network. If another phone or computer on the same Wi-Fi can browse normally, focus on the affected device. If every device fails, focus on the router, modem, connection equipment, or service provider instead.

Next, move close to the router and check whether the device remains connected. A weak or unstable wireless signal can cause repeated interruptions even when the device still displays an IP address. If possible, test the same device near the router or with an Ethernet cable. This helps separate a wireless interference problem from an internet-service problem.

If only one device is affected, turn Wi-Fi off and on, then reconnect to the network. Confirm that airplane mode is disabled and that the device isn't using a VPN, proxy, or security application that has stopped working. A VPN can make a healthy connection appear unavailable if its tunnel can't be established.

For a broader failure, inspect the router and modem or fiber equipment. Look for a status light indicating that the outside connection is down, but treat the labels and colors as model-specific. Restarting equipment can help when it has lost a session or entered a temporary error state: power off the modem or internet terminal and router, wait briefly, then power them back on in the order recommended by their manufacturer. Give the equipment time to reconnect before deciding that the restart failed.

Confirm the outside connection: If every device is affected, check your provider’s service-status information or support channel using mobile data or another connection. Equipment lights can narrow the problem, but they don’t always identify the cause.

How to tell whether DNS is the problem

A useful clue is that the device can reach the router but can't open websites by name. On a computer, a network diagnostic command can test whether a domain name resolves. Windows includes nslookup, while macOS and many Linux distributions include the same command. For example, running nslookup example.com shows whether a DNS server returns an address.

You don't need to use command-line tools to make progress. Try more than one familiar website and check whether an app that was already open can still refresh. If numerical network tests or some connected services work while new website names fail, DNS becomes more likely. If nothing outside the router responds, the gateway or upstream connection is a stronger suspect.

Changing the DNS server can sometimes work around an unreliable DNS service, but it shouldn't be your first response to every “no internet” message. It won't fix a disconnected modem, an unpaid or suspended service, a captive portal, or a failed Wi-Fi radio. On managed networks, manually changing DNS may also interfere with the network's required sign-in or filtering.

Why restarting and forgetting the network sometimes help

Restarting the affected device clears temporary software states and makes it request network settings again. Forgetting the Wi-Fi network removes its saved password and configuration, which can help after a password change, router replacement, security-mode change, or corrupted saved profile.

These actions are most useful when the problem is limited to one device. Before forgetting the network, make sure you know the Wi-Fi password and any required sign-in details. On phones and computers, a full “reset network settings” option can also remove saved networks, Bluetooth pairings, VPN settings, or other connection preferences, so reserve it for cases where simpler steps have failed.

Don't repeatedly factory-reset the router as a first measure. A reset can erase the Wi-Fi name, password, provider settings, parental controls, port rules, and other configuration. If the provider supplied the equipment or uses special connection settings, you may need its instructions to restore service.

When the IP address itself is a clue

An address beginning with 169.254 often means the device assigned itself a temporary link-local address because it couldn't obtain a normal address from the router. That points more directly to a DHCP, Wi-Fi, cable, or router communication problem. It is different from receiving a normal private address such as 192.168.x.x and then losing internet access later.

An address that looks normal doesn't guarantee that the gateway and DNS settings are correct. Check whether the device shows a default gateway and DNS server, but remember that the exact menus vary by operating system. Avoid judging the connection solely by the presence of an IP address or by the Wi-Fi icon; both are limited indicators.

The practical diagnosis

If one device has a normal private IP address while other devices work, reconnect that device, check for VPN or proxy interference, and consider a saved-profile or DNS problem. If one device has a 169.254-style address, investigate its connection to the router and whether DHCP is responding.

If every device has a local IP address but none can browse, the likely boundary is between the router and the internet provider, although DNS or a captive portal can still be responsible. Check the router's connection status, restart the equipment carefully, and verify whether the provider or venue reports an outage or requires an additional sign-in.

The key is to treat “has an IP address” as evidence of local connectivity, not proof of internet access. Check each stage in order—device to Wi-Fi, Wi-Fi to gateway, gateway to provider, DNS name resolution, and any required authorization. That approach usually identifies the failing stage while avoiding unnecessary settings changes and disruptive resets.