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.
Event logs
Check the System and DHCP Server service event logs at Applications and Services Logs > Microsoft > Windows > DHCP-Server for reported issues that are related to the observed problem.
Depending on the kind of issue, an event is logged to one of the following event channels:
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.
As a Windows Server hybrid administrator, you integrate Windows Server environments with Azure services and manage Windows Server in on-premises networks.