how-to block ads
|
aspiron
Premium
join:2006-03-04
Blue Springs, MO
| Cable modem keeps rebooting
So I had a Motorola 4100 (I believe) for about 4 years, worked flawlessly until a couple weeks ago when it kept rebooting about every 20 minutes. Comcast came out a checked the sinal inside and out and gave me a new SB5120 modem. Well I'm still having the same problem. The only thing that has changed with my setup has been the addition of a Belkin Wireless G+ router. I thought maybe that might be the problem so I went back to my cheap wired router that I had used for the last 2 years, but still the same problem.
I'm at a loss here and need help. What is causing this constant rebooting and how do I fix it?
Here is the error log from my modem stats:
060305192936 3-Critical R02.0 No Ranging Response received - T3 time-out
060305192341 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191656 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191654 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191603 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191124 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191057 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191031 3-Critical R02.0 No Ranging Response received - T3 time-out
060305191004 3-Critical R02.0 No Ranging Response received - T3 time-out
060305190320 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185725 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185724 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185723 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185656 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185604 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185447 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185033 3-Critical R02.0 No Ranging Response received - T3 time-out
060305185007 3-Critical R02.0 No Ranging Response received - T3 time-out
060305184744 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
060305184742 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
060305184742 7-Information B401.0 Authorized
060305184742 7-Information 7 I500.0 Registration Completed
060305184742 7-Information SEC: Co-Signer CVC from configuration file was verified
060305184740 7-Information REGISTRATION COMPLETE - Waiting for Operational status
060305184740 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
060305184740 7-Information Registration file - downloaded
060305184739 7-Information Trying to download Configuration file ...
060305184739 7-Information 7 D507.0 Retrieved Time....... SUCCESS
060305184739 7-Information Time of day - retrieved
060305184739 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
060305184739 7-Information DHCP - parameters acquired
060305184737 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
060305184737 7-Information Trying to register through CMTS...
060305184737 7-Information SYNCHRONIZED - 585000000 Hz , ucd 4
060305184735 7-Information Starting Ranging On Channel 4
060305184731 7-Information Downstream Locked - Collecting Upstream Information
060305184731 7-Information 7 T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
060305184729 7-Information Scanning frequency 585000000Hz
060305184729 7-Information Trying to synchronize ...
060305184729 7-Information Synchronization LOST
060305184729 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
060305184657 3-Critical R02.0 No Ranging Response received - T3 time-out
060305184450 3-Critical R02.0 No Ranging Response received - T3 time-out
060305184449 3-Critical R02.0 No Ranging Response received - T3 time-out
060305183402 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
060305183401 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
060305183401 7-Information B401.0 Authorized
060305183400 7-Information 7 I500.0 Registration Completed
060305183400 7-Information SEC: Co-Signer CVC from configuration file was verified
060305183359 7-Information REGISTRATION COMPLETE - Waiting for Operational status
060305183358 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
060305183358 7-Information Registration file - downloaded
060305183357 7-Information Trying to download Configuration file ...
060305183357 7-Information 7 D507.0 Retrieved Time....... SUCCESS
060305183357 7-Information Time of day - retrieved
060305183356 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
060305183356 7-Information DHCP - parameters acquired
060305183352 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
060305183352 7-Information Trying to register through CMTS...
060305183352 7-Information SYNCHRONIZED - 585000000 Hz , ucd 4
060305183349 7-Information Starting Ranging On Channel 4
060305183349 7-Information Starting Ranging On Channel 3
060305183346 7-Information Starting Ranging On Channel 4
060305183342 7-Information Downstream Locked - Collecting Upstream Information
060305183342 7-Information 7 T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
060305183340 7-Information Scanning frequency 585000000Hz
060305183340 7-Information Trying to synchronize ...
060305183340 7-Information Synchronization LOST
060305183340 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
060305183153 3-Critical R02.0 No Ranging Response received - T3 time-out
060305183127 3-Critical R02.0 No Ranging Response received - T3 time-out
060305183125 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182918 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182851 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182850 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182824 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182757 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182756 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182755 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182754 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182752 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182726 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182634 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182633 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182632 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182605 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182307 3-Critical R02.0 No Ranging Response received - T3 time-out
060305182241 3-Critical R02.0 No Ranging Response received - T3 time-out
060305180344 3-Critical R02.0 No Ranging Response received - T3 time-out
060305180020 3-Critical R02.0 No Ranging Response received - T3 time-out
060305175954 3-Critical R02.0 No Ranging Response received - T3 time-out
060305175902 3-Critical R02.0 No Ranging Response received - T3 time-out
060305174713 3-Critical R02.0 No Ranging Response received - T3 time-out
060305174712 3-Critical R02.0 No Ranging Response received - T3 time-out
060305173201 3-Critical R02.0 No Ranging Response received - T3 time-out
060305172220 3-Critical R02.0 No Ranging Response received - T3 time-out
060305171923 3-Critical R02.0 No Ranging Response received - T3 time-out
060305171806 3-Critical R02.0 No Ranging Response received - T3 time-out
060305171805 3-Critical R02.0 No Ranging Response received - T3 time-out
060305171623 3-Critical R02.0 No Ranging Response received - T3 time-out
Note those are all from just today, ugh!!! | |
NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA
 ·Cox HSI
4 edits | With those errors, there's not much more you can do yourself as it's a communications problem between your modem and the CMTS.
(You can also tell it's not electrical power-related as the date/time is maintained -- a power-off "reset" would cause the clock to reset to 1/1/1970)
Those errors also generally have nothing to do with any equipment you might attach to your modem (e.g. routers, PCs, etc.).
You might try increasing the distance between your modem and your wireless router (if they're right next to each other that is) ... RF energy can cause all sorts of hard-to-diagnose gremlins. (although I doubt this to be the cause if this indeed just started "out of the blue" w/o any changes on your end)
I'm also assuming that Comcast already inspected and "cleared" your home's wiring during their recent visit.
What are your modem's signal levels?
If your signal levels are in-spec all you can do is call Comcast again and keep after 'em until it's fixed. | |
|
