Re: Not Connection to some sites.
Gary N. McKinney (gmckinney@megabits.net)
Thu, 19 Sep 1996 05:18:36 -0700
Scott A. Lagos wrote:
>
> I have several users that are connecting to us to get to the net and
> trying to hit www.wcvb.com. They get delays of up to 3 minutes, but get
> to everywhere else fine. I have tried to get to the site from other
> providers and we get there no problem. My trace route shows only 4 hops
> to get to the site, and there is no packet loss. When browsing we get
> the host contacted from within Netscape, but then things just hang. OUr
> Upstream provider is UUNET and they have not acknowledged or denied any
> problems with our connection, which is a full T1. We also get a similar
> problem when trying to connect to www.hp.com.
>
> I know this seems vague and most would think that it is due a problem at
> either the host or on the net, but my traceroutes and test with the
> browser contradict this.
>
> TraceRoute from the problem net.
>
> Tracing route to 199.242.194.76
>
> 56 bytes from 199.242.194.76: time=199 ms
>
> 1 151 151 207.77.56.1
>
> 2 156 5 137.39.2.46 Loopback0.GW1.BOS1.Alter.Net
>
> 3 161 5 137.39.135.82 webmate-gw.ALTER.NET
>
> 4 165 4 199.242.194.76 wcvb.com
>
> host reached
>
> Traceroute from the OK net.
>
> Tracing route to 199.242.194.76
>
> 56 bytes from 199.242.194.76: time=202 ms
>
> 1 * * timed out
>
> 2 133 133 205.161.0.1 core1-ether0.derry.NH.tiac.net
>
> 3 144 11 207.60.45.5 core2-serial0.bedfo.MA.tiac.net
>
> 4 149 5 199.0.65.1 core-fddi4-0.bedfo.MA.tiac.net
>
> 5 145 -4 137.39.135.113 903.Hssi3-0.GW1.BOS1.ALTER.NET
>
> 6 148 3 137.39.135.82 webmate-gw.ALTER.NET
>
> 7 162 14 199.242.194.76 wcvb.com
>
> host reached
>
> If anyone has a clue as to what I might want to check, I'd appreciate
> it.
>
> Thanks, Scott
>
>
> --
> Scott A. Lagos
> ______________________________________
> http://www.net1plus.com
>
> NET1Plus
> Connected Data Systems, Inc.
> 119 Massachusetts Avenue
> Lunenburg, MA 01462
>
> v. 508.343.3011
> f. 508.345.1925
Scott ... While a traceroute or ping operation will inform you if you can reach a
spacific host machine they will not tell you if the DNS is setup properly for the
machine. Ping operates at the lowest level in the TCP stack while traceroute operates
higher in the stack. Neither tool will exercise the DNS ( Domain Name Server ) of the
requested machine ...
I performed a NSLOOKUP to see what the response was for the machines you listed
above. In both cases the nslookup returned a NON_AUTHORITATIVE ANSWER response which
will cause the type of problem you are describing. The problem is NOT at your site but
at the DNS servers for the machines you listed.
Hope the info helps.
Gary McKinney, Megabits.Net Systems Administrator & Janitor...