Dedicated Server: Network Analysis with WinMTR/MTR for Troubleshooting

Learn how to effectively detect network problems by analyzing forward and return paths – improve your diagnosis accuracy for latency and packet loss → Learn more now

10 November 202614 min read0 Views0 helpful

Introduction

Network issues can be really frustrating and are not part of everyday life. But when they do occur, it's important to quickly and efficiently find the cause to solve the problem. You can analyze detailed information about network problems very well with the WinMTR (Windows) or MTR (Linux/Mac OS) app.

WinMTR/MTR is a network diagnostic tool that combines ping and traceroute. It allows you to analyze both the forward path (Client → Server) and the return path (Server → Client) precisely by tracking the route of data packets in both directions. Important information such as latency and packet loss is recorded, which is crucial for accurate diagnosis and resolution of network problems.

Forward path (Client → Server): A report for the forward path is helpful when issues like connection drops, slow connections, or difficulties establishing a connection occur. The analysis helps identify possible problems on the way from the client to the server, such as network congestion, packet loss, or faulty routes.

Return path (Server → Client): A report for the return path only makes sense if a stable and functioning connection on the forward path has been confirmed. The return path report becomes especially relevant if the forward path shows no problems but slow server responses, delayed loading times, or incomplete data transfers still occur.

In short: If you notice network problems, you should first analyze the forward path (Client → Server). If the forward path shows no anomalies and the problems persist, check the return path (Server → Client) to find possible asymmetric issues. Asymmetric network problems occur when data packets flow smoothly in one direction but experience delays or packet loss in the other.

Dedicated Server: Network Analysis with WinMTR/MTR for Troubleshooting

Installation

Now that it's clear when reports for forward and return paths are useful, let's move on to installation on client and server sides.

Client

For the forward path, the application must be installed on the client (your computer). The following steps show you how to install the app for your operating system.

If you use a Windows PC, the network analysis is done with the WinMTR application. To install WinMTR on your computer, first download the app from the ZAP-Hosting website. After downloading, unzip the file. You will then get the executable file WinMTR.exe.

Application	Download
WinMTR	Link

On a Linux machine, you use the MTR application. To install MTR, open the terminal and run the appropriate installation command for your operating system:

Debian

Code

apt install mtr -y

Ubuntu

Code

apt install mtr -y

OpenSUSE

Code

zypper refresh
zypper install mtr

Fedora

Code

yum install mtr -y

On a Mac, you also use the MTR application. However, MTR is not pre-installed and not available in the Apple Store. You must first install Homebrew as a package manager.

Install Homebrew

Open the terminal and run this command to install Homebrew:

Code

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Install MTR

Follow the instructions in the terminal to complete the installation. Once Homebrew is running, install MTR with:

Code

brew install mtr

Server

For the return path, the application must be installed on the server. The following steps show you how to install the app for your server's operating system.

Connect to your server via SSH. To install MTR, run the appropriate command for your server OS:

Debian

Code

apt install mtr -y

Ubuntu

Code

apt install mtr -y

OpenSUSE

Code

zypper refresh
zypper install mtr

Fedora

Code

yum install mtr -y

Connect to your server via Remote Desktop Connection. To install WinMTR, download the application from the ZAP-Hosting website. After downloading, unzip the file and you will get the executable file WinMTR.exe.

Application	Download
WinMTR	Link

Creating a Report

Below is how to create a report with WinMTR/MTR – for both the forward path (Client → Server) and the return path (Server → Client).

Warning

Create report during active issues The report should be created while the problem is active and noticeable. Only then does the report provide useful information that helps with troubleshooting.

Forward path (Client → Server)

To analyze the path from your computer to the server, open the WinMTR/MTR app on your computer and follow the steps below.

Start WinMTR by double-clicking the file WinMTR.exe. Enter the IP address or hostname of the server in the Host field. Then start the analysis. Let the app run for at least one minute to collect enough data. When you have enough data, stop the analysis and save the result via Export TEXT.

Start MTR in the terminal with the following command:

Code

mtr <your-server-ip-address>

Let the app run for at least one minute to collect enough data. Then stop the analysis and save the result.

Return path (Server → Client)

To analyze the path from the server to your computer, connect to your server and follow the steps below.

Start MTR on your server in the SSH terminal with:

Code

mtr <your-client-ip-address>

