Client Connectivity Checks by Operating System
Key Takeaways
- Client checks follow the same logic across platforms: link or association, IP settings, gateway reachability, DNS, and application access.
- Windows, Linux, and macOS provide graphical settings and command-line tools for viewing adapter state and IP configuration.
- Android and iOS expose Wi-Fi, cellular, VPN, private address, and network detail settings through their system settings apps.
- A technician should document observed values and symptoms rather than making broad changes without approval.
Client Connectivity Checks
Client connectivity checks should be consistent even when operating systems look different. Start by confirming the expected access method: wired Ethernet, Wi-Fi, cellular, or VPN. Then verify that the interface is enabled and connected. Next inspect IP settings: IP address, subnet mask or prefix, default gateway, DNS servers, and whether the address came from DHCP or was manually set. Then test in layers: local link or Wi-Fi association, default gateway reachability, DNS name resolution, and the final application or website. This sequence works across Windows, Linux, macOS, Android, and iOS.
On Windows, the Settings app shows Ethernet and Wi-Fi status, known networks, adapter properties, IP assignment, DNS assignment, and proxy or VPN settings. The classic Control Panel and Device Manager can still be useful for adapter status and driver clues. At the command line, ipconfig /all shows detailed IP configuration, including DHCP, DNS, default gateway, and MAC address. ping can test reachability, tracert can show a path toward a destination, and nslookup can test DNS responses. Windows may show a network as connected but without internet if it cannot reach its connectivity test targets.
On Linux, the exact tools depend on the distribution and desktop environment. Graphical network settings usually show wired, Wi-Fi, VPN, and DNS details. Common command-line checks include ip addr for interface addresses, ip route for default gateway and routes, resolvectl status or /etc/resolv.conf for DNS details depending on the system, ping for reachability, tracepath or traceroute for path testing, and nmcli on NetworkManager-based systems. Linux interface names may look like eth0, ens33, enp0s3, or wlan0, so match the name to the active adapter.
On macOS, System Settings shows Wi-Fi, Ethernet, VPN, and network service details. The Details button for a network can show TCP/IP, DNS, proxy, hardware address, and privacy settings such as private Wi-Fi address behavior. Useful terminal commands include ifconfig for interface information, netstat -rn or route -n get default for routing, scutil --dns for DNS configuration, ping for reachability, and traceroute for path testing. macOS also has Wireless Diagnostics for deeper Wi-Fi review, but basic CCST work usually focuses on association, IP settings, DNS, and reachability.
On Android, Settings usually groups Wi-Fi and mobile data under Network and Internet, Connections, or a vendor-specific name. A technician can check whether Wi-Fi is on, which SSID is connected, signal strength, IP address details, private DNS, VPN status, airplane mode, hotspot or tethering status, and whether mobile data is enabled. Some Android devices randomize MAC addresses per Wi-Fi network. If a corporate network uses MAC-based controls, confirm whether the device is using a randomized or device MAC according to site policy.
On iOS and iPadOS, Wi-Fi settings show the connected SSID, IP address details, router, DNS, private Wi-Fi address, low data mode, and HTTP proxy settings. Cellular settings show mobile data status, roaming, SIM or eSIM lines, personal hotspot, and app-specific cellular permissions. VPN and device management profiles can alter routing, DNS, and certificate trust. A user may be connected to Wi-Fi but blocked by a captive portal, wrong password, expired certificate, or management policy.
Across all platforms, avoid changing many settings at once. Capture the current state first, especially static IP, DNS, proxy, VPN, and managed profile settings. If DHCP is expected, a self-assigned address, missing gateway, or DNS value outside site standards is important evidence. If the endpoint can ping the gateway but cannot resolve names, investigate DNS. If names resolve but one application fails, collect the application error and destination. The best CCST technician makes the next support step obvious by recording accurate observations.
Study Checkpoint
- Topic: Client Connectivity Checks by Operating System.
- Verify the official Cisco concept before memorizing a shortcut.
- Practice the technician action: observe, document, test, fix when supported, or escalate.
Which Windows command shows detailed IP configuration, including DNS servers and default gateway?
Which Linux command is commonly used to view interface IP addresses?
Why should a technician check private or randomized MAC address settings on Android or iOS?