× 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.



I've looked at the archives on this but still confused. I have an FTP
to a business that I'm wanting to convert to FTPS (I think that is SSL
FTP), this would be outbound only.

Right now I've tried to do a FTP from our Production System to
Development System using the command:

FTP RMTSYS(' xxx.xxx.xxx.xxx') PORT(*SECURE) SECCNN(*SSL)

but get this message back in FTP: "Cannot connect to host
xxx.xxx.xxx.xxx at address xxx.xxx.xxx.xxx. Try again later."

While straight FTP connects just fine, and I get UserID/PW messages and
can log on. I have Certificates loaded and some assigned to HTTP on
Client side, but non to the FTP Server or Client. So do I need to
assign trusted Cert's to FTP? If I do this will it affect "non" SSL
FTP's? Or is there something I've not started to do the FTPS?

If someone that has been down this road before can give me a couple of
pointers I'd appreciate it.

Thanks,
-- Jim Lowary
Mo Farm Bureau


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.