Normally, when you do cd /path/symlink, you actually end in /path/symlink, not in /symlink_target. While with your server, you actually end in /symlink_target. WinSCP cannot handle that.

We are using symbolic links in Unix (AIX) to reference files and paths to do FTP protocol transfers. I am using the DotNet components, GetFiles method, WinSCP version 5.2.1 and a few older versions (5.1.4, etc.). I am getting the error "Real path and requested remote path do not match". Is this a bug? I have used other FTP products and we never had this type of issue with not supporting symbolic links for simple FTP GET or PUT functions.

When I change the remove folder to use the physical path, it works fine. So I know this issue is isolated to using the symbolic links on the remote host. I reviewed the Transfer Options, Session Options and WinSCP.INI settings but could not find any way to suppress this edit.

Please advise if I can turn this "edit" off or how I might proceed to get this fixed.

I have attached the log file output from this issue.

Thank You!

Joseph McCloskey