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, I guess I did jinx it.
Everything runs fine as long as you're not doing anything serious with ReadyShare. But as soon as you try to write more than a couple of thousand files, the file system goes slower and slower until it simply times out with various weird error messages. If you're trying to read with a different process while you're writing, the read stream will be very choppy indeed. All other network traffic will continue as normal for a while, but if you keep throwing a lot of writes eventually the whole network will stop working. Only recourse is power-down, as the Netgear admin app stops responding as well.
If you have a big directory tree to copy, put the copy on pause every five minutes or so, letting the processor do whatever it wants for a couple of minutes.
This is just a rubbish implementation, dozens of bugs in the UI alone.