Let the app run for at least one minute to collect enough data. Then stop the analysis and save the result.

Info

Don’t know your IP address or how to find it? There are various ways to determine your IP address. The quickest is via an online service like WhatIsMyIPAddress.

Enter your connection’s IP address in the Host field. Start the analysis and let the app run for at least one minute to collect enough data. Then stop the analysis and save the result via Export TEXT.

Info

Don’t know your IP address or how to find it? The quickest way is via an online service like WhatIsMyIPAddress.

Evaluating the Report

When evaluating the results, there are some important points to consider. Below we explain these in more detail and show why they are important for analysis. Keeping these aspects in mind helps you better narrow down the cause of the problem.

Packet Loss

If you see packet loss in the results, it indicates possible network problems. A small temporary loss of 1-2% is usually uncritical; higher values indicate more serious issues. Packet loss can cause delays or connection drops. If the loss is evenly distributed across all hops, the problem is likely in your own network or on the server side. If the loss occurs only at a specific hop or area, the problem is likely at that node or the connection to the next. Important: Small losses at the first hops belonging to your local network are not necessarily critical, as these devices often prioritize and discard ICMP requests (e.g., ping) lower.

Latency (Ping Times)

Latency values (Avg, Best, Worst) give you insight into the speed and stability of the connection. If latency remains consistently high at a particular hop, it may indicate network congestion or a slow router. A sudden increase in latency between two hops often shows a bottleneck. Normally, latency increases gradually on the way to the destination. Watch out for sudden, strong spikes – these are often signs of problems. Comparing forward and return paths helps detect asymmetric issues where traffic in one direction has problems.

With careful analysis of these factors, you can determine well where the network problem lies – in your network, with the internet provider, or somewhere on the way to the server.

Diagnostic Examples

To better understand this, we show you some examples. The scenarios illustrate different situations and possible causes. This helps you interpret the data better and diagnose network problems more effectively.

Info

The following diagnostic examples are based on fictional WinMTR/MTR reports. The IP addresses, hostnames, and routes are completely made up and have no relation to real networks or hosts.

Example: Packet Loss on Client Side

Description

Packet loss occurs on the client side, visible on both forward and return paths.

Forward path (Client → Server)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                     15.0%   20    1.1    3.4   1.0   10.2  2.8
2. 10.0.0.1                        10.0%   20   12.3   15.7  10.5   30.8  5.5
3. 172.16.0.1                      0.0%   20   25.1   26.0  24.8   27.2  0.6
4. 203.0.113.5                    0.0%   20   35.4   34.5  33.2   36.1  0.9
5. be1234.ccr42.isp.net           0.0%   20   50.6   49.8  49.1   51.5  0.8
6. be5678.ccr21.isp.net           0.0%   20   60.1   59.9  59.5   61.0  0.4
7. 198.51.100.10                  0.0%   20   70.2   70.5  70.0   71.3  0.5
8. Destination IP (Server)        0.0%   20   80.2   80.0  79.5   81.2  0.6

Return path (Server → Client)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)        0.0%   20   80.2   80.0  79.5   81.2  0.6
2. 198.51.100.10                  0.0%   20   70.1   70.4  69.8   71.2  0.5
3. be5678.ccr21.isp.net           0.0%   20   60.2   60.0  59.6   60.7  0.4
4. be1234.ccr42.isp.net           0.0%   20   50.1   50.2  49.5   51.0  0.5
5. 203.0.113.5                   0.0%   20   35.5   35.0  34.5   36.0  0.4
6. 172.16.0.1                    0.0%   20   25.2   26.1  24.9   27.3  0.7
7. 10.0.0.1                     10.0%   20   15.8   16.5  15.0   35.2  6.2
8. 192.168.1.1                  15.0%   20    2.0    4.0   1.2   12.0  3.8

Evaluation

Packet loss is on the client side. Both routes show losses at the first hops (Hop 1 and 2), indicating a problem in the local network or router of the client.

Example: Packet Loss on Server Side

Description

