Our company connected to this server long long ago with WinSCP but then the server must have changed and we needed to use FTP Voyager from then on. I read some bug reports today that lead me to believe this issue was fixed in 5.2.5 (https://winscp.net/tracker/show_bug.cgi?id=1074), we were currently using 3.x.x so I updated today to latest version and we receive the same error message. I'd love to get this working on WinSCP because we love this ftp program and have everything else saved on it already.

Your folder names does not seem Windows-ish, so I do not think it's related to Bug 1074.

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private._________________Martin Prikryl

Your folder names does not seem Windows-ish, so I do not think it's related to Bug 1074.

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.