Network Infrastructure and Connectivity · Topic 8 of 9

Troubleshooting Client Connectivity

Troubleshoot wired and wireless clients on Windows, macOS and Linux: read IP settings, test reachability step by step, find wireless security mismatches.

  • 6 min
In a nutshell
  • Windows: ipconfig /all, /release, /renew, /flushdns, tracert, netsh wlan show interfaces.
  • Linux: ip address show, ip route show, resolvectl status, traceroute, iw dev, nmcli.
  • macOS: ifconfig, networksetup -getinfo Wi-Fi, scutil --dns, traceroute.

What it is

When a user says they cannot get online, start with what the client thinks its network settings are, then test outward from the client.

For wired clients the three questions are: is there a link, is the IP configuration right, and can the client reach the gateway, a remote address and a name. Wireless clients add a fourth: did the client associate and authenticate with the right security settings.

Windows, macOS and Linux have different commands, but the ideas are identical.

How it works

Check the link, read the IP settings, then test reachability one hop at a time.

Linkcable or Wi Fi associationIP settingsaddress, mask, gateway, DNSGatewaypingRemote IPpingNameDNS lookup

Reading the IP configuration

TaskWindowsmacOSLinux
Addressesipconfig /allifconfig or networksetup -getinfo Wi-Fiip address show
Default gatewayipconfignetworksetup -getinfo Wi-Fiip route show
DNS serversipconfig /allscutil --dnsresolvectl status
Renew DHCP leaseipconfig /release then /renewRenew in Network settingsNetwork manager restart or dhclient
Flush DNS cacheipconfig /flushdnssudo dscacheutil -flushcache then sudo killall -HUP mDNSResponderresolvectl flush-caches

networksetup -listallnetworkservices lists the service names on a Mac. On Linux the default gateway is the line that begins with default.

A healthy Windows client looks like this:

C:\> ipconfig
Ethernet adapter Ethernet:
   IPv4 Address. . . . . . . . . . . : 192.168.10.50
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.10.1

What a faulty configuration looks like

What you seeMeaning
Address starts with 169.254DHCP failed, check the DHCP path
Media disconnectedNo link: cable, port or wireless association
No default gatewayClient reaches only its own subnet
Gateway outside the client's subnetWrong gateway or wrong mask
Correct address, wrong DNS serverIP addresses work, names fail
Address correct but wrong subnet for the VLANClient plugged into the wrong VLAN, or a static address left behind

On Linux, the same fault looks like this:

$ ip address show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> ...
    inet 169.254.37.12/16 scope link

The scope link and the 169.254 range show a self-assigned address.

Testing reachability

Test outward, one hop at a time. The first step that fails shows where the problem lies.

  1. Ping the loopback 127.0.0.1 to confirm the TCP/IP stack works.
  2. Ping the client's own address.
  3. Ping the default gateway. A failure means a local link, VLAN or addressing problem.
  4. Ping a remote IP address such as 8.8.8.8. A failure here with a working gateway points past the gateway: routing, NAT or a firewall.
  5. Ping or look up a name. If step 4 works and this fails, the fault is DNS.
Loopback127.0.0.1thenOwn addressthenDefault gatewaythenRemote IP addressthenNameDNS
ToolWindowsmacOS and Linux
Pingping 8.8.8.8 (four packets)ping -c 4 8.8.8.8
Trace the pathtracert 8.8.8.8traceroute 8.8.8.8
DNS lookupnslookup example.comnslookup example.com or dig example.com
ARP tablearp -aarp -a or ip neighbor show
Test a TCP portTest-NetConnection host -Port 443 (PowerShell)nc -vz host 443
Exam tip

If a remote IP answers but a name does not, go straight to DNS. If the gateway does not answer, ignore everything beyond it.

A traceroute that stops at the first hop usually means the gateway cannot forward (or filters the probes). One that stops later shows the last router that answered, so the fault is usually on or after the next one.

Wireless clients

A wireless client must associate with the right SSID, band and security, then get an IP configuration like any other client.

Windows shows the connection details with netsh wlan show interfaces: SSID, BSSID, radio type, authentication, cipher, channel, signal and rates. On a Mac, option-click the Wi-Fi icon in the menu bar to see the channel, RSSI and security of the current network. On Linux, nmcli device wifi list shows nearby networks with channel and security, and iw dev wlan0 link shows the current connection (the interface name varies).

Wireless security parameter mismatches

The client's security settings must match the access point. A mismatch usually shows as a repeated password prompt or a failure to connect.

MismatchResult
Wrong passphraseAuthentication fails at the handshake and the client prompts again
Client supports only WPA2, network is WPA3 onlyClient cannot join, or does not see the network as joinable
Network needs 802.1X, client set to a passphrase (or the reverse)Authentication fails
Missing or untrusted certificate for 802.1XAuthentication fails
Wrong SSID, or hidden SSID not enteredClient never associates
6 GHz network on a client without WPA3 or 6 GHz supportNetwork is not usable

If the client associates and authenticates but still has no connectivity, the fault is not security. It is one of the IP configuration faults above, often a DHCP problem or the wrong VLAN on the SSID.

Weak signal causes a different symptom. The client joins and gets an address, but throughput is poor and drops out, with a signal near minus 80 dBm or worse.

Watch out

A 169.254 address on a wireless client does not prove DHCP is broken. First check that the client actually authenticated, because without that no traffic flows.

Common mistakes

Testing only with a name. A failed name could be DNS or routing. Ping an IP address as well.

Using the wrong OS command. ipconfig does not exist on Linux, and ip address does not exist on Windows.

Ignoring the gateway. A client with a valid address but a wrong gateway cannot leave its subnet.

Forgetting the DNS cache. After a DNS change, a client may keep an old answer until the cache expires or is flushed.

Blaming DHCP for a wireless authentication failure. If the client never joined, it never asked for an address.

What to remember for the exam

  • Windows: ipconfig /all, /release, /renew, /flushdns, tracert, netsh wlan show interfaces.
  • Linux: ip address show, ip route show, resolvectl status, traceroute, iw dev, nmcli.
  • macOS: ifconfig, networksetup -getinfo Wi-Fi, scutil --dns, traceroute.
  • A 169.254 address means no DHCP answer. No gateway means local only.
  • Test loopback, own address, gateway, remote IP and name, in that order.
  • Remote IP works but the name does not: DNS.
  • Wireless faults: wrong passphrase, mismatched security type, wrong SSID, missing certificate.
  • Associated but no connectivity: look at IP configuration, DHCP and VLAN.

Check yourself

  • A client has 169.254.20.5. What does that tell you and what do you check next?

    It has no DHCP answer and assigned itself an address. Check the link and VLAN, the DHCP server and any relay.

  • A client pings 8.8.8.8 successfully but cannot open a website by name. Where is the fault?

    DNS. Check the DNS server settings on the client and whether the DNS server is reachable.

  • A laptop keeps asking for the Wi-Fi password but the password is correct. What could be mismatched?

    The security type, such as a client limited to WPA2 on a WPA3-only network, or an 802.1X network where the client is set up for a passphrase.

Topic 8 of 9 in Network Infrastructure and Connectivity

Test yourself on Network Infrastructure and Connectivity

The full Cisco CCNA 200-301 v2.0 question bank has 1,242 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Cisco. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.