Please review this thread where I helped another user get his FTP working.
https://learn.microsoft.com/en-us/answers/questions/741961/windows-10-server-connection-failure.html?page=1&pageSize=10&sort=oldest
One of the key points is that we had a communication problem He would tell me that was "connecting to his server" and it failed. What he did not tell me was that he was using the external IP of his router and not local network address of his server. I had no way of knowing what he was doing.
So when you post that Test-NetConnection failed to connect, we are in the same situation. You removed the IP addresses and just posted ?.?.?.?. I understand your desire for privacy, but I have no idea what you are doing.
NO forum user can help you if you do not post the details of what you doing and what you have configured. I have tried to explain that to you before.
That thread has instructions and images that you should follow to troubleshoot your environment. We cannot do it for you.
To summarize:
If you want to transfer files over the internet through a router and portforwarded to an internal server, then OpenSSH/SFTP/port 22 is the preferred solution. That is mainly due to the way that classic FTP uses 2 channels.
If you wish to do a secure transfer using IIS/FTPS/port 21, then you will need to use a client that supports FTPS. Winscp and Filezilla support FTPS. The Windows explorer and ftp.exe do not support FTPS.
FTPS over the internet can work using passive mode, but as RipperT discovered, you will need to use WinSCP.