If the problem exists somewhere out of your control, you can compile the evidence and present your findings to the right people. If the problem is within your control, you can use PingPlotter’s collection of networking knowledge to fix it. Identifying the issue is good, but fixing it is better. We’ve compiled our best resources to help you nail down what’s causing you grief. By using some key indicators, you can narrow down the list of worst offenders to get a pretty good idea of what’s happening and where. Nobody’s born with the whole of networking knowledge lodged in their noggin.

This step is probably the most daunting, but don’t worry. See how PingPlotter helped Ruby, a remote receptionist company, answer the call. Once you think you have it, you’ll need to save the results to send to the right people or reference for yourself. Four Ways to Be More Productive and Not Drown in Tickets - RouterFreak. PingPlotter will be capturing a lot of useful data, but it’s up to you to catch the network problem in the act. Let’s hit that Start button and see what happens! Step 3: Record the Results With a target in place, you’re all ready to start sending trace packets. Luckily, there are a number of resources available to find the right target for a trace. Sometimes, the target is obvious (like the IP address for a game server). You need to figure out where your data’s going so you can trace its route correctly. Not much you can do when a undersea fiber gets cut and you are on a backup network.We’re going to follow a few steps to find the network problem, figure out what’s causing it, and do everything we can to fix it. ISP monitor their network and generally see issues and fix them if they can. Other stuff you would have to get lucky take to a ISP. Your really can only realistically fix hop1 (your equipment in your house) and hop2 (the connection to your ISP from your house). It not like you can call them up and complain. What can you possibly do about it if that router is owned by say google or maybe level3. The bad news is lets say you see a issue with HOP 6 that continues to the end IP address. Next you need to do tests to the actual game servers since the path to them is different. There is almost nothing that only runs on IPv6. So first I would turn off IPv6 in your machine nic settings. No matter how much they say IPv6 is the s been 25 years they say that.many ISP still do not have as good pathing for IPv6 as IPv4. This is also partially done to prevent denial of service attacks against a router. The reason you see loss to intermediate routers is equipment is generally configured to favor actually passing data than responding to test ping packets. You can not have issuers in the path and it not actually cause issues on the final destination.

There are a variety of scenarios where PingPlotter can help your troubleshooting. Where PingPlotter really shines is the ability to watch a route and graphically show you what may be causing poor performance. If 80% of the time you drive though a intersection you get a new dent it means you still would have those dents when you get to your destination. PingPlotters emphasis is on long-term monitoring and troubleshooting of the entire route to a particular host. Lets say the hops were intersections on way to work and packet less was big rocks hitting your car and putting dents into it. Everything you see is a result of the testing method and not actually any problems.

This is why people need to do ping and tracert by hand rather than depend on apps they click one button.

Pingplotter not responding