Interpreting Results

Related and interesting links

 

Occasionally, we run across an interesting topic, link or web site. We have no affiliation with any of these sites, and some of them may not even be up. Enter at your own risk (arrrggghhhh - pirate thoughts abound after reading the Traceroute and Pirates article).

Read more...


Building a Compelling Case

 

If you find a network problem, you'll most likely want to try and solve that problem. In some cases you might be able to solve this network problem yourself - possibly by upgrading the BIOS on a hardware device, replacing a network cable or changing network service providers. In most cases though, the network problem will need to be fixed by someone else. If this happens, you'll want to build a compelling case that clearly demonstrates the problem, and then also convey (or present) that information.

Read more...


Voice over IP (VoIP) troubleshooting

 

Introduction

Using an IP Network (like the internet) to conduct a voice conversation (VoIP) is becoming easier and easier for people to do. It can be inexpensive and relatively reliable.It can, however, also be challenging - with poor voice quality, the inability to hear and communicate, delays and other problems.

Read more...


Interpreting Results - Bandwidth Saturation

 

Every network connection has a limit, and in this example we'll talk about how to recognize bandwidth limits on a local DSL / Cable modem.

The scenario here is a 30Mbps downstream, 10Mbps upstream cable modem running a 2.5 second trace interval to our target. The computer running PingPlotter was connected to the cable modem via a wireless network card, which loses packets occasionally.

Read more...


Interpreting Results - Bad Hardware

 

Scenario: External customer has problems using your network resources.

A customer (not inside your network) has problems losing connecting to services inside your network. In this scenario, you are acting as a service provider for some network service. This might be provided via HTTP, or possibly through something like Citrix or Windows Terminal services.

Read more...


Interpreting Results - ISP Problems

 

For this example, we're assuming the role of a user that's having problems with a broadband connection. What we'll be taking a look at is a few days worth of trace data. One thing to keep in mind is that if you're doing long term monitoring and want to look at more than the largest default time span on the time-interval graph (48 hours), you can add custom time intervals in the pingplotter.ini file located in PingPlotter's installation directory.

Read more...


Interpreting Results - Gamers

 

For this example, let's assume you're an online gamer - specifically, a Quake III player (though the following is representative of any online game really - MMORPG, RTS, racing sims, fighting games, etc.). You've got two servers that are running the same maps you like to play, so the only issue you have is which one out of the two is going to give you a better connection. We realize some folks aren't going to be so patient as to use the method below to decide which server they're going to play on...

Read more...


Interpreting Results - Longterm Monitoring

 

PingPlotter allows you to use the timeline graphs to zoom in on any particular time, so even if you weren't there (or didn't save an image) when something was happening, you can still recover that exact image later. You shouldn't ever have to be sitting in front of your computer when an outage happens, or you experience other problems on your network, to get the data you need from PingPlotter.

Read more...