NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Since Windows 11 Update, Unable to Access RNDuoV2.0 Dashboard/Admin Screen
Dear Forum Members It's been a good while since I have been on this forum, about March 2023, and as you can imagine I have run into some technical problems that I cannot work out for myself and would be grateful for any help or advice that maybe passed my way. But first, my equipment: 4 x ReadyNAS Duo v2 running firmware 5.3.13 (including 1 failing RNDuo v2) 1 x ReadyNAS RN102 running firmware 6.10.10 1 x ReadyNAS RN104 running firmware 6.10.10 1 x PC running Windows 11 Pro Problem 1) I believe that ever since my Win11 O/S was upgraded, with a minor patch or fix, I have been unable to access my RNDuo v2's dashboard/admin screens. Back in March 2023, I could access my RNDuo v2's admin screens by installing the Apache2_2.2.34-arm-0.0.1.bin utility on all my V2's. However lately, I have totally lost this “admin access” facility, despite trying all of my five browsers, i.e. Firefox, Opera, Chrome, Edge and AVG. I can still access the admin screens of my RN102 and RN104 without any problems, apart from the initial warning screens. So I was wondering, is there a windows app/utility or setting that will allow me to regain access to my V2's admin screens. Problem 2) One of my RNDuo v2's has a partial failure, I think the internal network card is having problems because no other device on my network can communicate with this device anymore, even though it can still be seen by but not accessed by RAIDar v6.0. I was wondering which one the following two solutions would stand the most chance of success: a) Connect an external HD to the front USB2.0 socket and backup all my data to the ex HD, with the hope that I can stream that data to one of my other RN devices. b) Try to buy another RNDuoV2.0 (which are now extremely rare) and put the two WD Red Plus HDs, currently in the failing V2, in the new V2. Nevertheless, I am willing to try any other solution that forum members can think of, rather than use my own cumbersome ideas. Problem 3) Which is not really a problem but a search for some extra knowledge, I have just installed two 4TB WD Red Plus HDs in my RN104, both disks are now formatted and running as Raid 1. What will happen if and when I add two more (unformatted/unused) WD Reds to my RN104? Eagerly awaiting replies UK Bob
RR4360S new dropbox changes require an API header
We have a ReadyNAS RR4360S on the latest firmware (6.10.10). Dropbox has recently made changes to the team folder configuration. This affects the Dropbox API in the readynas OS to not be able to see team folders anymore. A small change needs to be made to the Dropbox API Header to fix this: "Dropbox-API-Path-Root" needs to be added to the header. Would it be possible to make the change and add it to a new firmware update? Here is a more detailed explanation from Dropbox: Up until now, all Dropbox API calls defaulted to the root of a user's account. Under our new folder structure, a user's account contains a folder with their name and all files owned by that person go into that folder. Any "team" folders (think of them like network shares or company managed folders) are in the root alongside the individual's folder. In reference to the screenshot above.... What is happening is you are dropped into the "Lauren Winslow" folder and can't go back to root to see the "Sales", "Finance", or "Assorted Team Content" folder. A small change to the path structure in the integration should resolve the issue. "Dropbox-API-Path-Root" needs to be added to the header. Details here... DBX Team Files Guide - DropboxReadyNas 104 500 error
Hey Folks! So i forgot my password to get into the readynas (password did not work). I did a os reinstall to reset the password back to default. now when I log in and it asks for the password it seems to work then i get this error. Now when I go to netgear RAIDar and it prompts for the password I try the default and I get this. Hoping someone can help me figure this out!!!Ready NAS RN212 UNABLE TO CHANGE ADMIN PASSWORD
I had my Ready NAS RN 212 disconnected for a few months. I hooked it back up but forgot my login and password. I tried the "admin" login but it would not work. I assumed I changed the "admin" password. I accessed the Boot Menu and did an OS reset. After that was complete I was able to access "admin" using default password. I accessed my account and reset my account password. I am now able to my account. The issue now is that when I try to change the "admin" password it will not change. I can enter the Current password field, click in the New Password field and it auto moves to Re-Enter New Password. The New Password field is blocked, nothing can be entered in this field. I tried on my account and on the "admin" account, both did the same thing.Scrub errors
I just checked the scrub status (btrfs scrub status /data) for an ongoing scrub and see this: total bytes scrubbed: 19.68TiB with 144 errors error details: csum=144 corrected errors: 0, uncorrectable errors: 144, unverified errors: 0 This is on one of my backup NAS, and a few backup jobs were run while the scrub was ongoing, if that might have anything to do with it. I've never seen scrub errors before. Is there a way to see where these errors occurred? I would think an rsync incremental backup job (pull) would fix any corrupted files, or is there a reason I need to manually tell it to do a complete backup next time?
EDA500 gone, now all shares on main NAS don't appear
I had two EDA500s connected to my 316. They both messed up, at the same time resulting in data loss. Now......... in Windows Explorer, I have always seen the old shares names appear in the list. Today I tried to delete the EDA500 and the result was: No shares except for one now shows up in Windows Explorer. Even ones on the main NAS that are folders in /data. There are about 5 shares in /data/ that SHOULD be appearing. If I do ls on /data, they are there. In the UI, there are no shares at all whatsoever. So I am guessing something is out of whack with the smb config. What can I do to f ix this?
