Klarinet Archive - Posting 000440.txt from 1999/06

From: "Mark Charette" <charette@-----.org>
Subj: [kl] Troubles getting to Sneezy
Date: Fri, 11 Jun 1999 20:53:27 -0400

Three people now have told me they had trouble getting to Sneezy for a day
or so. There's been no troubles that I can tell in the machine, and I can
get to it regularly. It was probably something else down on the Internet.

For those of you with Msft Windows 95/98, you can figure out the trouble by
typing into a MSDOS window:
tracert www.sneezy.org

If nothing at all comes back - then your service provider's DNS servers
aren't working.

You should see something like (this is what I get from home):

Tracing route to www.sneezy.org [207.252.168.41]
over a maximum of 30 hops:

1 105 ms 98 ms 114 ms liv1.oeonline.com [206.31.225.2]
2 109 ms 127 ms 120 ms cache.oeonline.com [206.31.225.254]
3 123 ms 120 ms 118 ms cisco.oeonline.com [206.31.224.1]
4 143 ms 141 ms 145 ms 204.70.229.69
5 140 ms 142 ms 139 ms core2-fddi-0.PompanoBeach.cw.net
[204.70.92.49]
6 154 ms 141 ms 138 ms bordercore3.PompanoBeach.cw.net
[166.48.152.1]
7 168 ms 156 ms 152 ms 204.70.12.1
8 156 ms 159 ms 172 ms cw-gw.attga.ip.att.net [192.205.32.1]
9 165 ms 182 ms 166 ms br2-a3120s2.attga.ip.att.net
[192.205.33.206]
10 173 ms 165 ms 179 ms br1-p390.wswdc.ip.att.net [12.127.9.138]
11 197 ms 195 ms 206 ms br2-a3120s2.wswdc.ip.att.net [12.127.8.226]
12 178 ms 177 ms 179 ms br1-p320.n54ny.ip.att.net [12.127.9.122]
13 177 ms 177 ms 177 ms gr1-a3110s1.n54ny.ip.att.net
[192.205.36.197]
14 178 ms 179 ms 180 ms atm10-0-0-1.nyc-bb7.cerf.net [134.24.32.161]
15 180 ms 181 ms 259 ms pos0-2-155M.nyc-bb8.cerf.net [134.24.32.193]
16 193 ms 191 ms 184 ms pos5-0-622M.chi-bb3.cerf.net [134.24.32.213]
17 221 ms 258 ms 183 ms pos1-0-0-155M.chi-bb2.cerf.net
[134.24.29.210]
18 192 ms 194 ms 194 ms atm5-0.det-bb1.cerf.net [134.24.46.153]
19 231 ms 238 ms 199 ms oeonline-gw.det-bb1.cerf.net [134.24.134.18]
20 205 ms 203 ms 206 ms www.sneezy.org [207.252.168.41]

Trace complete.

--------
This tells me how I get from the ISP provider (in this case oeonline.com) to
www.sneezy.org .
I go by the way of Livonia, MI to Pompano Beach, FL, to somewhere in GA to
Washington, DC, to NY, NY, to Chicago, IL to Detroit, MI back to Livonia,
MI.

The two machines (the oeonline.com dialin and Sneezy) are separated
physically by about 10 feet, but Internet routing-wise by a long way :^) Any
problem in any of those _other_ Internet systems would make Sneezy
unavailable to me from home if they couldn't be re-routed (BTW - the routes
from "here to there" for everyone can change on a second-by-second basis).

If you never get to oeonline-gw.det-bb1.cerf.net [134.24.134.18] then
something's wrong somewhere in the Internet; if you do get to
oeonline-gw.det-bb1.cerf.net but not to Sneezy then Sneezy's down.

Sneezy does go down regularly every Thursday around 10AM EDT for about 10
minutes for a scheduled reboot.

Mark Charette@-----.org
Webmaster, http://www.sneezy.org

-------------------------------------------------------------------------
Unsubscribe from Klarinet, e-mail: klarinet-unsubscribe@-----.org
Subscribe to the Digest: klarinet-digest-subscribe@-----.org
Additional commands: klarinet-help@-----.org
Other problems: klarinet-owner@-----.org