| Previous | Next |
| STATUS_OBJECTID_NOT_FOUND | STATUS_WRONG_CREDENTIAL_HANDLE |
STATUS_NO_IP_ADDRESSES
An installed network adapter is not the same as a usable local IP address
STATUS_NO_IP_ADDRESSES indicates that the local machine cannot satisfy an IP-dependent operation because no usable local IP address is available. Start with interface and address state rather than remote DNS or server availability. Windows distinguishes addresses that are Preferred from those that are Tentative, Duplicate, Deprecated, or Invalid.
A network adapter can be enabled and even have link while its address is still undergoing Duplicate Address Detection or has been rejected as duplicate. DHCP can also be incomplete, a manual address can be removed, or policy and compartment changes can leave the process without an applicable address. The status does not itself identify which configuration mechanism failed.
Record the address family required by the operation. A system with only IPv6 addresses may still fail code that explicitly requires IPv4, and vice versa. Enumerate the actual addresses and states at the moment of failure instead of relying on a later ipconfig snapshot after DHCP or DAD has recovered.
What to inspect
- Required address family and the interface/compartment in which the failing operation is running.
- Current addresses, prefix origins, suffix origins, and
AddressStatevalues from the affected time window. - DHCP, SLAAC, manual configuration, DAD conflict, or adapter transition events immediately before the status.
References
- Microsoft: Get-NetIPAddress address states
- RFC 4862: IPv6 Stateless Address Autoconfiguration
- Microsoft: Event 4199 and IPv4 duplicate-address detection
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.