NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
_frantic_
May 19, 2016Aspirant
Using ReadyNAS Replicate with OS 6.5.0
I am using Replicate to backup from my RN312 to a RN104. Both devices have been upgraded from latest 6.4 to 6.5.0. I am not able to get Replicate working again. Is there some documentation? ...
- Aug 03, 2016
Hi _frantic_,
Since you've performed FD, wait for the resync process to complete then add 8.8.8.8 DNS in the active NIC of your system. Once this is done, try to login again your old ReadyNAS Remote/Replicate ID credentials and see if it will accept it.
Kind regards,
BrianL
NETGEAR Community Team
kohdee
May 19, 2016NETGEAR Expert
1) We got rid of Remote in 6.5.0.
2) Replicate has always used Remote IDs and not ReadyCLOUD or NETGEAR accounts.
3) ReadyCLOUD and Replicate are only IPv4 service.
4) If you at some point you logged into ReadyCLOUD, and then you recently upgraded your ReadyCLOUD account to a NETGEAR account, try your NETGEAR account password with the Replicate account on replicate.readynas.com
- _frantic_May 20, 2016Aspirant
Thanks for those infos.
1) I am trying to understand: since 6.5, I have to activate ReadyCLOUD on my devices instead of ReadyNAS Remote. ReadyCLOUD uses MyNetgear credentials. The service seems to know about a connection between my MyNetgear account and my ReadyNAS Replicate ID, correct?
4) strange, but you were right: login to replicate.readynas.com does work with my Replicate User (Replicate ID) + password from MyNetgear account.
Backup jobs do not work. Both schedules and manually started.
Example error message:
[2016-05-20 16:45:37] [Error] Connect error code: -501 [2016-05-20 16:45:37] [Error] Please check network connection between devices
I can see both devices on replicate.readynas.com / views / network.
They are on the same network, same switch.
Perhaps a problem with the service (?).
"wait and see" might be a good idea.
- kohdeeMay 20, 2016NETGEAR Expert
_frantic_ wrote:
Thanks for those infos.
1) I am trying to understand: since 6.5, I have to activate ReadyCLOUD on my devices instead of ReadyNAS Remote. ReadyCLOUD uses MyNetgear credentials. The service seems to know about a connection between my MyNetgear account and my ReadyNAS Replicate ID, correct?
4) strange, but you were right: login to replicate.readynas.com does work with my Replicate User (Replicate ID) + password from MyNetgear account.
Backup jobs do not work. Both schedules and manually started.
Example error message:
[2016-05-20 16:45:37] [Error] Connect error code: -501 [2016-05-20 16:45:37] [Error] Please check network connection between devices
I can see both devices on replicate.readynas.com / views / network.
They are on the same network, same switch.
Perhaps a problem with the service (?).
"wait and see" might be a good idea.
1&4) ReadyNAS Remote functionality rolled into ReadyCLOUD. For RAIDiator devices and OS 6 devices before 6.5.0, you can continue to use Remote client, but for OS 6.5.0, you should be on ReadyCLOUD client. ReadyCLOUD and ReadyNAS Remote are not compatible with each other so you cannot install and run at the same time. For whatever reason, MyNETGEAR updates the ReadyNAS Remote ID + ReadyCLOUD password to match the MyNETGEAR account.
Regarding your backup jobs failing, it could be as simple as restarting both devices. Otherwise, is it doing a local LAN connection or trying to use P2P?
- _frantic_May 21, 2016Aspirant
kohdee wrote:
1&4) ReadyNAS Remote functionality rolled into ReadyCLOUD.I have never used ReadyCLOUD in the past and I have no plans to do so.
I activated it for the first time ever because Replicate would not work without it.
Can I use Replicate while ReadyCLOUD is in OFF state? Seems to be possible.
Can I remove my devices from ReadyCLOUD and still use Replicate?
kohdee wrote:Regarding your backup jobs failing, it could be as simple as restarting both devices. Otherwise, is it doing a local LAN connection or trying to use P2P?
Rebooting did not help:
[2016-05-21 14:27:22] [Info] p2p connect to nas-6D-EE-EA_*** in *** network [2016-05-21 14:27:22] [Error] Unable to connect to nas-6D-EE-EA_*** [2016-05-21 14:27:22] [Error] Connect error code: -501 [2016-05-21 14:27:22] [Error] Please check network connection between devices
I have set up an extra ourly schedule for testing. Still hoping this will get fixed on the backend service.
- _frantic_Jun 15, 2016Aspirant
kohdee wrote:3) ReadyCLOUD and Replicate are only IPv4 service.
The strange thing is: ReadyCLOUD and Replicate will not work at all on my devices, when IPv6 is disabled. I get messages Offline and Services Offline:
Anyway: even with IPv6 enabled, Replicate still does not work from my main RN312 to the backup device RN104. (It does work in reverse direction.)
From this point on I do not know what to do other than factory resetting the RN104.
I will also try to avoid IPv6 from now on.
My suspicion is, that the use of IPv6 was not a good idea at all.
I activated IPv6 in addition to IPv4 in 6.4.0. Seems to be nonreversible from the beginning on (for me as a Replicate user).
- Boston_RobJul 29, 2016Aspirant
Reimaged my NAS and it works again. (factory reset)
- _frantic_Aug 03, 2016Aspirant
Okay, I did a Factory Reset on my ReadyNAS 104.
I was offered to upgrade from 6.5.0 to 6.5.1, so did I.
Same problem as before - the device can not register to ReadyNAS Replicate. I get an invalid username/password message and then this:
ReadyNAS Replicate seems to be unreachable.
What is causing this? Do I need any special firewall clearance or port forwarding for Cloud Services?
Do I have to activate special services on my device? Which log files should I check?
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!