Pingplotter found high packet loss4/25/2023 If the final hop is showing 0 packet loss and acceptable latency, you can ignore whatever you see in the hops leading up to it. This is a great article with some scenarios to look for. For example, if 91 of 100 packets reach their destination the network experienced 9 packet loss. Gaming and VoIP have many similarities in their latency requirements. VoIP Troubleshooting with PingPlotter.Here are some additional good resources about troubleshooting: Keep collecting data with PingPlotter and save off images of problem periods to help them understand that there is a problem (which they'll often deny, of course, if you just call them with an 'I sometimes have problems, but it's OK now' story. If your problem is with your ISP, you'll have to contact them.Try eliminating parts, testing from other computers (if you have one), and swapping parts to isolate the problem. If your problem is inside your own (wired!) network (like happened to someone at Pingman Tools a bunch during a Skippy season), check your network cables, router/hubs, and network cards.If the problem is between your computer and your wireless router, and you're using 802.11(a/b/g/n), think about moving your router, changing wireless channels, or maybe even using network wires instead of wireless.Once you find the problem, you can take the proper steps to solve it. Try correlating the packet loss or latency problem with network activity that's happening. The problem *may* be caused by data being transferred to your network (is anyone else using the network and downloading/transferring data?).Your main goal here is to discover the source of the problem, so turn on time graphs for each hop until you find the first hop with problems. (See the 'Creating a comment or note' in our Getting Started Guide for instructions on how to do this). When you have an in-game network problem, and you get a chance, create a comment on the time period of the problem in PingPlotter.Let PingPlotter run in the background while you practice/race.You can find a list of iRacing IP addresses here. Enter the corresponding IP address for the server or region you are playing on.Set the trace interval to 2.5 seconds or 5 seconds. Here are the steps to follow to isolate the problem: Is it your wireless network? Is it a bad cable modem connection? Bad hub/router? ISP problem? With PingPlotter, you can isolate the problem. Most of the time, these days (2011), the problem is with your own network or your ISP - not with iRacing or the internet 'cloud'. PingPlotter does great on finding this type of problem. Of course, you were 1/2 lap ahead 45 minutes into a race when this happened and lost connection! AAAARRRRRRGGGGGHHHH! The lag indicator will show high latency, or the quality indicator shows problems. I often have network problems in iRacing.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |