Question

Difficulty: EasyWired and Wireless Network Issues

A network technician is troubleshooting a desktop computer that has lost network access. Following a bottom-up (physical to application layer) troubleshooting approach, in what order should the technician perform the diagnostic steps?

  1. 1Inspect the Ethernet cable connection and verify the status of the network interface card (NIC) link light.
  2. 2Run the ipconfig tool to verify if the workstation has received a valid IP address or an APIPA address.
  3. 3Execute a ping command to the local default gateway to confirm connectivity within the local subnet.
  4. 4Use the nslookup command to test DNS hostname resolution for external web addresses.

Answer

The correct order follows a bottom-up diagnostic sequence: first verify the physical link light and cable, next check the workstation IP configuration with ipconfig, then ping the default gateway to test local network access, and finally run nslookup to verify DNS name resolution.
The bottom-up OSI troubleshooting model moves sequentially from Layer 1 (Physical) to Layer 7 (Application). Checking the physical cable and NIC link light comes first. Once physical connection is confirmed, verifying the local IP configuration (Layer 3) is next. Testing ICMP connectivity to the default gateway ensures local communication works before finally checking DNS hostname resolution at the application layer.

Step-by-Step Solution

1
Verify physical layer connectivity.
Ensure the physical cable is securely attached and the NIC link light indicates an active connection.
Troubleshooting should start at the physical layer to confirm hardware connectivity before checking software settings.
2
Check protocol layer configuration.
Determine whether the host has a valid IPv4 address assigned via DHCP or a self-assigned 169.254.x.x APIPA address.
Verifying IP addressing ensures the device has valid network configuration settings.
3
Test local network routing.
Confirm whether ICMP packets can reach the default gateway router.
Pinging the gateway verifies local link integrity and subnet routing capabilities.
4
Test application service resolution.
Confirm whether fully qualified domain names (FQDNs) can be resolved to IP addresses.
DNS resolution represents high-level service functionality needed for web browsing and domain communication.

Key Concept

Bottom-Up Network Troubleshooting
Rate this question