This might occur if more than one DHCP server owns the address, or if an address was manually configured for a non-DHCP network client.The IP address considered for offering to a DHCP client does not have a record in a network table.
Solution: Determine the proper ownership of the address.
Correct either the DHCP server database or the host's network configuration.
restarting the DNS (plus RELOAD the entry) and DHCP services doesn't help at all and also entering the DHCP assigned IP address into the DNS server caused more problem since the address is assigned to different host already by DHCP but not gets updated in the DNS server (only to non-windows machine).
If anyone know how to diagnose and help me solve this problem that'd be very great helps. Check that your non-windows dhcp clients send out their hostname to the server.
DHCP provides an automated way to distribute and update IP addresses and other configuration information on a network.
A DHCP server provides this information to a DHCP client through the exchange of a series of messages, known as the DHCP conversation or the DHCP transaction.Use DHCP Manager or to examine the network table on this server and any other DHCP servers on the network and correct if necessary.You can also do nothing and allow the lease to expire, after which the client will automatically request a new address lease.DHCP provides support for client computers running any of the following Microsoft operating systems: DHCP supports Automatic Private IP Addressing (APIPA), which enables computers running Windows 2000, Windows XP, and Windows Server 2003 to configure an IP address and subnet mask if a DHCP server is unavailable at system startup and the Automatic private IP address Alternate Configuration setting is selected.This feature is useful for clients on small private networks, such as a small-business office or a home office.I am having a problem with my Windows Server 2008 R2 DHCP server.