Re: Ada In Crosstalk

["Dr. Michael Paus" <paus@ib-paus.com>]

John R. Strohm wrote:
> "Dr. Michael Paus" <paus@ib-paus.com> wrote in message
> news:b18383$j0t$1@news.online.de...
> 
>>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.
> 
> 
> 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]  über maximal 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.218]
   8   185 ms   187 ms   187 ms  iah-core-01.inet.qwest.net [205.171.5.186]
   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.142]
  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überschreitung 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