NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Ted2022's avatar
Ted2022
Aspirant
Sep 11, 2022

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 connection and pc related topics so if you can be so kind to explain in a way that a dummy like myself could understand, it would be really appreciated! 

 

For upstream bonded channels, it shows only 4 being used. From other postings I see all the 8 being used, does this have anything to do with the issue I am having?? 

 

Any help would be really appreciated! Thank you in advance!! 

 

 

 
 
TimePriorityDescription
Aug 31 2022 06:45:49Warning (5)TEK Invalid - Invalid Key Sequence Number
Aug 31 2022 11:22:46Error (4)Map Request Retry Timeout
Aug 31 2022 15:46:48Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Aug 31 2022 21:04:53Critical (3)No Ranging Response received - T3 time-out
Sep 01 2022 20:00:05Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 02 2022 03:58:18Critical (3)No Ranging Response received - T3 time-out
Time Not EstablishedCritical (3)DHCP FAILED - Discover sent, no offer received
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Sep 02 2022 21:03:19Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 02 2022 21:04:01Error (4)Map Request Retry Timeout
Sep 02 2022 21:12:42Critical (3)No Ranging Response received - T3 time-out
Sep 02 2022 22:01:42Error (4)Map Request Retry Timeout
Sep 03 2022 02:04:24Critical (3)No Ranging Response received - T3 time-out
Sep 03 2022 13:35:54Warning (5)Lost MDD Timeout
Sep 03 2022 18:29:24Critical (3)No Ranging Response received - T3 time-out
Sep 03 2022 20:31:41Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 03 2022 21:01:50Critical (3)No Ranging Response received - T3 time-out
Sep 04 2022 07:21:15Warning (5)Lost MDD Timeout
Sep 04 2022 09:35:59Critical (3)No Ranging Response received - T3 time-out
Sep 05 2022 02:45:51Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 05 2022 12:35:57Critical (3)No Ranging Response received - T3 time-out
Sep 05 2022 20:23:25Warning (5)Lost MDD Timeout
Sep 05 2022 23:23:58Critical (3)No Ranging Response received - T3 time-out
Sep 06 2022 14:45:51Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 06 2022 15:01:40Critical (3)No Ranging Response received - T3 time-out
Sep 07 2022 11:06:20Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 07 2022 11:10:36Warning (5)Lost MDD Timeout
Sep 07 2022 11:31:50Error (4)Map Request Retry Timeout
Sep 07 2022 19:16:57Critical (3)No Ranging Response received - T3 time-out
Sep 08 2022 12:56:03Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 08 2022 15:17:33Critical (3)No Ranging Response received - T3 time-out
Sep 09 2022 09:52:08Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 09 2022 09:52:10Warning (5)RCS Partial Service
Sep 09 2022 09:52:16Warning (5)Lost MDD Timeout
Sep 09 2022 10:22:08Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 09 2022 15:24:54Critical (3)No Ranging Response received - T3 time-out
Sep 10 2022 22:22:08Error (4)DHCP RENEW WARNING - Field invalid in response v4 option
Sep 11 2022 01:07:58Critical (3)No Ranging Response received - T3 time-out
Sep 11 2022 09:33:32Warning (5)Lost MDD Timeout
Sep 11 2022 09:46:32Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 25612561000000 Hz-0.2 dBmV40.9 dB00
2LockedQAM 25611567000000 Hz-0.2 dBmV40.3 dB00
3LockedQAM 25610573000000 Hz-0.2 dBmV40.9 dB00
4LockedQAM 2569579000000 Hz-0.4 dBmV40.3 dB00
5LockedQAM 2568585000000 Hz-0.7 dBmV40.3 dB00
6LockedQAM 2567591000000 Hz-1.0 dBmV40.9 dB00
7LockedQAM 2566597000000 Hz-1.0 dBmV40.9 dB00
8LockedQAM 2565603000000 Hz-0.9 dBmV40.9 dB00
9LockedQAM 2561609000000 Hz-1.2 dBmV40.3 dB00
10LockedQAM 2562615000000 Hz-1.5 dBmV40.3 dB00
11LockedQAM 2563621000000 Hz-2.0 dBmV40.9 dB00
12LockedQAM 2564627000000 Hz-2.2 dBmV40.3 dB00
13LockedQAM 25630633000000 Hz-2.2 dBmV40.3 dB00
14LockedQAM 25631639000000 Hz-2.0 dBmV40.9 dB00
15LockedQAM 25632645000000 Hz-1.7 dBmV40.3 dB00
16LockedQAM 25613651000000 Hz-1.7 dBmV40.9 dB00
17LockedQAM 25614657000000 Hz-2.0 dBmV40.3 dB00
18LockedQAM 25615663000000 Hz-2.0 dBmV40.3 dB00
19LockedQAM 25616669000000 Hz-1.9 dBmV40.3 dB00
20LockedQAM 25617681000000 Hz-1.5 dBmV40.9 dB00
21LockedQAM 25618687000000 Hz-1.5 dBmV40.3 dB00
22LockedQAM 25619693000000 Hz-1.7 dBmV40.9 dB00
23LockedQAM 25620699000000 Hz-2.0 dBmV40.9 dB00
24LockedQAM 25621705000000 Hz-2.0 dBmV40.4 dB00
25LockedQAM 25622711000000 Hz-2.0 dBmV39.9 dB00
26LockedQAM 25623717000000 Hz-2.2 dBmV40.3 dB00
27LockedQAM 25624723000000 Hz-2.2 dBmV39.9 dB00
28LockedQAM 25625729000000 Hz-2.5 dBmV39.9 dB00
29LockedQAM 25626735000000 Hz-2.7 dBmV39.9 dB00
30LockedQAM 25627741000000 Hz-2.9 dBmV39.5 dB00
31LockedQAM 25628747000000 Hz-3.2 dBmV39.5 dB00
32Not LockedN/AN/A0 Hz0.0 dBmV0.0 dB00

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA12560 Ksym/sec18000000 Hz36.0 dBmV
2LockedATDMA25120 Ksym/sec24600000 Hz36.8 dBmV
3LockedATDMA35120 Ksym/sec31000000 Hz37.3 dBmV
4LockedATDMA45120 Ksym/sec37400000 Hz37.5 dBmV
5Not LockedN/AUnknown0 Ksym/sec0 Hz0.0 dBmV
6Not LockedN/AUnknown0 Ksym/sec0 Hz0.0 dBmV
7Not LockedN/AUnknown0 Ksym/sec0 Hz0.0 dBmV
8Not LockedN/AUnknown0 Ksym/sec0 Hz0.0 dBmV

