What does NTSTATUS 0xC0000254 (STATUS_IP_ADDRESS_CONFLICT1) mean?

 
Previous Next
STATUS_LPC_REPLY_LOST STATUS_IP_ADDRESS_CONFLICT2

STATUS_IP_ADDRESS_CONFLICT1

Capture duplicate-address evidence before changing DHCP or disabling conflict detection

STATUS_IP_ADDRESS_CONFLICT1 belongs to duplicate IP address diagnosis. For IPv4, RFC 5227 defines Address Conflict Detection with ARP Probes and Announcements. For IPv6, RFC 4862 defines Duplicate Address Detection and requires a tentative address found to be duplicate not to be assigned to the interface. Windows exposes address states such as Tentative and Duplicate through the NetTCPIP cmdlets.

A conflict does not automatically mean the DHCP server issued the same lease twice. Microsoft documents Event 4199 cases where a switch or router IP Device Tracking feature sends an ARP probe while a Windows client is performing conflict detection, causing the client to interpret the probe as duplicate-address evidence. Static addresses, cloned virtual machines, stale network configuration, and layer-2 segmentation mistakes also need to be considered.

Preserve the interface, VLAN or broadcast domain, candidate IP, MAC addresses observed in ARP or Neighbor Discovery traffic, and the DAD state timeline. Disabling DAD removes a safety mechanism and can leave two nodes using the same address without a Windows warning; it should not be the first diagnostic action.

What to inspect

  • The affected interface, candidate address, prefix, address origin, and Windows AddressState at the failure time.
  • ARP Probe/Announcement or IPv6 Neighbor Solicitation evidence showing which link-layer addresses claim the IP.
  • DHCP lease history, static assignments, VM cloning, and switch/router features that can generate conflict-detection traffic.

References


Looking for a different code? Search another status or error code.