DHCP on Windows Server 2012 using 169.254.xx.xx as server name

1. Sam

   11/05/2020, 20:07

   Thanks, I’ve spent days trying to figure this out. This solution works in minutes on my personal home lab.

2. Johan

   26/09/2019, 21:26

   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

3. abdul

   08/08/2019, 11:25

   thanks

4. Guest

   17/05/2019, 00:16

   Thanks worked

5. siskum

   11/04/2019, 09:55

   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.

6. Christian

   21/12/2018, 13:27

   works perfect.

7. Alex

   11/12/2018, 18:51

   Very simple resolution. :D Thanks !

8. Luiz Castro

   17/10/2018, 22:36

   Thank you so much, it worked.

9. Anonymous

   19/07/2017, 08:32

   thanks it is working

Comments are closed