ndt-users list created

["Casarez, Rick" <>]

All,

After re-reading my initial email I would like to point out that I could
be in error and the issue could be end user and not server. I realized I
am blaming MLab when it might not be them. I am working with them now
and hopefully we can resolve this one way or another. 

Cheers,
Rick Casarez
Sr. IP Network Engineer
571.262.8709

-----Original Message-----
From: Peter Van Epp 
[mailto:]
 
Sent: Tuesday, June 01, 2010 7:49 PM
To: 

Subject: Re: Warning for those using tool off of measurementlab.net
website

On Tue, Jun 01, 2010 at 04:20:23PM -0400, Casarez, Rick wrote:
> Jason,
> 
> When we traced to the CA server we did not trace to the URL. We
actually
> took the IP address displayed when the test was run. For this
particular
> test it did not go to 38.106.70.173 but actually went to 64.9.225.154.
> We noticed this since our delay times were over 100ms. 
> 
> We have not been able to reliably replicate this issue. I seem to
always
> hit the NY server but my co-worker sometimes hits the CA one. In each
> case at the top of the web site it does state that the server is
located
> in New York. Even if it goes to the CA one. 
> 
> Cheers,
> Rick Casarez
> Sr. IP Network Engineer
> 571.262.8709
> 
        Given that one machine seems to have the problem and another
maybe not,
I'd look at the DNS entry / IP of the client that fails. The server
presumably 
uses one or both of those to decide (perhaps incorrectly) where the
client is 
and thus where the closest ndt server is ...

Peter Van Epp