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.
Kitsap - Thanks for the additional info. I guess I should've been more clear. I didn't leave my Laptop hooked directly into the modem for long - I was only doing that for triage to confirm my router wasn't blocking it somehow. My steady state network leverages my router (with firewall) - so I didn't bypass my home security for long.
That being said, my router doesn't appear to be the issue here - it's separate from the netgear modem and I can see everything on it. I have full control over my network in this regard and can set it to whatever I want much like yourself. Oddly enough though, I see the same behavior from my router's Public Internet IP address as I do when i tried my laptop (when it's hooked in directly) - the modem starts with 192.168.100.1 - then it flips to 192.168.100.10 (for a second) then it flips one more time to the 75.x.x.x IP from comcast and then I can no longer get into the Modem UI at 192.168.100.1 even though I have internet service. As far as I know, the modem has no security on it whatsoever (beyond admin password that I did change away from default by the way) - so I agree, hooking directly into it is no bueno even though I do have a firewall on this machine as well. (I checked my local logs as well with no blockers showing.)
I have cleared cache and tried different browsers on multiple windows machines as well as iPad/iPhone - which is why I tried bypassing my router (temporarily as well). When the modem COAX is disconnected, I can login to it on 192.168.100.1 - with no issues - and for a long time - the UI is fairly responsive, and I can get to all the modem settings when it's in this state. I also looked for some ebedded website configs options to see if some sort of DNS redirect option existed and was enabled - but I don't see anything. As soon as I plug the COAX back into the modem - the ip's flip (as describe above), and then I can no longer get into the modem. This behavior happens whether i go direct to the modem (temporarily) or through my usual router/network config.
Prior to the recent Comcast outage in my area, I was able to see the netgear Modem just fine from my home network so I am not really sure what changed.
If it matters - my home network is 192.168.1.x (with the router being 192.168.1.1) - but this shouldn't really matter as it all communicated correctly. As I understand it, even though I configured Google DNS servers on my router, Comcast will ultimately route it back to their DNS when packets leave my network. They do some goofy things with "shaping their traffic" on the back end that nobody in Xfinity support would truly explain. For giggles, I did try reverting my DNS servers to the Xfinity ones - with no change in behavior.
Additional information.
From a Windows computer, as an administrator, use the Command Prompt or Power Shell to issue the command: IPCONFIG /ALL.
The return information will show the IP v4 and v6 address of the computer, lease information, and the IP address of the gateway (should be your router). It will also list DNS servers as your router.
Within the router configuration, I recommend you enable IPv6. I am certain Comcast supports it across their network.
For DNS servers, I use a series of Open DNS, Comcast, and Next DNS. These work well for my location. See attached snips.
