NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM700 in and out connection issue
I have been having in and out connectivity issues lately. I have read some of the past postings but I'm not sure how I can solve it. Could someone please help me? I am very dim on internet connec...
On 17th, a technician from WOW came and he replaced the cable in the yard to the service box on the exterior wall. He said the cable was old.
He didn't do anything on the cable from the service box to the modem, said there was no splitter and it was only a joint.
Now that the new cable is buried and the work is complete, I am still not sure if it resolved the issue, looking at the log below.
Does anyone see a sign of improvement after 17th?
As I was writing I am encountering very slow connection, but it is not recorded in the log..
| Time | Priority | Description |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 11 2022 14:02:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 12 2022 17:11:43 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option |
| Sep 12 2022 18:25:26 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 13 2022 06:48:45 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Sep 13 2022 16:49:42 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 14 2022 04:45:24 | Error (4) | Map Request Retry Timeout |
| Sep 14 2022 06:50:09 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 14 2022 09:05:24 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option |
| Sep 14 2022 21:48:27 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 15 2022 01:29:25 | Warning (5) | TEK Invalid - Invalid Key Sequence Number |
| Sep 15 2022 03:22:23 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 15 2022 07:02:52 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 15 2022 07:22:34 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Sep 15 2022 12:32:11 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 16 2022 06:47:07 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option |
| Sep 16 2022 06:50:09 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 17 2022 10:56:03 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
| Sep 17 2022 10:56:08 | Warning (5) | Lost MDD Timeout |
| Sep 17 2022 10:56:09 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| Sep 17 2022 11:10:12 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Sep 17 2022 11:16:59 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
| Sep 17 2022 11:17:01 | Warning (5) | Lost MDD Timeout |
| Sep 17 2022 11:17:07 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| Sep 17 2022 11:17:27 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
| Sep 17 2022 19:36:04 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 18 2022 04:37:46 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 18 2022 07:42:38 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Sep 18 2022 07:44:09 | Error (4) | Map Request Retry Timeout |
| Sep 18 2022 14:29:58 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 19 2022 13:44:50 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option |
| Sep 19 2022 16:32:55 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 20 2022 13:17:35 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
| Sep 20 2022 13:17:40 | Warning (5) | Lost MDD Timeout |
| Sep 20 2022 13:17:42 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| Sep 20 2022 13:18:51 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Sep 20 2022 14:11:54 | Critical (3) | No Ranging Response received - T3 time-out |
| Sep 21 2022 13:31:51 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option |
| Sep 21 2022 15:04:54 | Critical (3) | No Ranging Response received - T3 time-out |
You have lots of errors and criticals that the ISP needs to review and resolve.