NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
"Cannot connect discovery server"
I've just reinitialized my 516 (X-RAID) and I can connect as a user. However, the LED display is giving me this message and I cannot log into it as admin using a browser. I tried powering off and p...
First if you have user accounts set up, you should recreate them on the RN516, matching the UID/GIDs.
There is an issue with files owned by nobody/nogroup - the UIDs/GIDs don't match on the RN516. Most of my shares are fully open, and were set to nobody/nogroup (or sharename/nogroup) on the pto. I changed the ownership of those shares to admin/admin.
Then frontview backup job for each share (running one at a time). Enable rsync and NFS on the pro for each share.
Then set up an NFS backup job on RN516 for one of the shares, specifying the IP address of the pro as the remote host. (using the nas name often fails). Run it, then edit the remote system to use rsync, and run it again. Probably makes sense to start with a smaller shares.
Repeat for every share.
There is an issue with files owned by nobody/nogroup - the UIDs/GIDs don't match on the RN516. Most of my shares are fully open, and were set to nobody/nogroup (or sharename/nogroup) on the pto. I changed the ownership of those shares to admin/admin.
Then frontview backup job for each share (running one at a time). Enable rsync and NFS on the pro for each share.
Then set up an NFS backup job on RN516 for one of the shares, specifying the IP address of the pro as the remote host. (using the nas name often fails). Run it, then edit the remote system to use rsync, and run it again. Probably makes sense to start with a smaller shares.
Repeat for every share.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
