Troubleshoot problems on the DHCP server

Try our Virtual Agent - It can help you quickly identify and fix common DHCP issues.

This article discusses how to troubleshoot problems that occur 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 verify availability, 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 haven't been excluded from the DHCP scope.

• Verify that the DHCP server binds to at least one IP address, and that this IP address is within the subnet of the scopes from which IP addresses must be leased out, unless using DHCP relay. To do this verification, 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 by running the netstat -anb command. No other process or other services, such as WDS or PXE, should occupy these ports.

• Verify that the DHCP server IPsec exemption is added if you're 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.

Data collection

DHCP Server log

The DHCP Server debug logs provide more information about the IP address lease assignment and the DNS dynamic updates that are done by the DHCP server. These logs by default are located in %windir%\System32\Dhcp. For more information, see Analyze DHCP Server Log Files.

Network trace

A correlating network trace may indicate what the DHCP server was doing at the time that the event was logged. To create such a trace by using the Windows Troubleshooting Tools (TSS), follow the instructions at DHCP troubleshooting guidance - Data collection.

See also

• DHCP troubleshooting guidance
• Troubleshooting guide for Dynamic Host Configuration Protocol (DHCP)
• Introduction to TroubleShootingScript toolset (TSS)