|
Posted by Bit Twister on August 15, 2006, 9:47 am
If you were Registered and logged in, you could reply and use other advanced thread options
>
> Well, it is requesting and receiving a 192.168.100.xxx series address from
> the modem.
But that maybe the default when there is no connection to the
WAN/headend equipment.
> Funny, I am still confused about whether the Comcast modem is supposed to
> hand out a public or private IP.
I would suggest it would give out a WAN side ip address. CableOne.net
and Comcast.net modems give you a WAN ip address. Not a 192.168.x.x ip.
> So far, for me, the two modems I have had dealings with that are not
> working would hand out a private IP (i.e. 192.168.100.10).
That I can beleive. It would be default so you could access the modem
web page.
> The only modem I have had experience with that was working
> properly handed out a public IP to the computer itself (single computer
> connected). So... beats me. I don't really care what IP it hands out. Just
> looking for where to start troubleshooting.
>
> This is the first time I've messed with Comcast cable modems. But it sure
> seems strange that the power on sequence for all the devices is so critical
> (modem, router [if any], computer(s), etc.). What the hell happens after a
> power failure and restore? Do you have to go through all this manually
> again? I understand that the DHCP server has to be up before requesting an
> address, but...
This powerup sequence is for when you change MAC devices. In your
power outage example, you have a race condition, Usually the computer
will be the last piece of equipment to to ask for ip, depending on
operating system. If you were to watch for awhile, you will notice the
public ip address does not change very often.
Now a power glich/brownout could leave the modem logic dinked up, which
would require a good power reset.
> One of my "problems" may be solved when the owner returns from his trip and
> I can try the power down for 1 minute sequence on it. At least his modem has
> all lights on (synched, I guess). The other one I'm having trouble with
> doesn't come up with all lights. Seems it might not be synced with Comcast.
> So... I suppose a phone call to Comcast is definitely in order there.
Yep, no sync, no dhcp lease from the headend, and no connectivity to internet.
> Unfortunately, I have not been able to devote adequate troubleshooting time
> to either of these cases. I keep having to leave the respective sites before
> I get a handle on it. Definitely not time to call Comcast, punch in a bunch
> of menu numbers, wait for a technician and go through all the expected
> troubleshooting steps.
I'll do the power steps just like the tech would walk me through
before placing the call. As soon as we get through the customer
verification steps, I'll reel off each step preformed in the same
order they would had me do it in the past. Helpdesk says, ok, let's move the
problem up the chain. :)
> I'll get the time sooner or later. So far my
> involvement has been just hit and run.
Maybe a batch job/script to watch for outage and it grabs the signal data
from the modem for checking later.
Ping failure will tell you when you loose connectivity.
You can use wget to fetch the modem web page.
I wrote a perl script to tell me about signal level and lease/ip
changes on my Linux OS.
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map