A DHCP Server is a server that automatically assigns IP addresses and other parameters for the network to the devices, but many users reported that DHCP Server keeps stopping.
This can be a big problem and in this article, we will explore some of the best proven troubleshooting methods available. Please make sure to follow the steps for each method closely in order to avoid causing any additional issues.
What to do if DHCP Server keeps stopping?
1. Update your Windows version to the latest release
- Click on Start button -> Settings button.
- Click on Update and Security.
- Click on the ‘Check for updates’ button, and install any available updates.
2. Flush the DNS
- Press Win + X keys on your keyboard, and choose Windows PowerShell (Admin).
- Inside the PowerShell window, type in the following command: ‘ipconfig /flushdns’ (without quotes), and press Enter.
- When the process is completed, you should receive the following message: Windows IP Configuration
Successfully flushed the DNS Resolver Cache
3. Reboot DHCP Server
- Save any work you’re currently performing on the computer.
- Click on Start button -> Power button.
- Select the ‘Restart’ option.
4. Sync time settings
For this step, you will need to make sure that the time settings on your DHCP Server are the same as with the client’s terminal. Any difference in this area can cause issues with the IP packages your DHCP Server can distribute over the network and may cause the DHCP service to stop entirely.
5. Fix any connectivity issues between DHCP Server and domain controller
- Log into your DHCP server -> press ‘Win + R’ keys to open the Run window.
- Type in ‘cmd’ (without quotes) -> press Enter.
- Inside the Command Prompt, type ‘ping server_FQDN’ (where server_FQDN is the full domain name of the domain controller.
- Press Enter.
If the ping is successful, you will see a reply similar to this : ”Reply from IP_address: bytes=32 time=3ms TTL=59”
Follow these steps to ping the IP address of the domain controller:
- Inside the command prompt window, type ‘ping IP_address’ (where ‘IP_address’ is the IP address of the domain controller.
- Press Enter.
If you successfully managed to ping the FQDN but not the domain controller IP address, this means that you might have a problem with the DNS host name resolution.
In case you can not ping the domain controller by IP address, this means that there are possible issues with your DHCP server‘s firewall configuration, network connectivity, or IPsec configuration.
Please feel free to let us know if this guide helped you solve your DHCP Server issues, by using the comment section below.