Email

info@ssh-assistant.com

Have any questions? Email us!

Kontakt
View Categories

Common Troubleshooting Scenarios

Network Diagnostics isn’t just about running commands—it’s about knowing how to interpret them and apply them to real-world problems. Here are some common scenarios and step-by-step solutions.

Website Won’t Load #

Step 1: Ping the Domain

bash

ping example.com
  • ✅ If successful → DNS and server are fine, check your browser.
  • ❌ If fails → Continue troubleshooting.

Step 2: Ping a Known Working Site

bash

ping 8.8.8.8
  • ✅ If successful → Your internet works, issue is with the specific site.
  • ❌ If fails → Your internet connection has problems.

Step 3: Try DNS Lookup

bash

nslookup example.com
  • ✅ If returns IP → DNS works.
  • ❌ If fails → DNS problem, try a different DNS server.

Step 4: If DNS Works But Ping Fails

  • The server might be down.
  • The server might be blocking ping (ICMP).
  • A firewall might be blocking the connection.

🐢 Slow Website #

Step 1: Ping the Website

bash

ping example.com
  • Check average response time.
  • Look for packet loss.
  • High times or loss = connection issues.

Step 2: Use Traceroute

bash

traceroute example.com
  • Identify where delays occur.
  • Early hops → Your network/ISP.
  • Late hops → Destination network.

Step 3: Compare with Other Sites

  • If all sites are slow → Problem with your connection.
  • If only one site is slow → Problem with that site.

DNS Issues #

Problem: nslookup fails

Solution 1: Try Different DNS Server

bash

nslookup example.com 8.8.8.8
  • ✅ If works with 8.8.8.8 → Your DNS server has issues.
  • Change your DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).

Solution 2: Wrong IP Returned

  • Use dig to check TTL values.
  • DNS cache may be stale.
  • Flush DNS cache or wait for TTL to expire.

Problem: DNS is slow

Solution:

  • Compare query times with different DNS servers.
  • Example:bashdig @8.8.8.8 example.com dig example.com
  • Switch to a faster DNS server if needed.