Free course · Lesson 3 of 5
Basic Troubleshooting: Ping, DNS & Connectivity Checks
In this lesson you will
- Use the ping ladder
- Recognise DHCP and DNS faults
A few simple commands and a logical process solve most everyday connectivity problems without needing to guess randomly.
pingtests whether one device can reach another (e.g.ping 8.8.8.8tests general internet reachability).- If you can ping an IP address (like
8.8.8.8) but not a website name, the problem is likely DNS (the service that turns website names into IP addresses). - Isolation testing: Try another device on the same network — if it also fails, the problem is the network; if only one device fails, the problem is that device.
- Restarting the router (unplug 10 seconds, plug back in) resolves a large share of everyday connectivity issues.
Practical Skill: Practice the diagnostic flow below on a real "no internet" scenario, narrating each step and what it tells you.
=== "NO INTERNET" DIAGNOSTIC FLOW === 1. ping 127.0.0.1 (tests your own device's network stack)2. ping 192.168.1.1 (tests reaching your router — use your actual gateway IP from ipconfig)3. ping 8.8.8.8 (tests reaching the internet by IP)4. ping google.com (tests DNS — turning names into IPs) Result interpretation: Step 1 fails -> problem is your own device's network settings Step 2 fails -> problem is between your device and the router Step 3 fails -> problem is your router's internet connection Step 4 fails but Step 3 works -> DNS problem specifically All succeed -> the specific website/app you're testing may be down, not your network
Practice exercise
Ping your loopback address, gateway, 8.8.8.8 and example.com, and explain what each result tells you.
Key takeaways
- Test outwards from your own device
- A 169.254 address means DHCP failed
- Working IP but failing names means DNS
Free self-study lesson — no certificate. For the full instructor-led program, see registration options.