Re: Strange internet case . . .

[Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>]

Ken Sims wrote:

> I would suspect a DNS problem or a routing problem.  I would use NSLOOKUP,
> PING, and TRACERT from all three connection methods and compare the
> results.  NSLOOKUP and PING should give the same results for all
> three.  TRACERT will be different at the beginning, but should merge together.

Neither PING nor TRACERT gets there.  But both do resolve to an IP
address, 199.8.210.3.  Can't PING or TRACERT that IP address either.
TRACERT goes through about 8-10 hops, the last 3 just before the
acpl.lib.in.us are sprintnet.

I can PING it here at work today.  I can TRACERT it too, but that looks
weird.  The first hop is to our router here in the office, then 8 hops
of timing out, then the library site.  Does the same exact thing for
espn.com.

NSLOOKUP may not be installed at home (Win ME) because it wasn't found.
It was 11pm though (too many kids ballgames and homework requiring the
computer . . .) so I went to bed.

--
-Jeff

New email address: jlcrosby@dilgardfoods.com

The opinions expressed are my own and not necessarily
the opinion of my company.  Unless I say so.