DHCP in Plain Terms: Why Devices Suddenly Cannot Get an Address

It is 6:40 a.m. and the day shift is arriving. The charting tablets show Wi-Fi connected, yet nothing opens. The front desk computer says "no network access." The night nurse says it worked fine at midnight. The router lights are on, and everyone is guessing.

One common cause is a problem with DHCP, the service that hands out network addresses. It is invisible when it works, and when it fails, devices that look connected cannot actually communicate.

What DHCP does

Every device on a network needs an address, a bit like a room number, so traffic knows where to go. Instead of someone typing an address into each phone, tablet and computer, a DHCP server hands one out automatically when the device joins. It also tells the device the other settings it needs, such as where to send traffic to reach the internet.

In most buildings, this job is done by the firewall or router, or by a server. The addresses are handed out from a pool, a range set aside for the purpose, and each is leased for a set time. When the lease runs out, the device renews it or gives it back.

How the pool runs out

A pool has a fixed number of addresses. Count the devices in your building, and the number can surprise you. Staff phones, tablets, computers, medication carts, cameras, smart TVs, residents' devices on guest Wi-Fi and building systems all take one.

When every address in the pool is leased, a new device asking for one gets nothing. Typical triggers include:

Shift change, when a wave of staff phones joins Wi-Fi at the same time

An event, such as a family day or holiday visit, when many visitors join guest Wi-Fi

A pool that was sized years ago and never enlarged

Long lease times, so addresses from devices that left remain tied up

A device that keeps rejoining and takes a new address each time

The symptom is that some devices work and newer ones do not, or things fail at busy times and fix themselves later.

The second device problem

A less obvious cause is a second device handing out addresses that should not be. Someone plugs in a spare wireless router, or a small switch with its own router features, or an old piece of equipment. It starts answering requests, and now some devices get addresses from it. Those addresses do not match your network, so the devices connect but cannot reach anything.

This is sometimes called a rogue DHCP server, though it is usually innocent. It often follows a new installation, a contractor's temporary setup or someone plugging a home-style router into a wall jack to boost Wi-Fi in a room. The pattern is intermittent: some devices work, others fail, and the problem moves around.

What you can check without being technical

Before calling, a few observations help your IT provider enormously.

Which devices are affected, and which still work? Is it only Wi-Fi, only wired or both?

Is it one wing, one floor or the entire building?

When did it start, and what changed? A new device, a power flicker, a contractor visit?

Does it improve if a device is turned off and back on, or the Wi-Fi is toggled?

Do affected devices show an address that starts with 169.254, which is a sign they never got one from DHCP? On many devices this is visible in the network settings.

Is there any new router or switch plugged in somewhere that is not part of the official setup?

Do not restart everything at once. A cold restart might hide the clues and may cause another burst of requests.

What to tell your IT provider

Give them a plain description: what failed, when, how many devices and what changed. Mention the 169.254 address if you saw it. Say whether the problem is spread across the building or only in one area. Tell them about any equipment recently added, including anything a contractor or staff member plugged in.

Ask them afterward to explain the cause in one sentence, and ask what will prevent it. A well-managed building has a pool larger than it needs, sensible lease times, monitoring that warns before addresses run out and a rule that nobody adds network equipment without approval.

How we can help

UnityCare IT designs and supports networks for care buildings, including sizing address pools, separating resident Wi-Fi from clinical and office networks and tracking down stray equipment. Our help desk offers 24/7 after-hours support, so a 6:40 a.m. outage gets answered. After an incident, we can explain what happened in plain terms and help prevent a repeat.

Related service

Wi-Fi, switching, firewalls and internet that hold up across a whole facility.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support