NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000P crashes with Readyshare usage
Nighthawk router running fine with 2.4 and 5GHz users. Hook up 2 TB USB drive (Western Digital, nothing exotic) formatted as NTFS (probably MBR, but not sure). Basic readyshare read/write with driv...
Well, I don't want to jinx this, but I believe all the above issues have been resolved. I've been running for 5 days now with 100% functionality, no reboots, and a more responsive/reliable administrative app (NetGear's Genie on the PC).
The big change: doing a factory-reset on the router and manually reconfiguring it to my needs (i.e., not doing a backup/restore of settings).
Seems like something somewhere in the router's little mind had gotten corrupted, causing all kinds of confusion.. What may have caused this was its moving to a totally new network (when it was new, it was on one ISP...then it got moved to a new ISP without making any changes). Note that in during all my wild-goose chases I had updated the firmware, and the confusion persisted because the problem was buried somewhere in the configuration/settings data.
So the morals of my story are:
- When troubleshooting, start with a factory refresh and brand new settings
- When moving a router across networks, see #1
Well, it only took a day to demonstrate that Nighthawk itself is still failing.
Failure mode is interesting:
- Runs for days as long as you don't use the network
- Most common failure is a minute or so after client PCs come out of sleep/hibernate mode (network runs fine for the first few seconds)
- When the failure occurs, (1) pings to router are fine, (2) pings to 8.8.8.8 time out at all clients, and (3) the readyshare disk is spun up.
The reason for #3 is either (1) some weird Netgear bug spontaneously making a request of the disk, or (2) Windows networking making some sort of request as part of refreshing its network map about connected shares. Note that this symptom occurs on three separate disks and controllers I've tested, so I don't suspect the drive itself.
Well, I don't want to jinx this, but I believe all the above issues have been resolved. I've been running for 5 days now with 100% functionality, no reboots, and a more responsive/reliable administrative app (NetGear's Genie on the PC).
The big change: doing a factory-reset on the router and manually reconfiguring it to my needs (i.e., not doing a backup/restore of settings).
Seems like something somewhere in the router's little mind had gotten corrupted, causing all kinds of confusion.. What may have caused this was its moving to a totally new network (when it was new, it was on one ISP...then it got moved to a new ISP without making any changes). Note that in during all my wild-goose chases I had updated the firmware, and the confusion persisted because the problem was buried somewhere in the configuration/settings data.
So the morals of my story are:
- When troubleshooting, start with a factory refresh and brand new settings
- When moving a router across networks, see #1