NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAXE500 using readyshare cause router to malfunction and causes PC net adapter to give weird errors
firmware version: Firmware Version V1.0.10.86_2.0.40 I have a new RAXE500 that i have hooked a USB 3.0 4Tb drive upto for use in backing up my PC. I am able to access the drive over the network t...
now that i seem to have the ipv6 tunnel situation sorted out, the router seem to be behaving itself, at least for now. Is it possible that trying to use now disallowed 6in4 settings on the 6to4 ipv6 page was the cause of ALL my issues?
Hard to say, though from the way that readyshare is implemented, it may be worth doing a local test on the external hard drive.
Basically if you have another drive with around 4TB or more of free space, then moving 4TB of data to or from the drive, and seeing if it hangs for some time.
One limitation with some routers, is related to how long they will wait for a drive to respond to an IO operation. For example, if a drive if having issues where at certain points, it will struggle to read or write data, the router may not wait long enough for the drive's ECC to respond with the data, especially in cases of drives that do not have a time limited error recovery.
I currently use my RAXE500 with a cheap SATA to USB 3.0 dock, and a 4TB WD Red (CMR) hard drive, and it has worked well with windows backup, as well as copying many large files, and even launching programs saved on the network storage (great for games that store their gamesaves in a subfolder, so far, it has handled tasks like that really well.
I actually tested the drive before hooking it up, since it had been sitting a while unused. the tests came back with zero errors and no bad blocks
the drive itself had no issues, it was the router that was misbehaving, and then only when readyshare was in use. the drive i am using is essentially a 3.5 sata HDD put into an enclosure by Seagate, and the dock portion of the unit provides the sata to usb. Seagate had various connection docks that could be purchased for the drive such as firewire, thunderbolt, etc. the USB 3.0 dock it came with was always enough for me.
now that the ipv6 issues i was having have been corrected, the router seems to be behaving itself. I spent the day hooked up to the router via ethernet, which meant stringing a cable half way across the house. I can't keep it that way because it presents a trip hazard. my mom keeps complaing that if she trips she will break her hip, so i am going to call the current round of tests done. the wifi portion of the router seems to have stabilized as well. no more of the weirdness described in my op.
it has been several weeks now, and the readyshare seems to be stable as well as the router. no issues to report. switching/correcting the ipv6 tunnel settings seems to have solved all of my issues.
So what did you do exactly to fix the IPv6 6to4 Tunnel problem?
Be aware that there is new FW available for the 500:
There isn't an issue with hanging. The issue is the router starts wigging out, as described in my previous posts. Unplugging the drive and then rebooting the router solves the issue. The drive is listed as supported on every other netgear router. however, the raxe500 was not listed on the support page. in fact, none of the 6e router models were. The secondary issue i mentioned in my op, was in fact, not caused by my system, or my router, but by my Epson printer. Microsoft changed the way network printing works in win11 22h2. There are support documents about it. Epson has not yet updated their driver software to accommodate the change. So every time my printer software or windows did a check-in with the printer to see if it was ready to print (or whatever) the net adapter error was generated. simply changing a windows registry entry or two so that windows reverted to the old way of doing things solved the net adapter error. Making the change also caused the printer to start working properly again (which i had not noticed it was not, until I actually needed to print something out).
