<!– BODY START –>
If you use X-plore's LAN or FTP features regularly, you have probably met this annoyance: a connection that worked yesterday fails today, and the only thing that changed is the address. Your phone's local IP address — the number other devices use to find it on your network — is normally assigned automatically by the router, and it can change whenever the phone reconnects, the router restarts, or another device claims the address first. Each change breaks bookmarks, saved FTP connections, and the habits you built around yesterday's address. Setting a static IP, or better, a DHCP reservation, ends that churn. Your phone keeps the same local address indefinitely, and your saved connections keep working.
Dynamic addresses and why they change
Most home networks use DHCP, a system in which the router hands out local addresses to devices as they join, and reclaims them when devices leave. Each assignment comes with a lease — a period after which the device must renew it. In a stable household, a phone often renews the same address for weeks, which is why the problem feels intermittent: everything works until the day it does not. A router restart, a phone that was away for a weekend, a new device joining the network, or a lease expiring while the phone was off can all result in a different address being handed out next time.
This matters more for servers than for clients. A phone browsing the web does not care what its own address is, because it initiates every connection. But a phone running X-plore's Wi-Fi sharing, LAN service, or FTP server is a server: other devices initiate connections to it, and they need to know where it is. When its address changes, every saved reference to the old address — a browser bookmark, an FTP client's saved site, a note on your desk — points at the wrong place or at nothing at all. Worse, the old address may now belong to a different device, which will refuse the connection and produce a confusing error that looks like a fault in X-plore.
The two ways to get a stable address
There are two ways to give a device a stable local address, and they are not equivalent. The first is a true static IP, configured on the phone itself: you tell the phone to always use a particular address, gateway, and DNS servers, ignoring whatever the router offers. The second is a DHCP reservation, configured on the router: you tell the router to always hand the same address to this particular phone, identified by its hardware address. The phone still uses DHCP, but the answer is always the same.
The reservation is the better choice for almost everyone, and it is the one this guide recommends. It avoids the main risk of a true static IP — accidentally choosing an address the router might hand to another device, creating a conflict where two devices claim the same address and both malfunction. With a reservation, the router knows the address is taken and will not offer it to anyone else. A reservation also keeps working if you change network settings later, since the phone still receives its gateway and DNS automatically. A true static IP is only preferable when you cannot access the router at all, or when the router's reservation feature is missing or broken.
Step one: gather the details you need
Before changing anything, collect three pieces of information from the phone's current connection. In the phone's Wi-Fi settings, tap the connected network and note the phone's current IP address, the gateway (usually the router's address), and the network's prefix or subnet mask. Also note the phone's MAC address, a hardware identifier sometimes shown in the same screen or under About phone and network details. On newer Android versions, the phone may use a randomised MAC address per network for privacy; for a reservation to work reliably, you need the MAC address the phone actually presents to this network, so read it from the connected network's details rather than from a generic hardware listing.
Next, decide which address to reserve. The safe approach is to keep the phone's current address if it is working well, since that address is already known to be free and functional. Alternatively, pick an address near the top of your network's range but outside the router's automatic pool, if your router shows that pool. For a typical home network, addresses ending in a high number, well away from the low numbers the router hands out first, are a good choice — but the simplest robust rule is: reserve the address the phone already has, and let the router protect it from now on.
Step two: create the reservation on the router
Log into the router's administration page from a computer or the phone's browser. The address is usually the gateway you noted, and the login details are often printed on the router itself unless you changed them. Find the DHCP, LAN, or address reservation section — the name varies by brand, with common labels including "DHCP reservation", "static lease", "address reservation", or "LAN setup". Look for a list of connected devices; your phone should appear there, often by its device name. Select it, confirm or enter the address you chose, and save.
Some routers require a restart, or require the phone to disconnect and reconnect, before the reservation takes effect. Disconnect the phone's Wi-Fi and reconnect it, then check the phone's Wi-Fi details again: the address should now be the reserved one. If it is not, double-check that you selected the correct device — a household with several similar phones makes this mistake easy — and that the reservation was saved rather than merely entered on screen. A few routers have a two-step process where you add the reservation and then separately enable it.
Step three: update your saved connections
With the address stable, update everything that references the phone. In your FTP client, edit the saved site to use the new stable address, and test the connection. In your browser, update any bookmark for X-plore's sharing page. If you keep a note of the address, update that too. Then test the full workflow: start sharing in X-plore, open the address on the computer, and confirm the file listing loads. Repeat the test after disconnecting and reconnecting the phone's Wi-Fi, and ideally after a router restart, to confirm the address genuinely holds across the events that used to change it.
This is also a good moment to tidy up. Delete old saved connections pointing at previous addresses, since a stale entry that now belongs to another device produces exactly the confusing refusal errors this guide aims to eliminate. A single, correct, stable entry per purpose — one for Wi-Fi sharing, one for FTP if you use it — is far easier to maintain than a list of historical guesses.
If you cannot access the router: a static IP on the phone
When the router is not yours to configure — a shared house, a workplace, a landlord's router — a static IP on the phone itself is the fallback. In the phone's Wi-Fi settings, open the advanced options for the connected network and change the IP settings from DHCP to static. Enter the address you want, the gateway, and DNS servers. For DNS, you can use the router's address as the DNS server, which is the simplest choice and keeps local name resolution working.
Choose the address with care. Pick one that is unlikely to be handed out automatically — a high number in the range is a reasonable bet — and check first that no other device is using it, for example by trying to reach it from a computer before assigning it. If a conflict occurs, both devices will behave erratically, and the fix is to pick a different address. Also note that a static IP configured for your home network will not work on other networks: when you join a café or office network, the phone will still try to use the static address, which will almost certainly be wrong there. Android handles this per-network, so the static setting applies only to the network you configured it on, but remember to switch that network back to DHCP if you ever change routers or restructure your home network.
Troubleshooting a reservation that does not stick
If the phone keeps getting a different address despite a reservation, work through the likely causes. The commonest is a MAC address mismatch caused by per-network randomisation: the reservation was made for one hardware identifier while the phone presents another. Check the MAC address the phone currently shows for this network and compare it with the one in the reservation. Some phones let you change the privacy setting for a network to use the device's permanent MAC address; doing so for your home network makes reservations reliable, at a negligible privacy cost on a network you own.
Another cause is a router that only applies reservations to devices that reconnect after the reservation is created. Forgetting the network on the phone and rejoining it forces a fresh DHCP request that the router answers with the reserved address. A third cause is an address that falls inside a pool the router manages differently, such as a guest network pool; moving the reservation to an address clearly in the main network's range resolves that. If none of these help, the router's reservation feature may simply be unreliable, in which case a carefully chosen static IP on the phone, following the guidance above, is the pragmatic alternative.
Is a static address a security risk?
A stable local address does not meaningfully change your security. Local addresses are not reachable from the internet, and anyone on your home network can already discover connected devices regardless of whether their addresses change. What a stable address does change is convenience and reliability: saved connections work, automation works, and troubleshooting gets easier because the address is one less variable. The security habits that matter — sharing narrow folders, using passwords on sharing sessions, stopping sharing when done — are unchanged. Think of a static IP or reservation as giving your phone a permanent room number in a building you own, rather than a different room each time it checks in. The building's locks are what keep it safe; the room number just means your friends can find you.
<!– BODY END –>
Frequently asked questions
What is the difference between a static IP and a DHCP reservation?
A static IP is set on the device itself, while a reservation is set on the router, which then always hands the same address to that device. Reservations are safer because the router will not give the reserved address to anyone else.
Will a static IP make my transfers faster?
No, it does not change speed. It improves reliability by stopping the address from changing, so saved connections, bookmarks, and FTP sites keep working.
How do I find my phone's MAC address for a reservation?
In the phone's Wi-Fi settings, tap the connected network and look at its details. Use the MAC address shown for that network, since newer phones may randomise it per network.
Why did my reservation not work after I set it?
The usual causes are a MAC address mismatch, the phone needing to disconnect and reconnect, or the reservation not being saved properly. Forgetting and rejoining the network forces a fresh request.
Should I set a static IP on networks I do not own?
No. A static IP configured for one network will be wrong on others. Use a reservation on networks you administer, and leave other networks on automatic assignment.


