Jensen IT Notes
Back to blog

Networking & Homelab

Ping, Tracert, and Nslookup Explained for Beginners

June 24, 2026

A practical beginner guide to three common networking commands used in IT support troubleshooting.

Network+NetworkingTroubleshootingPingTracertNslookup

Ping, tracert, and nslookup are simple commands, but they can tell you a lot during a help desk networking ticket. They help answer three different questions: can I reach it, where does the path go, and does the name resolve?

Ping

ping tests whether a device responds over the network. It is often used to check basic connectivity.

Examples:

  • Ping the default gateway to test local network reachability.
  • Ping a known internal server to check access to a company resource.
  • Ping a public IP only if your workplace allows it.

If ping fails, it does not always mean the device is down. Firewalls may block ping.

Tracert

tracert shows the route traffic takes to reach a destination. It can help identify where traffic stops or slows down.

This is useful when a local gateway works but a remote system does not. Beginner-friendly version: tracert is like asking, “Which roads did my network traffic try to take?”

Nslookup

nslookup checks DNS name resolution. It helps you confirm whether a name like a website or internal server can be translated into an IP address.

If you can reach an IP address but not a domain name, DNS may be part of the problem.

Practical help desk example

A user says they are connected to Wi-Fi but cannot open an internal website. You might:

  1. Run ipconfig to find the gateway.
  2. Ping the gateway.
  3. Ping the internal server if allowed.
  4. Use nslookup on the internal site name.
  5. Use tracert if routing might be the issue.

Beginner Note

These commands are clues, not final answers. Cantonese-friendly: “呢啲 command 係幫你搵線索,唔係一行完就一定知道全部答案.”

Common Mistake

A common mistake is assuming failed ping always means a system is offline. Some networks block ping by design.

FAQ

Which command should I run first?

Start with ipconfig, then ping the gateway. After that, choose ping, tracert, or nslookup based on what you are testing.

Does nslookup test internet connectivity?

Not directly. It tests DNS resolution. DNS can fail even when network connectivity works.

Is tracert always easy to read?

No. Some hops may time out or hide replies. Look for patterns, not perfection.

Quick Check

Original beginner-friendly review questions — not real exam questions.

1. Easy: A user can browse some sites but not an internal hostname. Which command best tests name resolution?
A. nslookup internal hostname
B. chkdsk /r
C. shutdown /a
D. sfc /scannow

Answer: A. nslookup internal hostname.

Why: nslookup tests DNS. The other commands are for disk/system/shutdown tasks.

2. Medium: Ping to a server fails, but the server blocks ICMP by policy. What is the best conclusion?
A. Ping failure alone does not prove the server is down
B. The server is definitely offline
C. DNS must be the only issue
D. The client IP must be APIPA

Answer: A. Ping failure alone does not prove the server is down.

Why: Ping can be blocked. Other tests are needed before concluding outage.

3. Medium: Traffic reaches the local gateway but fails after the next hop. Which tool is most useful for seeing that path?
A. tracert
B. notepad
C. sfc /scannow
D. Print Management

Answer: A. tracert.

Why: tracert shows hops along the route. The other tools do not map network paths.

Keep exploring practical fixes

Browse more support notes and build a stronger troubleshooting routine.

View all posts