We have FTPS need to run on windows 2008 R2 server. I am using explicit FTP over SSL/TLS protocol. I was using port 21 with version 4.3.5 to connect, everything looks fine. Later, we were asked to switch a new SSL certificate and the port number change to 20021. Version 4.3.5 does not support the new certificate so I have to upgrade to version 5.7.6. I can connect to port 20021, however, the connection take a long time. I tried run the same version on windows 7 and it's normal. Does version 5.7.6 not support windows 2008? I post my log below:
FROM Windows 2008
. 2016-01-20 12:22:34.123 Connecting to *******com:20021 ...
. 2016-01-20 12:22:34.123 TLS layer changed state from unconnected to connecting
. 2016-01-20 12:22:34.123 TLS layer changed state from connecting to connected
. 2016-01-20 12:22:34.123 Connected with *********com:20021, negotiating TLS connection...
< 2016-01-20 12:22:34.295 220 **** FTPS (Version Wed Jan 20 12:22:33 2016) server ready.
> 2016-01-20 12:22:34.295 AUTH TLS
< 2016-01-20 12:22:34.342 234 Enabling TLS, awaiting negotiations.
. 2016-01-20 12:22:34.950 TLS connect: SSLv3 read server hello A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 read server certificate A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 read server key exchange A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 read server done A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 write client key exchange A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 write change cipher spec A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 write finished A
. 2016-01-20 12:22:35.543 TLS connect: SSLv3 flush data
. 2016-01-20 12:22:35.855 TLS connect: SSLv3 read finished A
. 2016-01-20 12:22:35.855 Verifying certificate for "*********" with fingerprint xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx and 20 failures
. 2016-01-20 12:23:20.894 Certificate common name "*********com" matches hostname
. 2016-01-20 12:23:20.894 Certificate for "*********" matches cached fingerprint and failures
. 2016-01-20 12:23:20.894 Using TLSv1.1, cipher TLSv1/SSLv3: DHE-RSA-AES256-SHA, 2048 bit RSA
. 2016-01-20 12:23:20.910 TLS connection established. Waiting for welcome message...
FROM WINDOWS 7
. 2016-01-20 23:17:52.426 Connecting to *********com:20021 ...
. 2016-01-20 23:17:52.426 TLS layer changed state from unconnected to connecting
. 2016-01-20 23:17:52.426 TLS layer changed state from connecting to connected
. 2016-01-20 23:17:52.426 Connected with *********com:20021, negotiating TLS connection...
< 2016-01-20 23:17:52.568 220 **** FTPS (Version Wed Jan 20 23:17:52 2016) server ready.
> 2016-01-20 23:17:52.568 AUTH TLS
< 2016-01-20 23:17:52.594 234 Enabling TLS, awaiting negotiations.
. 2016-01-20 23:17:53.808 TLS connect: SSLv3 read server hello A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 read server certificate A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 read server key exchange A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 read server done A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 write client key exchange A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 write change cipher spec A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 write finished A
. 2016-01-20 23:17:54.519 TLS connect: SSLv3 flush data
. 2016-01-20 23:17:54.857 TLS connect: SSLv3 read finished A
. 2016-01-20 23:17:54.857 Verifying certificate for "*********" with fingerprint xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx and 20 failures
. 2016-01-20 23:17:54.913 Certificate verified against Windows certificate store
. 2016-01-20 23:17:54.914 Certificate common name "*********com" matches hostname
. 2016-01-20 23:17:54.914 Using TLSv1.1, cipher TLSv1/SSLv3: DHE-RSA-AES256-SHA, 2048 bit RSA
. 2016-01-20 23:17:54.954 TLS connection established. Waiting for welcome message...