none
Losing DHCP IP address RRS feed

  • Question

  • Hi,

    We've been having a weird issue where PC's have been losing the IP address out of the blue and end up with a 169.254.xxx.xxx address. People are working fine and all of a sudden the network stops working. Looking at the network information, all the information is fine except for the IP address now at 169.254.xxx.xxx.

    This is happening network wide and I can't find anything in my DNS/DHCP event logs. I have 2 domain controllers with integrated DNS.

    The DHCP lease is 24h and this might happen 1h after a machine was booted.

    Thank for the help.

    Luc


    • Edited by llacasse Tuesday, July 3, 2018 7:12 PM added info
    Tuesday, July 3, 2018 7:08 PM

All replies

  • Hi,

    Thanks for your question.

    First of all, I need to confirm whether this is a single event or a general phenomenon.

    When the DHCP server is unable to respond to the client's request, the client gets the IP address of the 169.254.x.x segment.

    If it is a single event, the problem may be on the client side.

    • Use the ping command to test connectivity from the client to the server. Your next step would be to either verify or manually attempt to renew the client lease. Depending on your network requirements, it might be necessary to disable IP autoconfiguration at the client.

    Refer to the following link:

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc757164(v%3dws.10)

    If it is a general event, the problem may be on the server side.

    • Scopes or superscopes on the DHCP server have not been either configured or activated for use. Add scopes and make sure that they are correctly configured along with any DHCP scope options that need to be assigned for client use.
    • The server is located on a different subnet as some of its clients and is not providing service to clients on remote subnets. If you are using a DHCP server in a routed network, you might want to review issues related to DHCP relay agents and the appropriate use of superscopes.
    • The DHCP server is not authorized in Active Directory. If the DHCP server is a domain member, authorize the server in Active Directory.
    • The IP address of the DHCP server was changed. Check the IP address of the DHCP server.

    Refer to the following link:

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc779112%28v%3dws.10%29

    Hope you have a nice day!

    Best regards,

    Travis


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, July 4, 2018 5:42 AM
    Moderator
  • I'm seeing the same problem post patching our domain controllers (which are also doing DHCP servers)

    we are running Server 2016 std server. Both Hyper-V and physical. 

    The source for us seemed to be KB4284833. Removing that update from our domain controllers fixed the issues. (We saw the issue in 8 offices and 5 DCs)

    Are you running 2016 and patch with KB4284833? 

    • Proposed as answer by NeilRawlinson Thursday, July 5, 2018 9:39 AM
    Thursday, July 5, 2018 3:36 AM
  • Ditto to the KB4284833 update on Domain controllers running DHCP

    Neil Rawlinson

    Thursday, July 5, 2018 9:39 AM
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Travis


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, July 9, 2018 1:19 AM
    Moderator
  • KB4284833 now has breaking DHCP as a known issue in the description of the patch, fix tentatively promised as "mid July".
    Monday, July 16, 2018 6:22 AM