Table of Contents
1. Why is a WinMTR Report Useful
2. How to Operate the WinMTR Tool
3. How to Read the Results of a WinMTR Report
This article describes the purpose and function of the Network Diagnostic Tool WinMTR.
Why is a WinMTR Report Useful
When dealing with player's network issues it is useful to know what you are dealing with. Is it a bad routing, peering, where is package loss to be located and how may the dynamic between these factors influence each other.
WinMTR provides some indications for network issues, but some interpretation is needed when reviewing the data which contains ping values of each network node on the assigned route.
How to Operate the WinMTR Tool
The handling of this tool is fairly straight forward.
- Download the WinMTR.exe
- Start the file
- Insert the desired IP into the Host field
- Press Start
- Press Stop to end the diagnostic process (the longer you wait for the more average the data becomes. It is useful to let the tool to be run in the background for a few minutes)
The results can be saved as .txt or .html file and easily shared via ticket or email.
How to Read the Results of a WinMTR Report
Now we collected some data, but what do we see?
First, let's get a definition of the values we see:
- Host - This is the network-node we poked
- Loss % - The percentage of lost packets on this node
- Sent - The number of packages we sent to this node
- Recv - The number of packages we received from this node
- Best - The best ping on this node
- Avrg - The average ping from this node during the test
- Wrst - The worst ping on this node
- Last - The last ping result during this test
Now that we got the terminology, let's get on it!
This is an average looking WinMTR report:
1. "No response from host" - This shows up on a regular basis but is nothing to worry about. It simply means that the network node doesn't reply to our trace-route packages. You can ignore these.
2. Here you see package loss as a percentage value. Interesting is only the first node and the last. Everything in-between can be ignored as long as you don't see a steady increase or consistent package loss through all the nodes.
3. Everything we sent we also receive. This ratio should be 1:1 otherwise something goes wrong on the way to our destination node.
4. This column interesting to identify lag-spikes. The average ping to the left may seem ok, but to have a huge spike might result in a disconnect or lag.