Problems with DSS FTP connection with Client WinSCP or automated script.

Lukasz Ossowski

I have been attempting to get our automated script to connect to our site hosted.datascope.reuters.com.

When I test the connection with the client, CoreFTP, I AM successful using

Server: hosted.datascope.reuters.com/reports/

Port: 22

User: r9025260

Pass: xxxxxx (obscured) and no private key

I am NOT successful if I use the Client WinSCP

OR my automated script.

What I get back as a return value from your server is as follows:

“<?xml version="1.0"?><FTPResults xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><Success>false</Success><Msg>Connection has been unexpectedly closed. Server sent command exit status 0.

Authentication log (see session log for details):

Using username "r9025260".

Access denied.

Authentication failed.</Msg><FileInfo><string xsi:nil="true" /></FileInfo></FTPResults>"

Can you please have someone look at the log for this user and see if it reveals why one way works and the other doesn’t? Each method should be presenting the same public key.

Gurpreet

Hi @Lukasz Ossowski

I have tried with latest WinSCP and have been able to connect both FTP and SFTP.

Like OpenSSL, WinSCP uses its own certificate store and prompted me to accept the new certificate - the first time I connected.

I would recommend that you update to the latest version and clear your old cached certificates.