× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes please do Scott!!! I'd love to see some examples (especially yours
since I know they will work!!)

On Mon, Jun 8, 2009 at 1:19 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

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?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.