NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ORBI CBR750 requires manually releasing/renewing the IP
I have Netgear Orbi CBR750 with RBS750 satellite.
I own this for two month now.
Four days ago, it started dropping internet every 1.5 hours.
Rebooting the router would bring the internet back.
I called Xfinity, the tech came by and he checked the line all the way to the router. He showed me all the reading he got, the gain, the frequencies test and it all looks green. So it is not the cable.
After some digging, I noticed that 1.5 hours corresponds to the Lease Expires time that is present on the Connection Status page.
So I tried hitting Release and than Renew buttons once the internet went down - and that would bring the internet back.
As of right now, I am going to the Connection Status page and doing the release/renew every 1.5 hours.
I am not sure what happened and why it started doing it. It was fine for two months. I didn't update the firmware.
I tried setting up the static IP - it didn't help. It still dies after 1.5 hours.
Any help would be appreciated.
Logs:
[DHCP IP: (192.168.77.3)] to MAC address AC:3C:8E:00:7A:E7, Friday, Oct 22,2021 13:00:53 [DHCP IP: (192.168.77.14)] to MAC address 3E:C8:09:FA:E3:B8, Friday, Oct 22,2021 12:42:23 [DHCP IP: (192.168.77.9)] to MAC address CE:25:AD:5D:D5:9D, Friday, Oct 22,2021 12:40:53 [DHCP IP: (192.168.77.2)] to MAC address AC:3C:8E:00:76:95, Friday, Oct 22,2021 12:18:41 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 12:15:38 [Internet connected] IP address: 98.41.205.35, Friday, Oct 22,2021 11:59:44 [Internet disconnected] Friday, Oct 22,2021 11:59:42 [DHCP IP: (192.168.77.14)] to MAC address 3E:C8:09:FA:E3:B8, Friday, Oct 22,2021 11:59:28 [Internet disconnected] Friday, Oct 22,2021 11:59:18 [DHCP IP: (192.168.77.5)] to MAC address F4:5C:89:B1:98:4B, Friday, Oct 22,2021 11:54:02 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:48:38 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:48:25 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:44:01 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:43:33 [DHCP IP: (192.168.77.5)] to MAC address F4:5C:89:B1:98:4B, Friday, Oct 22,2021 11:43:33 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:43:24 [DHCP IP: (192.168.77.3)] to MAC address AC:3C:8E:00:7A:E7, Friday, Oct 22,2021 11:43:23 [DHCP IP: (192.168.77.2)] to MAC address AC:3C:8E:00:76:95, Friday, Oct 22,2021 11:37:42 [DHCP IP: (192.168.77.3)] to MAC address AC:3C:8E:00:7A:E7, Friday, Oct 22,2021 11:32:57 [DHCP IP: (192.168.77.5)] to MAC address F4:5C:89:B1:98:4B, Friday, Oct 22,2021 11:26:46 [DHCP IP: (192.168.77.2)] to MAC address AC:3C:8E:00:76:95, Friday, Oct 22,2021 11:15:44 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:05:01 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:04:36 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:04:25 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:03:31 [DHCP IP: (192.168.77.5)] to MAC address F4:5C:89:B1:98:4B, Friday, Oct 22,2021 11:03:30 [DHCP IP: (192.168.77.17)] to MAC address 6C:CD:D6:E6:EB:8A, Friday, Oct 22,2021 11:03:24
Firmware Version for the modem is V4.6.3.6_2.0.48. I have updated the satellite firmware today to V4.6.3.16.
Event log screenshot is attached.
50 Replies
Please post a copy and paste of the modems connection status page.
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#M12853Please do not post MAC addresses in public forums.
Connection Status page screenshot is attached.
There are no splitters. I am using good quality coax cable. I tried powering off and on.How do I make sure ISP provisions the modem correctly?
There should be a connections status page silimar to this:
Cable Connection
Cancel Apply
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
837000000
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 837 MHz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked 256 QAM 31 837000000 Hz 0.1 dBmV 37.4 dB 0 0
2 Locked 256 QAM 1 651000000 Hz -1.6 dBmV 36.6 dB 0 0
3 Locked 256 QAM 2 657000000 Hz -1.6 dBmV 36.6 dB 0 0
4 Locked 256 QAM 3 663000000 Hz -1.3 dBmV 36.8 dB 0 0
5 Locked 256 QAM 4 669000000 Hz -1.3 dBmV 36.7 dB 0 0
6 Locked 256 QAM 5 675000000 Hz -1.1 dBmV 36.7 dB 0 0
7 Locked 256 QAM 6 681000000 Hz -0.8 dBmV 37.0 dB 0 0
8 Locked 256 QAM 8 693000000 Hz -0.5 dBmV 37.1 dB 0 0
9 Locked 256 QAM 9 699000000 Hz -0.2 dBmV 37.3 dB 0 0
10 Locked 256 QAM 10 705000000 Hz -0.2 dBmV 37.0 dB 0 0
11 Locked 256 QAM 11 711000000 Hz 0.0 dBmV 37.1 dB 0 0
12 Locked 256 QAM 12 717000000 Hz 0.4 dBmV 37.4 dB 0 0
13 Locked 256 QAM 13 723000000 Hz 0.3 dBmV 37.1 dB 0 0
14 Locked 256 QAM 14 729000000 Hz 0.6 dBmV 37.1 dB 0 0
15 Locked 256 QAM 15 735000000 Hz 0.9 dBmV 37.3 dB 0 0
16 Locked 256 QAM 16 741000000 Hz 1.0 dBmV 37.3 dB 0 0
17 Locked 256 QAM 17 753000000 Hz 1.1 dBmV 37.5 dB 0 0
18 Locked 256 QAM 18 759000000 Hz 1.0 dBmV 37.5 dB 0 0
19 Locked 256 QAM 19 765000000 Hz 0.7 dBmV 37.4 dB 0 0
20 Locked 256 QAM 20 771000000 Hz 0.8 dBmV 37.6 dB 0 0
21 Locked 256 QAM 21 777000000 Hz 0.7 dBmV 37.7 dB 0 0
22 Locked 256 QAM 22 783000000 Hz 0.6 dBmV 37.7 dB 0 0
23 Locked 256 QAM 23 789000000 Hz 0.7 dBmV 37.8 dB 0 0
24 Locked 256 QAM 24 795000000 Hz 0.5 dBmV 37.7 dB 0 0
25 Locked 256 QAM 25 801000000 Hz 0.4 dBmV 37.5 dB 0 0
26 Locked 256 QAM 26 807000000 Hz 0.5 dBmV 37.7 dB 0 0
27 Locked 256 QAM 27 813000000 Hz 0.5 dBmV 37.6 dB 0 0
28 Locked 256 QAM 28 819000000 Hz 0.1 dBmV 37.3 dB 0 0
29 Locked 256 QAM 29 825000000 Hz 0.4 dBmV 37.6 dB 0 0
30 Locked 256 QAM 30 831000000 Hz 0.2 dBmV 37.5 dB 0 0
31 Locked 256 QAM 32 843000000 Hz 0.0 dBmV 37.4 dB 0 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 5120 Ksym/sec 22000000 Hz 31.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 36000000 Hz 32.8 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29000000 Hz 31.3 dBmV
4 Locked ATDMA 6 2560 Ksym/sec 16000000 Hz 33.3 dBmV
5 Not Locked Unknown 0 0 0 0.0 dBmV
6 Not Locked Unknown 0 0 0 0.0 dBmV
7 Not Locked Unknown 0 0 0 0.0 dBmV
8 Not Locked Unknown 0 0 0 0.0 dBmV
Downstream OFDM Channels
Channel Lock
Status Modulation /
Profile ID Channel
ID Frequency Power SNR /
MER Active Subcarrier
Number Range Unerrored
Codewords Correctable
Codewords Uncorrectable
Codewords
1 Locked 0 ,1 ,2 33 547000000 Hz -3.82 dBmV 36.6 dB 1108 ~ 2987 64457020 52608446 0
2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Extended Upstream Transmit Power
Current System Time:Sat Oct 23 13:44:57 2021
System Up Time:02:07:41
Great.
Do you have a snippet of the Events Log page as well?
Time Priority Description Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 13:12:30 Notice (6) TLV-11 - unrecognized OID Oct 21 2021 13:12:30 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 21 2021 13:12:32 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 21 2021 13:12:49 Alert (2) CM Certificate Error Oct 21 2021 16:21:53 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 16:21:54 Notice (6) TLV-11 - unrecognized OID Oct 21 2021 16:21:54 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 21 2021 16:21:57 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 21 2021 16:22:14 Alert (2) CM Certificate Error Oct 21 2021 19:55:41 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 21 2021 19:55:42 Notice (6) TLV-11 - unrecognized OID Oct 21 2021 19:55:42 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 21 2021 19:55:45 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 21 2021 19:56:03 Alert (2) CM Certificate Error Oct 21 2021 21:17:03 Critical (3) No Ranging Response received - T3 time-out Oct 22 2021 09:05:12 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 22 2021 09:05:13 Notice (6) TLV-11 - unrecognized OID Oct 22 2021 09:05:13 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 22 2021 09:05:16 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 22 2021 09:05:28 Alert (2) CM Certificate Error Oct 22 2021 10:51:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 22 2021 10:51:31 Notice (6) TLV-11 - unrecognized OID Oct 22 2021 10:51:31 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 22 2021 10:51:34 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 22 2021 10:51:51 Alert (2) CM Certificate Error Oct 22 2021 12:15:16 Critical (3) No Ranging Response received - T3 time-out Oct 22 2021 14:39:51 Alert (2) CM Certificate Error Oct 22 2021 15:12:17 Critical (3) No Ranging Response received - T3 time-out Oct 23 2021 12:57:46 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 23 2021 12:57:47 Notice (6) TLV-11 - unrecognized OID Oct 23 2021 12:57:47 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 23 2021 12:57:50 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 23 2021 12:58:07 Alert (2) CM Certificate Error Oct 23 2021 13:04:30 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Oct 23 2021 13:04:31 Notice (6) TLV-11 - unrecognized OID Oct 23 2021 13:04:31 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11 Oct 23 2021 13:04:34 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Oct 23 2021 13:04:51 Alert (2) CM Certificate Error Oct 23 2021 17:24:41 Critical (3) No Ranging Response received - T3 time-out
One item you need to ask your ISP about:
These shouldn't be seen in the logs I believe. Maybe why the CBR can't get a seamless connection and can't get a IP address seamlessly from the ISP. The ISP needs to ensure the CBR is getting the config file correctly. Have them check the events log on the CBR as well.
Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11" Purchased combo router/modem Oct '21 and in the past 2 or 3 months, connectivity drops 4 or 5 times a day requiring a reboot. I updated to the latest firmware v4.6.5.8.
I had Spectrum out here yesterday to test the line and everything looks good on their end. I've used Orbi products for the past 6 or 7 years and never had a problem until I purchased this current model.