Packet loss occurs on the server side, visible on both forward and return paths.

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20    1.2    1.3   1.1    2.0  0.3
2. 10.0.0.1                      0.0%   20   10.5   11.1  10.0   12.5  0.7
3. 172.16.0.1                   0.0%   20   20.2   20.5  19.5   21.0  0.5
4. 203.0.113.5                  0.0%   20   30.6   30.3  29.5   31.5  0.6
5. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0  0.4
6. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5  0.7
7. 198.51.100.10               10.0%   20   70.5   72.5  70.0   80.0  4.5
8. Destination IP (Server)      15.0%   20   85.3   90.2  85.0  105.0  7.0

Return path (Server → Client)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      15.0%   20   85.3   90.2  85.0  105.0  7.0
2. 198.51.100.10               10.0%   20   70.5   72.5  70.0   80.0  4.5
3. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5  0.7
4. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0  0.4
5. 203.0.113.5                 0.0%   20   30.6   30.3  29.5   31.5  0.6
6. 172.16.0.1                  0.0%   20   20.2   20.5  19.5   21.0  0.5
7. 10.0.0.1                    0.0%   20   10.5   11.1  10.0   12.5  0.7
8. 192.168.1.1                 0.0%   20    1.2    1.3   1.1    2.0  0.3

Evaluation

Packet loss is on the server side. Both routes show losses at the last hops (Hop 7 and 8), indicating a problem at the server.

Example: Latency Issues on Client Side

Description

High latency times occur on the client side, visible on both forward and return paths.

Forward path (Client → Server)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20  150.5  130.5  50.0  200.0  40.0
2. 10.0.0.1                     0.0%   20  120.7  115.5  60.0  190.0  30.0
3. 172.16.0.1                   0.0%   20   25.2   26.1  24.9   27.3   0.7
4. 203.0.113.5                  0.0%   20   35.5   35.0  34.5   36.0   0.4
5. be1234.ccr42.isp.net         0.0%   20   50.1   50.2  49.5   51.0   0.5
6. be5678.ccr21.isp.net         0.0%   20   60.2   60.0  59.6   60.7   0.4
7. 198.51.100.10                0.0%   20   70.2   70.5  70.0   71.3   0.5
8. Destination IP (Server)      0.0%   20   80.2   80.0  79.5   81.2   0.6

Return path (Server → Client)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      0.0%   20   80.2   80.0  79.5   81.2   0.6
2. 198.51.100.10               0.0%   20   70.1   70.4  69.8   71.2   0.5
3. be5678.ccr21.isp.net         0.0%   20   60.2   60.0  59.6   60.7   0.4
4. be1234.ccr42.isp.net         0.0%   20   50.1   50.2  49.5   51.0   0.5
5. 203.0.113.5                 0.0%   20   35.5   35.0  34.5   36.0   0.4
6. 172.16.0.1                  0.0%   20   25.2   26.1  24.9   27.3   0.7
7. 10.0.0.1                   0.0%   20  120.7  115.5  60.0  190.0  30.0
8. 192.168.1.1                0.0%   20  150.5  130.5  50.0  200.0  40.0

Evaluation

Latency is high on the client side. Both routes show increased latency at the first hops (Hop 1 and 2), indicating a problem at the client.

Example: Latency Issues on Server Side

Description

High latency times occur on the server side, visible on both forward and return paths.

Forward path (Client → Server)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20    1.2    1.3   1.1    2.0   0.3
2. 10.0.0.1                     0.0%   20   10.5   11.1  10.0   12.5   0.7
3. 172.16.0.1                   0.0%   20   20.2   20.5  19.5   21.0   0.5
4. 203.0.113.5                  0.0%   20   30.6   30.3  29.5   31.5   0.6
5. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.4
6. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5   0.7
7. 198.51.100.10               0.0%   20  200.5  210.0 200.0  230.0  10.0
8. Destination IP (Server)      0.0%   20  300.5  320.0 300.0  350.0  15.0

Return path (Server → Client)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      0.0%   20  300.5  320.0 300.0  350.0  15.0
2. 198.51.100.10               0.0%   20  200.5  210.0 200.0  230.0  10.0
3. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5   0.7
4. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.4
5. 203.0.113.5                 0.0%   20   30.6   30.3  29.5   31.5   0.6
6. 172.16.0.1                  0.0%   20   20.2   20.5  19.5   21.0   0.5
7. 10.0.0.1                   0.0%   20   10.5   11.1  10.0   12.5   0.7
8. 192.168.1.1                0.0%   20    1.2    1.3   1.1    2.0   0.3

Evaluation

