This can be verified by opening the DHCP service console to view service status, or by opening Services and Applications under Computer Manager.
If the appropriate service is not started, start the service.
Hence, the scopes are not required to be imported on the second server (DHCP2).
However the failover setup wizard (or cmdlet), does not replicate server level configuration to the second DHCP server.
To make the initial lease database, just create an empty file called /var/lib/dhcpd/dhcpd.leases.
You can do this with: In order to prevent the lease database from growing without bound, the file is rewritten from time to time.
If the DHCP server is stopped, complete the following procedure to restart it: To restart a DHCP server that is stopped The DHCP Relay Agent service provided with Multi-Protocol Routing (MPR) does not provide a TCP/IP address from a remote DHCP server.
When dhcpd is first installed, there is no lease database.
However, dhcpd requires that a lease database be present before it will start.
Every time a lease is acquired, renewed or released, its new value is recorded at the end of the lease file.
So if more than one declaration appears for a given lease, the last one in the file is the current one.