<div>
Traced it down, turns out our DHCP relay agent/device was only configured for the Primary DHCP. Used net mon to track the traffic, saw it dying on the agent, added the second ip to the relay, and now all is well. Thanks for the Net Mon took me right down the path.<br />
<br />
thanks<br />
<br />
Ryan
</div>


Traced it down, turns out our DHCP relay agent/device was only configured for the Primary DHCP. Used net mon to track the traffic, saw it dying on the agent, added the second ip to the relay, and now all is well. Thanks for the Net Mon took me right down the path.

thanks

Ryan

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I am testing the 2012 DHCP failover solution for MS Server 2012.<br />
<br />
I followed the directions numerous times. The Standby says it is good, the scope populates, and everything looks perfect. I then stop the DHCP service on my primary and the Standby display the little orange arrow on the IPv4 but never releases any IPs. The test client never gets a new lease. The old lease, when it expires, even drops from the Standby. I have no idea where to go no logging clues/errors. Ideas would be apprecitated.<br />
In addition, I am using VMs for servers and test clients.<br />
The same thing happens when trying the load balance as well.<br />
Been all over the web and can't find anything on this. Every thing looks fine until I terminate services on the primary DHCP server then try to get a new lease. Clients ping the standby before primary terminates, and resolve netbios. Any ideas?<br />
Ryan
</div>
</div>


Hello,

I am testing the 2012 DHCP failover solution for MS Server 2012.

I followed the directions numerous times. The Standby says it is good, the scope populates, and everything looks perfect. I then stop the DHCP service on my primary and the Standby display the little orange arrow on the IPv4 but never releases any IPs. The test client never gets a new lease. The old lease, when it expires, even drops from the Standby. I have no idea where to go no logging clues/errors. Ideas would be apprecitated.
In addition, I am using VMs for servers and test clients.
The same thing happens when trying the load balance as well.
Been all over the web and can't find anything on this. Every thing looks fine until I terminate services on the primary DHCP server then try to get a new lease. Clients ping the standby before primary terminates, and resolve netbios. Any ideas?
Ryan

DHCP 2012 Hot Standby doesn't give new leases

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.