Per Jessen wrote:
Joachim Schrod wrote:
We don't actually use a redundant DHCP setup - I just tested it a while ago. IMO, there is little need for a redundant DHCP setup - clients will keep their addresses after they have expired even if they can't get an ACK.
We had a server outage not long ago, and the clients reconfigured themselves to 169.254.* addresses after the lease expired. This enabled me to convince the management that budget for redundancy is needed. The reconfiguration was done due to the APIPA feature of Windows. It can be disabled in the registry[*], and I'm fighting to get this done on all Windows systems to avoid that problem, but this is not always successful as client software release and configuration management is made by another department. So the HA setup for dhcpd is planned as another protection against outages. Joachim [*] http://www.windowsnetworking.com/articles_tutorials/w2knoaip.html for those who are interested in this issue. Though you want to create a .reg file or include it in your master image, and don't edit each Windows system configuration anew. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany