After some additional testing I discovered that the server was NOT actually running FTP though initially it appeared it was. This was the cause and all is now OK. WinSCP was working fine. Thanks for the swift response.
Do I understand right that you can connect using another SFTP client, but not with WinSCP?
Can you attach a complete session log (not XML log) using both WinSCP and the another client?
I have WinSCP 4.3.6 (Build 1655). I can connect to my dedicated server at admin level and from there see every file on the machine and its owner but I cannot connect directly to an admin user within a website on that machine using his username and password. The admin user for this particular website has an Outlook account that works fine using the password used for SFTP. With WinSCP I get an immediate bounce saying the server has closed the connection when using either SFTP or FTP. The log just shows the following:
<?xml version="1.0" encoding="UTF-8" ?>
<session xmlns="https://winscp.net/schema/session/1.0" name="firstname.lastname@example.org" start="2014-01-04T18:23:07.078Z" />
The shutdown window says:
Connection has been unexpectedly closed. Server sent command exit status 0
Cannot initialize SFTP protocol. Is the host running a SFTP server?