Verdict: If your phone stays on “Obtaining IP address,” first test another device on that Wi-Fi network and your phone on a different network. Those two checks help separate a phone problem from a router or network problem; copying a random static IP address can make diagnosis harder. Start with a restart and a fresh connection, then investigate the network’s address settings if the failure stays with one network.
This guide covers joining Wi-Fi and obtaining a usable local address. If the phone already connects but websites fail, use our Wi-Fi connected but no internet guide. The words shown by Android and iPhone differ, so record the actual message instead of assuming every spinning connection indicator means the same fault.
First, find which connection fails
Restart the phone, turn Wi-Fi off and back on, and try close to the router. Then make two comparisons: connect another device to this network, and connect your phone to a different trusted network. This follows Google’s connection-isolation guidance. Keep a short note of each result so you do not repeat the same failed step.
| Observed Symptom | Likely Cause | Recommended Action |
|---|---|---|
| Phone works on other Wi-Fi networks | A setting or compatibility problem on this network | Check the router and its access rules before resetting the phone. |
| Several devices cannot join the same network | A shared router, addressing or network problem | Restart your own router and check its status; contact the administrator on managed Wi-Fi. |
| Only this phone fails on several working networks | Phone settings, software or hardware need investigation | Update, investigate app interference, then consider a network reset. |
| Phone connects, but the browser requests sign-in | A public-network registration requirement | Complete the network’s official sign-in page. |
| Network details show a 169.254.x.x IPv4 address | Link-local addressing rather than a routable IPv4 configuration | Ask the administrator to check DHCP; the number alone does not identify a broken component. |
Restore a normal Wi-Fi connection
1. Forget this network and join it again
Have the Wi-Fi password ready. For work or school Wi-Fi, check with IT first if joining requires certificates or a managed profile.
- Pixel: Open Settings > Network & internet > Internet > Saved networks, select the network and tap Forget. Select the network again and provide its details.
- Samsung Galaxy: Open Settings > Connections > Wi-Fi, press and hold the affected network, then choose Forget network. Reconnect using the correct password.
These are the current paths in Pixel support and Samsung’s Wi-Fi guide; labels can vary by software and model. On iPhone, follow Apple’s Forget This Network instructions. Apple notes that this also forgets the network on other devices using iCloud Keychain with the same Apple Account, so keep that password.
2. Restart the router you control
Use the router’s documented restart procedure, or disconnect and reconnect its power as its manufacturer directs. Wait for its normal status lights before testing. A restart interrupts everyone using that network; arrange a suitable moment. Do not press a recessed factory-reset button as a substitute for restarting.
Samsung recommends checking router firmware and restarting the access point. At a hotel, office or campus, report the network name and error to staff instead of changing shared equipment. If the access point is another phone, the separate hotspot troubleshooting guide helps check that source phone.
3. Check address allocation on the network
DHCP normally supplies a local IPv4 address automatically. On a typical home network, check that the intended router provides DHCP and that its address pool has space for new clients. Apple warns that multiple DHCP servers on a home network can cause address conflicts and that an exhausted pool can prevent new connections. Use the router’s own manual, and save its settings before making changes. See Apple’s router recommendations.
For a managed network, ask the administrator to inspect the client entry, address pool, applicable access rules and network segment. An old device staying online does not prove a new device can obtain an address. This is a reason to inspect allocation, not proof that the pool is full.
4. Keep private Wi-Fi addresses unless a specific conflict is confirmed
A private address normally works with Wi-Fi and makes cross-network tracking harder. Apple advises updating software before considering disabling it. A blanket instruction to turn privacy protection off is a poor first fix.
On iOS 18 and later, Settings > Wi-Fi > the network’s information button > Private Wi-Fi Address offers Off, Fixed and Rotating. Fixed still uses a private address, but keeps it stable for that network. If an administrator needs to register your device, discuss the address used on that network. Do not repeatedly change modes while the administrator is checking the connection.
What DHCP and a 169.254 address actually tell you
The DHCP standard defines an exchange in which a client discovers servers, receives an offer, requests configuration and receives acknowledgement. A phone’s brief status label does not expose a packet trace. It cannot prove which message was lost, whether a router is overloaded, or whether a particular radio component failed.
An address beginning 169.254. belongs to the IPv4 link-local range. RFC 3927 describes communication on the local link, with routers prohibited from forwarding those packets beyond it. That is a useful addressing clue, not a complete diagnosis of every connection the phone might have.
DNS serves a different purpose: it resolves names such as website addresses. Changing DNS does not itself assign the phone a valid local IP address. Diagnose the failed stage before changing settings for a later one.
Why a copied static IP is not a universal fix
A manual configuration needs an unused address appropriate to the actual network, its subnet and gateway. A high final number does not guarantee that an address is free. TP-Link’s network guide explains address pools and reservations tied to client addresses; the values depend on that network.
If a network administrator needs a fixed address for your phone, have them configure a reservation or provide all required settings. Record previous values first. A successful manual-address test may help narrow the problem, but it should not leave an unexplained DHCP fault for the next device. Keep automatic addressing for ordinary use unless your network requires otherwise.
When the problem follows the phone
Install available system updates using a working connection. On Android, follow your manufacturer’s safe-mode instructions to check whether downloaded software contributes to the problem. Google’s Pixel guide notes that airplane mode may turn on when entering safe mode; turn it off before testing Wi-Fi.
If earlier checks fail, consider a network reset after saving connection details:
- Pixel: Settings > System > Reset options > Reset Bluetooth & Wi-Fi.
- Samsung: Settings > General management > Reset > Reset Wi-Fi and Bluetooth settings. Samsung explains that apps and personal data remain, but Wi-Fi and Bluetooth connections must be set up again.
- iPhone: Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. Apple lists Wi-Fi passwords, cellular settings, VPN and APN settings among the affected settings; consult IT first for a managed device.
Read the confirmation screen so you select the intended network reset, not an erase option.
When to contact support
If this phone still fails on multiple known-working networks, contact its manufacturer with the model, software version, exact message and comparison results. If the failure stays with one network, contact its owner or router provider. Once joining works but internet access still fails, move to that separate diagnosis. Our Wi-Fi and networking guides cover related next steps.
Research basis: official device, router and networking documentation checked on October 8, 2026. This is an AI-assisted troubleshooting synthesis, not a report of hands-on testing.