NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR850 blocking certain websites
Hi, fellow Orbians! I had an older Orbi system (AX4200) and was gifted this RBR850 (AX6000) kit. It was fully installed and going about our business until I wanted to source parts to build a chic...
Amazing how people don't want to listen.
Worth reading:
Potentially related:
- Why is Akamai Blocking Me? Part 2 - Penetration Testers, Bug Bounty Hunters and Security Researchers
- Why is Akamai Blocking Me? Part 3 – Partners Performing Web Scraping Activity
Part 2 should be easy to answer (unless the recent user which got the same public IP address triggered this)
Part 3 might be caused by malware or similar.
You won't get anywhere wasting Comcast/Xfinity helpdesk resources.
kskreider wrote:
I had an older Orbi system (AX4200) and was gifted this RBR850 (AX6000) kit. It was fully installed and going about our business until I wanted to source parts to build a chicken coop. For some reason, neither Lowes nor Home Depot's site would load and appeared blocked.
Extreme unlikely we're facing a router issue here - this message does come from edgesuite.net, the Akamai Technologies content delivery network (CDN) blocking the public IP address you presenting there, this is typically the public IP address assigned to your Internet connection, and finally your router WAN/Internet port.
kskreider wrote:
I rebooted the modem and the router and pow! Home Depot and Lowes both work fine now
Very likely your ISP does dynamically assign typically changing IP addresses - so Akamai does no longer block your connection.
kskreider wrote:
So I go to watch a baseball game and MLB.tv now gives me this error:
mlb.mlb.com does not support HTTPS requests
This URL does neither connect by http nor by https. So completely unclear from where you have got that URL.
Nothing wrong with any troubleshooting and enhancements you applied to your Orbi config - good job!
- Well, I thought I had fixed it with the MAC address error since Home Depot was accessible again, however I just went to pay a bill and got the same error on the Macy's website. I tried Home Depot again and it's blocked again too.
I did not do the clean sweep reset last night like I said I would so I'll still have to try that, I guess.
Do others have problems with their RBR850? Maybe I should just swap this one out?If you turn off the CM modem and RBR, then disconnect the RBR from the CM modem, connect up this one ethernet connected PC to the back of CM modem, power ON the CM modem, give about 2 minutes, can you access these web sites that have been giving problems?
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-routerOK, something really strange is going on.
I did exactly what you told me to, the steps, in order and followed the instructions for the link. My PC is currently connected directly to the CM.
I could not get the modem to connect so I reset the static IP address on my workstation and rebooted. I could not initially get to 192.168.100.1 but it would not let me log in. I had to RESET the modem. Once I did I was able to get to sites like Facebook or CNN but not much else. It took about 10 tries to get to this post. The modem's admin console keeps resetting itself and asking me to log in again. After about 5 or 6 logins I got this:
Now about 5 minutes in it seems like I can get to Home Depot, Macy's, and the other problematic sites just fine.
Here is the current event log (which probably reset when I hard reset the modem):
Time Priority Description 2024-04-14, 22:30:21 Critical (3) UCD invalid or channel unusable;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:30:21 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:30:08 Notice (6) Honoring MDD; IP provisioning mode = IPv6 2024-04-14, 22:30:03 Critical (3) UCD invalid or channel unusable;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6 Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:28:12 Critical (3) UCD invalid or channel unusable;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:55 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:53 Critical (3) UCD invalid or channel unusable;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:44 Critical (3) UCD invalid or channel unusable;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:27:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2024-04-14, 22:26:59 Critical (3) UCD invalid or channel unusable;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:90:f0:31:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=14:59:c0:f7:f4:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
