To measure the throughput between devices at endpoints, simply configure a display filter between their IP addresses.

Let's look in the CAP_1674_06_04 file from Statistics | Conversations. In this file, we can see that the three busiest connections are as follows:

• One connection from a terminal server client 192.168.1.192 to the terminal server at 172.30.0.10
• Two connections from the terminal server 172.30.0.10 to the database server at 172.30.0.22

In the following screenshot, we can see the Conversations window:

The parameters set in the filter fields are as follows:

• ip.addr==172.30.0.22 && tcp.port==57604 && ip.addr==172.30.0.10 && tcp.port==445
• ip.addr==172.30.0.22 && tcp.port==58479 && ip.addr==172.30.0.10 && tcp.port==445
• ip.addr==192.168.1.192 && tcp.port==45214 && ip.addr==172.30.0.10 && tcp.port==3389

As we can see in the following screenshot, when we look at the I/O graphs, we can see two peaks from the terminal server 172.30.0.10 to the database server 172.30.0.22. The Client-Server Traffic 1 in brown peaks on the right, while Client-Server Traffic 2 in green peaks on the left:

Since the bandwidth of the two bit-streams from the terminal server to the database server are much higher than the terminal server stream, we don't see the last one on this window (dashed line has been added to the screenshot). In order to see it, we disable the two higher bit-stream checkboxes, and what we get is the following:

Here, we can see that the highest peaks in the terminal server traffic are around 400,000 bits per second (a dashed line has been added in the preceding screenshot).