Cannot get real path WinSCP error but no error in other SFTP clients

Advertisement

Infrastructure
Joined:
Posts:
1

Cannot get real path WinSCP error but no error in other SFTP clients

Following an upgrade of my Cygwin installation from Cygwin version 1.7.32 to 2.7.0 my WinSCP as the only SSH/SFTP client can no longer navigate into the folders in his \home directory. Home directory has two folders called "in" and "out" and although the user is still able to view list them as usual the moment he changes path to /in or /out he receives error

for example:

Cannot get real path for '/cygdrive/f/username/in'.
Permission denied.
Error code: 3
Error message from server: Permission denied

This also happens if the user tries to enter the parent folder by clicking on ".." I have also noticed that prior to Cygwin upgrade if the user tried entering ".." folder they would receive a slightly different but more familiar error denied:

Permission denied.
Error code: 3
Error message from server: Permission denied

Other clients such as Linux SSH, Putty PSFTP or FileZilla do not produce the permission denied problem and continue working as expected allowing the user to navigate into in and out folders.

This happens on all versions of WinSCP I used old and the latest and there has been no changes to the operating systems or permissions on my system apart from Cygwin upgrade.

I have also noticed that if the protocol is changed from SFTP to SCP then WinSCP is not suffering from this error.

Any help is greatly appreciated.
Many thanks.

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
29,234
Location:
Prague, Czechia

Re: Cannot get real path WinSCP error but no error in other SFTP clients

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

To generate the session 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.

Though the problem is likely with the server anyway. WinSCP is the possibly the only widespread SFTP client that actually follows the specification by normalizing the entered paths ("get real path") - If the server has problems with that, you will have problems with WinSCP, but not with the other clients. That does not mean it's WinSCP fault.
_________________
Martin Prikryl

Reply with quote

Advertisement

You can post new topics in this forum