ipconfig reports and manages Windows IP configuration
The basic ipconfig command summarizes addressing for active adapters. ipconfig /all adds details such as physical address, DHCP status, DHCP server, DNS servers, lease timestamps, and other adapter information. Its greatest value is showing what the client believes its network configuration is before you test the path.
A plausible ipconfig value still needs comparison with the intended segment and effective traffic path. The AP Networking CLI Command Output Troubleshooting Practice Test includes gateway/prefix mismatches, inactive-adapter screenshots, VPN route overrides, and configuration that differs from the actual application resolver.
It does not prove that the gateway, DNS server, or Internet is reachable merely because those addresses appear.
These fields determine the client's local subnet
Suppose the client shows 192.168.40.77 with mask 255.255.255.0. The /24 network is 192.168.40.0/24, so destinations 192.168.40.1 through 192.168.40.254 are treated as local by that host. A wrong mask changes that local-versus-remote decision even if the IPv4 address itself looks reasonable.
Use Wrong Subnet Mask Symptoms when the boundary is suspect.
The gateway is used for destinations the host considers remote
A gateway field of 192.168.40.1 is plausible for the /24 example because it is local to the client. A gateway of 192.168.50.1 would not normally be directly reachable from that /24 without special behavior. Compare the configured gateway with the network plan and a working peer.
The presence of a gateway value does not prove the router is online.
Lease evidence separates automatic configuration from fallback addressing
When DHCP is enabled, ipconfig /all can show the DHCP server and lease information. An IPv4 address in 169.254.0.0/16 commonly indicates Windows self-assigned link-local addressing after normal DHCP configuration was unavailable. That is a DHCP-path clue, not an Internet address supplied by the router.
Use DHCP commands when you specifically need a new lease transaction
ipconfig /release relinquishes DHCP configuration for applicable adapters, while ipconfig /renew requests configuration again. These commands can help verify a repaired DHCP service, but releasing a working remote-management interface can disconnect your session. Use them deliberately.
Renewing repeatedly does not fix an exhausted scope, missing VLAN, or unreachable DHCP server.
flushdns affects the client's resolver cache, not the DNS server
ipconfig /flushdns clears the Windows DNS resolver cache. It can remove stale cached answers after a DNS record changes. It does not repair a DNS server that is unreachable or correct the wrong DNS server delivered by DHCP.
Use nslookup when you need to see what a resolver currently answers.
Interpret the fields as one configuration
| Field | Example | Interpretation |
|---|---|---|
| IPv4 Address | 10.24.8.146 | Client address |
| Subnet Mask | 255.255.255.128 | /25; network is 10.24.8.128/25 |
| Default Gateway | 10.24.8.129 | Local gateway inside that /25 |
| DHCP Server | 10.24.1.20 | Server that supplied the lease; can be remote via relay |
| DNS Servers | 10.24.2.53 | Resolver the client will query |
Swipe horizontally to see the full table.
Configuration is not the same as reachability
A perfectly formatted address can still be duplicated. A correct gateway can be offline. A listed DNS server can time out. After validating configuration, choose a test for the dependency you need to prove: ping/ARP for local reachability, nslookup for DNS response, or an application/port test for the service.
This distinction makes ipconfig evidence much more useful than treating it as a pass/fail command.