NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
CM1100 and Mesh 6 system not working after power failure; all lights working fine
Greetings! - CM1100 modem and MR60 mesh router (2 satellites) installed June of 2021. Comcast is my ISP in the PNW and is relatively reliable historically. - Over last 4 years, I've had to p...
Ok you got in. This is good.
Yes, two LAN ports however one will only be active with your ISP. Usually LAN1 is active. However seems you have LAN2 working.
Looking at your cable connections data, looks good and power levels are with in specs: https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
Correctables and Un-correctables should remain zero or may some some slow up tickin value numbers, however should not see major high values here.
The event logs looks bad though. Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
I think I may have stumbled upon an incorrect configuration that's been present for awhile. I have no idea if it has anything to do with the recent issues.
In reading my user manual for the CM1100, it appears while there are two LAN ethernet ports, only one is functional at a time in normal circumstances (aside from port aggregation, which I doubt I need or use). Ever since issues I had with the router a few years ago, I've been utilizing wifi on the desktop computer, even though the ethernet cable has been connected directly to the modem. I always wondered why this didn't work but didn't take the time to dive into it since the wifi worked well.
Tonight, I removed the ethernet cable that had connected the desktop computer to LAN 2 in the modem and plugged it into the second ethernet port on the router instead. Now, my desktop has hard-wired ethernet and the wifi works (after two additional power-cycles of the modem and router).
Again, not sure this has anything to do with my issues recently, since these cables have been in these positions for years.
I am going to pick up a new modem tomorrow when I am out, as I'm starting to think it's worth having a backup around.
If the logs provide any helpful insight to you, let me know. I really appreciate all your assistance on this!
I would love to get that info but 198.168.100.1 has not been working, at least since 12/7. That was the first time I'd tried it in many months, maybe over a year. I'm not sure why it's not working.
My internet is down again today. I swapped out the old coax for a brand new one and still not working, so I'm back on the hotspot. I will try to get a new modem today or tomorrow but I am honestly wondering if even that will work, considering things seem to work fine for a variable amount of time (hours to weeks) and then fail again. This is very puzzling.
If you have any ideas of how to regain the ability to access router info, I will try those. I came across someone else on these forums that had that difficulty but never got a solution that I could find. (I did try accessing things once the internet was running properly after 12/7 and still couldn't get in. Tried two different browsers, too.)
Try disconnecting the modem from the ISP coax cable. Then press the reset button in back of the modem for 15 seconds then release. Give 1-2 minutes. Make sure you can connect to that IP address on the modem. Then reconnect the ISP coax cable to the modem. Give about 1-2 minutes. Log back in and try to connect the logs requested.
I can leave the computer on while I reset the modem? Same with router?
I'll give this a try.
Yes.
I unplugged the coax cable from the modem and hit the reset button on the modem for 15 seconds. I waited about 10 minutes. I am unable to connect to the IP address 198.168.100.1. I also tried the alternative IP (10.0.0.1) and get the same messages as below.
Error message from Firefox:
I receive a similar message from Chrome: