DHCPDISCOVER ... No DHCPOFFERS received Networking Origin: Network OSI layer 7 · Application Last updated 5 Nov 2026

Networking: dhclient: DHCPDISCOVER on eth0 ... No DHCPOFFERS received. No working leases in persistent database - sleeping.

The client broadcast a DHCP request and no server answered.

Exact message you may see No DHCPOFFERS receivedDHCPDISCOVER on eth0 intervalNo working leases in persistent database - sleepingdhclient: No DHCPOFFERS receivedDHCPDISCOVER no offers
Explore the map of this error Full error map →
Seen on: Linux Networking

Meaning

Same causes as 169.254 but from the Linux side: no DHCP server on the VLAN, a missing relay, cable/Wi-Fi isolation, MAC filtering, or DHCP snooping blocking offers. Capture with tcpdump -ni eth0 port 67 or port 68 to see whether the DISCOVER leaves and any OFFER returns.

Common causes

  • No DHCP server reachable on this VLAN
  • DHCP relay/ip helper missing
  • Switch DHCP snooping or port security blocking
  • MAC filtering on the server
  • Link flapping at boot

⚡ Quick fix

  1. Watch the exchange: sudo tcpdump -ni eth0 port 67 or port 68
  2. Check the server logs and scope
  3. Fix relay/VLAN, or set a static IP temporarily

Detailed fix by platform

Linux

  1. bash
    sudo dhclient -v eth0
sudo tcpdump -ni eth0 port 67 or port 68

How to diagnose

  1. DISCOVER — Sent?
  2. OFFER — Received?
  3. Relay/VLAN — Correct?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

169.254.x.x self-assigned IP (DHCP failed) — Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP (Networking)169.254.x.x self-assi…DHCPDISCOVER: no free leases — Networking: dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via eth0: network 192.168.1.0/24: no free leases (Networking)DHCPDISCOVER: no free…Native VLAN mismatch / wrong VLAN, no connectivity — Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway (Networking)Native VLAN mismatch …nf_conntrack: table full, dropping packet — Networking: kernel: nf_conntrack: table full, dropping packet — new connections fail on a Linux firewall/NAT host (Networking)nf_conntrack: table f…nfs: server not responding, still trying — Networking: kernel: nfs: server nas01 not responding, still trying / nfs: server nas01 OK (Networking)nfs: server not respo…Rogue DHCP server hands out wrong gateway/DNS — Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first (Networking)Rogue DHCP server han…Windows has detected an IP address conflict — Networking: Windows has detected an IP address conflict / Duplicate address detected by 00:aa:bb:cc:dd:ee (Networking)Windows has detected …DHCPDISCO…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.