Skip to content
FORGENO ADS GAMESUnlock all $8

IT Support & Networks · Unit 7 of 8

Unit 7: Network troubleshooting tools

ipconfig, ping, tracert and nslookup, and a bottom-up method for finding exactly where a connection breaks.

Opens the first lesson of this unit in IT Support & Networks. Every lesson is open from the start.

Lesson 1: ipconfig: what address do I have?

Goal: Read a computer's network settings from the command line.

Command-line tools are the stethoscope of network troubleshooting. They are fast, precise and the same on every computer. On Windows, open Command Prompt or PowerShell; on a Mac or Linux, open Terminal.

ipconfig (Windows) shows your network settings. On a Mac, ifconfig or the Network settings show the same information; on Linux, ip addr.

C:\> ipconfig

Wireless LAN adapter Wi-Fi:
   IPv4 Address. . . . . . . . . . . : 192.168.1.42
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

What to look for:

  • An address like 192.168.1.42 means DHCP worked.
  • An address starting 169.254. means DHCP failed: the device never got a proper address.
  • No default gateway means the device does not know how to leave the local network.
  • ipconfig /all adds the DNS servers and the MAC address.
  • ipconfig /release then ipconfig /renew asks DHCP for a fresh address; ipconfig /flushdns clears the DNS cache.

Hands-on lab in the room: Command line simulator. A simulated command line. Try ipconfig and ipconfig /all. Type help to see every command.

ipconfig
A Windows command that shows a computer's IP address, subnet mask, gateway and more.
Command line
A text interface where you type commands, such as Command Prompt, PowerShell or Terminal.

Remember: ipconfig first: a 169.254 address or a missing gateway tells you the problem is local.

Lesson 2: ping: can I reach it?

Goal: Use ping to test reachability and read latency and packet loss.

ping sends small test messages to an address and times the replies. It answers two questions: can I reach it, and how quickly?

C:\> ping 192.168.1.1

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
  • Replies with low times (a few ms on a local network, tens of ms to the internet): the path works.
  • "Request timed out" or "Destination host unreachable": no reply. The device may be off, disconnected, or blocking pings.
  • Some lost packets, or times jumping around wildly, point to an unstable connection, often weak Wi-Fi.

Ping in a smart order: first your gateway (the router). If that works, ping an internet address such as 1.1.1.1 or 8.8.8.8, which are well-known public DNS servers that usually answer pings. Then ping a name such as example.com. Where the chain breaks tells you where the problem is.

Watch out: Some servers are set to ignore pings on purpose. A failed ping to one website is a clue, not proof that it is down. Try another tool or address to confirm.

ping
A tool that sends test messages to an address and measures whether and how fast replies come back.
Packet loss
The share of test messages that never got a reply. Any regular loss points to a problem.

Remember: Ping the gateway, then an internet IP, then a name. Where it breaks is where to look.

Lesson 3: tracert and nslookup: where and what?

Goal: Trace a route and query DNS directly.

tracert (Windows) or traceroute (Mac and Linux) shows each hop, each router, that packets pass through on the way to a destination, with the time to each one.

C:\> tracert example.com
  1     3 ms   192.168.1.1        (your router)
  2    11 ms   10.42.0.1          (your ISP)
  3    14 ms   203.0.113.9
  4     *      Request timed out.
  5    25 ms   203.0.113.10       (destination)

If the times jump sharply at one hop and stay high after it, that hop may be where the slowdown is. A single line of * in the middle, while later hops still answer, is normal: some routers simply do not reply to trace requests.

nslookup asks DNS directly for a name's address:

C:\> nslookup example.com
Server:  dns.home.example
Address: 192.168.1.1

Name:    example.com
Address: 203.0.113.10

If nslookup fails or times out while pinging an IP address works, DNS is the problem. Fixes include restarting the router, flushing the DNS cache, or temporarily using a different DNS server.

tracert / traceroute
Shows each router (hop) packets pass through on the way to a destination.
Hop
One router along the path between you and a destination.
nslookup
A tool that asks a DNS server for the address of a name.

Remember: tracert shows where along the path things slow down; nslookup tests DNS directly.

Lesson 4: Bottom-up: find exactly where it breaks

Goal: Use a layered, bottom-up checklist to locate any network fault.

Networks are built in layers, each depending on the one below. Professionals use models like OSI and TCP/IP to describe them, but the practical version is a bottom-up checklist. Start at the bottom, and the first thing that fails is your problem:

CheckHowIf it fails
1. Physical linkCable plugged in? Wi-Fi connected? Link lights on?Fix the cable, port or Wi-Fi connection
2. Addressipconfig: a proper address and gateway?169.254 or no gateway: DHCP or local network problem
3. Local networkping the gatewayProblem between the device and the router
4. Internetping 1.1.1.1Problem at the router, modem or ISP
5. Namesnslookup example.com or ping example.comDNS problem
6. ApplicationDoes the website or app itself work? Try another browser or deviceThat one site or app has an issue

Hands-on lab in the room: Command line simulator. Two mystery computers. Use the commands to work out exactly what is broken on each.

This approach turns "the internet is broken" into a precise diagnosis like "DNS is failing on this laptop", which tells you exactly what to fix, and gives you the facts for a strong ticket note or escalation.

Bottom-up troubleshooting
Checking from the physical connection upward until the first failing layer is found.
OSI model
A seven-layer model describing how network communication is organized, from physical cables up to applications.

Remember: Link, address, gateway, internet IP, names, app. The first failure is your answer.

Practise it in IT Support & Networks

Each lesson ends with two or three questions that check you can use the idea, not just recognise it. Wrong answers explain why and come back in Review. The unit ends with a 6-question quiz; pass it with 80% or more to master the unit. Hands-on lab: Command line simulator.

Every lesson is free: no ads, no lives and no paywall.