NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
raden10
Aug 19, 2016Aspirant
Rsync over SSH - cannot connect to remote
Hello!
I am trying to push data from a local ReadyNAS 202 to a remote ReadyNAS 102 accross the internet using a backup job initiated on the local 202.
I get "Unable to connect to host - 7077010011" if I test the remote destination connection.
If I run the job I get:
"Backup Status: Fail: failure during copy.
Failed to run rsync, return rc 65280 (255)
'rsync' command returns rc=65280
ssh: connect to host X.XXX.XX.XX port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]"
(where X.XXX.XX.XX is the 102's WAN IP address).
Both NAS's are on 6.5.1. Both have SSH enabled.
I am able to log into the remote 102, both locally and across the internet, with pUTTY and an SSH user I have set up. This is the same SSH user I am trying to connect to run the backup job. I am able to log in using a public/private key combo, Shell Access is "allowed," "Rsync only" is unchecked,
I have installed the public key for the 102 on the 202, both for the admin user and for the SSH user.
I have set up my router (a BT hub 3) to forward port 873 to the LAN IP Address of the remote 102. It is translating to port 22 on the 102.
The Destination part of the backup looks like this:
Type: remote
Name: remote: Rsync over Remote SSH
Host: X.XXX.XX.XX
Path: Documents/
Login: <SSH Username>
The overall SSH setting on both boxes is "Enable Password Authentication - No."
The "Documents/" share on the target 202 is set to "Allow Anonymous Access - Yes", "Everyone - Read/Write," no Hosts or DFS defined, and "Hide this folder: No."
I am totally stuck... any help is much appreciated!!!!
I finally got this working!!
I had two problems with my setup:1) I was using the WAN IP of the ReadyNas - I should have been using the WAN of my Router! Doh....
2) I had to put /data in front of my Remote Path - eg /data/Documents/
As soon as I did both of these things everything works via the frontend. :)
Hope this helps someone...
8 Replies
Replies have been turned off for this discussion
- raden10Aspirant
I finally got this working!!
I had two problems with my setup:1) I was using the WAN IP of the ReadyNas - I should have been using the WAN of my Router! Doh....
2) I had to put /data in front of my Remote Path - eg /data/Documents/
As soon as I did both of these things everything works via the frontend. :)
Hope this helps someone...- mdgm-ntgrNETGEAR Employee Retired
Great! You can now mark as the accepted solution your post that answered your own question!
- StephenBGuru - Experienced User
I believe you need to forward port 22->22, not 873->22
- raden10Aspirant
Thanks for the replies!
I have set port forwarding on the router that the 102 is sitting behind to 22-> 22 now - but still unable to connect, although I can connect remotely via PuTTY using a key pair as before.So the 102 is listening, I just can't get the 202 to connect to it over SSH.
Should I have a passphrase on the key combo? At the moment I do, so if I log into the 102 remotely via SSH I have to put in a password.
Do I need to define Hosts in my shares or something like this? Or some other user permissions?
Related Content
NETGEAR Academy

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