NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
raylo32
Aug 25, 2022Aspirant
CM700 time mismatch and login issues
I have been having trouble logging into the GUI for my modem. Lots of page not found and one "unsupported protocol" error. I read about that and it says a time discrepancy could be the cause. I hav...
- Aug 25, 2022
Well, it looks like it was that butt connector... or perhaps just needing to also clean and tighten the ISP side.
First, I connected the ISP cable directly to the modem outside and plugged the ethernet into a laptop. Accessed the GUI and correctables and uncorrectables were 0. So, I installed a fresh new splitter out there to the cable that runs to the network closet and tested similarly in there and success, errors still 0, so my cable is good. Phew.
So, I then reconnected CM700 modem output ethernet to the router to restore my network and everything is working... EXCEPT I can no longer log onto the modem GUI to check or monitor this going forward. On any device, wired or wifi. On any browser. I just get "can't reach page, took too long to respond" errors. Just like it had been for weeks lately until somehow miraculously I started being able to logon this morning. But that is just gone again? I really don't understand what is blocking me from reaching the modem admin GUI.
raylo32
Aug 25, 2022Aspirant
Well, it looks like it was that butt connector... or perhaps just needing to also clean and tighten the ISP side.
First, I connected the ISP cable directly to the modem outside and plugged the ethernet into a laptop. Accessed the GUI and correctables and uncorrectables were 0. So, I installed a fresh new splitter out there to the cable that runs to the network closet and tested similarly in there and success, errors still 0, so my cable is good. Phew.
So, I then reconnected CM700 modem output ethernet to the router to restore my network and everything is working... EXCEPT I can no longer log onto the modem GUI to check or monitor this going forward. On any device, wired or wifi. On any browser. I just get "can't reach page, took too long to respond" errors. Just like it had been for weeks lately until somehow miraculously I started being able to logon this morning. But that is just gone again? I really don't understand what is blocking me from reaching the modem admin GUI.
raylo32
Aug 25, 2022Aspirant
This is what windows network diagnostics says:
- FURRYe38Aug 25, 2022Guru
Have you factory reset the modem by pressing the reset button for 10 seconds then release with out the ISP coax cable connected the modem and 1 wired PC connected to the back of the modem?
- raylo32Aug 25, 2022Aspirant
No, I am afraid that will cause me to have to call Comcast to redo the provisioning. Don't want to do that. But LOL it just started responding again, who knows why? All errors are zero except channel 1 correctables which is 7. I am ready to call this one solved.
- FURRYe38Aug 25, 2022Guru
Looks like what you did with that one connector hopefully solved it.
Glad you got it working. Please mark your thread as solved so others will know. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router
Enjoy. 📡 - KitsapAug 25, 2022Master
Make sure you are not using 192.168.100.xxx as the base IP address for your router. Suggest 192.168.1.1 or 10.0.0.1.
- raylo32Aug 26, 2022Aspirant
We'll see. So far so good and the data look stable with few errors. But I did have one T3 timeout in the event log from last night. I'll keep monitoring it. No longer having any issue logging onto the GUI except on one laptop and then only on Edge browser saying "incompatible protocol". Works on Chrome on that PC. Edge browser and Chrome works fine to access the GUI on all other devices.
To answer the other poster, the modem IP is completely out of my router's subnet.
If I keep getting T3 timeouts I'll post another thread to chase that down. So far I have not noticed any more connectivity issues in use. But need more time to see if this is truly solved.
- FURRYe38Aug 26, 2022Guru
Glad you got it working better. Any line issues and such. Have the ISP take a look.
Enjoy.