Results 1 to 6 of 6
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Nov 2007
trying to scp from linux to Windows
hostname:~ # scp file firstname.lastname@example.org:'c:\temp' Password Authentication: user's password: lost connection hostname:~ #
I'm afraid you can't use scp to transfer files between Linux and Windows. I think you would need to have something like winscp or samba to perform such task.
kralj,Please create thread for new questions.
Ps: moderators please move this question to new thread.
You have 2 options to SCP between windows and Linux.
1. Install something like cygwin on windows to get a Linux shell and then run the scp command in the cygwin shell on the windows computer.
2. Install a server program on windows (freesshd or ssh.com) and then run the scp command on Linux.
scp -v file email@example.com:'c:\temp'"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." Linus Benedict Torvalds
- Join Date
- Nov 2007
Thanks for replying, all.
I've tried -v option. Of course, I can't make anything sensible out of it.
Just to mention again, I have Tectia client running on Windows, not server. Is that the problem?
hostname:/tmp # scp -v file firstname.lastname@example.org:'c:\temp' Executing: program /usr/bin/ssh host 192.168.50.2, user user, command scp -v - t c:\temp OpenSSH_4.2p1, OpenSSL 0.9.8a 11 Oct 2005 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.50.2 [192.168.50.2] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version 184.108.40.206 SSH Tectia Server debug1: no match: 220.127.116.11 SSH Tectia Server debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: sending SSH2_MSG_KEXDH_INIT debug1: expecting SSH2_MSG_KEXDH_REPLY debug1: Host '192.168.50.2' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:9 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: gssapi-with-mic,password,publickey,ke yboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Offering public key: /root/.ssh/id_dsa debug1: Authentications that can continue: gssapi-with-mic,password,publickey,ke yboard-interactive debug1: Next authentication method: keyboard-interactive Password Authentication: user's password: debug1: Authentication succeeded (keyboard-interactive). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = POSIX debug1: Sending env LC_CTYPE = en_US.UTF-8 debug1: Sending command: scp -v -t c:\\temp debug1: channel 0: free: client-session, nchannels 1 debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.2 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status -1 lost connection hostname:/tmp #
- Join Date
- Nov 2012
Disregard this message. The user didn't want to use sftp, but that would have been my solution.
Last edited by questargon; 11-30-2012 at 02:59 PM. Reason: Misunderstanding intention