|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: Eric <eric@roxanne.org> In-Reply-To: <51C5283E.4020802@gmail.com> Date: Mon, 24 Jun 2013 09:13:34 -0400 To: NANOG <nanog@nanog.org> Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org +1. It's especially helpful for wireless troubleshooting in a campus environ= ment. You can get a lot of info from the AP, but tend not to know what the c= lient is seeing and it's great for catching transient events (oh, whenever t= he elevator goes by...) Eric On Jun 22, 2013, at 12:29 AM, "Carlos M. Martinez" <carlosm3011@gmail.com> w= rote: > May sound silly, but in another life I faced a similar problem and by > hosting local SpeedTest.net servers in our network we could fend off > many of these calls. >=20 > But I guess it will depend on your customers, whether they take it or not.= >=20 > cheers, >=20 > ~Carlos >=20 > On 6/20/13 9:45 PM, Jeffrey Ollie wrote: >> Are there any tools out there that we could give to our end users to help= >> diagnose network problems? We get a lot of "the Internet is slow" support= >> calls and it would be helpful if we had something that would run on the e= nd >> user's computer and help characterize the problem. We have central >> monitoring system of course but that doesn't always give a complete >> picture, as the problem could always be on the end user's computer - slow= >> hard drive, not enough memory, wrong name servers, etc. >=20
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |