Ann, an internal user, has been accessing an internal SaaS solution on a different subnet for the last several months. When Ann tries to connect to the application today, she receives an error…

`ipconfig` or `ifconfig` are used to display a device's network configuration (IP address, subnet mask, gateway, DNS servers). While useful for verifying client-side network settings, they do not test connectivity to a remote resource, nor do they help identify if the problem lies between the client and the server.

`ping` is the best first step to determine if there is basic network connectivity and if the hostname of the SaaS solution resolves to an IP address that is reachable from Ann's machine. The error "resource cannot be found" indicates a potential DNS or network reachability issue, which `ping` can quickly identify.

`netstat` displays active network connections, routing tables, and network interface statistics on the local machine. It can show if a connection is established but won't help diagnose why a remote resource "cannot be found" or where a connection might be failing along the path.

`tracert` or `traceroute` shows the path (hops) a packet takes to reach a destination and the latency at each hop. While useful for diagnosing routing or latency issues, it is generally performed after `ping` confirms basic reachability is absent, or to pinpoint specific network segment issues causing high latency, not just a "resource cannot be found" error.