Follow

Test procedures for sites reporting slow or bad connections.

New: I've created a batch file that will do this automatically for Windows machines:

 

Download this file to the clients computer, preferably onto their desktop or into their My Documents folder, and run it. It will run all the tests below and open a window for you to grab the output files:

This thing

 

As a note, this doesn't do much in the way of error checking, so if you do get an error, you'll need to do the stuff below.

----

In order to do this, we need to run several commands and capture the output.

Through an LMI session into the client's computer, launch the command prompt (Start -> Run & type cmd for windows, launch a terminal for Mac)

When you run these commands, there will be nothing output to the screen, since it's saving it to a text file, when each command completes, it will just move the cursor to a new line with the command prompt (C:\users\*****>)

tracert i.gomjfreeway.com >> .\traceroutes.txt

tracert i2.gomjfreeway.com >> .\traceroutes.txt

tracert i4.gomjfreeway.com >> .\traceroutes.txt

tracert i5.gomjfreeway.com >> .\traceroutes.txt

 

(For Mac machines, change tracert to traceroute and omit the path, so you have >> traceroutes.txt at the end)

 

 

ping -n 100 -l 1500 i.gomjfreeway.com >> .\ping1500.txt

ping -n 100 -l 1500 i2.gomjfreeway.com >> .\ping1500.txt

ping -n 100 -l 1500 i4.gomjfreeway.com >> .\ping1500.txt

ping -n 100 -l 1500 i5.gomjfreeway.com >> .\ping1500.txt

 

ping -n 100 -l 8000 i.gomjfreeway.com >> .\ping8000.txt

ping -n 100 -l 8000 i2.gomjfreeway.com >> .\ping8000.txt

ping -n 100 -l 8000 i4.gomjfreeway.com >> .\ping8000.txt

ping -n 100 -l 8000 i5.gomjfreeway.com >> .\ping8000.txt

 

ping -n 100 -l 25000 i.gomjfreeway.com >> .\ping25000.txt

ping -n 100 -l 25000 i2.gomjfreeway.com >> .\ping25000.txt

ping -n 100 -l 25000 i4.gomjfreeway.com >> .\ping25000.txt

ping -n 100 -l 25000 i5.gomjfreeway.com >> .\ping25000.txt

 

(On a Mac, change the ping commands "ping -c 100 -s 1500 >> ping####.txt" - with the appropriate numbers for each test line. Same rules as above with the path (>> ping1500.txt))

Once all of these are complete (this will take quite a while, expect around 20 minutes or so), have the customer attach all four of the text files on their desktop to an email and have them send it to you.

 

Once you get them, please attach all of them to an email that also contains the company name of the client experiencing the issues, their MJ Freeway URL, their physical address, what ISP they're with and, if possible, their ISP customer ID number and email it to Jason and Ike.

 

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

Comments