Diagnose co-location networking problem

[Stephan Wehner]

> So login to the FreeBSD machine and trace back to your client IP -
> or as close as you can get.  That may mean just to the edge of your
> current provider but that may give you some idea.

Ok, here is the result.

$ traceroute 64.114.83.92
traceroute to 64.114.83.92 (64.114.83.92), 64 hops max, 40 byte packets
 1  VPS-18-137.virtualprivateservers.ca (65.110.18.137)  1.098 ms
0.991 ms  1.151 ms
 2  a.core.65-110-0-1.van.data-fortress.com (65.110.0.1)  4.357 ms
1.557 ms  1.147 ms
 3  64.69.87.37 (64.69.87.37)  1.740 ms  1.255 ms  1.150 ms
 4  216.187.88.241 (216.187.88.241)  1.742 ms  2.438 ms  2.182 ms
 5  204.239.129.214 (204.239.129.214)  1.910 ms  2.881 ms  3.489 ms
 6  nwmrbc01dr02.bb.telus.com (154.11.4.72)  5.095 ms  3.309 ms  2.322 ms
 7  64.114.45.106 (64.114.45.106)  6.555 ms  80.103 ms  9.048 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *

What does this tell??

By the way, other servers look "good". Meaning when I repeatedly
access other websites (not my own) I don't see failures.

Stephan

>
> Bill
> --
> Bill Vermillion - bv @ wjv . com
>


-- 
Stephan Wehner
> http://stephan.sugarmotor.org
> http://stephansmap.org
> http://www.trafficlife.com
> http://www.buckmaster.ca