Provide Windows and Linux/Unix command examples for basic network troubleshooting.

Provide Windows and Linux/Unix command examples for basic network troubleshooting.

• A. Windows: ls, cd, mkdir; Linux: rg, awk.
• B. Windows: ping, ipconfig, tracert; Linux: ping, ip command, traceroute, netstat.
• C. Windows: ping; Linux: ifconfig.
• D. Windows: traceroute; Linux: tracert.

Answer: (B)

Testing basic network problems relies on commands that confirm reachability, reveal how the machine is configured, trace the path to a destination, and show current connections and routes. For Windows, ping quickly checks if a host can be reached and measures response time, while ipconfig shows the computer’s IP address, subnet mask, gateway, and DNS settings—information you need to spot misconfigurations. Tracert then maps the route to a remote host, listing each hop and its latency, which helps identify where delays or drops occur along the path. On Linux and Unix systems, ping serves the same purpose of verifying connectivity. The ip command is the modern, versatile tool to view and manage networking details like addresses and routes, replacing older utilities and giving a clear picture of how interfaces are configured. Traceroute provides a route-by-route view to the destination, just like tracert on Windows, helping pinpoint where traffic is being slowed or blocked. Netstat shows active connections, listening ports, and routing information, which is invaluable for diagnosing which services are communicating and how traffic is flowing through the machine. Together, these tools cover the core steps of basic network troubleshooting across both platforms: verify reachability, inspect configuration, trace the path, and review active connections and routes. Other options either rely on non-network tools or use outdated or mismatched commands for the operating system, making them less effective for quick, practical diagnostics.

Testing basic network problems relies on commands that confirm reachability, reveal how the machine is configured, trace the path to a destination, and show current connections and routes. For Windows, ping quickly checks if a host can be reached and measures response time, while ipconfig shows the computer’s IP address, subnet mask, gateway, and DNS settings—information you need to spot misconfigurations. Tracert then maps the route to a remote host, listing each hop and its latency, which helps identify where delays or drops occur along the path.

On Linux and Unix systems, ping serves the same purpose of verifying connectivity. The ip command is the modern, versatile tool to view and manage networking details like addresses and routes, replacing older utilities and giving a clear picture of how interfaces are configured. Traceroute provides a route-by-route view to the destination, just like tracert on Windows, helping pinpoint where traffic is being slowed or blocked. Netstat shows active connections, listening ports, and routing information, which is invaluable for diagnosing which services are communicating and how traffic is flowing through the machine.

Together, these tools cover the core steps of basic network troubleshooting across both platforms: verify reachability, inspect configuration, trace the path, and review active connections and routes. Other options either rely on non-network tools or use outdated or mismatched commands for the operating system, making them less effective for quick, practical diagnostics.