A network technician is troubleshooting a wired desktop client that has completely lost network access. Sequence the following diagnostic and troubleshooting steps according to the standard bottom-up OSI model methodology.
- 1Inspect the Ethernet cable connection and check the physical network interface card (NIC) LED link lights.
- 2Run `ipconfig /all` at the command prompt to inspect the host's current IP address assignment, subnet mask, and DHCP status.
- 3Execute a ping command to the local default gateway's IP address.
- 4Execute a ping command using a fully qualified domain name (FQDN) such as `ping www.comptia.org`.
Answer
The correct troubleshooting sequence follows the standard bottom-up approach: first inspect physical Ethernet cables and NIC link lights, second execute `ipconfig /all` to check IP addressing, third ping the local default gateway, and fourth ping an external FQDN to test DNS resolution.
Following the standard bottom-up OSI troubleshooting approach requires inspecting physical layer components (cables and link status lights) first, verifying local IP configuration settings (`ipconfig`), confirming local gateway reachability (`ping gateway`), and lastly testing higher-level services like DNS name resolution (`ping FQDN`).
Step-by-Step Solution
Key Concept
Bottom-up network troubleshooting methodology for wired network issues.