I have 2 machines, A and B, both running windows 2003 / IIS 6, inside a firewall, and I have admin rights on both.
I am using CoreFTPPro ( v1.3, b1385) on both machines.
I can do FTP transfers back and forth between A and B, from either side, with no problems.
All of the SSL, PASV, and Use Proxy options are deselected or disabled, and I can use either port 21, or 22.
However, I can not get SFTP to work.
In changing my setup from FTP to SFTP, the only changes I made were:
(1) Using Putty, I created public and private keys for both A and B..
(2) On Machine A, Site A and B, I selected SSH/SFTP.
(3) On Machine A, Site A, I set the private key for Machine A, and used the Putty password.
(4) On machine A, Site B, I set the public key for Machine B, and used the Putty password.
(5) On machine B, Site A and B, I selected SSH/SFTP
(6) On machine B, Site A, I set the public key for Machine A, and used the Putty password.
(7) On Machine B, Site B, I set the private key for Machine B, and used the Putty password.
On Machine A, I tried to connect to Site B:
Resolving "xxx.xxx.x.xx"
Connecting to xxx.xxx.x.xx port 22
Connected socket #1940 to xxx.xxx.x.xx port 22
When I tried to transfer a file from A --> B ( from Machine A ), it eventually just seems to timeout:
Unable to initialize SFTP: could not connect (sftp not enabled?)
Can't establish connection --> xxx.xxx.x.xx:22 @ Wed Sep 29 17:20:44 2004 (10038-1)
Connection Failed
Unable to initialize SFTP: could not connect (sftp not enabled?)
Can't establish connection --> xxx.xxx.x.xx:22 @ Thu Sep 30 15:08:26 2004 (10038-1)
Network error: Socket operation on non-socket ( I only get this one occasionally)
Or I just get: Connection Failed.
None the SSL options, PASV, Use Proxy options are selected in either the FTP nor the SFTP options. I get the same results whether I try using ports 21 or 22, and it doesn’t matter whether I use Putty’s ssh1 or ssh2 keys, or whether I use legacy protocol options or simulate ascii mode.
What step am I missing??
Randy
newbie trying to set up SFTP
Ok, you were right on the first issue, I need an SFTP Server. I've installed winsshd from Bitvise, and now I can get further: The server is listening on port 22. what dumb thing am I missing now?
***
Welcome to Core FTP, release ver 1.3b, build 1385 (A) -- © 2003-04
WinSock 2.0
Mem -- 1,046,520 KB, Virt -- 2,097,024 KB
Started on Monday October 04, 2004 at 15:18:PM
Resolving "xx.xxx.xx.xxx"
Connecting to xx.xxx.xx.xxx port 22
Connected socket #624 to xx.xxx.xx.xxx port 22
Server version: SSH-2.0-1.43 sshlib: WinSSHD 3.28b
version: SSH-2.0-SSH-Local: Aug 4 2004 16:36:52
Using SSH protocol version 2
processing key exchange
Host key fingerprint is:
ssh-dss 1024 1f:bd:a4:d5:09:a5:68:71:e5:37:25:cd:f6:80:12:2f
Initialized AES-256 client->server encryption
Initialized AES-256 server->client encryption
Sent password
Access granted
Opened channel for session
Unexpected response to shell/command request: packet type 95
Unable to initialize SFTP: could not connect (sftp not enabled?)
Can't establish connection --> xx.xxx.xx.xxx:xx @ Mon Oct 04 15:19:48 2004 (10038-1)
***
Welcome to Core FTP, release ver 1.3b, build 1385 (A) -- © 2003-04
WinSock 2.0
Mem -- 1,046,520 KB, Virt -- 2,097,024 KB
Started on Monday October 04, 2004 at 15:18:PM
Resolving "xx.xxx.xx.xxx"
Connecting to xx.xxx.xx.xxx port 22
Connected socket #624 to xx.xxx.xx.xxx port 22
Server version: SSH-2.0-1.43 sshlib: WinSSHD 3.28b
version: SSH-2.0-SSH-Local: Aug 4 2004 16:36:52
Using SSH protocol version 2
processing key exchange
Host key fingerprint is:
ssh-dss 1024 1f:bd:a4:d5:09:a5:68:71:e5:37:25:cd:f6:80:12:2f
Initialized AES-256 client->server encryption
Initialized AES-256 server->client encryption
Sent password
Access granted
Opened channel for session
Unexpected response to shell/command request: packet type 95
Unable to initialize SFTP: could not connect (sftp not enabled?)
Can't establish connection --> xx.xxx.xx.xxx:xx @ Mon Oct 04 15:19:48 2004 (10038-1)