3 Network Connectivity Diagnosis Free Online FlashCards

In what order should you diagnose network connectivity?

Test outward from the network interface and local link, through IP configuration and the gateway, then toward remote destinations.

What can a down or disconnected network link indicate?

A down link can point to a loose or faulty cable, a disabled interface, or a switch-port problem.

Which IP settings should you inspect?

Check the IP address, subnet mask or prefix length, default gateway, and relevant DNS servers.

What sequence of targets can you test with ping?

Test 127.0.0.1, the device’s configured address, the gateway, and then a known remote IP.

What does a successful ping demonstrate—and what does it not establish?

It shows that ICMP echo traffic received a reply; it does not prove that a particular application or service is reachable.

How does tracert discover hops?

It sends probes with increasing TTL values; routers may reply with a time-exceeded message when a probe’s TTL expires.

What should you investigate if a remote IP responds but a named destination or application fails?

Check name resolution and the application’s specific port or service.

What does a link light not prove?

A link light does not prove that IP configuration or the routed connection is working.

Where should the configured default gateway normally be reachable?

The gateway should normally be reachable on the device’s local network.

What should you investigate if loopback or local-address tests fail?

Investigate the device’s network stack or interface configuration.

What should you check when local tests succeed but the gateway test fails?

Check the link, addressing, subnet, VLAN, and local network path.

What should you investigate when the gateway responds but a remote IP does not?

Investigate routing and intermediate network devices; compare the route trace with the expected path.