Question

Difficulty: MediumWired and Wireless Network Issues

A desktop computer in a corporate office suddenly loses access to the company intranet after a workstation relocate. A technician is dispatched to troubleshoot the issue using a standard OSI bottom-up approach. In what sequence should the technician perform the following diagnostic steps?

  1. 1Inspect the physical RJ-45 cable connections and check the link LED lights on the Network Interface Card (NIC).
  2. 2Execute the ipconfig /all command to verify whether the host has received a valid IP address or an APIPA address.
  3. 3Ping the local default gateway address to confirm local network segment communication.
  4. 4Perform an nslookup query to verify domain name resolution for the intranet server.

Answer

The correct troubleshooting sequence from first to last is: 1) Inspect the physical RJ-45 cable connections and link LED lights, 2) Execute ipconfig /all to verify IP configuration, 3) Ping the local default gateway address, 4) Perform an nslookup query to test domain name resolution.
Following the standard bottom-up troubleshooting methodology, the technician begins at Layer 1 by physically checking cable connections and NIC status LEDs. Next, at Layer 2/3, local IP addressing is checked with ipconfig /all. Third, Layer 3 routing reachability is verified by pinging the default gateway. Finally, higher-layer services such as DNS resolution are tested with nslookup.

Step-by-Step Solution

1
Verify Physical Connectivity (Layer 1)
Ensure physical cables are securely seated and link LEDs indicate active hardware signal.
Bottom-up troubleshooting mandates confirming physical Layer 1 media before testing software or network protocols.
2
Verify Logical IP Configuration (Layer 2/3)
Determine whether the NIC has a valid DHCP configuration or a 169.254.x.x APIPA address.
Before sending network traffic, the host must possess a properly assigned IP address and subnet mask.
3
Test Local Gateway Reachability (Layer 3)
Confirm ICMP echoes return successfully from the default gateway.
Pinging the default gateway isolates whether the issue is local to the subnet or further up the routing path.
4
Test Name Resolution (Layer 7 / DNS)
Verify that domain names resolve correctly to destination IP addresses.
Testing DNS name resolution with nslookup confirms high-level application service accessibility.

Key Concept

OSI Model Bottom-Up Network Troubleshooting Sequence
Estimated Time:1m 30s
Rate this question