Yes right, SFTP tools do not support interactive(Manual) mode of authentication.
Only 1. mobile app notification works.

Thank you all.

The authentication possibly involves a use of a shell. In that case you cannot use SFTP. It's not a problem of a client, but of a wrong implementation of the authentication on the server side.

Post a PuTTY screenshot and event log, if you want us to check, if my assumption is correct. Use PuTTY 0.72.

yes i tried others tools too.
no SFTP tool support that mode.

Can you login with "Manual MFA code entry" using any SFTP client? Like PuTTY psftp or OpenSSH sftp?

We have MFA activated(PingID) on login.
So there are 2 modes how MFA works
1. mobile app notification
2. Manual MFA code entry
While login to WInSCp if we choose 2. Manual MFA code entry...it directly throw below error.
But we can login if we choose 1. mobile app notification.
also both options work if we login to normal CLI(putty) shell.
Just winscp client doesnt ask for MFA code while login and throws error.

How to resolve this. Does WinSCp not support this?


. 2019-08-01 02:29:24.613 Offered public key
. 2019-08-01 02:29:24.713 Offer of public key accepted
! 2019-08-01 02:29:24.714 Authenticating with public key "imported-openssh-key"
. 2019-08-01 02:29:24.874 Sent public key signature
. 2019-08-01 02:29:24.970 Access granted
. 2019-08-01 02:29:24.970 Opening session as main channel
. 2019-08-01 02:29:25.063 Opened main channel
. 2019-08-01 02:29:25.289 Started a shell/command
. 2019-08-01 02:29:25.351 Doing startup conversation with host.
> 2019-08-01 02:29:25.375 Type: SSH_FXP_INIT, Size: 5, Number: -1
. 2019-08-01 02:29:26.228 Server sent command exit status 255
. 2019-08-01 02:29:26.229 Disconnected: All channels closed
* 2019-08-01 02:29:26.263 (EFatal) **Connection has been unexpectedly closed.** Server sent command exit status 255.
* 2019-08-01 02:29:26.263 Cannot initialize SFTP protocol. Is the host running an SFTP server?