NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Lagging/Dropouts?
We've been having problems with our network having lag spikes, constant lag, webpages or videos taking longer than they should to load. Internet completely dropping out saying the cable isnt connected when it is and there is no work or repairs being done to the lines. There are quite a few devices connected to the network with people streaming/gaming plus phones but even when there is very low activity on the network with maybe myself or another using it we still experience these problems. I've checked the Event log and it comes up with "Warning" & "Critical" messages but I have no idea what they mean and I want to see if it's something I could possibly fix before we call tech guys to come have a look. Last time they came they just gave us a new modem but I don't think it's our modem that's having the issues.
| 2017-11-07, 16:01:48.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 15:49:11.0 | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 15:49:08.0 | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| 2017-11-07, 15:48:51.0 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:cb;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 15:48:20.0 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:cb;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 15:48:19.0 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:cb;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 15:46:45.0 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 15:46:42.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 15:46:13.0 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 15:46:01.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 15:14:03.0 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 15:13:27.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 14:37:58.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 12:22:24.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 12:17:42.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 11:59:05.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 11:58:45.0 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.0;CM-VER=3.0; |
| 2017-11-07, 11:58:30.0 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 11:58:16.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 11:35:20.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-11-07, 10:33:29.0 | Critical (3) | SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-31, 19:00:40.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-26, 00:59:34.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-24, 11:00:09.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-20, 08:46:55.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-15, 19:34:30.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-15, 19:32:25.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-15, 19:32:05.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-15, 19:31:25.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| 2017-10-15, 19:31:05.0 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=dc:ef:09:88:74:10;CMTS-MAC=00:1d:70:cc:49:ca;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
1 Reply
I see alot of T3 timeouts which typically indicates a line issue either in your home or your neighborhood I suggest contacting your ISP have them send a tech out check the lines and signal levels.
DarrenM
