Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

2nd DHCP Server Not Working

$
0
0

Hi,

I have a pure WS2K9/Win10 domain and clients.

Originally, the single PDC had a DHCP which worked fine out of the box.

For redundancy reasons, I added a DHCP server on the second DC, and defined a Load-Balancing Failover Relationship, from the PDC DHCP to the DC DHCP. This worked fine immediately.

The second DC (physical server) was getting old, so I virtualized it. However, there were a few problems with it after it was virtualized. So I decided to build a new virtual DC server. I put a DHCP server on this new, 2nd DC.
I deleted the failover relationship from the PDC to the 1st DC, and added a failover relationship to the new, 2nd DC. The DHCP scope settings appeared to be correctly copied to the 2nd DC.

BUT - the 2nd DC is not responding to client requests - if I turn off the DHCP on the PDC, the 2nd DC does not react, and the ipconfig/renew fails on any client.

The Win10 client's DHCP-Client log shows:

Event ID: 1003 OpCode IpLeaseRenewalFailed:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0x3402866FA54B.  The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

I would greatly appreciate any help.

mlavie



Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>