connectivity – Internetblog.org.uk https://www.internetblog.org.uk Web hosting, Domain names, Dedicated servers Fri, 29 Jan 2016 11:05:52 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.5 https://www.internetblog.org.uk/files/2016/01/cropped-favico-32x32.png connectivity – Internetblog.org.uk https://www.internetblog.org.uk 32 32 Troubleshooting website connectivity issues https://www.internetblog.org.uk/post/1170/troubleshooting-website-connectivity-issues/ Mon, 05 Apr 2010 21:31:50 +0000 http://www.internetblog.org.uk/post/1170/troubleshooting-website-connectivity-issues/ Traceroute command
Nothing is worse than waking up and finding out your website is down. The immediate reaction is to grab the phone and drop an anger bomb on your web hosting provider. While it certainly could be a problem with your server, there are a few things to check before going ballistic on the IT guys.

1. Check your own network connectivity. If your website (or the email associated with it) was the first sign of a problem, you might find that other websites are down as well. If this is the case go through normal ISP connectivity troubleshooting.

2. Check your web host’s website for any connection status notices.

3. Try to connect to your server via FTP and/or SSH.

4. Try a traceroute to see if there are connection hiccups along the way.

5. Use a remote service to run a traceroute. It may be a connection problem only for your service provider. You can also check the Internet health.

6. Contact your web host.

You can do all of these checks in less than 5 minutes, so do not worry about wasting time when you could have been tearing into your web host on the phone. With the right tools at your disposal, you can be up and running again in a matter of minutes.

Photo Source: Wikimedia Commons

]]> Monitoring Connectivity with Traceroute https://www.internetblog.org.uk/post/682/monitoring-connectivity-with-traceroute/ Mon, 16 Nov 2009 22:33:23 +0000 http://www.internetblog.org.uk/post/682/monitoring-connectivity-with-traceroute/ traceroute
In the hopefully unlikely event that you are unable to access your website, the first thing you should check is your own network connection. You may find that you cannot access any websites. If that is not the case, there is a network problem between your computer and your server.

Normally, your computer must connect through several different connected locations before reaching the destination of a website. With traceroute, you can follow that path to see if there is a problem along the way that might explain connectivity problems. In Windows, run traceroute by opening a command window. Click “Run” and type “cmd”. Then type the command:

tracert domain.com

In Linux and Mac OS X you basically follow the same procedure in a terminal window but type the command as:

traceroute domain.com

There are two things to look for: 1. Sites that take a long time to connect (measured in milliseconds), and 2. Sites that do not connect at all (usually displayed as an *).

Photo Source: Flickr

]]>