Stuck on Obtaining IP Address on Piso WiFi: What It Means and the Fix Order That Works

Answer first: Your device is still waiting for a usable address, so it cannot open the portal yet. Do not pay yet; work through the fix order in order, testing after each step, and use the second-device test to tell a device problem from a machine problem.

Up: Troubleshooting | Also in Troubleshooting and Fixes: No Internet After Paying and Portal Not Loading

Obtaining IP Address means your device has found the WiFi network and is asking the machine for a network address, but it has not received one yet, or it has not received one it can use. Without that address, the device cannot open the portal, and it cannot start a session. Do not pay yet, because payment comes after the portal opens, not before an address is assigned.

This post covers only this one message and its fix order. For a portal that opens but will not accept payment, go to the Portal Not Loading post. For a portal that opens and shows a timer but browsing fails, go to the No Internet After Paying post. For full login steps once an address is assigned, go to the Login pillar.

What an IP Address Is, in Plain Terms

An IP address is a number the machine gives your device so it can tell your device apart from other devices on the same network. The service that gives out those addresses is called DHCP. Think of it as a reception desk that hands each visitor a room number. If the desk is busy, closed, or out of numbers, a visitor waits at the desk, and that waiting state is what your phone shows as Obtaining IP Address.

A device that is stuck in this state has not yet reached the portal, so portal fixes such as clearing browser cache will not help yet. Fix the address step first.

How Long to Wait Before You Act

Wait about 30 seconds on the first try. A short delay is normal when many devices join at once, or when a phone has just woken from sleep. If the message is still there after 30 seconds, and the WiFi name is correct, start the fix order below. Do not wait through a full session time, because no session has started yet.

The Fix Order, Step by Step

Work in order, and test after each step. Do not change several settings at once.

Step 1: Confirm the WiFi name and move closer

Confirm you joined the exact WiFi name of the machine you intend to use. Move closer to the machine or access point, and try again. A weak signal can cause an address request to fail or time out, even when the WiFi icon shows a connection. If the message clears when you move closer, the problem was signal and placement, not a machine fault.

Step 2: Turn WiFi off and on, once

Turn WiFi off, wait a few seconds, turn it back on, and rejoin the same network. This clears a stuck local request for that device, without changing any saved settings. Test again. If it clears, you are done. If it sticks again, move to Step 3.

Step 3: Forget the network and rejoin it

Forget the network in your device WiFi settings, then rejoin it and enter the WiFi password again if the network asks for one. This clears a stale saved address, a stale portal redirect, and a saved setting that no longer matches the machine. After rejoining, wait for the address step to complete before opening a browser.

On Android, forget is in WiFi settings, under the saved network options for that network name. On iPhone, forget is under the network details for that network name. On a laptop, forget is in the WiFi network settings for that network name.

Step 4: Restart the phone or laptop, if Steps 1 to 3 fail

Restart your device, then rejoin the same network. A restart clears a stuck network service on the device that WiFi off and on does not always clear. Do not restart the machine. A device restart is a user fix. A machine restart is an operator fix.

Step 5: Test a second device

Test a second phone, tablet, or laptop on the same machine. This is the decisive check, and it tells you who can fix the problem.

If the second device gets an address and opens the portal

The problem is specific to the first device. Return to the first device, and check: WiFi sleep and battery saver settings that turn WiFi off, a VPN or security tool that interferes with local networks, a saved static address for that network that conflicts with the machine, and whether the device works on a different WiFi network. If the first device works elsewhere but not on this machine, and the second device works on this machine, the first device settings are the likely cause.

If the second device also sticks on Obtaining IP Address

Stop changing device settings. The problem is more likely the machine DHCP service, the access point, or a machine that needs a restart from the admin panel. Report it to the operator with the details at the end of this post. Do not keep forgetting and rejoining on many devices, because that does not fix a machine service fault.

Special Cases That Look Like an IP Problem, but Are Not

A saved static address that conflicts

If a device was set to use a fixed, static address for another network, and that address conflicts with the machine address range, the device can stick on obtaining an address, or it can connect without a working portal. Check whether the device is set to automatic address assignment for this network, rather than a manual static address. If you do not know what static address means, check with someone who set up the device, and do not guess an address.

A private address change that confuses the machine

A private WiFi address that changes between connections can make the machine treat the same phone as a new device. This affects resume after a pause more than first login, but it can also affect a device that repeatedly fails to get a stable address. Do not change the private address setting repeatedly during troubleshooting. Set it once, before you pay, if you are troubleshooting a machine that repeatedly fails to recognise your device, and tell the operator if you changed it.

A machine that is full, or an access point that is overloaded

A machine or access point can have a limit on how many devices it can serve at once, set by the operator or by the hardware. If the message appears only at peak times, when many customers are present, and clears when the area is quiet, tell the operator the time pattern. That pattern points to capacity or access point load, not to a single phone fault. The operator fix may be an access point change, a setting change, or a capacity check, not a phone reset.

A power cut or reboot just before you joined

If the machine just rebooted, its address service may take a short time to start, or local sessions may have cleared. Wait a minute, try again, and if the message persists on two devices, tell the operator that a reboot happened just before the problem. That detail helps the operator decide whether a further restart from the admin panel is needed, or whether a setting was lost in the reboot.

What You Should Not Do

Do not restart a machine you do not own. Do not open the machine box. Do not pay before the portal opens, in the hope that payment will force an address. Do not keep toggling WiFi, VPN, and private address settings in a loop, because each change can look like a new device to the machine and can hide the original pattern from the operator.

What to Tell the Operator

If the second device test shows a machine problem, send one message with these details:

  • Machine location and WiFi name.
  • Device types tested, and whether each one stuck on Obtaining IP Address.
  • What you tried, in order: move closer, WiFi off and on, forget and rejoin, device restart.
  • Whether the problem happens at all times or only at peak times.
  • Whether a power cut or reboot happened just before the problem.
  • Whether the portal opened at any point, or whether the device never got past the address step.

Do not send banking passwords, social media passwords, or admin passwords. A real operator does not need those to check an address service.

Frequently Asked Questions About Obtaining IP Address

Is Obtaining IP Address the same as no internet?

No. Obtaining IP Address happens before the portal, before payment, and before browsing. No internet after paying happens after a session starts. The fix order is different, because the first problem is about getting an address, and the second problem is about browsing after a session is already running.

My phone gets an address on home WiFi, but not on Piso WiFi. Is my phone broken?

Not necessarily. If your phone works on home WiFi and a second device works on the same Piso WiFi machine, the problem is more likely a saved setting for that Piso WiFi network, such as a static address or a private address change. Forget and rejoin that network, and check automatic address assignment, before concluding the phone is broken.

Should I try a different WiFi name for the same machine?

No, unless the operator tells you there is a second network name for that machine. Joining a neighbouring network with a similar name will not give you a session on the intended machine, and it can make the problem look like a machine fault when it is actually a wrong network choice.

How many times should I forget and rejoin before I report it?

Once, properly, after moving closer and trying WiFi off and on. If forget and rejoin plus a device restart still fails, and a second device also fails, report it. Repeating forget and rejoin many times does not fix a machine address service fault.

Can a weak signal cause Obtaining IP Address to stick?

Yes. A weak signal can cause an address request to time out, even when the WiFi icon shows a connection. Move closer to the machine or access point and try again, before changing other settings. If it clears when you move closer, signal and placement were the cause.

Will paying fix Obtaining IP Address?

No. Payment comes after the portal opens, and the portal needs an address first. Do not pay until the device gets an address and the portal opens cleanly.

DHCP Pool Exhaustion and IP Conflicts at Peak Times

A machine can run out of free local addresses at peak times, especially if lease times are short and many devices have recently connected. In that case, a second device will also stick on Obtaining IP Address, and no device setting will fix it. A secondary router or extender that shares the gateway address can cause the same symptom through an IP conflict. Both are operator checks: flush expired leases, check for a second device using the gateway address, and restart the machine service if needed. As a customer, report the time, whether other customers are affected, and whether the problem started at a busy time, and do not keep rejoining in a loop, because that does not free an address.

If the portal opens but will not load a payment page, go to the Portal Not Loading post. If the portal opens and shows a timer but browsing fails, go to the No Internet After Paying post. For full login steps once an address is assigned, go to the Login pillar. For the general diagnostic method, go to the Troubleshooting pillar.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *