Troubleshooting

From CTWUG Wiki
Revision as of 17:10, 12 February 2017 by Spin (talk | contribs) (Establish if your pc can connect to your destination server's address)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Before you go off asking an admin for help, why don't you take the time and try and learn something today. You might even be able to sort your own problem out, with the help of this guide.

You need to learn 2 commands: ping and tracert
To get access to these commands, Click Start and in the Search box (Win7 & Windows Vista) type cmd and press enter.
On Windows XP Click Start and in the Run box, type cmd and press Enter.
You will be presented with the Command Prompt box.
Prompt.png

The recommended steps for troubleshooting why you can't access the service that you are trying to connect to is this:

Establish if you are able to connect to your own routerboard

Open your Command Prompt (as explained above) and ping your routerboard (RB) by typing the command as follows:

ping ip.of.your.rb -- It should be and ip looking similar to 172.18.20.22

ping 172.18.20.22

If you are able to ping your RB, it should look like this. Go to next step

Pinging 172.18.20.22 with 32 bytes of data:
Reply from 172.18.20.22: bytes=32 time<1ms TTL=128
Reply from 172.18.20.22: bytes=32 time<1ms TTL=128
Reply from 172.18.20.22: bytes=32 time<1ms TTL=128
Reply from 172.18.20.22: bytes=32 time<1ms TTL=128
Ping statistics for 172.18.20.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


If your are NOT able to ping your RB, it will look something like this.Troubleshoot this problem

Pinging 172.18.20.22 with 32 bytes of data:
Reply from 172.18.20.21: Destination host unreachable.
Reply from 172.18.20.21: Destination host unreachable.
Reply from 172.18.20.21: Destination host unreachable.
Reply from 172.18.20.21: Destination host unreachable.
Ping statistics for 172.18.20.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Establish if your pc can connect to your highsite

Open your Command Prompt (as explained above) and ping the ip address of the highsite that you are connecting to. (This IP should have been given to you by the admin that connected you to the wug. ping ip.of.your.highsite -- It should be and ip looking similar to 172.18.20.254

ping 172.18.20.254

If you are able to ping your RB, it should look like this. Go to next step

Pinging 172.18.20.254 with 32 bytes of data:
Reply from 172.18.20.254: bytes=32 time<1ms TTL=128
Reply from 172.18.20.254: bytes=32 time<1ms TTL=128
Reply from 172.18.20.254: bytes=32 time<1ms TTL=128
Reply from 172.18.20.254: bytes=32 time<1ms TTL=128
Ping statistics for 172.18.20.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


If your are NOT able to ping your Highsite, it will look something like this.Troubleshoot this problem

Pinging 172.18.20.254 with 32 bytes of data:
Reply from 172.18.20.21: Destination host unreachable.
Reply from 172.18.20.21: Destination host unreachable.
Reply from 172.18.20.21: Destination host unreachable.
Reply from 172.18.20.21: Destination host unreachable.
Ping statistics for 172.18.20.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Establish if your pc can connect to your destination server's address

a) Ping the server's IP

ping 172.18.240.1

If you could ping the server's IP addres, try to ping the Hostname.
If you couldn't ping the server's IP address, Troubleshoot this problem


b) Ping the server's Hostname

ping audi.ctwug.za.net

If you could ping the server's Hostname, try to access the server again or contact the admin of the server to establish if the service is working correctly.
If you couldn't ping the server's Hostname, Troubleshoot this problem

Troubleshooting Section

Can't Ping your RB

If you can't ping your RB, you have an issue on your personal network, thus there is no connection between your pc and your routerboard. Stuff to try:

  • Check all the cabling between your pc and routerboard
  • Check all network switches on your local network
  • Check if there is power to your routerboard
  • Make sure your pc's ip addresses are configured properly


Can't Ping your Highsite

If you can ping your RB, but not the highsite that you are linking into, the problems could be the following:

tracert 172.18.240.1
  • The routes on your highsite might be configured incorrectly
    • (Contact your highsite admin)

Can't Ping your Server IP

If you can ping your highsite, but not the Server you are trying to connect to, the problems could be the following:

  • The server might be off
    • Establish if other people can still ping the server's ip. In IRC #ctwug channel type the following:
bottie: ping 172.18.240.1
  • Your highsite might be missing routes to connect to the server (very unlikely)

Can't Ping your Server Hostname, but can ping the IP

If you can ping the destination server's IP, but not the hostname, the problems could be the following: