I’ve previously theorized that the NVG-510’s implementation of the gateway’s DNS forwarder (which is based on the open source dnsmasq code) has a too-short timeout on failed queries. Quite often, these errors occur in clusters and the clusters can continue for minutes at a time, so it’s not surprising that devices on my network using DHCP configurations would exhibit poor connectivity. In the NVG-510’s log (which is a circular log that is way too short) I saw multiple occurrences of DNS failures for example, from earlier today: I recently had cause to use PingPlotter again when devices on my network that configure their network connections via DHCP served up by my AT&T U-verse NVG-510 ADSL+ gateway started to slow down. Pingplotter … gets a rating of 5 out of 5.
Pingplotter test pro#
Pingplotter comes in freeware, Standard ($24.95) and Pro ($199.95) versions. The tool also measures "packet jitter" (the variation in how quickly packets are handled), VoIP Mean Opinion Score or MOS (an estimation of perceived voice quality), and standard deviation of packet transit time. What PingPlotter is actually doing is repeatedly running a traceroute to identify all of the intermediate routers between your machine and the targets and testing each for how long it takes to respond. Nessoft's PingPlotter … tests connectivity to one or more target hosts on your local network or on the Internet and plots the results.
Here’s my summary of PingPlotter from my last roundup of my favorite tools: In fact, this utility has helped me so many times it’s ridiculous. I’ve written about PingPlotter several times ( the last time in 2011, although it did also have a starring role in sorting out my problems with AT&T in 2012). One of my favorite tools for tracking down network problems is a tool called PingPlotter published by Nessoft.
0 kommentar(er)
