Share via


Windows Server 2012 r2 DHCP not serving addresses

Question

Sunday, May 15, 2016 10:14 AM

Hello Technet!

Yesterday I encoutered a DHCP problem. After windows update and restart, my dhcp won't serve any new IP addresses. The ones wich has been sent before are working but no new IP-s. I tried restarting the DHCP server the Full server sevral times but no success. The settings hasn't been changed, but I checked and it has a lot's of free IP -s and the scope is activated and the server is Authorized to serve DHCP.
I tried adding a RogueDetection disabling registry key but no success.
I tried to check it with wire shark but suprisingly from the server there is no outgoing DHCP packet. I checked from the client too and it send discovery packets but it didn't get any offer.

And now I'm out of ideas... :/

I will attach the DHCP server log and the client and server Wireshark log.

https://dl.dropboxusercontent.com/u/28212715/LOGS.rar

Please if someone has any other ideas or solutions, I would be very happy.

Thanks Forward.

Thomas

All replies (3)

Sunday, May 15, 2016 10:51 AM ✅Answered

Hi

 There is "Unreachable Domain" error on your logs;

an means ;

Unreachable domain

The DHCP server could not locate the applicable domain for its configured Active Directory installation. ; https://technet.microsoft.com/en-us/library/dd759178%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

Also check this similar case and try the mentioned steps to fix the issue,https://social.technet.microsoft.com/Forums/windowsserver/en-US/babd49b5-da0d-4838-9fcd-2591efa17dc5/unable-to-authorize-dhcp-server-event-id-1046-1059?forum=winserverNIS

This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur


Sunday, May 15, 2016 9:19 PM ✅Answered

As already mentioned, you have multiple errors stating "Unreachable Domain". This means that your DHCP server is trying to communicate with your DCs but is unable to.

The first thing I would recommend to check is DNS resolution and if your DCs are properly registered in DNS. You can use **NSlookup **to check the A and SRV records: http://social.technet.microsoft.com/wiki/contents/articles/29184.nslookup-for-beginners.aspx

In addition, you need to check the errors in eventviewer of your DHCP server. You may find errors related to DNS resolution or others that may help on figuring out what is wrong.

In addition, you need to check that required ports to communicate with your DCs are open and are not blocked or filtered: https://technet.microsoft.com/en-us/library/dd772723%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

This posting is provided AS IS with no warranties or guarantees , and confers no rights.

Ahmed MALEK

My Website Link

My Linkedin Profile

My MVP Profile


Monday, May 16, 2016 6:19 AM

Hi Thomas,

>>I will attach the DHCP server log and the client and server Wireshark log.

https://dl.dropboxusercontent.com/u/28212715/LOGS.rar

It seems that  DHCP can't contact AD. Do you change your DNS settings of the server?

For example.

  • Using an ISP's DNS address in the NIC's properties
  • Using the router's IP as a DNS address in the NIC's properties.

It is extremely important that only the internal DNS servers hosting the AD zone are the only DNS servers used. Otherwise, numerous issues can result.

If you can post an unedited ipconfig /all, we can further evaluate the machine's configuration to eliminate any basic configuration problems, and possibly provide suggestions and recommendations.

________________________________________
Best Regards,
Cartman
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].