How can I troublshoot: 530 No security mechanism selected

by Matt   Last Updated September 11, 2019 16:00 PM - source

I am using BitVise SSH Server. Normally I have it listening on 49000 for SSH/SFTP requests which works fine. I am trying to set it up to listen for FTP on 21. According to the logs the connection is established and terminates normally. However the client side is not connecting correctly.

Using WinSCP I see this in the logs and on screen

. 2019-09-11 11:10:31.735 Connecting to ...
. 2019-09-11 11:10:31.735 Connected with Waiting for welcome message...
< 2019-09-11 11:10:31.735 220 Bitvise SSH Server 8.32
> 2019-09-11 11:10:31.735 USER scanner
< 2019-09-11 11:10:31.735 530 No security mechanism selected
. 2019-09-11 11:10:31.735 Connection failed.
* 2019-09-11 11:10:31.773 (EFatal) Connection failed.
* 2019-09-11 11:10:31.773 Authentication failed.
* 2019-09-11 11:10:31.773 Connection failed.
* 2019-09-11 11:10:31.773 No security mechanism selected

Surely I need to do something on the server side. All I did was add a listening port under Settings > Server > Bindings and UPnP > IPv4 for FTP on port 21.

So I am looking to either FTP was not setup correctly or what I need to do on the client side to offer the correct security mechanism. I am doing this as we have some old printers that do not support modern security protocols like SMBv2 so FTP is supposed to be an acceptable compromise and I am using Bitvise to broker the connection so that users can scan to folders but using FTP.

Related Questions

How to connect to server with with ssh key?

Updated January 26, 2018 14:00 PM

Network error: Software caused connection abort(SSH)

Updated February 24, 2017 11:00 AM

WinSCP sending a file via console?

Updated June 09, 2017 06:00 AM

Not able to put correct domain while using FTP

Updated December 04, 2018 14:00 PM