A Windows 11 client workstation is unable to access an internal corporate web application by its domain name. A tier 2 support technician needs to isolate the root cause by following a systematic bottom-up network diagnostic methodology using standard Windows command-line tools. Place the diagnostic actions in the correct logical sequence, starting from verifying the local system protocol stack up to testing domain name resolution.
- 1Execute 'ping 127.0.0.1' to confirm the local TCP/IP protocol stack is initialized and functioning.
- 2Execute 'ping 192.168.1.105' (the workstation's assigned IP) to verify the network interface card adapter software and driver response.
- 3Execute 'ping 192.168.1.1' to test connectivity to the local subnet default gateway.
- 4Execute 'ping 10.20.4.50' (the target server's IP address) to determine if IP routing across internal subnets is functioning.
- 5Execute 'nslookup intranet.company.local' to check if DNS servers can successfully resolve the fully qualified domain name.
Answer
The correct sequence begins with testing the local loopback address (ping 127.0.0.1), followed by testing the local adapter IP address, pinging the local default gateway, pinging the destination server's IP address directly, and finally testing DNS name resolution using nslookup.
Systematic bottom-up troubleshooting requires testing local host components before moving outward across network boundaries. The sequence starts internally with the loopback adapter (127.0.0.1), progresses to the local assigned IP, verifies the local default gateway, checks IP routing to the destination IP address, and concludes by validating DNS host name resolution using nslookup.
Step-by-Step Solution
Key Concept
Bottom-up TCP/IP network troubleshooting methodology on Windows clients