Articles

Fix DHCP No Offers Received from Server (2026)

April 18, 2026 6 min read

The DHCP server stopped responding to client requests because its network interface was not properly configured with an IP address.

Common Causes and Fixes for "DHCP No Offers Received"

This error means your client machine (laptop, desktop, etc.) broadcast a DHCP Discover message asking for an IP address, but it never heard back with a DHCP Offer from a server. It’s like shouting into a void. Here’s what’s likely going on, from most to least common:

  1. DHCP Server Service Not Running: The most frequent culprit is the DHCP server service itself isn’t active.

    • Diagnosis: On the DHCP server (usually a Windows Server or a router’s firmware interface):
      • Windows: Open services.msc. Look for "DHCP Server." Is its status "Running"?
      • Router: Log into your router’s web interface. Navigate to the DHCP server settings. There’s usually a toggle or status indicator.
    • Fix:
      • Windows: In services.msc, right-click "DHCP Server" and select "Start." If it fails to start, check the Event Viewer (Application and System logs) for more specific errors related to the service.
      • Router: Enable the DHCP server function on the router.
    • Why it works: The DHCP server process needs to be running to listen for Discover messages and send out Offers.

  2. IP Address Conflict on Server: The DHCP server itself might have an IP address that’s already in use on the network, preventing it from functioning correctly.

    • Diagnosis:
      • Windows: Check the IP configuration of the server: ipconfig /all in Command Prompt. Note the server’s IP address and subnet mask. Then, ping that IP address from another machine: ping <server_ip>. If you get a reply, there’s a conflict. Also, check your router’s ARP table or connected devices list for duplicate IPs.
      • Router: Check the router’s current IP address and compare it against devices listed as connected.
    • Fix:
      • Windows: Change the server’s static IP address to one that is not in use and is within the correct subnet. For example, if the server is 192.168.1.10 and another device is also 192.168.1.10, change the server to 192.168.1.11 (assuming 192.168.1.11 is free). Ensure the new IP is outside the DHCP scope but within the same subnet.
      • Router: If the router is the DHCP server, ensure its own IP address is not within the range it’s handing out to clients.
    • Why it works: Network devices need unique IP addresses to communicate. A conflict disrupts the server’s ability to establish its own network identity.

  3. Incorrect IP Helper Address (for multi-subnet DHCP): If your DHCP server is on a different subnet than your clients, a router or Layer 3 switch needs to be configured to forward DHCP broadcast traffic. This is done with an "IP helper" or "DHCP relay" address.

    • Diagnosis: On the router/L3 switch that connects the client subnet to the DHCP server subnet:
      • Cisco IOS: show running-config | section interface and look for ip helper-address <dhcp_server_ip>. Also check show ip interface brief to ensure the interface facing the clients has an IP address.
      • Other Vendors: Consult your device’s documentation for DHCP relay configuration.
    • Fix:
      • Cisco IOS: On the interface facing the client subnet, add the command: ip helper-address <dhcp_server_ip>. For example, if your DHCP server is at 192.168.10.5 and clients are on 192.168.20.0/24, and the router interface facing 192.168.20.0/24 is GigabitEthernet0/1, you’d configure interface GigabitEthernet0/1 then ip helper-address 192.168.10.5.
    • Why it works: DHCP Discover messages are broadcasts, which routers typically do not forward between subnets. The IP helper address tells the router to convert these broadcasts into unicast packets destined for the specified DHCP server.

  4. Firewall Blocking DHCP Traffic: A firewall on the server, a network firewall, or even client-side firewall software can block UDP ports 67 and 68, which DHCP uses.

    • Diagnosis:
      • Server Firewall (Windows): Check Windows Defender Firewall with Advanced Security. Look for Inbound Rules related to DHCP. Ensure rules allowing UDP port 67 (DHCP Server) are enabled.
      • Network Firewall: Check your network firewall’s access control lists (ACLs) or security policies.
      • Client Firewall: Temporarily disable client-side firewall software to test.
    • Fix:
      • Windows: Create or enable an inbound rule for "DHCP Server" to allow UDP traffic on port 67.
      • Network Firewall: Add an ACL entry to permit UDP traffic from any IP to the DHCP server’s IP on port 67, and from the DHCP server on port 68 back to the client’s ephemeral port (though this return path is usually less problematic).
    • Why it works: DHCP relies on UDP packets. Firewalls, by default, can block unsolicited incoming traffic on specific ports.

  5. DHCP Scope Exhaustion or Misconfiguration: The DHCP server might have run out of available IP addresses to lease, or the scope itself might be misconfigured.

    • Diagnosis:
      • Windows: Open the DHCP console (dhcpmgmt.msc). Expand the server, then IPv4. Check the "Scope Options" and "Addresses Leased" for the relevant scope. Does the "Total Addresses" value seem too low? Are all addresses leased? Check the "Exclusion Range" and "Reservations" to ensure they aren’t accidentally blocking a large chunk of the available IPs.
      • Router: Check the DHCP settings for the IP address pool size and current usage.
    • Fix:
      • Windows: Increase the total number of addresses in the scope, or adjust the exclusion range. For example, if your scope is 192.168.1.100 to 192.168.1.200 (101 addresses) and you have many devices, change it to 192.168.1.100 to 192.168.1.254 (155 addresses). You might also need to remove old, stale leases.
      • Router: Increase the size of the DHCP IP address pool.
    • Why it works: The DHCP server can only assign IP addresses that are within its configured pool and are not already leased or excluded.

  6. Incorrect Network Interface Binding on Server: The DHCP server service might be configured to listen on the wrong network interface, or no interface at all.

    • Diagnosis:
      • Windows: In the DHCP console (dhcpmgmt.msc), right-click the server name and select "Properties." Go to the "Advanced" tab. Check the "Bindings." Ensure the correct network interface (the one with the server’s IP address that clients can reach) is checked.
    • Fix:
      • Windows: In the "Bindings" dialog, check the box next to the network interface that has the IP address clients should use to reach the server.
    • Why it works: The DHCP server needs to know which of its network cards to use to listen for and respond to client requests.

  7. Client Network Adapter Driver Issues: Less common, but a faulty or outdated network adapter driver on the client can sometimes prevent it from processing DHCP responses correctly.

    • Diagnosis: On the client machine, check Device Manager for any yellow exclamation marks next to the network adapter. Try updating the driver.
    • Fix: Update or reinstall the network adapter driver.
    • Why it works: A corrupted driver can interfere with network communications, including the receipt of DHCP offers.

After addressing these, the next likely issue you’ll encounter is the client receiving an IP address but being unable to reach the internet due to incorrect DNS server settings.

Want structured learning?

Take the full Computer Networking course →