NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
CM1000v2 cannot access 192.168.100.1
How many times did you have to perform the factory reset? I am having the same problem - performed a factory reset as specified in the note - no change in behavior.
rkalinka wrote:
Kitsap - I don't think my Netgear modem has those configurations available to it as it's only a Modem (not a router). When I get a minute do more testing on my environment, I'll see if there is a way to drop in a static route on the MODEM (but I don't think so).
That being said, I could always try to put the static route you mentioned on my ROUTER to see if that fixes the issue - certainly a good idea. That being said, I was having the same URL failure problem when I hooked up my laptop directly to the modem (bypassing the router completely) so I doubt putting a static router on my ROUTER will fix it.... but, I will chase this down as anything is possible and I would like to get it working again.
The static route for access to your modem is a configuration you apply to the router.
rkalinka did you ever figure out a resolution to this issue? I'm having this exact same issue. Can reboot the modem without the coax plugged in and can access the web configuration interface, but once I connect that cable and internet access is restored I can no longer access and/or ping.
I'm also on Comcast/Xfinity. My internet connection and bandwidth are working as expected otherwise, however I have been having intermittent internet drop issues over the past week and looked further into the modem where I discovered this issue. I suspect that the modem may be having internal issues.
Thanks!
Setting up a static route within your router has helped some overcome this situation.
See attached.
Kitsap - I don't think my Netgear modem has those configurations available to it as it's only a Modem (not a router). When I get a minute do more testing on my environment, I'll see if there is a way to drop in a static route on the MODEM (but I don't think so).
That being said, I could always try to put the static route you mentioned on my ROUTER to see if that fixes the issue - certainly a good idea. That being said, I was having the same URL failure problem when I hooked up my laptop directly to the modem (bypassing the router completely) so I doubt putting a static router on my ROUTER will fix it.... but, I will chase this down as anything is possible and I would like to get it working again.
Kitsap and rkalinka thank you very much for your replies. Adding a static route for this in the router did end up resolving my issue. Interesting, because this was not previously required before for me to access the modem page. Something must have changed recently on Xfinity's end perhaps.
Should be more able to resolve my intermittent internet issues now more easily with visibility into the modem - thank you again.
rkalinka wrote:
Kitsap - I don't think my Netgear modem has those configurations available to it as it's only a Modem (not a router). When I get a minute do more testing on my environment, I'll see if there is a way to drop in a static route on the MODEM (but I don't think so).
That being said, I could always try to put the static route you mentioned on my ROUTER to see if that fixes the issue - certainly a good idea. That being said, I was having the same URL failure problem when I hooked up my laptop directly to the modem (bypassing the router completely) so I doubt putting a static router on my ROUTER will fix it.... but, I will chase this down as anything is possible and I would like to get it working again.
The static route for access to your modem is a configuration you apply to the router.
Just curious, what brand and model routers do you have connected to the CM modem?
Kitsap - Static route did the fix, but I had to do it a little differently than what you showed in your screenshots because my modem and router are separate devices. BUT - adding in a static route to the modem admin page going out the WAN interface fixed the issue.
After some asking around, it appears that XFINITY has a DOCSYS 3.1 modem script that runs once the modem attaches to the XFINITY ecosystem. It's pushed by XFINITY and nothing that you have control over. No idea why it's suddenly a problem, but it does explain a bit of the behavior.
In all cases, the static route was the fix and I can see everything now.
