New to using RSync so not surprised I cant get this to work.
I have two identical RN104 (FW 6.1.5) Units in different locations. I need the data to be mirrored and accessible from both locations. Using RSync I can pull data from Drive A to Drive B with no issues but not the other way round.
As stated in the title the connection tests ok but i get the following message after a few minutes on the failing backup job.
rsync: failed to connect to 81.140.XX.129 (81.140.XX.129): Connection timed out (110) (I Added the XX's for privacy) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
Service is running on the destination machine, have tried rebooting source unit, restarting service on source unit, updating DNS servers on both, pushing from the unit that the 'Pull' copy works on (i cant get push to work in either direction but its unimportant to me whether we push or pull) and shouting at it.
I'm guessing if the connection tests ok then the port forwarding on the router is correct.
Further testing has revealed that I can't get Readynas remote or replicate to start on one system. (Was trying to piggy back rsync over the VPN as suggested in another post here) I'm back to looking at the router but as said previously, I can pull data from the unit, I can access front view from remote sites.
Does anyone know which ports the cloud services require opening (although I understood no config was supposedly necessary)?
I'm still no further forward with this, but I'm sure the issue is related to the Cloud Services not getting a connection.
So Summary:
NAS Frontview is accessible over WAN My Second NAS can pull data via RSync from the problem unit over WAN BUT: The Problem NAS can not pull data from the second NAS Remote / Replicate wont start on the problem NAS (status says 'offline - Connecting' then after a while 'Services Offline' Could not attach device please try agian later)
Any ideas or is there a better forum to post this issue within?
Hello McMacca, did you find any solution? I'm having a different problem - unable to use ReadyCLOUD - but seemingly with the same root problem, getting this dreaded "Services Offline" message.
