Skip to content

Guide

An APIPA Ticket From First Report to Resolution

Illustration of a terminal window beside a warning triangle representing a failed DHCP lease

Short answer

When a Windows machine shows an address starting 169.254, it asked for a DHCP lease and never received one. Three commands confirm it: ipconfig /all shows a self assigned address with no default gateway and no DNS servers, a ping to the gateway loses every packet, and a name lookup fails because there is no resolver to ask. Checking all three before changing anything is what separates a diagnosis from a guess.

This ticket arrives worded the way real tickets are worded. The employee says the internet is down and that no websites will load. The browser is showing a DNS error on every site, which makes it tempting to treat the whole thing as a DNS problem. It is not, and the very first command tells you why.

Working the ticket in order

  1. Verify who you are speaking to and which device they are on before you connect to anything.
  2. Run ipconfig /all and read the address. An address beginning 169.254 with an empty default gateway means no DHCP server answered.
  3. Ping the default gateway. Every packet is lost, which confirms the machine has no usable path off its own segment.
  4. Try a name lookup. It fails because the adapter never received a DNS server to ask, which explains the browser error without DNS being the cause.
  5. Run ipconfig /renew, then read the result rather than assuming it worked.

That last step is where this stops being a quiz. The renew does not succeed. It returns an error saying it was unable to contact your DHCP server and that the request timed out, and the address is unchanged. A technician who typed the command and closed the ticket would have closed it broken, and the user would be calling back within the hour.

What the output has already told you

  • The adapter is enabled and reports a physical address, so this is not a disabled interface.
  • DHCP is enabled on the adapter, so nobody has manually set a static address.
  • A self assigned address with an empty gateway means the request left and nothing answered.
  • The failed name lookup is a consequence of having no DNS server, not a separate fault.
  • A failed renew means the problem is still live rather than a stale lease that needed refreshing.

From here the evidence allows exactly two possibilities: something on this machine cannot complete a DHCP request, or nothing on that network segment is answering them. The question that splits them is whether anyone else is affected, and that single answer decides whether this is a desk side fix or an escalation to whoever owns the network.

Whatever the cause turns out to be, the ticket is not finished until the machine holds a real address, the user has loaded a page themselves while you watch, and the note records what you found. A note saying fixed internet is worth almost nothing to the next technician. A note recording the self assigned address, the failed renew, and what finally restored the lease is worth a great deal.

Common questions

What does an address starting 169.254 mean on Windows?
An address starting 169.254 is an automatic private address that Windows assigns to itself when no DHCP server answers. The adapter is working and the request left the machine, but nothing replied, so the computer can reach its own segment and nothing beyond it.
Why does the browser show a DNS error if the fault is DHCP?
Because the adapter never received DNS server addresses along with a lease, every name lookup fails and the browser reports a DNS error. The name resolution failure is a downstream symptom, so changing DNS settings directly will not fix it.
What should you do when ipconfig /renew fails?
Read the error instead of running the command again. A message saying the DHCP server could not be contacted means the request is leaving the machine and nothing is answering, so the next question is whether anyone else on the same network segment is affected.

Related guides