NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RAX45 Config corrupted after firmware update
Prompted to do firmware update on Netgear admin page. After kicking me offline I noticed the default SSIDs pop up instead of my configuration. Hardwired into my router and lo-and-behold, my settings ...
A backup is always a good plan to have. But sometimes firmware changes enough a reset is needed because the old settings can cause issues.
There should be a little more warning in those cases but it happens. Again why a backup is always nice to have.
Was able to bypass the Nighthawk app prompt and console in. No DHCP from the modem whatsoever, so no IP no internet passthrough. I reflashed the new firmware and same result. Rolled back to the former firmware .chk to same result. Factory reset the hardware too, same result.
So I ordered an AX12 router and it immediately did the same behavior (no internet) during setup. Upon factory resetting the modem once more and consoling into the new router I found that there was internet passthrough showing. Once I tried connecting my laptop to the WLAN the modem flops back to the dual LAN solid amber LEDs and gives showed Not Connected (Internet) on the console page. So pretty much anytime something wireless connects it'll nerf the modem and crash the whole setup.
I'm convinced now that the Router firmware update pushed the modem off the cliff, and/or the ISP provided ones created for the modem compounded the problem. In any case, I'm super disappointed in the Netgear experience and have never seen this before. This hardware combo didn't last me more than two years. I'm a seasoned IT professional with networking experience so this one really grinds my gears.
So I ordered an AX12 router and it immediately did the same behavior (no internet) during setup. Upon factory resetting the modem once more and consoling into the new router I found that there was internet passthrough showing. Once I tried connecting my laptop to the WLAN the modem flops back to the dual LAN solid amber LEDs and gives showed Not Connected (Internet) on the console page. So pretty much anytime something wireless connects it'll nerf the modem and crash the whole setup.
I'm convinced now that the Router firmware update pushed the modem off the cliff, and/or the ISP provided ones created for the modem compounded the problem. In any case, I'm super disappointed in the Netgear experience and have never seen this before. This hardware combo didn't last me more than two years. I'm a seasoned IT professional with networking experience so this one really grinds my gears.
if 2 routers have the same issue, it tends to indicate the modem.
You have the CM1100?
Just an fyi, most ISP's only support 1 device connected to the cm1100 even though it has 2x ethernet ports.
So make sure you only have 1 device connected to it.
If you have/had more than 1 connected, power off the modem and the router for 2 minutes (disconnect the coax from the modem)
Wait a bit and then power the modem on. Give it a couple minutes to fully boot.
Then connect the router's wan port to the modem and power it on.
Make sure to only have 1 device connected to the modem
- Appreciate the note. Didn't know about that limitation with simultaneous LAN connections on the CM1100. Agreed with the conclusion that next variable is the modem.
So I followed your instructions step-by-step and still no go. I can sustain an IP for about three quick Google searches then limited connectivity then no internet. This is the same as what I was able to accomplish before unfortunately.
I have a CM2000 on order. I can buy my way out of this for this time, hopefully it gets me moving. Either way I will put Netgear on my s***list in case the firmware bunks my hardware again.
I'm open to any other ideas you or the community might have. I'm perplexed short of wiping everything out and starting blank slate one last time. I'll let you know how the CM2000 goes.When its working, get a screensnip of the cable connections page and event logs from the modem. Also do it when it goes down.
That'll tell us a lot of info on the connection back to the ISP
Thanks again for digging into this with me. It was kind of tricky to tether into the router to Admin the modem and keep the one connection-only condition going, but I did what I could here. When I triggered a failed state on the modem - which I've narrowed down to connecting any device to the WiFi - I pulled the connections from both Netgear devices and immediately tethered into the modem again. Pulled failed state logs and Cable Connections page.
- I had originally seen an almost auto-drop behavior before. This was because I renamed the defaulted configuration's SSIDs back to the original name/password from prior firmware update on the RAX45 Router, so multiple devices were reconnecting and crashing the signal. Same deal with new SSIDs and only my phone or laptop know them now. Auto-connect is disabled on both devices.
Is it normal to see an "Access Denied" Connectivity State (occurred during failed state)? Or is that a byproduct of the hot swapping of cables I was doing mid-stream?
Also, the logs are showing sync errors. It almost presents like when switch hardware loses its NTP server timing. I've tried connecting using my Samsung notebook and Samsung S23 to WiFi so I'm confident I've ruled out some crazy systemtime or Windows Date/Time off sync issues on my PC. FWIW, I have seen Windows fudge Date/Time before on this PC but it's really uncommon and internet works fine when physically tethered to either Netgear hardware.
Windows Event Viewer logs show DNS loss during web searches (e.g., google "Tacos", etc.) >> limited connectivity >> WLAN kaput.
(Last) Warning - System:
WLAN Extensibility Module has stopped.
Module Path: C:\WINDOWS\system32\IntelIHVRouter06.dll
Hotspot hasn't been up to snuff w/ Comcast ISP-fed for work activities this week, so I'm going to nuke everything and swap in the CM2000 + RAX120 (as opposed to CM1100 + RAX45, or + RAX120).
Any final input before I hit the [Reset] buttons?
Failed state - had to pull out of the router and tether into the recovering mdoem (one connection only!)
Previous working state (not connected to wireless)
Logs from post-failed state - very similar to functional state logs
Recovered state (not connected to wireless)