Re: Can a bad patch cable cause this?
From: Tom Cat (stry_cat_at_yahoo.com)
Date: 2 Jan 2005 13:58:11 -0800
> Tom Cat wrote:
Thanks for the reply
> Ie., packet flow, etc was fine within your lan with no noticable
> of trouble.
> If it was _just_ a patch cord problem, signs of it should have shown
> lan connections as well inet traffic.
That's why I thought i'd ask here.
> My guess is that your ISP was:
> a: experiencing temporary problems
I called comcast they claimed there were no problems and no upgrades.
> To investigate:
> a: ping your default GW
did this. Time is just under 30msec(is that slow??)
> ping your DNS servers (in order listed)
primary ping time is just over 9msec
secondary was just over 10msec
> http to a site via IP rather than by name
I didn't think to do this. If the problem reoccurs I try this.
> traceroute to an IP then by name
traceroute by name would have random timeouts. I didn't think to try
by IP. Will do that the next time.
> view your CM logs via (usually) http://192.168.100.1/
This was interesting. I have an RCA cable modem (which I'm leasing
from comcast). The page loads except the images all timeout. Could
this be a cable modem problem? However Comcast says the checked my
modem and everything was working correctly.
> b: go here and see what you can find for your ISP/area:
This is a great site. Thanks for telling me about it. Thanks to this
site I found the http://192.168.100.1/moreInfo.html page. This page
loaded except for the images which all timed out. Looking at the
information it provides and the info on dslreports.com, everything
seems to be good with the modem.
> c: see b above
> difficult to know how they may change your "service level"
> by way of the config loaded at boot (a TFTP setup that can
> cap service in several ways on a DOCSIS modem)
No discussion or reports of Comcast doing anything in my area.
> A _very_ good setup/diagnostic primer is here:
Another good site. Thanks!
> Except for dslreports above or your CM logs, you have to try these as
> soon as you note any service problems -- once the symptoms are gone,
> are the clues/evidence ;)
Yep looks like once the problem is gone I can't find what caused it.