Server 2019 with a new FTP site, add virtual host name, set binding to port 990 (FTPS). Add valid wildcard cert to IIS FTP settings section. The binding is "1.2.3.4:990:abcd.mydoman.com"
This all worked in 2008R2, but in 2019 it fails. The server immediately closes the connection after receiving the Client hello packet. If I eliminate the virtual host name and let it go with a * and the binding becomes "1.2.3.4:990:" then it all works.
So how to make 2019, map a FTP binding with a virtual host name to a cert, and accept the connection?
Thanks ross h
rossh