Author Topic: Detect and Avoid IP Address Conflicts  (Read 2019 times)

0 Members and 1 Guest are viewing this topic.

Detect and Avoid IP Address Conflicts
« on: July 03, 2010, 03:47:58 PM »

Offline Nick

  • Administrator
  • Platinum Member
  • *
  • Posts: 46027
  • Karma: +1000/-0
  • Gender: Male
  • NickCS
    • http://www.facebook.com/nickcomputerservices
    • http://www.twitter.com/nickcomputer
    • Computer Chiangmai

Detect and Avoid IP Address Conflicts

To better detect and avoid potential conflicts, you can enable IPv4 address conflict detection by following these two simple steps.

IPv4 address conflicts are a common cause of problems with DHCP. No two computers on the network can have the same unicast IP address. If a computer is assigned the same unicast IPv4 address as another, one or both of the computers might become disconnected from the network.

To better detect and avoid potential conflicts, you can enable IPv4 address conflict detection by following these steps:

1. In the DHCP console, expand the node for the server you want to work with, right-click IPv4, and then click Properties.

2. On the Advanced tab, set Conflict Detection Attempts to a value other than 0. The value you enter determines the number of times the DHCP server checks an IP address before leasing it to a client. The DHCP server checks IP addresses by sending a ping request over the network.


Real World Example: A unicast IPv4 address is a standard IP address for class A, B, and C networks. When 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 checks only the list of current leases to determine whether an address is available. It doesn’t actually query the network to see whether an address is in use.

Unfortunately, in a busy network environment, an administrator might have assigned this IPv4 address to another computer or an offline computer might have been brought online with a lease that it believes hasn’t expired, even though the DHCP server believes the lease has expired. Either way, you have an address conflict that will cause problems on the network. To reduce these types of conflicts, set the conflict detection to a value greater than 0.

From the Microsoft Press book Windows Server 2008 Administrator’s Pocket Consultant, Second Edition by William R. Stanek.


credit: technet.microsoft.com


 
Share this topic...
In a forum
(BBCode)
In a site/blog
(HTML)


Related Topics

  Subject / Started by Replies Last post
0 Replies
2898 Views
Last post July 03, 2010, 03:19:06 PM
by Nick
0 Replies
2077 Views
Last post February 26, 2013, 02:17:35 PM
by Nick
0 Replies
616 Views
Last post March 22, 2013, 12:24:50 PM
by Nick
0 Replies
196 Views
Last post February 04, 2020, 08:26:21 AM
by nitipat