<div>
Thank you. &nbsp;We are in Houston and our DC has 4.5 feet of water in it so we are scrambling to recover to PHX and this DHCP failover was killing us.
</div>


Thank you.  We are in Houston and our DC has 4.5 feet of water in it so we are scrambling to recover to PHX and this DHCP failover was killing us.

<div>
<div class="content wysiwyg-content">
We have two 2012 R2 server running DHCP in failover mode. &nbsp;We have lost one DHCP server and it's partner is not issuing IP address.<br />
<br />
The partner server is never coming back.<br />
<br />
My remaining DHCP server is not issuing IPs.<br />
<br />
Can I break the replication and get the remaining DHCP server to issue IP addresses? &nbsp;If yes, how?<br />
<br />
Thanks<br />
<br />
Cliff
</div>
</div>


We have two 2012 R2 server running DHCP in failover mode.  We have lost one DHCP server and it's partner is not issuing IP address.

The partner server is never coming back.

My remaining DHCP server is not issuing IPs.

Can I break the replication and get the remaining DHCP server to issue IP addresses?  If yes, how?

Thanks

Cliff

Broken DHCP Replication

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).