NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Dan_0
May 13, 2025Aspirant
Can't Login to my Account - No matter what I do!
I can't Login to my Account - No matter what I do. Everything seems to go fine (resetting password, etc.) And at the end, when I think I'm about to get in, it comes back with the message... "S...
- May 14, 2025
You need to factory reset the router with the PC and web browser and setup from scratch. First disconnect the router from the yellow WAN port in back.
Press and hold the reset button in back of the router for 15 seconds then release:
https://kb.netgear.com/9665/How-do-I-perform-a-factory-reset-on-my-NETGEAR-router
Have one wired PC connected to the back of the router:
https://kb.netgear.com/22697/How-do-I-install-my-NETGEAR-router-using-the-router-web-interface
Walk thru the setup wizard, skip the part where it says try again if the internet detection fails, manually set up the router path. Once at the home screen, reconnect the WAN port in back to the ISP service.
Dan_0
May 16, 2025Aspirant
So before I do a factory reset, I decided to call customer support. I was on Hold for over 30 minutes before she picked up. She told us that she would have to transfer me (even though I had already told the system which product I was calling about). Anyway, it was at least another 30 minutes before someone came on the line.
This guy was very patient and we went through all the steps and I finally got into my router with the ip address, but it was not a clean process. Not easily repeatable. I was receiving the error message, I backed up and tried again and managed to get in.
My question is, why is it taking me to their website so that I can access my Router with the ip address?
Is that how they do it now?
FURRYe38
May 16, 2025Guru - Experienced User
Could have avoided all that and saved time with the FR.
There is a bug in there latest FW version that causes this. I saw this as well on my RAX50v2. FR resolved it and have not seen it again.
If you see this happen again, try a FR as previously described.