none
DHCP service fails on Windows Server 2008 R2 with non-Legacy DUID RRS feed

  • Question

  • A Windows Server 2008 R2 DHCP server is failing to give out any more DHCP leases after it encounters a DHCP client using longer non-legacy IPv4 device unique identifers (DUID). The DHCP server is accustomed to unique identifiers only being composed of Link Layer 2 MAC addresses: the standard xx:xx:xx:xx:xx:xx format.

    The DHCP server will continue to register any leases, legacy or not, but it will then silently fail to give out the leases for any subsequent DHCP requests. To get the DHCP server again I must delete the offending lease and reboot the Server. Restarting the DHCP service is not sufficient.

    The devices that are 'crashing' the DHCP server are Chromebooks and Android tablets running up to date Cyanogenmod. Some of the tablets can use a legacy DHCP mode to avoid causing the DHCP server to crash.

    Is this a known issue? Is there a fix coming?
    Monday, September 5, 2016 5:05 PM

Answers

  • Hi orbitingPluto,

    >longer non-legacy IPv4 device unique identifers (DUID).

    1. Could you explain the "non-legacy" and "legacy" a little further, seems it's not a glossary with DUID;

    2. As you have already mentioned, IPv4 address lease is related with MAC address;

    3. Could you use network monitor on both client and DHCP server to capture traffic packet to check which DHCP progress has issues.

    Network monitor download link:

    https://www.microsoft.com/en-us/download/details.aspx?id=4865

    Best Regards,

    Anne


    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 tnmff@microsoft.com.

    Tuesday, September 6, 2016 8:05 AM
    Moderator

All replies

  • Hi orbitingPluto,

    >longer non-legacy IPv4 device unique identifers (DUID).

    1. Could you explain the "non-legacy" and "legacy" a little further, seems it's not a glossary with DUID;

    2. As you have already mentioned, IPv4 address lease is related with MAC address;

    3. Could you use network monitor on both client and DHCP server to capture traffic packet to check which DHCP progress has issues.

    Network monitor download link:

    https://www.microsoft.com/en-us/download/details.aspx?id=4865

    Best Regards,

    Anne


    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 tnmff@microsoft.com.

    Tuesday, September 6, 2016 8:05 AM
    Moderator
  • Hi orbitingPluto,

    Could the above replies be of help? If yes, you may mark it as answer, if not, feel free to feed back.

    Best Regards,

    Anne


    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 Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 20, 2016 8:41 AM
    Moderator