Backup Station NAS to NAS using SSH, QTS 4.2
-
- Starting out
- Posts: 10
- Joined: Sat Jan 31, 2009 12:48 am
Backup Station NAS to NAS using SSH, QTS 4.2
We're using QTS 4.2. I need to replicate some shares using the Backup Station NAS to NAS, but using SSH over open Internet (secured). I have done this NAS to NAS previously in a private network using direct rsync. No problems with that. So, I have tried to get it setup where the source is using port 22 SSH to connect to the remote NAS with NAS to NAS, but I can't seem to satisfy the test connection. Strange. I can make a merely successful SSH connection to the remote NAS as a side test remotely. All good there, the SSH connection server is certainly working on the remote NAS. It would appear that there is some trick to this? I tried the Remote Host Test with ports 873 (default), and 22. I setup the Options first for the SSH connections. No combinations seem to work? Anyone out there able to make this work???
- AcerTravel
- Know my way around
- Posts: 208
- Joined: Wed Jul 20, 2011 4:03 pm
- Location: Going From Mars To Saturn
Re: Backup Station NAS to NAS using SSH, QTS 4.2
Hello,
Please, post your configuration here.
Please, post your configuration here.
TS-212
TS-453PRO 8GB + UX-500P
TS-453A 8GB + UX-800P
TS-453PRO 8GB + UX-500P
TS-453A 8GB + UX-800P
- jorhett
- New here
- Posts: 9
- Joined: Tue Jan 26, 2016 2:21 pm
Re: Backup Station NAS to NAS using SSH, QTS 4.2
I had the same problem. There is no configuration because you can't save the client unless it succeeds. Best we could do is show you a screenshot of it saying the service isn't enabled on the remote side.
-
- Getting the hang of things
- Posts: 70
- Joined: Fri Apr 04, 2008 7:53 pm
Re: Backup Station NAS to NAS using SSH, QTS 4.2
I just did this, so I might have some input.
Nas 1 is behind a NAT firewall where ISP provides public IP. Nas 2 is behind a NAT firewall where ISP provided NAT:ed IP. If ISP provides NAT:ed IP, there will be problem with incoming traffic (i.e. backup from Nas 1 -> Nas 2 will never work). You can check if you have NAT:ed IP by checking your routers outside address and compare with what whatsmyip.com says. In my case I had 10.188.xxx.xxx on my router's outside and 95.155.xxx.xxx on internet. Even if you use DDNS service like myqnapcloud or dyndns, it won't work.
After telling my ISP I needed a public IP, I had the same address on my router as on internet.
I then forwarded ports 22 and 873 to the Nas's internal ip address.
I set up the Nas to Nas and the test worked great.
I chose folder to replicate on local site and on remote site.
I did set up a schedule.
When the job was added, I removed the forwarding rule for 873 in the firewall.
Now, jobs are running smoothly without errors.
If I have to add another job, or edit a job, I have to open and forward 873 again. I've read that 873 is not encrypted traffic, so when setting up the job and browsing remote folders that's actually exposing your login credentials to the internet.
Hope that helps you.
Nas 1 is behind a NAT firewall where ISP provides public IP. Nas 2 is behind a NAT firewall where ISP provided NAT:ed IP. If ISP provides NAT:ed IP, there will be problem with incoming traffic (i.e. backup from Nas 1 -> Nas 2 will never work). You can check if you have NAT:ed IP by checking your routers outside address and compare with what whatsmyip.com says. In my case I had 10.188.xxx.xxx on my router's outside and 95.155.xxx.xxx on internet. Even if you use DDNS service like myqnapcloud or dyndns, it won't work.
After telling my ISP I needed a public IP, I had the same address on my router as on internet.
I then forwarded ports 22 and 873 to the Nas's internal ip address.
I set up the Nas to Nas and the test worked great.
I chose folder to replicate on local site and on remote site.
I did set up a schedule.
When the job was added, I removed the forwarding rule for 873 in the firewall.
Now, jobs are running smoothly without errors.
If I have to add another job, or edit a job, I have to open and forward 873 again. I've read that 873 is not encrypted traffic, so when setting up the job and browsing remote folders that's actually exposing your login credentials to the internet.
Hope that helps you.
TS-209 Pro -> TS-212P -> TS-251