Differences

This shows you the differences between the selected revisions of the page.

2009-06-05 2009-06-12
no summary (113.22.80.67) (hidden) no summary (198.253.49.6)
Line 181: Line 181:
Another possibility is that the server is configured to only allow the SCP protocol and not the SFTP protocol, in such a way that SCP fallback mechanism of WinSCP does not work. The solution is to choose SCP protocol on the [[ui_login_session|login dialog]]. Another possibility is that the server is configured to only allow the SCP protocol and not the SFTP protocol, in such a way that SCP fallback mechanism of WinSCP does not work. The solution is to choose SCP protocol on the [[ui_login_session|login dialog]].
 +Other found resolution -- Check full path in which the client is attempting to connect to: for instance /export/home/username /export, /export/home need read rights.  If this is a mounted file system verify the
 +directory you are mounting onto also has permissions for read rights.  You may need to unmount the filesystem and change underlined directory's perms.
 +
===== [[return_code_127]] Command failed with return code 127 (or 255) ===== ===== [[return_code_127]] Command failed with return code 127 (or 255) =====
You will get the error with [[protocols#scp|SCP protocol]], if command necessary for facilitate operation you were trying to do does not exist on remote server or the shell cannot find it. Typically your get the error for ''scp'' command that is used to transfer files. You will get the error with [[protocols#scp|SCP protocol]], if command necessary for facilitate operation you were trying to do does not exist on remote server or the shell cannot find it. Typically your get the error for ''scp'' command that is used to transfer files.

Last modified: by 198.253.49.6