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-7-bit X-Google-Thread: 103376,b7f81184e76b0532 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-29 00:26:43 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!npeer.de.kpn-eurorings.net!rz.uni-karlsruhe.de!schlund.de!news.online.de!not-for-mail From: "Dr. Michael Paus" Newsgroups: comp.lang.ada Subject: Re: Ada In Crosstalk Date: Wed, 29 Jan 2003 09:26:41 +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=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.online.de 1043828803 19485 80.131.7.239 (29 Jan 2003 08:26:43 GMT) X-Complaints-To: abuse@online.de NNTP-Posting-Date: 29 Jan 2003 08:26:43 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: <3E36C29A.2030302@cogeco.ca> Xref: archiver1.google.com comp.lang.ada:33540 Date: 2003-01-29T08:26:43+00:00 List-Id: Warren W. Gay VE3WWG wrote: > Wes Groleau wrote: > >> >>I think it's like a miniature slashdot effect. >> >>C.L.A. mentions the site, and their server can't >> >>handle the sudden flood (of twenty-five people). >> >>> No, this is an issue that Dr. Paus has mentioned befor in this forum >>> -- the >>> .mil sites deny access to certain foreign IP addresses. >> >> >> I can believe that. >> >> On the other hand, almost every time >> I try to follow an STSC reference in CLA, >> (from my Indiana worksite, through >> a proxy in Boston, Dallas, or Los Angeles), >> it fails. It usually works the next day. > > > Many times, people have confused "access" with "name > server resolution errors". When you go to a web site, > two things must happen : > > 1. The "resolver" must lookup the site name (host name) > by contacting a chain of name servers. > 2. Using the IP # from the resolver, you then establish > a session with the webserver. > > These are two completely different processes, although they > look "combined" when you make use of a browser (you are > more aware of this when you do socket programming). > > Try contacting directly by IP # 137.241.248.34 (this > was an "unauthoritative" answer according to my nslookup). > > Some of you may just not be "resolving" the host site name. > Others may indeed have IP access related issues. > 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. Michael