From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,b7f81184e76b0532 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-29 06:43:22 PST From: "Dr. Michael Paus" Newsgroups: comp.lang.ada Subject: Re: Ada In Crosstalk Date: Wed, 29 Jan 2003 15:43:19 +0100 Organization: 1&1 Internet AG Message-ID: References: <3E34330C.62C5A6F0@adaworks.com> <29yZ9.2563$c6.2666@bos-service2.ext.raytheon.com> <3E36C29A.2030302@cogeco.ca> NNTP-Posting-Host: p508307ef.dip0.t-ipconnect.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: news.online.de 1043851399 28427 80.131.7.239 (29 Jan 2003 14:43:19 GMT) X-Complaints-To: abuse@online.de NNTP-Posting-Date: 29 Jan 2003 14:43:19 GMT User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en In-Reply-To: Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!news.teledanmark.no!news.equant.no!uio.no!feed.news.nacamar.de!news.belwue.de!news.uni-ulm.de!rz.uni-karlsruhe.de!schlund.de!news.online.de!not-for-mail Xref: archiver1.google.com comp.lang.ada:33556 Date: 2003-01-29T14:43:19+00:00 List-Id: John R. Strohm wrote: > "Dr. Michael Paus" wrote in message > news:b18383$j0t$1@news.online.de... >=20 >>Well, I think I can tell difference between a time out and a >>name resolution problem. Here is my answer from nslookup: >> >>Nicht autorisierte Antwort: >>Name: wbmas-stsc1.hill.af.mil >>Address: 137.241.248.34 >>Aliases: www.stsc.hill.af.mil >> >>So you see the name resolution is not the problem. >> >>If I do a ping with the above IP # I never get to the >>target. I get a time out somewhere in between and this is >>always true for a couple of months now. >> >>I have already posted the details in a previous post which >>I do not want to repeat now. >=20 >=20 > For those of us who came in late, what does traceroute show? >tracert 137.241.248.34 Routenverfolgung zu wbmas-stsc1.hill.af.mil [137.241.248.34] =FCber maxi= mal 30 Ab schnitte: 1 1 ms 1 ms 1 ms 192.168.1.32 2 58 ms 59 ms 60 ms 217.5.98.32 3 59 ms 59 ms 59 ms 217.237.152.246 4 147 ms 147 ms 146 ms NYC-gw14.USA.net.DTAG.DE [62.156.131.146= ] 5 145 ms 147 ms 145 ms jfk-brdr-02.inet.qwest.net [205.171.1.49= ] 6 146 ms 147 ms 148 ms jfk-core-03.inet.qwest.net [205.171.230.= 26] 7 155 ms 153 ms 151 ms dca-core-03.inet.qwest.net [205.171.8.21= 8] 8 185 ms 187 ms 187 ms iah-core-01.inet.qwest.net [205.171.5.18= 6] 9 187 ms 187 ms 187 ms iah-core-02.inet.qwest.net [205.171.31.2= ] 10 216 ms 218 ms 216 ms bur-core-01.inet.qwest.net [205.171.205.= 25] 11 215 ms 216 ms 215 ms lax-core-01.inet.qwest.net [205.171.8.41= ] 12 217 ms 216 ms 216 ms lax-edge-08.inet.qwest.net [205.171.19.1= 42] 13 220 ms 220 ms 220 ms 65.113.16.22 14 221 ms 220 ms 223 ms 198.26.130.34 15 221 ms 219 ms 220 ms BU-WCX-SAND.NIPR.MIL [198.26.130.33] 16 227 ms 223 ms 223 ms 198.26.130.34 17 221 ms 221 ms 220 ms BU-WCX-SAND.NIPR.MIL [198.26.130.33] 18 222 ms 224 ms 221 ms 198.26.130.34 19 221 ms 223 ms 265 ms 198.26.118.34 20 272 ms 262 ms 265 ms 198.26.118.33 21 266 ms 263 ms 264 ms 198.26.118.34 22 266 ms 265 ms 265 ms 198.26.118.33 23 264 ms 302 ms 317 ms 198.26.122.9 24 245 ms 240 ms 245 ms 198.26.122.10 25 243 ms 249 ms 246 ms 198.26.122.9 26 241 ms 248 ms * 198.26.122.10 27 * * * Zeit=FCberschreitung der Anforderung. 28 ^C This looks worse than usual. Some machines at the end of the chain seem to be sending messages back and forth to each other. Michael