OK, case closed. I leaned two things today:
1. I had to use "ftpes://..." and not "ftp://..." to define the protocol as I had been doing. Something my Host failed to inform me about, and I only discovered it when trying out the "Session/Generate session Url" from the WinSCP GUI. I had tried "ftps://..." but that failed. I would never have guessed in a million years that it should be "ftpes".
and
2. If the Certificate is unauthorised then I have to use the "-certificate" parameter on the "open" command, not the "/certificate" parm.
TLS is kicking in and it's all working nicely now. Thanks for looking.
Bill
1. I had to use "ftpes://..." and not "ftp://..." to define the protocol as I had been doing. Something my Host failed to inform me about, and I only discovered it when trying out the "Session/Generate session Url" from the WinSCP GUI. I had tried "ftps://..." but that failed. I would never have guessed in a million years that it should be "ftpes".
and
2. If the Certificate is unauthorised then I have to use the "-certificate" parameter on the "open" command, not the "/certificate" parm.
TLS is kicking in and it's all working nicely now. Thanks for looking.
Bill