Recipe 14.4. Enabling Address Conflict DetectionProblemYou want to enable address conflict detection on a DHCP Server. With conflict detection enabled, the DHCP Server will ping the IP address it wants to grant a lease for to make sure no other computers are using that IP address. If the ping request receives a reply, the server will mark the IP as BAD_ADDRESS. SolutionUsing a graphical user interface
Using a command-line interfaceThe following command configures conflict detection: > netsh dhcp server \\<ServerName> set detectconflictretry <PingAttempts> This command displays the current conflict detection setting: > netsh dhcp server \\<ServerName> show detectconflictretry Using VBScriptSee Recipe 14.0 for more information on how to run the netsh command from within a script. DiscussionEnabling address conflict detection is generally a good idea so clients don't obtain an IP address in use by another computer. The DHCP Server will ping the IP address it is about to grant to ensure nothing responds. You can configure the number of ping attempts, but one or two should be sufficient in most cases. You might wonder why conflict detection is even necessary. There are three situations where a DHCP Server can give a lease for an IP address that is already in use:
Enabling conflict detection adds some overhead to the lease request process. Each ping attempt must timeout, which takes about a second per attempt, before the server can grant the lease. For this reason, you don't want to configure more than one or two ping attempts. See AlsoMS KB 161430 (DHCP: Detecting and Flagging Duplicate IP Addresses) |