Many users are familiar with the situation where a device endlessly displays the status "Obtaining IP address..." or "Connected, no internet access." The smartphone or laptop screen freezes on this phrase, creating the illusion of activity, although there is no actual connection to the global network. This state means that your device has physically connected to the router but is unable to receive digital access to the network.
The problem lies in the protocol DHCP, which is responsible for automatically distributing addresses on the local network. If this mechanism fails, your device simply doesn't know where to send data requests. The causes could be software-related, such as a driver or firmware error, or hardware-related, such as an overheated router or damaged cable.
In this article, we'll detail the steps to resolve the error. We'll cover router settings, computer network card settings, and hidden features of mobile operating systems that often block connections.
How DHCP Works and Why Authorization Fails
When you try to connect to a wireless network, a complex handshake process occurs between the client and the router. Your device sends a broadcast request, and the router, if everything is working correctly, should assign it a unique IP address, subnet mask, and gateway address. It's at the point where this information is most often encountered.
The main culprit is address pool overflow. In standard settings, home routers such as TP-Link or Asus, allocate a limited range of addresses (for example, from 192.168.0.100 to 192.168.0.199). If many guests or smart devices try to connect to your network at the same time, there may simply be no free addresses left.
⚠️ Note: In some cases, the cause of a freeze is not a lack of addresses, but an IP conflict. If two devices on the network attempt to use the same address, the router may block both connections, leaving them in the "Obtaining IP" status.
It's also worth keeping in mind that the DHCP protocol has timeouts. If a response from the server isn't received within a certain amount of time, the client device may enter a retry cycle, visually appearing to wait forever. This often happens when the signal is weak, and data packets are lost in the air.
Router diagnostics and service reboot
The first step should always be checking the router's status. Don't rush to reset the settings to factory defaults, as this will require reconfiguring the internet. Start by analyzing the indicators: if the light WLAN or Wi-Fi If the light is flashing rapidly or, on the contrary, is not lit, the problem may be in the hardware.
A simple but effective procedure—a full power-up cycle—often helps. Unplug the router's power cord, wait at least 30 seconds, and then plug it back in. This clears the device's RAM and restarts any frozen IP address distribution processes.
If the problem persists, you should log into the administrator's web interface. This is usually done at 192.168.0.1 or 192.168.1.1In the LAN or DHCP Server settings, check if the address distribution function is enabled. Sometimes it's accidentally disabled after power surges.
It's important to check your router's logs, if this feature is available. They may contain entries about authorization errors or connection attempts by unknown devices, which could clog the ARP table.
Setting up a network card on a computer (Windows)
If Wi-Fi works fine on other devices, but the problem only occurs on a specific laptop or PC, you need to look for the cause in the operating system settings. Most often, the protocol settings are incorrect. IPv4Instead of automatically obtaining an address, a static IP may be assigned there, which is not suitable for the current network.
To fix the situation, open the Network Control Panel. Click Win + R, enter the command ncpa.cpl and press Enter. Find your wireless connection, right-click it, and select "Properties." In the list, find the line "Internet Protocol Version 4 (TCP/IPv4)" and make sure the checkboxes for "Obtain automatically" are selected.
Another common issue is the DNS cache and network resets. Windows may store old, outdated entries that prevent new connections. Clearing the cache often resolves the issue of getting stuck while obtaining an IP address.
☑️ Windows setup checklist
Don't forget about drivers. Outdated Wi-Fi module software, especially on older models Realtek or Atheros, may not correctly handle modern WPA3 encryption standards, causing connection timeouts.
Solution for Android and iOS devices
On mobile platforms, the situation is complicated by aggressive power saving and operating system quirks. If your iPhone or Android smartphone displays "Obtaining IP Address" but won't connect, first try the "Forget Network" action. This will delete the saved profile, along with any potential configuration errors.
On Android systems, switching between security protocols often helps. If the router is configured for mixed mode, WPA2/WPA3Some older devices may not authenticate correctly. Try temporarily changing your router settings to a clean one. WPA2-PSK.
There's a hidden feature on iOS that sometimes interferes with IP sharing. Go to Wi-Fi settings, tap the information icon (the blue "i" in a circle) next to your network, and select "IP Configuration." Make sure it's set to "Automatic" and not "Manual."
Secret MAC filtering function
If all else fails, check your router's MAC filter list. Your device's address may have been accidentally blacklisted or blocked by parental controls.
It's also worth paying attention to the date and time. If the device's clock is out of sync, security certificates won't be verified, and the connection will be lost early, simulating an IP issue.
Manually registering a static IP address
When automatic address assignment fails, manual configuration is the most reliable solution. You can manually assign the device an address that is guaranteed to work on your local network. This eliminates dependence on the router's DHCP service.
To do this, you need to know the gateway address (usually the router's address, for example, 192.168.1.1). Choose a free address, for example, 192.168.1.155, so that it doesn't conflict with other devices. Leave the default subnet mask. 255.255.255.0.
It's also important to specify DNS servers. Using public DNS from Google or Cloudflare often speeds up network response times and resolves issues with slow internet, even if the IP address is correctly obtained.
| Parameter | Standard value | Recommended value | Description |
|---|---|---|---|
| IP address | Automatically | 192.168.1.X (where X is from 2 to 254) | Unique device number on the network |
| Subnet mask | 255.255.255.0 | 255.255.255.0 | Determines the size of the local network |
| Gateway | 192.168.1.1 | 192.168.1.1 | Your router's address |
| DNS 1 | Automatically | 8.8.8.8 | Primary name server (Google) |
| DNS 2 | Automatically | 1.1.1.1 | Backup Name Server (Cloudflare) |
⚠️ Important: When manually assigning an IP address, make sure you don't use an address that's already taken by another device (such as a printer or phone). This will cause a conflict and cause both devices to lose network connectivity.
Reset network settings and update software
If software glitches have accumulated, the most radical yet effective method is a complete network reset. On Android, this can be done via the menu "System" → "Reset settings" → "Reset Wi-Fi, mobile data, and Bluetooth settings." On Windows, the command netsh winsock reset works wonders in the command line.
Don't ignore updating your router firmware. Manufacturers regularly release patches that fix TCP/IP stack bugs and improve compatibility with new smartphones. Visit the manufacturer's website for your model, for example, Zyxel or Tenda, and check for a new version of the software.
In rare cases, the problem lies with antivirus software or a firewall that blocks DHCP requests, considering them suspicious activity. Try temporarily disabling the protection and checking the connection.
Frequently Asked Questions (FAQ)
Why does Wi-Fi work on one device, but the other shows "Obtaining IP"?
This indicates a problem specifically with the client device. Most likely, the TCP/IP settings are incorrect, the Wi-Fi driver is outdated, or the MAC address randomization feature is enabled and the router cannot process it correctly.
Can an antivirus block the receipt of an IP address?
Yes, some aggressive firewall settings in antivirus software (such as Kaspersky or ESET) may block DHCP broadcast requests, treating them as an attempt to scan the network.
What should I do if my router issues an IP address, but there's still no internet?
This is a different issue. If you've received an IP address (e.g., 192.168.xx), but websites aren't loading, check your DNS settings or WAN connection status in your router. Your ISP may have blocked access or your account may be out of money.
Does changing the Wi-Fi channel help with this error?
Changing the channel helps if the problem is severe interference from neighboring devices. If data packets are lost due to noise, the IP acquisition process can be interrupted and restarted endlessly.