Re: How to do FTP using TN5250 Mochasoft

Hi,

Just to clarify here -FTP has nothing to do with Telnet(TN5250) but what I
wanted to say is that I am just trying to do FTP to pub400.com through DOS
command prompt but as mentioned earlier it's not getting connected and
giving below error :-

"530 Log on attempt by user rejected.
Login failed."

And within Mocha TN5250 for Windows 7/8/10/11 Version 3.8 I can connect to
Pub400.com with this FTP command by entering my user id and password.
But the same credentials give the above error message when I try to connect
through my system using the DOS command prompt.


*Regarding IBM i ACS *-- I tried all the 3 below options ( each with three
different port number as well 23,992 and 2222) which are available on IBM
i ACS's emulator screen for pub400.com
--->communication-configure-connection-Protocol-->

1) Use IBM i Access Client Solutions setting. 23,992,2222

2) Telnet -Not secured 23,992,2222

3) Telnet TLS/SSL 23,992,2222




But all of the above test cases gave me the same error
:-""CPF1120-CPF1120-User does not exist or password not correct for user
profile."



Thanks.






On Mon, 29 May 2023 at 03:58, Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I must admit to being confused by the subject - FTP is usually port 21
and TN5250 is telnet at port 23 - unless using ssl - but in either case,
what does FTP have to do with Telnet (TN5250)?

Now I am in the US - I thought I'd try connecting - ftp from a command
window in Windows connected fine - I used to have a profile at
pub400.com, long forgotten, but there was no problem with the
connection, pub400.com responded as ftp server always does on IBM i.

Then I tried telnet from an IBM i command line - the signon screen
showed up - again, I didn't do anything special. I don't have telnet on
my Win 10 yet, so that might have been different, not a full-fledged IBM
i logon screen. But the IBM i at pub400.com responded as if it had been
connected to.

My tests were done with the regular ports - no SSL. So a basic question
for Tim, the OP - with ACS, have you tried it without SSL? I ask in
order to keep this very simple - the conversation seems to have got very
complicated.

Cheers
Vern

On 5/28/2023 4:11 PM, Patrik Schindler wrote:

Hello Peter,

Am 28.05.2023 um 19:48 schrieb Peter Dow <petercdow@xxxxxxxxx>:

I'm guessing it has to do with CCSID/Codepage.

Meanwhile, I'm pretty sure it isn't. CCSID related issues would arise

only if the password contains characters outside of standard alphabet and
probably some types of extra chars. I had issues with 273 vs. 37 where @
and § share the same numeric code but are interpreted differently depending
on the CCSID settings of components being involved.

If that works, then the remaining mystery is why ftp does not work.

This and ssh is another hard proof why I think it's not a CCSID related

issue.

:wq! PoC

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.