Ping checks for the connectivity between your computer and DataQuest servers, while tracert/traceroute specifies the route between them. Here’s how you can run these commands:
Windows XP, 2000, or 7
- Click the Start button
- On the Start menu, click Run....
- If you do not see the Run command in Windows 7, enter ‘cmd’ in the Search bar
- Type the following command and press enter: ping yourdomainname.com.
- Next, type the command: tracert yourdomainname.com.
- Press Windows+X on to open the WinX Menu.
- Right-click on Command Prompt and select Run as Administrator.
- Type the following command and press Enter: ping yourdomainname.com
If the command was successful, you will see ping statistics such as packet sent, received and lost as well as approximate time taken.
- Next, type the command: tracert yourdomainname.com
If the command was successful you will see the message ‘Trace complete’.
1. Press Windows + R.
2. Type cmd and press enter.
3. In the command prompt, type: tracert hostname
where hostname is the name of the server connection you are testing (that is your domain name)
4. To ping your website, please type PING space domain name (hostename).
5. Please press Enter and you can see the result.
How Do I Run a Traceroute on a Mac?
Traceroute is a utility that records the route between your computer and your server. It also displays the amount of time each hop takes. If you cannot reach your site, a traceroute will help us determine the issue.
To run traceroute on a Mac, follow these steps:
These steps were created using Mac OS X. For earlier operating systems, you will need to download and use a third party program.
1) From your hard-drive, open the Applications folder, and click to open the Utilities folder.
2) Double-click Terminal.
3) Type traceroute followed by your domain name and hit Enter.
Traceroute will tell you how many routers your packets travel through, and how long it takes for them to travel between routers. If the routers have DNS entries, traceroute will list the names of the routers as well as their network affiliation and geographic location.
4) Check for times between hops that are greater than 200 ms or that return asterisks *** which indicate that your request has timed out.