How to read ipconfig /all: what the output tells you
“Send me an ipconfig” is a common first step when troubleshooting Windows network problems. The ipconfig /all output is long, though, and people often look only for the IP address. Some of the most useful clues are in the lines that follow.
Why use ipconfig /all instead of just ipconfig
Without parameters, ipconfig shows the IPv4 address, subnet mask and default gateway for each adapter; IPv6 addresses may also be listed. For a diagnosis, this leaves out the fields that make the difference: DHCP status, DHCP server, DNS servers, lease times, physical address and the media status of disconnected adapters. The /all option adds those details and does not require administrator rights.
Another point is often overlooked: ipconfig /all lists all adapters, including virtual ones. VPN clients, Hyper-V switches, Bluetooth network connections and WSL adapters appear there. This complete list is a decisive clue when troubleshooting routing.
Annotated example output
The following output is from a fictional, working workstation. The fields to check first are highlighted.
Windows IP Configuration
Host Name . . . . . . . . . . . . : ARBEITSPLATZ-042
Primary Dns Suffix . . . . . . . : firma.intern
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : firma.intern
Description . . . . . . . . . . . : Ethernet controller (example)
Physical Address. . . . . . . . . : 00-00-5E-00-53-11
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.10.42(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, August 12, 2026 8:14:02 AM
Lease Expires . . . . . . . . . . : Thursday, August 13, 2026 8:14:02 AM
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.10
192.168.10.11
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth device (Personal Area Network)
Physical Address. . . . . . . . . : 00-00-5E-00-53-33
Example data: All names and addresses in the output are fictional. 192.168.10.0/24 is a private IPv4 range; the MAC addresses are from the documentation range reserved by RFC 7042.
Field-by-field guide
| Field | What to look for |
|---|---|
| Host name | Make sure it matches the support ticket. A different name means the output came from the wrong device, the most common source of conflicting findings. |
| Primary DNS suffix | If this field is empty on a device that should belong to a domain, the DNS suffix may be missing or misconfigured, or there may be a domain membership issue. |
| Media state | Appears only for disconnected adapters. “Media disconnected” on a laptop Ethernet adapter while using Wi-Fi is normal; on a desktop PC it indicates a cable or port problem. |
| Description | The actual adapter type. This reveals virtual adapters from VPN clients, Hyper-V or WSL that the user has not mentioned. |
| DHCP enabled | “No” means the adapter is not obtaining its IPv4 configuration through DHCP; a static address is often configured. In a DHCP network, an unexpected static configuration can cause a wrong subnet, address conflicts or outdated DNS entries. |
| IPv4 address | It should be in the expected subnet. An automatically configured address in 169.254.0.0/16 typically means the adapter did not obtain a usable DHCP configuration. |
| Subnet mask | A wrong mask can make Windows route a local destination through a gateway, or treat a remote destination as local. |
| Lease obtained / expires | Shows when the DHCP lease was obtained and when it expires. An old lease with a short lease duration may indicate a renewal problem; also check the DHCP server and current connection state. |
| Default gateway | When this field is empty, destinations outside the directly reachable network are usually unreachable without an additional route. Multiple adapters with their own gateways can cause unclear routing. |
| DHCP server | An unexpected DHCP server, such as a personal router on a corporate network, can explain an incorrect subnet, gateway and DNS configuration. |
| DNS servers | Corporate networks should use the designated internal resolvers. A public resolver can prevent internal names from resolving even when the internet works. |
Common symptoms
Address in the 169.254.x.x range
If DHCP is enabled for IPv4 and no usable DHCP configuration is obtained, Windows may use an Automatic Private IP Address (APIPA). The address alone does not prove whether a physical or Wi-Fi link is present.
Check whether the wall port is assigned to a VLAN without DHCP, whether 802.1X authentication is missing, or whether the device is on a guest network. An empty gateway and DHCP server are additional clues, but they do not identify the cause by themselves.
No default gateway
Devices on the local network may be reachable while destinations outside it are not. A user may report: “The printer works, but the internet does not.”
Check whether the DHCP router option (option 3) is missing or not being applied, or whether a manually configured gateway was omitted. Also inspect the routing table; the IPv4 default route 0.0.0.0/0 may be missing.
Two adapters with a gateway
Common with an active VPN, a dock or simultaneous Ethernet and Wi-Fi connections. Windows selects among routes that match the destination; for routes with the same prefix length, the combined route and interface metrics matter. A more specific route can take precedence over a default route.
Check which adapters have a gateway and compare the destinations and metrics in the routing table. This can explain why internal servers are reachable in one connection state but not another.
Incorrect or incomplete DNS servers
Public websites work, but internal shares and applications do not. This is often reported as “the server is down.”
Check whether the internal resolvers are listed first and whether the order is the same on all devices at the site. Then test name resolution itself: a correct server list does not prove that the server is responding.
DHCP disabled unexpectedly
A static address may have been left in place after earlier troubleshooting. This can go unnoticed until a later change, such as a subnet migration.
Look for “DHCP enabled: No” alongside an address that looks plausible but falls outside the current subnet or allocation range.
A troubleshooting order that saves time
- Host name – did the output come from the right device?
- Which adapter is active? First rule out adapters marked “Media disconnected.”
- IPv4 address and subnet mask – expected subnet or APIPA?
- Default gateway – present and on the same subnet?
- DNS servers – internal, complete and in the right order?
- Then run separate checks: ping the gateway, then an internet IP address, and finally a host name. Ping tests ICMP, and filters can block replies. Using an IP address avoids name resolution, but ping success or failure alone does not prove whether an application is reachable.
For how to interpret the measurements from step 6, see the Windows packet loss guide.
admin-tools captures ipconfig /all together with the routing table, DNS cache, ARP table and ping results in one run, and displays each adapter with its IP configuration so you do not have to search through raw output.
The Windows diagnostic features describe the available checks. A static Windows sample report shows a report containing fictional data only.