Re: Strange internet case . . .

[Ken Sims <ken@xxxxxxxxx>]

Hi Jeff -

> > 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'm a little confused as to how you know that the sprintnet routers were
the last ones before www.acpl.lib.in.us if the tracert didn't complete.

In any case, it sounds like a routing problem.  If you send the tracert
information to the support people at Comcast, they should be able to
forward it to the persons responsible.  If that doesn't get any results,
you could send the tracert information to the ISP associated with the last
successful hop.

Ken
http://www.ke9nr.org/
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.