Re: SFTP with client

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hi Mark,

FTP is a standard internet protocol for file transfer.  It's not secure, 
however, so should only be used in a trusted environment.  People have 
tried to improve it's security by adding SSL support, so you have FTP 
over SSL.  This is sometimes called "Secure FTP", and it's sometimes 
called "FTPS" (especially in URLs, ftps://server.com/dir/file.ext).  It 
is not the same thing as SFTP.

SFTP is not FTP at all.  It is an FTP-like user interface to the SSH 
protocol.  That's why you seee "SSH-2.0-1.36" in your log.  Because you 
are connecting to an SSH server, not an FTP server!

The simple fact is, your FTP client is NOT going to work.  It doesn't 
understand the SSH protocol.  You need an SSH client.

IBM provides a (free) port of OpenSSH, which is the most popular SSH 
client in the world.  It's provided with the free licpgm, 5733-SC1.  But 
it does run in PASE.

I've written a bunch of articles on this stuff.  Let me know if you'd 
like me to post links.

Mark Allen wrote:
> I have a customer who is switching effective immediately (this Friday) and
> they want is to connect using the server name they specified (which I do see
> connections to) and port 13266.
>
> We can't seem to get it working and my secureftp knowledge is limited and
> their "i5" skills are none existent.  They are saying that the user name and
> password from the clients they have "automagically" get passed but that the
> limit of their technical details.  Screen shot below on what happens below
> what I am using for the Connection:
>
> FTP RMTSYS(EXTERNALFTP.XXXXXXX.COM) PORT(13266) SECCNN(*SSL)
>
> Connecting to host EXTERNALFTP.XXXXXXX.COM at address 2xx.xx8.xxx.xxx using
> port 13266.
> SSH-2.0-1.36 sshlib: GlobalScape   ---> this is where the "Vendor" says it
> is hanging up.
>
> Is there some "simple" piece I am missing on the FTP command line or another
> "vital" piece I am blank about?