Paul
Sun Jun 01 18:31:48 PDT 2008
Ritter 197 wrote:
> ALL hops timed out. 30 of them.
There is some background information on traceroute here.
http://en.wikipedia.org/wiki/Tracert
What if an important port number was blocked by Comcast
for their own customers ? That might mean the difference
between a Comcast customer running the test, and those
of us outside the Comcast network running the test.
I didn't have any problem running traceroute here,
against either www.comcast.net or just comcast.net,
and I'm outside Comcast.
Maybe you can make enough sense out of that Wikipedia
article, to come up with another test. Perhaps your
own firewall is the reason the test failed.
Comcast had some issues just recently, and may have
made adjustments to their network in an effort to
figure out the problem. And in any case, like any
ISP, if you phone up and ask them a question, you'll
get that "we're innocent" routine. Tech support will
never admit to any filtering, even if it is for good
and logical reasons.
http://www.dailytech.com/article.aspx?newsid=11925
Paul
>
> "Big Al" <BigAl@nowhere.com> wrote in message
> news:nXG0k.1093$jX.28@trnddc04...
>> Ritter 197 wrote:
>>> yes, mine times out. have tried it now many times.
>>>
>>> "neil" <neilp67_@_hotmail.com> wrote in message
>>> news:RQz0k.10559$yb3.4637@newsfe18.ams2...
>>>> So when you type "tracert www.comcast.net" into a command prompt
>>>> window it times out, I've just tried it and it's ok in 9 hops.
>>>> Neil
>>>> "Ritter 197" <Ritter197@comcast.net> wrote in message
>>>> news:A2AD317C-94C4-4238-9DEB-A9D25023900B@microsoft.com...
>>>>> I want to do a tracert on comcast.net (my ISP) and it always times
>>>>> out, yet I can get e-mail and see newsgroups.
>>>>>
>>>>> What does it mean then and what to do to do a tracert?
>>>>
>>>>
>> I've been *told* that a single hop timeout is not an issue.
>> Especially if it gets to the end of the route.
>