| Previous | Next |
| STATUS_IP_ADDRESS_CONFLICT1 | STATUS_REGISTRY_QUOTA_LIMIT |
STATUS_IP_ADDRESS_CONFLICT2
Do not infer the direction of the conflict from the numeric suffix
Microsoft publishes the same default description for STATUS_IP_ADDRESS_CONFLICT1 and STATUS_IP_ADDRESS_CONFLICT2: an IP address conflict exists with another system on the network. The public NTSTATUS catalog does not define 1 as “local,” 2 as “remote,” or assign any other documented conflict role. Diagnostic logic should not invent such a distinction.
Use the actual duplicate-address protocol evidence instead. RFC 5227 specifies IPv4 ARP probing and announcement behavior, while RFC 4862 defines IPv6 DAD and the Duplicate state. Windows can expose the address state through Get-NetIPAddress. The packet capture and interface event timeline show which address was tentative and which link-layer identity answered or asserted ownership.
This page is intentionally different from simply repeating the first conflict code: the important engineering point is that software should not branch on the suffix as though it were a documented subtype. Record and propagate the original NTSTATUS, but base remediation on address family, interface, DAD state, ARP/ND evidence, and address-assignment source.
What to inspect
- Whether product code assigns undocumented meanings to the
CONFLICT1/CONFLICT2names. - The address family and DAD state, plus ARP or Neighbor Discovery packets from the conflict interval.
- The source of the address assignment: DHCP, manual configuration, SLAAC, or another provisioning system.
References
- Microsoft Open Specifications: NTSTATUS values
- RFC 5227: IPv4 Address Conflict Detection
- RFC 4862: IPv6 Stateless Address Autoconfiguration
- Microsoft: Get-NetIPAddress address states
Looking for a different code? Search another status or error code.