Non password SSH connect Windows to Linux

3 posts / 0 new
Last post
cafetechla
Offline
Last seen: 1 year 5 months ago
Joined: 13.05.2013 - 20:29
Non password SSH connect Windows to Linux

I am trying to pull information from a RedHat Enterprise Linux 6.3 server to a Windows Server 2008 R2 server. I have installed the cwRsync client on the Windows rsync client, I have created and copied the id_rsa.pub file from the Windows client to the Linux rsync host and imported the id_rsa.pub public key into the authorized_hosts file on the Linux side. Everything works great to pull from Linux to Windows, as long as I run the command manually and input the Linux user password when prompted on the Windows client.

I need to automate this batch job on the Windows client side to run as a scheduled task, which means that I need to connect from Windows to Linux via SSH without a password prompt. I have scoured the forums and FAQs and found no solutions or configurations that works.

What is the solution for this?

itefix
Offline
Last seen: 16 hours 18 min ago
Joined: 01.05.2008 - 21:33
Try to create a batch file

Try to create a batch file via cwRsync GUI or edit the supplied cwrsync.cmd. The key point is to inform ssh where to look fo keys. You can do that by specifying the environment variable HOME. Then ytou should be able to schedule a batch job. Please also remeber to use absolute paths all the way.

cafetechla
Offline
Last seen: 1 year 5 months ago
Joined: 13.05.2013 - 20:29
I did all of that and it is

I did all of that and it is still not connecting passwordless. Now the message in the command window says it cannot make a connection because it cannot find file "id_dsa" and file "id_ecdsa" in the local path "/Home/Administrator/.ssh/" (that would be the local Windows client path correct?) The id_rsa and id_rsa.pub files are in that path that were created when running the "ssh-keygen -t rsa" command.

Go figure. So how do I clear this problem?

I am not using copssh on the Windows box because I only want the cwRsync client running on it. The only thing I found in the fourms mentioning this error message pertains to copssh.