Latency is high on the server side. Both routes show increased latency at the last hops (Hop 7 and 8), indicating a problem at the server.

Example: Routing Problem (ISP Routing)

Description

The route from Client X to the server works fine, while Client Y to the server has routing problems with packet loss. This indicates a problem with the internet service provider (ISP).

Forward path (Client X → Server)

Code

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20    1.2    1.3   1.1    2.0   0.3
2. 10.0.0.1                     0.0%   20   10.5   11.1  10.0   12.5   0.7
3. 172.16.0.1                   0.0%   20   20.2   20.5  19.5   21.0   0.5
4. 203.0.113.5                  0.0%   20   30.6   30.3  29.5   31.5   0.6
5. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.4
6. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5   0.7
7. 198.51.100.10               0.0%   20   70.2   70.5  70.0   71.3   0.5
8. Destination IP (Server)      0.0%   20   80.2   80.0  79.5   81.2   0.6

Forward path (Client Y → Server)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20    1.2    1.3   1.1    2.0   0.3
2. 10.0.0.1                     0.0%   20   10.5   11.1  10.0   12.5   0.7
3. 172.16.0.1                   0.0%   20   20.2   20.5  19.5   21.0   0.5
4. 203.0.113.5                 30.0%   20   30.6   50.3  29.5   95.0  20.5
5. be1234.ccr42.isp.net         25.0%   20   80.2  120.0  70.0  250.0  55.0
6. be5678.ccr21.isp.net         10.0%   20   60.1   60.2  59.5   61.5   0.7
7. 198.51.100.10                0.0%   20   70.2   70.5  70.0   71.3   0.5
8. Destination IP (Server)      0.0%   20   80.2   80.0  79.5   81.2   0.6

Return path (Server → Client X)

Code

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      0.0%   20   80.2   80.0  79.5   81.2   0.6
2. 198.51.100.10               0.0%   20   70.2   70.5  70.0   71.3   0.5
3. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5   0.7
4. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.4
5. 203.0.113.5                 0.0%   20   30.6   30.3  29.5   31.5   0.6
6. 172.16.0.1                  0.0%   20   20.2   20.5  19.5   21.0   0.5
7. 10.0.0.1                    0.0%   20   10.5   11.1  10.0   12.5   0.7
8. 192.168.1.1                 0.0%   20    1.2    1.3   1.1    2.0   0.3

Return path (Server → Client Y)

Code

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      0.0%   20   80.2   80.0  79.5   81.2   0.6
2. 198.51.100.10               0.0%   20   70.2   70.5  70.0   71.3   0.5
3. be5678.ccr21.isp.net         0.0%   20   60.1   60.2  59.5   61.5   0.7
4. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.4
5. 203.0.113.5                 0.0%   20   30.6   30.3  29.5   31.5   0.6
6. 172.16.0.1                  0.0%   20   20.2   20.5  19.5   21.0   0.5
7. 10.0.0.1                    0.0%   20   10.5   11.1  10.0   12.5   0.7
8. 192.168.1.1                 0.0%   20    1.2    1.3   1.1    2.0   0.3

Evaluation

The ISP routing is faulty. The route from Client X to the server is stable, but Client Y’s route shows severe problems with packet loss and high latency.

Example: Packet Loss Only on Forward Path (Client → Server)

Description

Packet loss occurs only on the forward path (client to server), while the return path (server to client) shows no loss. This can indicate a problem in a network segment toward the server, e.g., faulty routers, congestion, or poor connection.

Forward path (Client → Server)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20    1.2    1.5   1.1    2.5   0.3
2. 10.0.0.1                     0.0%   20   10.5   11.1  10.0   12.5   0.7
3. 172.16.0.1                   0.0%   20   20.2   20.5  19.5   21.0   0.5
4. 203.0.113.5                 10.0%   20   35.7   35.0  34.5   36.5   0.6
5. be1234.ccr42.isp.net         15.0%   20   50.6   55.5  50.0   70.0   6.0
6. be5678.ccr21.isp.net         10.0%   20   65.1   65.9  65.0   67.0   0.6
7. 198.51.100.10                0.0%   20   75.2   75.5  75.0   76.2   0.4
8. Destination IP (Server)      0.0%   20   85.3   85.0  84.5   86.0   0.5

Return path (Server → Client)

