Read Windows network settings with ipconfig /all

Detailed practical guide

Prepare your workspace and inputs

Use the affected workstation and an approved working comparison on the same intended network. Record the problem time, wired or wireless connection and VPN state. Keep remote access connected while collecting evidence.

Platform context: Windows 11 or Windows Server with Command Prompt; PowerShell is used only for the explicit interface listing in step 1.

Scenario to reproduce or investigate

A computer shows connected but cannot reach the business application. The first listed adapter may be a VPN or virtual switch rather than the one carrying the failed traffic.

1. Identify candidate active adapters

   Run ipconfig /all in Command Prompt. If several adapters are present, use the PowerShell listing to relate interface aliases and addresses. Find the adapter expected for this connection rather than choosing the first Ethernet label.

   Command, configuration or input

   ipconfig /all
   
   PowerShell:
   Get-NetIPConfiguration | Format-List InterfaceAlias,InterfaceIndex,IPv4Address,IPv4DefaultGateway,DNSServer

   Expected result · ผลที่ควรเห็น

   You can name the intended interface and record its IP address, prefix or mask, gateway, DNS servers and DHCP state.

   If it fails · เมื่อไม่ผ่าน

   If the expected adapter is media-disconnected, check cable, switch port or Wi-Fi association before changing DNS. If only a VPN adapter has the business route, include its state in the ticket.

2. Classify the observed address and assigned services

   Compare the observed settings with the approved subnet and working peer. An IPv4 address in 169.254.0.0/16 on a DHCP client can indicate that a normal DHCP lease was not obtained. A valid private address does not prove the default gateway or resolver is correct. Record the DHCP server and lease timing where shown.

   Command, configuration or input

   Record: interface | address/mask | gateway | DNS servers | DHCP enabled | DHCP server | lease time

   Expected result · ผลที่ควรเห็น

   The finding states the specific mismatch or explicitly says that the configuration matches inventory; it does not equate every private address with a valid network assignment.

   If it fails · เมื่อไม่ผ่าน

   If the network intentionally uses static or link-local addressing, verify that design with the owner. Do not infer DHCP failure solely from the address without the intended configuration.

3. Test address reachability and name resolution separately

   Use the actual documented gateway in place of the example and resolve the application hostname with the assigned resolver. The addresses below are placeholders, not public test targets. An ICMP timeout is inconclusive if policy blocks ICMP.

   Command, configuration or input

   ping -n 4 192.0.2.1
   nslookup app.example.invalid

   Expected result · ผลที่ควรเห็น

   The record distinguishes gateway reachability, resolver response and the application name answer. It includes the actual approved values used in place of placeholders.

   If it fails · เมื่อไม่ผ่าน

   If the gateway is reachable but name resolution fails, investigate the resolver path and answer before renewing the lease. If DNS works but the application fails, test its supported service endpoint rather than flushing all caches.

Recovery and cleanup

The procedure is read-only. If a later approved setting change is made, record the original static or DHCP configuration so it can be restored without dropping an unattended remote session.

Apply to actual work and known limits

Use actual network inventory for the comparison. No expected IP address or gateway is universal, and a correct IP configuration does not establish that the application service is available.

Authored against the cited documentation. Execution on the stated vendor product or physical equipment remains to be verified.