SCP not willing to transfer remote to remote
Clash Royale CLAN TAG#URR8PPP
My family and I are attempting to sync all our data across multiple locations and devices. Seeing as we are just setting it up, we were wanting to start with the basics before building on it further, but are somehow already running into issues.
The setup I'm testing with currently is:
Location A:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
Location B:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
All of These devices are already connected to eachother through a VPN.
When attempting to run this command:
scp -v -3 admin@10.8.0.102:/volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures
It will request a Password, that when filled in gives the following error:
admin@10.8.0.102's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
At first I thought it was a wrong password, but after muliple tries I have given up on this theory, mainly because:
When attempting to sync local data instead of remote/remote it does work. Both to and from Location A and Location B:
Respective commands are:
scp -v -3 pictures/ admin@10.8.0.102:/volume1/pictures/
and
scp -v -3 admin@10.8.0.103:/volume1/Backup/LocA/pictures/ pictures/
Both yielding something along the lines of:
admin@10.8.0.102's password:
debug1: Authentication succeeded (password).
Authenticated to 10.8.0.102 ([10.8.0.102]:22).
Sending file modes: C0644 66 test.txt
Sink: C0644 66 test.txt
test.txt 100% 66 57.9KB/s 00:00
Transferred: sent 2468, received 2892 bytes, in 0.1 seconds
Bytes per second: sent 32340.0, received 37896.0
Could someone please give me any insight how I can see what is going on? It doesn't seem to be a permission issue of writing/reading, nor a wrong Password.
ssh scp synchronization nas
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
add a comment |
My family and I are attempting to sync all our data across multiple locations and devices. Seeing as we are just setting it up, we were wanting to start with the basics before building on it further, but are somehow already running into issues.
The setup I'm testing with currently is:
Location A:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
Location B:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
All of These devices are already connected to eachother through a VPN.
When attempting to run this command:
scp -v -3 admin@10.8.0.102:/volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures
It will request a Password, that when filled in gives the following error:
admin@10.8.0.102's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
At first I thought it was a wrong password, but after muliple tries I have given up on this theory, mainly because:
When attempting to sync local data instead of remote/remote it does work. Both to and from Location A and Location B:
Respective commands are:
scp -v -3 pictures/ admin@10.8.0.102:/volume1/pictures/
and
scp -v -3 admin@10.8.0.103:/volume1/Backup/LocA/pictures/ pictures/
Both yielding something along the lines of:
admin@10.8.0.102's password:
debug1: Authentication succeeded (password).
Authenticated to 10.8.0.102 ([10.8.0.102]:22).
Sending file modes: C0644 66 test.txt
Sink: C0644 66 test.txt
test.txt 100% 66 57.9KB/s 00:00
Transferred: sent 2468, received 2892 bytes, in 0.1 seconds
Bytes per second: sent 32340.0, received 37896.0
Could someone please give me any insight how I can see what is going on? It doesn't seem to be a permission issue of writing/reading, nor a wrong Password.
ssh scp synchronization nas
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
add a comment |
My family and I are attempting to sync all our data across multiple locations and devices. Seeing as we are just setting it up, we were wanting to start with the basics before building on it further, but are somehow already running into issues.
The setup I'm testing with currently is:
Location A:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
Location B:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
All of These devices are already connected to eachother through a VPN.
When attempting to run this command:
scp -v -3 admin@10.8.0.102:/volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures
It will request a Password, that when filled in gives the following error:
admin@10.8.0.102's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
At first I thought it was a wrong password, but after muliple tries I have given up on this theory, mainly because:
When attempting to sync local data instead of remote/remote it does work. Both to and from Location A and Location B:
Respective commands are:
scp -v -3 pictures/ admin@10.8.0.102:/volume1/pictures/
and
scp -v -3 admin@10.8.0.103:/volume1/Backup/LocA/pictures/ pictures/
Both yielding something along the lines of:
admin@10.8.0.102's password:
debug1: Authentication succeeded (password).
Authenticated to 10.8.0.102 ([10.8.0.102]:22).
Sending file modes: C0644 66 test.txt
Sink: C0644 66 test.txt
test.txt 100% 66 57.9KB/s 00:00
Transferred: sent 2468, received 2892 bytes, in 0.1 seconds
Bytes per second: sent 32340.0, received 37896.0
Could someone please give me any insight how I can see what is going on? It doesn't seem to be a permission issue of writing/reading, nor a wrong Password.
ssh scp synchronization nas
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
My family and I are attempting to sync all our data across multiple locations and devices. Seeing as we are just setting it up, we were wanting to start with the basics before building on it further, but are somehow already running into issues.
The setup I'm testing with currently is:
Location A:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
Location B:
- 1x NAS (Synology DS214+)
- 1x Raspberry Pi running Rasbian.
All of These devices are already connected to eachother through a VPN.
When attempting to run this command:
scp -v -3 admin@10.8.0.102:/volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures
It will request a Password, that when filled in gives the following error:
admin@10.8.0.102's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
At first I thought it was a wrong password, but after muliple tries I have given up on this theory, mainly because:
When attempting to sync local data instead of remote/remote it does work. Both to and from Location A and Location B:
Respective commands are:
scp -v -3 pictures/ admin@10.8.0.102:/volume1/pictures/
and
scp -v -3 admin@10.8.0.103:/volume1/Backup/LocA/pictures/ pictures/
Both yielding something along the lines of:
admin@10.8.0.102's password:
debug1: Authentication succeeded (password).
Authenticated to 10.8.0.102 ([10.8.0.102]:22).
Sending file modes: C0644 66 test.txt
Sink: C0644 66 test.txt
test.txt 100% 66 57.9KB/s 00:00
Transferred: sent 2468, received 2892 bytes, in 0.1 seconds
Bytes per second: sent 32340.0, received 37896.0
Could someone please give me any insight how I can see what is going on? It doesn't seem to be a permission issue of writing/reading, nor a wrong Password.
ssh scp synchronization nas
ssh scp synchronization nas
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
asked Dec 28 '18 at 11:48
KagetazeKagetaze
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
let's start by sshing into 10.8.0.102 and running
scp -v -3 /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
if this doesn't work then you need to add A's public key to B's ~/.ssh/known_hosts and vice versa.
also are you sure you want the entire directory to be copied or the contents of the directory?
did you mean to do this?
scp -v -3 -r /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491286%2fscp-not-willing-to-transfer-remote-to-remote%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
let's start by sshing into 10.8.0.102 and running
scp -v -3 /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
if this doesn't work then you need to add A's public key to B's ~/.ssh/known_hosts and vice versa.
also are you sure you want the entire directory to be copied or the contents of the directory?
did you mean to do this?
scp -v -3 -r /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
add a comment |
let's start by sshing into 10.8.0.102 and running
scp -v -3 /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
if this doesn't work then you need to add A's public key to B's ~/.ssh/known_hosts and vice versa.
also are you sure you want the entire directory to be copied or the contents of the directory?
did you mean to do this?
scp -v -3 -r /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
add a comment |
let's start by sshing into 10.8.0.102 and running
scp -v -3 /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
if this doesn't work then you need to add A's public key to B's ~/.ssh/known_hosts and vice versa.
also are you sure you want the entire directory to be copied or the contents of the directory?
did you mean to do this?
scp -v -3 -r /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
let's start by sshing into 10.8.0.102 and running
scp -v -3 /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
if this doesn't work then you need to add A's public key to B's ~/.ssh/known_hosts and vice versa.
also are you sure you want the entire directory to be copied or the contents of the directory?
did you mean to do this?
scp -v -3 -r /volume1/pictures/ admin@10.8.0.103:/volume1/Backup/LocB/pictures/
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
answered Dec 28 '18 at 12:21
Zypps987Zypps987
612
612
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
add a comment |
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
That command worked (with obviously the -r tag).
– Kagetaze
Dec 28 '18 at 13:00
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
What was the problem with the authentication between point A and point B? The -r tag shouldn't have fixed that, strange.
– Zypps987
Dec 28 '18 at 21:55
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
If this is solved please this post as solved.
– Zypps987
Dec 30 '18 at 15:45
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491286%2fscp-not-willing-to-transfer-remote-to-remote%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown