NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
CM3000 Browser Issues
I am writing to report an issue with the cable connection site on Chromium-based browsers. While other functions of the site are functioning correctly, the loading time for the cable connection site ...
It appears that the issue was caused by an extension, which is challenging to identify. The problem lies primarily on the development side of the extension I am using. Therefore, the issue has been resolved. Still find it ironic noone from netgear even responds to forums pretty disappointing just like the XR1000 that's been left to rust,
Does this happen with MS Edge and Firefox and Opera?
Last time I had my CM3000 online, MS Edge worked fine...
Is this with a PC directly connected to the modem or is there a wifi router connected in between?
What PC OS platform is this? Apple or MS?
As previously mentioned, this feature is exclusive to chromium-based browsers. The links provided indicate the platform I am using and the necessary analytics. This issue does not occur in Firefox. This is connected to a router, which would be how 99% of users would be using the modem.
Please find the link demonstrating its complete functionality in Firefox. No issues were encountered. Brave is stuck in a loop, similar to the behavior of most other Chromium browsers.
Here is another link demonstrating the feature in Microsoft Edge. Do you understand that virtually all browsers, excluding Firefox and Safari, are based on Chromium? Briefly, the most common browsers are all Chromium-based.
Does this happen if you disconnect the ISP cable coax line from the modem then try to access the modems web pages?
Which ISP are you connected too?
Checking my CM3000, as previously mentioned, both MS-Edge and Google Chrome access and navigate the modems web pages correctly and successfully. Windows 11 24H2:
During direct testing of the connection to the modem, I observed that it successfully loaded content more efficiently. However, this observation does not provide a definitive explanation for why the connection fails to load in certain browsers while functioning correctly in others when connected to the router. I have tested it using different DNS servers in case it was a DNS failure, but that doesn’t seem to be the case.
I am currently subscribed to the Comcast/Xfinity residential next-generation speed tier.
It appears that the issue was caused by an extension, which is challenging to identify. The problem lies primarily on the development side of the extension I am using. Therefore, the issue has been resolved. Still find it ironic noone from netgear even responds to forums pretty disappointing just like the XR1000 that's been left to rust,