 
| Subject: | |
| From: | |
| Reply To: | [log in to unmask][log in to unmask], 10 Apr 1998 13:38:13 -0400452_ISO-8859-1 We are in need of some troubleshooting assistance on our local area network at our facility in El Paso, Texas. If anyone has any recommendations or if you are a provider of such services, please contact me (preferably off-list). Thanks. Jim Phillips Manager of Information Systems E-Mail: [log in to unmask] Therm-O-Link, Inc. Phone: (330) 527-2124 P. O. Box 285 Fax: (330) 527-2123 Garrettsville, Ohio 4423153_10Apr199813:38: [log in to unmask] |
| Date: | Tue, 14 Apr 1998 14:25:13 -0400 |
| Content-Type: | Text/Plain |
| Parts/Attachments: |
|
|
In <[log in to unmask]> [log in to unmask] writes:
> More on the "I can't access the Interex advocacy pages" topic...
>
> From our site, any place I've chosen to "ping" responds in
> less than a second...
> except for www.interex.org.
[snip]
We see:
---- $C697FB0A PING Statistics ----
18 packet(s) transmitted, 13 packet(s) received, 27 % packet loss
round trip (ms) min/avg/max = 101 / 128 / 221
> Who is at fault?
>
> traceroute www.interex.org
> traceroute to www.interex.org (198.151.251.10), 30 hops max, 40 byte packets
> 1 gateway.allegro.com (198.102.6.1) 6 ms 4 ms 5 ms
> 2 r2.brainstorm.net (205.164.112.34) 77 ms 31 ms 87 ms
> 3 r1-rtr0.brainstorm.net (205.164.112.33) 39 ms 35 ms 72 ms
> 4 mae-west.nap.net (198.32.136.13) 68 ms 35 ms 42 ms
> 5 mae-west.exodus.net (198.32.136.33) 682 ms * *
> 6 * * *
> 7 sc3-f6-0-0.exodus.net (209.1.169.6) 1874 ms 1890 ms 1876 ms
> 8 * * *
> 9 206.79.7.202 (206.79.7.202) 1983 ms * *
> 10 www.interex.org (198.151.251.10) 1892 ms * *
[snip]
> 1 foo.fum.fie (x.x.x.x) 2 ms 1 ms 2 ms
> 2 a.b.c (x.x.x.x) 85 ms 8 ms 200 ms
> 3 core2-fddi-0.Bloomington.mci.net (204.70.208.49) 135 ms 11 ms 339 ms
> 4 * *
> core5.SanFrancisco.mci.net (204.70.4.85) 241 ms
> 5 pb-nap-OC3-1.exodus.net (198.32.128.25) 21 ms 22 ms 24 ms
> 6 scca-02-f2-1-0.core.exodus.net (209.185.9.37) 22 ms 27 ms 23 ms
> 7 sc3-f6-0-0.exodus.net (209.1.169.6) 24 ms 23 ms 24 ms
> 8 santaclara-cisco12.exodus.net (207.82.200.12) 26 ms 25 ms 25 ms
> 9 206.79.7.202 (206.79.7.202) 26 ms 30 ms 28 ms
> 10 www.interex.org (198.151.251.10) 30 ms 27 ms 27 ms
>
> maybe it's mae-west.exodus.net?
Our traceroute doesn't go through mae-west.exodus.net either. From your
first traceroute, the big delay seems to be between sc3-f6-0-0... and
mae-west.exodus.net. I'd guess that their mae-west router is a bit
overloaded.
FYI, here's a traceroute from one of our boxes;
traceroute to www.interex.org (198.151.251.10), 30 hops max, 40 byte packets
1 troi.3k.com (198.151.172.1) 3.872 ms 3.571 ms 3.5 ms
2 207.86.48.65 (207.86.48.65) 28.261 ms 13.522 ms 10.854 ms
3 dca1-core2-fa0-1-0.atlas.digex.net (165.117.17.2) 11.078 ms 10.571 ms 1
791 ms
4 iad1-core1-h1-0.atlas.digex.net (165.117.50.89) 14.576 ms 36.228 ms 14.
3 ms
5 vnva-01.core.exodus.net (192.41.177.119) 41.585 ms * 226.91 ms
6 heva-01-h8-1-0.core.exodus.net (209.1.169.162) 197.981 ms 50.343 ms 46.
6 ms
7 * * *
8 sc3-f6-0-0.exodus.net (209.1.169.6) 96.58 ms 96.564 ms *
9 * santaclara-cisco12.exodus.net (207.82.200.12) 97.492 ms 91.931 ms
10 206.79.7.202 (206.79.7.202) 169.452 ms 121.475 ms 105.038 ms
11 www.interex.org (198.151.251.10) 119.202 ms 121.844 ms 99.362 ms
-Chris Bartram
|
|
|