10 Replies

  • I forgot to mention, WOWWAY tech support told me to contact the modem manufacturer to change 2.4Ghz and 5 Ghz channels. 

    Does this mean anything to you guys? 

    Thanks! 

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    Power and Correct and Uncorrectables look fine. 
    However you have Criticals and Errors in the event log. Something that the ISP needs to review and resolve.

     

    Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended. 
    What is the brand and model of the host wifi router connected to the modem?

    Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
    Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
    Be sure your using good quality RG6 coax cable up to the modem. 
    Be sure to power OFF the modem for 1 minute then back ON.
    https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
    https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router?article=24311
    https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
    https://highspeed.tips/docsis-events/

     

    The CM700 is a modem only. No built in router or wifi here. 

    • Ted2022's avatar
      Ted2022
      Aspirant

      Thanks for your reply! 

      The host wifi router connected to the modem is Deco AC1300. I will need to replace the cable between the modem and the router with CAT6. 

      Regarding the connection up to the modem, I need to check with WOW. 

      WOW was blaming the modem not correctly channeling between 2.4 and 5.0Ghz, but I will check with them again. 

       

      Turning off and on the modem I have tried but I still get this issue... 

       

      Sep 11 2022 14:02:29Critical (3)No Ranging Response received - T3 time-out
      Sep 12 2022 17:11:43Error (4)DHCP RENEW WARNING - Field invalid in response v4 option

       

      Thank you again for your reply and guidance! 

      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User

        "WOW was blaming the modem not correctly channeling between 2.4 and 5.0Ghz" < Be sure they understand and you understand that this model modem does NOT have a built in route or wifi. 

         

        Also those errors and criticals in the event log needs to be reviewed at addressed by the ISP.