Code

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      0.0%   20   85.3   85.0  84.5   86.0   0.5
2. 198.51.100.10               0.0%   20   75.2   75.5  75.0   76.2   0.4
3. be5678.ccr21.isp.net         0.0%   20   65.1   65.2  65.0   66.0   0.3
4. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.5
5. 203.0.113.5                 0.0%   20   35.7   35.0  34.5   36.5   0.6
6. 172.16.0.1                  0.0%   20   20.2   20.5  19.5   21.0   0.5
7. 10.0.0.1                    0.0%   20   10.5   11.1  10.0   12.5   0.7
8. 192.168.1.1                 0.0%   20    1.2    1.5   1.1    2.5   0.3

Evaluation

Packet loss occurs only on the forward path. Losses at hops 4, 5, and 6 indicate a problem on the way from client to server, e.g., congestion or defective network devices. The return path is stable.

Example: Packet Loss Only on Return Path (Server → Client)

Description

Packet loss occurs only on the return path (server to client), while the forward path (client to server) shows no loss. This can indicate a problem in a network segment on the return path.

Forward path (Client → Server)

Code

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.1.1                   0.0%   20    1.2    1.5   1.1    2.5   0.3
2. 10.0.0.1                     0.0%   20   10.5   11.1  10.0   12.5   0.7
3. 172.16.0.1                   0.0%   20   20.2   20.5  19.5   21.0   0.5
4. 203.0.113.5                  0.0%   20   30.6   30.3  29.5   31.5   0.6
5. be1234.ccr42.isp.net         0.0%   20   50.2   50.5  49.5   51.0   0.4
6. be5678.ccr21.isp.net         0.0%   20   65.1   65.2  64.5   66.5   0.5
7. 198.51.100.10                0.0%   20   75.2   75.5  75.0   76.2   0.4
8. Destination IP (Server)      0.0%   20   85.3   85.0  84.5   86.0   0.5

Return path (Server → Client)

console

Host                               Loss%   Snt   Last   Avg  Best  Wrst StDev
1. Destination IP (Server)      0.0%   20   85.3   85.0  84.5   86.0   0.5
2. 198.51.100.10               0.0%   20   75.2   75.5  75.0   76.2   0.4
3. be5678.ccr21.isp.net         0.0%   20   65.1   65.2  64.5   66.5   0.5
4. be1234.ccr42.isp.net        10.0%   20   50.6   51.0  50.0   55.0   1.2
5. 203.0.113.5                15.0%   20   35.7   36.5  34.5   40.0   1.8
6. 172.16.0.1                 10.0%   20   20.2   21.5  19.5   25.0   2.5
7. 10.0.0.1                   0.0%   20   10.5   11.1  10.0   12.5   0.7
8. 192.168.1.1                0.0%   20    1.2    1.5   1.1    2.5   0.3

Evaluation

Packet loss occurs only on the return path. Losses at hops 4, 5, and 6 on the return path indicate a problem on the way from server to client.

Reporting Issues

Even though ZAP-Hosting constantly monitors the network, it is important to quickly contact our support in case of network problems. To help us diagnose the problem precisely and solve it quickly, please send us the results of your WinMTR/MTR reports for both forward and return paths. This way, we can accurately identify possible problem areas and assist you promptly.

FAQ

Frequently asked questions

A network diagnostic tool that combines ping and traceroute. It analyzes both the forward path (client to server) and the return path (server to client), recording latency and packet loss for precise network problem diagnosis.

Start with the forward path (client to server). If no issues appear there but problems persist, then check the return path (server to client) to find possible asymmetric problems.

On Windows, use the WinMTR app (download from the ZAP-Hosting website). On Linux, use MTR, installable via commands like 'apt install mtr -y' (Debian/Ubuntu). On Mac, MTR is not pre-installed and must be installed via Homebrew.

Feedback

Was this article helpful?

Your feedback helps us prioritize and improve content.

0 of 0 Users found this article helpful.

Personal support

Need more help than the guide provides?

Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.

Which 🍪 cookies would you like to allow?

Dedicated Server: Network Analysis with WinMTR/MTR for Troubleshooting

Introduction

Installation

Client

Server

Creating a Report

Forward path (Client → Server)

Return path (Server → Client)

Evaluating the Report

Packet Loss

Latency (Ping Times)

Diagnostic Examples

Reporting Issues

Frequently asked questions