Troubleshoot problems on the DHCP server

Troubleshooting checklist

Check the following settings:

  • The DHCP server service is started and running. To check this setting, run the net start command, and look for DHCP Server.
  • The DHCP server is authorized. See Windows DHCP Server Authorization in Domain Joined Scenario.
  • Verify that IP address leases are available in the DHCP server scope for the subnet the DHCP client is on. To do this, see the statistic for the appropriate scope in the DHCP server management console.
  • Check whether any BAD_ADDRESS listings can be found in Address Leases.
  • Check whether any devices on the network have static IP addresses that have not been excluded from the DHCP scope.
  • Verify that the DHCP server is bound to at least one IP address, and that this is within the subnet of the scopes from which IP addresses must be leased out (unless using DHCP relay). To do this, run the Get-DhcpServerv4Binding or Get-DhcpServerv6Binding cmdlet. Server connection bindings are configured in the DHCP server management console under IPv4 / IPv6 Advanced Properties.
  • Verify that only the DHCP server is listening on UDP port 67 and 68. No other process or other services (such as WDS or PXE) should occupy these ports. To do this, run the netstat -anb command.
  • Verify that the DHCP server IPsec exemption is added if you are dealing with an IPsec-deployed environment.
  • Verify that the relay agent IP address can be pinged from the DHCP server.
  • Enumerate and check configured DHCP policies and filters.
  • TSS Ron Trace 20321:DhcpAdminEvents NoSDP NoPSR NoProcmon NoGPresult
  • File: %Computername%_date_time_packetcapture_InternetClient_dbg.etl

Event logs

Check the System and DHCP Server service event logs (Applications and Services Logs > Microsoft > Windows > DHCP-Server) for reported issues that are related to the observed problem.

DHCP Server log

These logs by default are located in %windir%\System32\Dhcp.