One simple tool for complex network troubleshooting.
Use Cases and Deployment Scope
We use PingPlotter to troubleshoot issues from within our network on a regular basis. The best use of this tool is to confirm whether the reachability of an external network resource, server, or website is a problem within our network or outside it. With the evidence PingPlotter provides, we can confidently engage the provider's support team and guide them to the issues we see as needing their attention. Most often, we act on behalf of our staff who are experiencing problems with software-as-a-service, for instance.
Pros
- Finding latency in the path of any network based service.
- Determining the reach-ability of any software-as-a-service.
- Confirming that the final destination in the path of a network is reachable.
- Connection consistency to any network service/s.
Cons
- My limited experience suggests we cannot ping/trace multiple TCP ports at once. If that is true, it would be helpful to have that ability. Also, place the port field out in the open instead of burying it in the Options submenu.
- Reach into the offending network and fix their problems so I don't have to spend hours on the phone trying to get someone else to fix them for my clients.
Return on Investment
- Simple evidence of network problems that most tech support can understand.
- We use it as a training tool for new network staff.
- Provides satisfaction to our clients that we are able to see where problems exist.
- We are a public agency. Our ROI is based entirely on customer satisfaction, which PingPlotter provides very well.
Usability
Other Software Used
Cisco ThousandEyes, SolarWinds AppOptics, Nmap
