A network technician is troubleshooting a client workstation that cannot access an internal web portal by its fully qualified domain name (FQDN). Following a standard bottom-up troubleshooting workflow to isolate network issues from local network configuration to name resolution, place the following command-line steps in the correct logical diagnostic sequence.
- 1Run ipconfig /all to verify the client machine's local IP address, subnet mask, default gateway, and primary DNS server configuration.
- 2Run ping 192.168.1.1 to confirm Layer 3 network connectivity from the client to its local default gateway.
- 3Run ping 10.0.5.25 to verify ICMP reachability directly to the target web server's IP address, bypassing DNS.
- 4Run nslookup portal.lab.internal to test whether the configured DNS server correctly resolves the host name to an IP address.
Answer
The correct sequence begins with checking local interface settings using ipconfig /all, testing local subnet routing using ping to the default gateway, testing remote host IP reachability using ping to the target IP, and finally diagnosing DNS name resolution using nslookup.
The logical sequence follows standard CompTIA network troubleshooting: first, check local host configuration using ipconfig /all; second, verify local subnet network reachability by pinging the default gateway IP; third, verify end-to-end network path reachability by pinging the destination server's IP address directly; fourth, test domain name lookup functionality using nslookup to confirm FQDN-to-IP mapping.
Step-by-Step Solution
Key Concept
Command-Line Troubleshooting Methodology & Tool Selection