Re: Ada In Crosstalk

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

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