Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: AUTH command ok. Expecting TLS Negotiation on FTP server running on Win 2019 IIS 10

I've meant logs from both client machines. The one, where it works, and the one, where it does not. Also does any other FTP client work on the machine, where WinSCP does not?
PandiPanda

log files

Please find attached log files from the WinSCP session and from the FTP server.
martin

Re: AUTH command ok. Expecting TLS Negotiation on FTP server running on Win 2019 IIS 10

Please attach full session log files from both machines (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
PandiPanda

AUTH command ok. Expecting TLS Negotiation on FTP server running on Win 2019 IIS 10

I have configured a FTP server on a Windows 2019 server IIS 10 platform, configured to use SSL explicitely.

When I use WinSCP from another server, I can successfully connect to this FTP server using FTPS.

When I use WinSCP from a desktop in my office, I get the message:
AUTH command ok. Expecting TLS Negotiation.

And I cannot connect.

So this seems related to my desktop configuration, which is a Windows 10 PC connected to a Tenda 4G router.

Any idea on how to diagnose this deeper and fix it?

Documentation

Support

Associations

Follow Us