Cjn801's profile

New Contributor

 • 

12 Messages

Closed

Netgear N900 CG4500BD Issues

My router/modem combo won't maintain connection to the internet. It seems to be going through a constant refresh or reboot cycle. I have been on the phone with cox and they haven't been able to help thus far, only to send a tech out tomorrow to hopefully figure something out. I thought it might be a faulty router/modem so I just had it replaced and the new one still does the same. I have done hard resets, soft resets, cycled the modem on and off to no avail.

Any one know of this happening before and know how to resolve? Many thanks!

Valued Contributor III

 • 

4.2K Messages

Has this been happening since the start or a recent occurrence? Could you describe the reboot cycle it goes through?

New Contributor

 • 

12 Messages

This has been recent.  I first noticed it a few days ago after upgrading my service for "faster speeds."  I will receive a wifi signal but no connection at all.  

The cycle goes like this:
-Everything is fine, connection great, signal great
-Lose all connection, signal still great
-Lose signal
-Router/modem reboots, all lights off for a second then solid green (how it appears on this router/modem)
-Regular lights appear, green and two blue (how it appears on this router/modem)
-5-10 minutes later, cycle repeats

I found this thread that pretty closely hits on what I am experiencing here: http://forums.cox.com/forum_home/internet_forum/f/5/t/8057.aspx 

Valued Contributor III

 • 

4.2K Messages

Good catch on the other post. It does seem similar. Maybe a firmware issue?

What are you signal levels BTW? You can log into page 192.168.100.1 with user; admin password: password. Then Maintence > Connection. See page 22 of manual for more info.

New Contributor

 • 

12 Messages

Possibly?  I am unsure really, this is not my field of expertise whatsoever.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 831000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK 161001_vm2.0_d.cfg
Security Enabled BPI+

Downstream Bonded Channels
Lock Status Modulation Channel ID Symbol rate Frequency Power SNR DOCSIS/EuroDOCSIS locked
Locked QAM256 16 5360 Ksym/sec 831000000 Hz 4.1 dBmV 40.3 dB DOCSIS
Locked QAM256 13 5360 Ksym/sec 813000000 Hz 3.9 dBmV 40.4 dB DOCSIS
Locked QAM256 14 5360 Ksym/sec 819000000 Hz 4.0 dBmV 40.1 dB DOCSIS
Locked QAM256 15 5360 Ksym/sec 825000000 Hz 4.0 dBmV 40.3 dB DOCSIS
Locked QAM256 21 5360 Ksym/sec 861000000 Hz 4.0 dBmV 40.0 dB DOCSIS
Locked QAM256 22 5360 Ksym/sec 867000000 Hz 4.2 dBmV 39.9 dB DOCSIS
Locked QAM256 23 5360 Ksym/sec 873000000 Hz 4.1 dBmV 40.0 dB DOCSIS
Locked QAM256 24 5360 Ksym/sec 879000000 Hz 4.0 dBmV 39.9 dB DOCSIS

Upstream Bonded Channels
Lock Status Modulation Channel ID Symbol rate Frequency Power
Locked ATDMA 4 2560 Ksym/sec 39963000 Hz 41.0 dBmV
Locked TDMA and ATDMA 1 2560 Ksym/sec 29988000 Hz 42.5 dBmV
Locked ATDMA 2 2560 Ksym/sec 33313000 Hz 39.5 dBmV
Locked ATDMA 3 2560 Ksym/sec 36638000 Hz

42.0 dBmV

Valued Contributor III

 • 

4.2K Messages

Signal levels very good. Anything in the logs around the time(s) of the reboots? You can find that under Maintenance > Event logs. 

Also, is the gateway plugged directly into the wall for electricity?

New Contributor

 • 

12 Messages

Logs below.  It is plugged into a power strip.  Should I try to plug into a wall?  I think I may need a firmware update?  

Time Priority Description
 Wed Feb 04 23:21:15 2015    Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 23:21:15 2015    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 23:21:11 2015    Notice (6)   Honoring MDD; IP provisioning mode = IPv4 
 Wed Feb 04 23:21:08 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.0;CM-VER=3.0; 
 Wed Feb 04 23:21:03 2015    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.0;CM-VER=3.0; 
 Wed Feb 04 23:21:01 2015    Notice (6)   WiFi Interface [wl1] set to Channel 36 (Side-Band Channel:N/A) - Reason:GUI 
 Wed Feb 04 23:20:57 2015    Notice (6)   WiFi Interface [wl0] set to Channel 9 (Side-Band Channel:N/A) - Reason:GUI 
 Wed Feb 04 23:20:54 2015    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 23:18:44 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:51:20 2015    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:50:37 2015    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:50:36 2015    Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:50:32 2015    Notice (6)   Honoring MDD; IP provisioning mode = IPv4 
 Wed Feb 04 22:50:28 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.0;CM-VER=3.0; 
 Wed Feb 04 22:50:26 2015    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.0;CM-VER=3.0; 
 Wed Feb 04 22:50:17 2015    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:48:08 2015    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:48:07 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:47:24 2015    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:47:23 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:40:53 2015    Warning (5)   Dynamic Range Window violation 
 Wed Feb 04 22:33:57 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:33:11 2015    Warning (5)   Dynamic Range Window violation 
 Wed Feb 04 22:18:14 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:09:32 2015    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:09:29 2015    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 22:09:29 2015    Warning (5)   Dynamic Range Window violation 
 Wed Feb 04 21:46:36 2015    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 21:45:54 2015    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 21:45:53 2015    Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.1;CM-VER=3.0; 
 Wed Feb 04 21:45:50 2015    Notice (6)   Honoring MDD; IP provisioning mode = IPv4 
 Wed Feb 04 21:45:40 2015    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a4:2b:8c:29:60:b0;CMTS-MAC=00:26:99:89:eb:b1;CM-QOS=1.0;CM-VER=3.0; 

New Contributor

 • 

12 Messages

I changed the Channel to 9 instead of Auto on the 2.4GHz and left it at auto on the 5GHz, it seems to be working well now.  My Mac computer (personal) is getting speeds now of 80+ mbps download and ~12 mbps upload on the 5GHz.  My PC (work) is getting 4 mbps download and 14 mbps upload on the 2.4GHz.

So this is my next issue to resolve it seems.

New Contributor

 • 

12 Messages

Here's $100 worth of solution to this issue, as I found out in the 5 minutes of having Cox Tech Solutions on the phone for.

Change the channel to 1 or 11.

After the Tech Solutions did that within the first few minutes of the $100 call, everything was fixed, no issues at all now.

Boy do I feel like a sucker...

You win again local cable company.

Valued Contributor III

 • 

4.2K Messages

I don't see how a wireless channel issue would cause the gateway to reboot and for there to be T3 error in the log. Odd fix.

New Contributor

 • 

12 Messages

actually it didn't fix the issue at all.  I'm still encountering the same thing.

Former Moderator

 • 

7.1K Messages

@Cnj801

I'm thinking at this point it may be time to arrange for a technician to come out and take a closer look at everything.