Problem: after installing a new Windows Server 2012 R2 machine with the DHCP role enabled, adding a DHCP server used a 169.254.x.x IP address as server name. Instead of the servers hostname…

Solution: do you have more than one network adapters on the server, but are not connected? Disabling the not connected network adapters solves this issue. The DHCP server was bound to the wrong adapter.

8 replies
  1. Johan
    Johan says:

    I have no other functional unbound adapters and the server still starts with a non present 169.254… Dhcp which I delete and add the appropriate dhcp manually after every startup. This is bollox from Microsoft, you specify the bindings and only those adapters should be bound, the system should not override, especially with 169…phantom adapters. I suspect what’s happening is that dhcp is initializing before the adapters are properly online. Still the bindings should not be ignored. Very poor Microsoft. Server 2019 has a bug that the internal adapter is assigned 169…so no l2tp connections are possible. They released a registry workaround but on a commercial product, dhcp in sever does not work correctly. Bindings should be set, how can the server just choose whatever it feels like. Broken

    Reply
  2. siskum
    siskum says:

    Ohhh..awesome..you are genius.. I spent a days and days to get rid of this nusty ugly IPv4 169.254.hh.hh. Many guys suggest many different commands non of them working. Finally you gave me so simple solution. It works within a second. I cannot see any more ugly IPv4 169.254.0.0/16.. Thanks my genius…cheers.

    Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *