DHCP Failover Issue

Ran into this one today when setting up DHCP failover between 2 Windows servers.

On the first screen after selecting Setup Failover the Relationship Name field showed up as “169.254.x.x – Actual Server Name”.   This was on a functional production DHCP server that was also a Domain Controller.   169.254.x.x is an APIPA address so this threw me for a minute.   What it ended up being was that there was a 2nd NIC on this server in an unplugged/disconnected state.  As soon as I disabled this NIC and then restarted the Failover wizard the correct DNS name of the server showed up in the relationship name.

 

What’s your Reaction?
+1
0
+1
0
+1
0
Scroll to Top