Times out on first hop

Times out on first hop
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.modems.cable  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Times out on first hop Captain California 05-11-2005
Posted by Captain California on May 11, 2005, 5:52 am
If you were  Registered and logged in, you could reply and use other advanced thread options


I am a Comcast customer. Ran a trace route to 209.176.20.69 and the first
hop times out. Actually the first hop times out choosing many ip
addresses. Talked to tech support. They can't tell me where the first hop
is located. I am guessing it is the node. Anyone got any ideas where the
problem is?




Spring Sale Save 20% Banner - Sale Ended 5/3/07 So Updated to NonPromo Ad
Posted by Bit Twister on May 11, 2005, 8:10 am
If you were  Registered and logged in, you could reply and use other advanced thread options


On Wed, 11 May 2005 05:52:17 -0700, Captain California wrote:
> I am a Comcast customer. Ran a trace route to 209.176.20.69 and the first
> hop times out. Actually the first hop times out choosing many ip
> addresses. Talked to tech support. They can't tell me where the first hop
> is located. I am guessing it is the node. Anyone got any ideas where the
> problem is?


I'll guess it is your gateway. Clickup CMD and do a
ipconfig /all
for it's number.


Posted by Warren on May 12, 2005, 11:00 am
If you were  Registered and logged in, you could reply and use other advanced thread options


Captain California wrote:
>I am a Comcast customer. Ran a trace route to 209.176.20.69 and the first
>hop times out. Actually the first hop times out choosing many ip
>addresses. Talked to tech support. They can't tell me where the first hop
>is located. I am guessing it is the node. Anyone got any ideas where the
>problem is?

Why does it matter where it is, and what's the problem? A router not sending
back responses to ICMP packets doesn't mean there's a problem. It could be a
problem, or it just could mean it's configured to not send back responses to
ICMP packets.

And if they could tell you where the router was located, what exactly were
you planning on doing with that information?

--
Warren H.

==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.
Find Black and Decker Landscaping Equipment. Get a Hog:
http://www.holzemville.com/mall/blackanddecker/index.html





Posted by Robert Nichols on May 12, 2005, 5:32 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


:I am a Comcast customer. Ran a trace route to 209.176.20.69 and the first
:hop times out. Actually the first hop times out choosing many ip
:addresses. Talked to tech support. They can't tell me where the first hop
:is located. I am guessing it is the node. Anyone got any ideas where the
:problem is?

It's just a gateway router that isn't configured to respond to pings.
Not a problem, and it's pretty lame that tech support didn't know that
since much of Comcast's network is configured that way. If it bugs you
to see that timeout, run your traceroute with an initial TTL of 2.

--
Bob Nichols AT comcast.net I am "rnichols42"


Posted by Captain California on May 13, 2005, 6:24 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


What I am trying to find out is why I need to keep repairing the connection
in XP. I don't know much about the Comcast network or any network for that
matter. It's just annoying having to right click the connection icon on my
taskbar and chose repair. It works fine as long as I don't stop browsing.
As soon as I stop to read something for five minutes or so, I click to go
somewhere and it times out. I just don't know where the problem is.


> :I am a Comcast customer. Ran a trace route to 209.176.20.69 and the
> first
> :hop times out. Actually the first hop times out choosing many ip
> :addresses. Talked to tech support. They can't tell me where the first
> hop
> :is located. I am guessing it is the node. Anyone got any ideas where
> the
> :problem is?
>
> It's just a gateway router that isn't configured to respond to pings.
> Not a problem, and it's pretty lame that tech support didn't know that
> since much of Comcast's network is configured that way. If it bugs you
> to see that timeout, run your traceroute with an initial TTL of 2.
>
> --
> Bob Nichols AT comcast.net I am "rnichols42"





other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map