Sunday, April 4, 2010

How to detect and avoid the IPv4 Conflicts in the Windows Network Environment

If you have a conflict of your IPv4 Address with the DHCP, you don’t need to worry as it is a common problem. As you know, it is not possible to use the same unicast IP Address for two Computers. If you still assign the same unicast IPv4 Address for two Computers, one or both of the Computers will get disconnected from the Network. For a better detection and to avoid the potential conflicts, you can enable the IPv4 Address Conflict using the following steps.
•    In the DHCP console, you have to expand the node for the Server you want to work with and then right click on the IPv4 and select the Properties.
•    Then, in the Advanced tab, set Conflict Detection Attempts to a value other than 0. Remember, the value you enter will determine the number of times the DHCP Server checks an IP Address before leasing it to a client. By sending a ping request in the Network, the DCHP Server checks the IP Address and conflicts.

A unicast IPv4 address is a standard IP address for class A, B and C Networks. If a DHCP client requests a lease, a DHCP server checks its pool of available addresses and assigns the client a lease on an available IPv4 address.
By default, the server is able to check if the list of current leases available or not. At the same time, it doesn’t query the network to check if an address is in use. Unfortunately, if an administrator might have assigned the same IPv4 address to other Computer or an offline Computer enters the online with a lease line, the conflicts may occur. In order to reduce these types of conflicts, you can set the conflict detection to a value greater than 0. This type of conflict is one of the well-known examples around the world.

By , ,