Voice Servers
Troubleshooting: How do I WinMTR, PING or Traceroute?
When reporting any network related issues (lag, people getting booted out, etc), we really need a MTR run and a PING. This needs to be run at the same time you are experiencing the issue, otherwise it may not capture the issue.
To run a PING:
You can grab WinMTR (the Windows version of MTR) from here: http://winmtr.sourceforge.net
It will be best to let this run continuously in the background while you are trying to catch a Ping Spike or Lag issue. If it's run continuously, there is a greater chance of WinMTR catching the spike/lag as it's happening. It should not cause any more lag itself as it's just an automated traceroute/ping utility, but only run this when you need to trace to a host to look for why you are getting lag or ping spikes. Let it run for quite some time, so you have experienced the issue a few times. Running for 5 minutes (300 packets) is typically a good sample. Running for less than 120 packets (2 minutes) is not a good enough sample.
--------------------------------------------------------------------------------
If you are somehow unable to run an MTR, the following will provide some information but may not be enough to further assist in debugging a lag issue that may be associated with a router on your route to the server. A WinMTR is the best utility to use for this.
To run a TRACERT:
To run a PING:
- Open a Windows Command Prompt (known as a DOS Prompt in Windows 95/98/98SE/ME).
- Type the following command (substitute the Hostname or IP Address you want to ping to for the word HOSTNAME below): ping HOSTNAME
- Copy/Paste the output in an email to us. To Copy, you may need to right-click in the window and select "Mark" to be able to highlight the text.
You can grab WinMTR (the Windows version of MTR) from here: http://winmtr.sourceforge.net
It will be best to let this run continuously in the background while you are trying to catch a Ping Spike or Lag issue. If it's run continuously, there is a greater chance of WinMTR catching the spike/lag as it's happening. It should not cause any more lag itself as it's just an automated traceroute/ping utility, but only run this when you need to trace to a host to look for why you are getting lag or ping spikes. Let it run for quite some time, so you have experienced the issue a few times. Running for 5 minutes (300 packets) is typically a good sample. Running for less than 120 packets (2 minutes) is not a good enough sample.
- Unzip the archive
- Double-click the WinMTR.exe file
- In the "Host" field, type in the Hostname or IP Address of the server you need to trace to
- Press the "Start" button
- Since this is being run continuously (as described above) to catch the Lag / Ping Spike, press the "Stop" button after your Lag or Ping Spike has occurred.
- Press the "Copy Text to clipboard" button
- Paste the text, and supply your IP Address (that your ISP gave you), into a Support Ticket. You can open a support ticket by logging into Client Care or sending an email to support@guildlaunch.com.
--------------------------------------------------------------------------------
If you are somehow unable to run an MTR, the following will provide some information but may not be enough to further assist in debugging a lag issue that may be associated with a router on your route to the server. A WinMTR is the best utility to use for this.
To run a TRACERT:
- Open a Windows Command Prompt (known as a DOS Prompt in Windows 95/98/98SE/ME).
- Type the following command (substitute the Hostname or IP Address you want to tracert to for the word HOSTNAME below): tracert HOSTNAME
- Run that command at least 5 times in a row.
- Copy all of the output and paste it into an email to us. To Copy, you may need to right-click in the window and select "Mark" to be able to highlight the text.
Last edited by GL_Support on Fri Oct 07, 2011 12:33 pm; edited 3 times in total
