// Lesson 12 of 49 · IPv4 addressing and subnetting
Verifying IP settings on hosts
Checking and testing addressing on Windows, Linux and macOS clients — the first step of most support tickets.
2 min read#windows#linux#macos#troubleshooting
When a user says "the network is down", the first thing to check is the client's own IP configuration. It takes a minute and rules out a surprising number of problems.
Windows
C:\> ipconfig /all
IPv4 Address. . . . . . . . . . . : 192.168.10.25(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Useful companions:
ipconfig /releaseandipconfig /renew— request a new DHCP lease.ipconfig /flushdns— clear cached DNS answers.ping,tracert,nslookup,route print,arp -a.
Linux
$ ip address show
$ ip route show
default via 192.168.10.1 dev eth0
$ resolvectl status # or: cat /etc/resolv.conf
macOS
$ ifconfig en0
$ netstat -rn | grep default
$ scutil --dns
What to check, in order
- Is there an address at all? 169.254.x.x (or none) → DHCP problem.
- Is the mask right for this VLAN?
- Is the gateway in the same subnet and reachable?
pingthe gateway. - Can you reach something beyond the gateway by IP? (
ping 8.8.8.8— if allowed.) - Does DNS work?
nslookup www.example.com.
Each step isolates one layer: if 3 works and 4 does not, the problem is beyond the gateway — routing, NAT or a firewall — not on the client.
Key points
ipconfig /all,ip addressandifconfigshow the client's view.- Test in order: address → mask → gateway → beyond the gateway → DNS.
- A ping to the gateway is the single most useful client-side test.
Sign in to save your lesson progress across devices. You can read every published lesson without an account.