PingPlotter
is a network troubleshooting and diagnostic tools for Windows User. It
uses a combination of traceroute, ping and whois to collect data
quickly, and then allows you to continue collect data over time to give
you the information you really need to indentify on your Internet
Connection to the server. You may download PingPlotter Freeware on your local computer to trace your domain name or IP address using the PingPlotter application. BENEFITS Ping plotter offers some unique value for network monitoring and troubleshooting on Microsoft Windows. - Graphically display performance metrics about the route of your data takes to a server. - Monitor network performance over time, capturing the moments when problems surface. - Zoom in on a problem period and construct a compelling case to have someone help you solve a problem. - Get notified when there is a network problem. - Save data or images, and send to others for review - Troubleshoot without having to call your ISP, allowing you to know about the problems before they do. ANALYSIS Below is the exmple of normal connection of pingplotter result images obtained. ![]() As you observed from the above traceroute result, there was 9 hops required to reach our server. Each hops represents a router or server that it has to pass through to reach the webserver and there was no packet loss during the route. You may also saw that the IP address for each hops and DNS Name if available. The Avg and Cur show an average of 9 milliseconds for response time and latency. From this graph, we may conclude that the there was no problem with the connection from the user end to the web server. Below is an example of our oversea server which having connection problem while accessing our server. ![]() As you may observed from the traceroute, it requires 14 hops to reach the server. The numbers of hops may increase if you are tracing from a high network system or to far distanced server such oversea. You may also observed that there was a packet loss on 2nd hop and starting from 10th hop, there as a massive packet loss. This is enough to prove a connection problem from the user end to the server. It also requires an average of 324 milliseconds and 330 of latency for reaching the server. From the graph, we can concludes that there was a connection problem from the user to the target server. GLOSSARY
|