1.11 Verifying IP Parameters on Client Operating Systems
Key Takeaways
- Use 'ipconfig' on Windows and 'ifconfig' or 'ip addr' on Linux/macOS to view IP configuration.
- Key parameters to verify: IP address, subnet mask, default gateway, DNS server, and DHCP status.
- The 'ping' command tests Layer 3 connectivity; 'traceroute' shows the path packets take.
- A 169.254.x.x (APIPA) address indicates the DHCP process has failed.
- The 'nslookup' command tests DNS resolution; 'arp -a' shows the local ARP cache.
Last updated: March 2026
Verifying IP Parameters on Client Operating Systems
The CCNA tests your ability to verify and troubleshoot IP configuration on end-user devices. You must know the commands used on different operating systems.
Windows Commands
C:\> ipconfig ! Show IP, mask, gateway for all interfaces
C:\> ipconfig /all ! Detailed info including DHCP, DNS, MAC address
C:\> ipconfig /release ! Release DHCP lease
C:\> ipconfig /renew ! Request new DHCP lease
C:\> ipconfig /flushdns ! Clear DNS cache
C:\> ping 10.0.0.1 ! Test connectivity to an IP
C:\> ping -t 10.0.0.1 ! Continuous ping
C:\> tracert 10.0.0.1 ! Trace the route to destination
C:\> nslookup www.example.com ! Test DNS resolution
C:\> arp -a ! Show ARP cache
C:\> netstat -an ! Show active connections
Linux / macOS Commands
$ ip addr show ! Show IP configuration (Linux, modern)
$ ifconfig ! Show IP configuration (Linux legacy, macOS)
$ ip route show ! Show routing table
$ cat /etc/resolv.conf ! Show DNS server configuration
$ ping 10.0.0.1 ! Test connectivity
$ traceroute 10.0.0.1 ! Trace the route (Linux/macOS)
$ nslookup www.example.com ! Test DNS resolution
$ dig www.example.com ! Detailed DNS query
$ arp -a ! Show ARP cache
Key Parameters to Verify
| Parameter | What to Check | Possible Problem |
|---|---|---|
| IP address | Is it in the correct subnet? | Wrong VLAN, wrong DHCP scope |
| Subnet mask | Does it match the network design? | Mismatched mask prevents communication |
| Default gateway | Is it reachable? (ping test) | Wrong gateway, gateway down |
| DNS server | Can it resolve names? (nslookup) | DNS server unreachable, wrong DNS IP |
| DHCP status | Is it Enabled or Static? | 169.254.x.x = DHCP failure |
Troubleshooting with Ping
| Ping Target | Tests | Failure Indicates |
|---|---|---|
| 127.0.0.1 (loopback) | Local TCP/IP stack | TCP/IP stack broken |
| Own IP address | Local interface | NIC or interface problem |
| Default gateway | Local LAN connectivity | Cable, switch, or gateway issue |
| Remote host IP | End-to-end connectivity | Routing problem, firewall blocking |
| Remote hostname | DNS + connectivity | DNS not working or connectivity issue |
On the Exam: If a host has a 169.254.x.x address, it means DHCP failed and the host auto-assigned an APIPA address. Check DHCP server availability, DHCP scope, and ip helper-address on the router.
Test Your Knowledge
A Windows computer has an IP address of 169.254.10.50. What does this indicate?
A
B
C
D
Test Your Knowledge
Which command on Windows shows detailed IP configuration including DHCP server, DNS servers, and MAC address?
A
B
C
D