|
It was determined that the entire issue was due to the fact that the server we were attempting to get files from has the control channel unencrypted with the data channel encrypted. the OS/400 FTP client only lets you set the data channel to unencrypted (*CLEAR) or encrypted (*PRIVATE) and sets the control channel to whatever the data channel is. Since the customer we are connecting to refuses (at least so far) to change on their end I submitted a PMR to IBM that has since turned into a DCR to allow controlling the control channel seperately or allowing you to connect unencrypted and then use the SECDATA P ftp subcommand to change only the data channel. Currently if you try the SECDATA P subcommand while connected unencrypted it will allow it saying for the data channel to be private the control channel must be private. Mark Allen IS Manager Wilkes Telephone & Electric 11 W. Court Street Washington, GA 30673 Phone: (706) 678-9565 Fax: (706) 678-1000
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
