DHCP 2012 Hot Standby doesn't give new leases


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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kryanCAuthor Commented:
Any help is appreciated
Rob StoneCommented:
To confirm, the DHCP log file is not showing any attempts to request an IP?

I would sugget downloading Network Monitor v3.4, installing on a client and run a IPCONFIG /RENEW and see where it's going.

Is the DHCP failover server on the same subnet as the primary DHCP server?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kryanCAuthor Commented:
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.


It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.