No IP address? Doh

Linksys router and linksys cable modem. Cable modem is whre the service enters the house, from there it is cat5 up to my office area where the WRT54G takes over. I wasn't getting an IP, so I connected my PC right up to the cable modem - eliminating the modem, still didn't get an IP. Called Comcrap they guided me through some bullshit - blah blah - nothing I hadn't tried before after all; I'm an IT guy. Didn't work. She puts me on hold to see if there is a problemin my area - viola. I have an IP. I told her I'm fixed and say thanks. I'm always nice to those people, no need to people others' lives difficult.

30 minutes later - same thing. no IP. I shut everything down - cable modem and router - unplugged. I mow the lawn and take a shower (45 minutes). I come back, plug in the modem, plug in my router - no IP. I make something to eat. A hoagie. No mayo. I now have an IP. So did Comcast simply want me to make a hoagie?
Reply to
Edward
Loading thread data ...

What's the length of your DHCP lease? Maybe they're working on splitting the network in your area, although that should usually be a lot more seamless than it's apparently been for you.

Reply to
Bill M.

I can't find out how long the lease is in my router's information...

Reply to
Edward

I have a WRT54G, but I'm running dd-wrt firmware so I can't help you find it. If the Linksys firmware doesn't provide that information, you could bypass the router and connect directly to the modem. That way you could use "ipconfig /all" from a command prompt to see it.

Meanwhile, maybe someone else will chime in with a better answer.

Reply to
Bill M.

I connected the damn PC right up to theinternet. The lease is 30 days. I am out of town, so as soon as I left its f***ed. The people living with me, tried resetting the modem/router, waiting 45 minutes - NOTHING. Comshit blames the router; despite the fact there has been no change to the god damn thing.

Reply to
Edward

Are you saying that your DHCP lease is 30 days but at some point before that period you lose connectivity and can't reacquire an IP address?

It might be time to start at the beginning. What are the lights on the cable modem doing when you lose connectivity? When you can access it, what do the modem's signal levels look like? Do they fluctuate over time, such as time of day or from one day to the next?

Reply to
Bill M.

correct.

The lights on the cable modem are as follows: US: lit DS: lit. ethernet: blinking

I'll get the signal levels when I get back home. Every month this happens.Rain or shine.

Reply to
Edward

Only 3 lights on the modem? What make/model is it? Does it even have a web server available?

Reply to
Bill M.

I came home to see none of the lights were on, except power. I reset it and now I have everything.

formatting link
Here is the info from the cable modem's webserver

Acquire Downstream Channel 723000000 Hz Locked Connectivity State Operational Operational Boot State OK Operational Security Enabled BPI+

--------------------------------------------------------------------------------

Downstream Channel

Lock Status Operational Modulation 256QAM Channel ID 0 Provisioned Rate 6600 kbps Symbol Rate 5360.537 Ksym/sec Downstream Power 2.9 dBmV SNR 34.4 dB

--------------------------------------------------------------------------------

Upstream Channel

Lock Status Operational Modulation 16QAM Channel ID 3 Provisioned Rate 384 kbps Symbol Rate 2560 Ksym/sec Upstream Power 35.0 dBmV

Time Priority Description 2007-07-08 21:50:28 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-08 21:50:15 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-07 07:22:51 critical SYNC Timing Synchronization failure

- Failed to acquire QAM/QPSK symbol timing 2007-07-07 07:22:46 critical No UCD's Received - Timeout 2007-07-07 07:19:38 critical SYNC Timing Synchronization failure

- Failed to acquire FEC framing 2007-07-07 07:19:37 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-07 07:19:34 critical No Ranging Response received - T3 time-out 2007-07-07 07:19:18 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received

- T4 timeout 2007-07-07 07:19:16 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-07 07:17:45 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-07 06:01:08 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-07 05:49:07 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 16:41:42 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 16:40:43 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 16:33:45 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 16:33:29 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 16:33:25 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 16:33:04 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 16:33:01 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 14:29:26 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 14:24:26 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 13:24:54 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 10:55:00 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 10:54:08 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 10:38:56 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 10:38:53 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 10:10:39 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 10:10:13 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 10:09:52 critical SYNC Timing Synchronization failure

- Failed to receive MAC SYNC frame within time-out period 2007-07-06 09:59:57 critical Started Unicast Maintenance Ranging

- No Response received - T3 time-out 2007-07-06 08:34:08 critical Init RANGING Critical Ranging Request Retries exhausted 2007-07-06 08:34:08 critical No Ranging Response received - T3 time-out

Reply to
Edward

Oh, it's a Linksys!

Downstream power and SNR look acceptable to me. Upstream power looks good, too.

The log entries, as bad as they look, seem to be pretty common, at least in the modems that I've come across.

I'm not seeing anything obviously wrong so far, except that you said that ALL of the lights were off when you got home, even the Ethernet light. I could be wrong, but it seems like the Ethernet side of the modem should stay lit as long as something is connected to it.

It might be tempting to go down and pick up a (rental) cable modem from your local TWC office to use as a troubleshooting aid. If it doesn't help, just return it.

Reply to
Bill M.

Correction, ethernet was lit. So far today everything is OK. But ALL damn weekend it was toast. One would think that after a while botuh would reset; the router would try to get an IP, and the modem would try to resync itself instead of just sitting there like a brick.

Reply to
Edward

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.