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-28 10:08:21 PST Message-ID: <3E36C29A.2030302@cogeco.ca> From: "Warren W. Gay VE3WWG" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada In Crosstalk References: <3E34330C.62C5A6F0@adaworks.com> <29yZ9.2563$c6.2666@bos-service2.ext.raytheon.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 28 Jan 2003 12:49:14 -0500 NNTP-Posting-Host: 198.96.47.195 X-Complaints-To: abuse@sympatico.ca X-Trace: news20.bellglobal.com 1043776154 198.96.47.195 (Tue, 28 Jan 2003 12:49:14 EST) NNTP-Posting-Date: Tue, 28 Jan 2003 12:49:14 EST Organization: Bell Sympatico Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!nntp.cs.ubc.ca!torn!webster!nf1.bellglobal.com!nf2.bellglobal.com!news20.bellglobal.com.POSTED!not-for-mail Xref: archiver1.google.com comp.lang.ada:33505 Date: 2003-01-28T12:49:14-05:00 List-Id: 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. -- Warren W. Gay VE3WWG http://home.cogeco.ca/~ve3wwg