NAS326 with SFTP

lescarlson
lescarlson Posts: 14
First Comment Fourth Anniversary
 Freshman Member
I am trying to remedy a 'Twonky' server problem addressed here:


Following the directions in the above post;
I am able to connect to the NAS326 via FTP but not SFTP (port 22). As the 'WinSCP' program reports "The server rejected SFTP connection, but it listens for FTP connections.".

If I try to change the NAS326 FTP port to '22' the ftp control panel says "port used by another service".

If I access the NAS326 'admin' folder with the 'WinSCP' FTP, I am not allowed to see the hidden folders. Apparently only SFTP will show the hidden folders within the NAS326 'admin' folder. Thus I am not able to correct the 'Twonky' server problem mentioned above.

Does anyone know how to get the 'WinSCP' program to access the NAS326 via SFTP ?
Or does anyone know how to get the NAS326 to accept an 'SFTP' connection?


Accepted Solution

  • Mijzelf
    Mijzelf Posts: 2,143
    100 Answers 1000 Comments Friend Collector Fifth Anniversary
     Guru Member
    Answer ✓
    Are you sure you enabled the ssh server on the NAS? Are you able to login over ssh? If yes, try the scp protocol instead of sftp.

All Replies

  • lescarlson
    lescarlson Posts: 14
    First Comment Fourth Anniversary
     Freshman Member
    Mijzelf, Right on! I had reset the NAS326 back to factory, then brought back a saved configuration. Anyway the SSH setting was not enabled. It is working now. Thank you very much for taking the trouble.
    Les Carlson
    Sio
  • lescarlson
    lescarlson Posts: 14
    First Comment Fourth Anniversary
     Freshman Member
    I am able to access the 'twonky server' folder using SSH WinSCP program.
    I am NOT able to remove the file 'twonkyserver.ini'.
    I am told:
    "Permission denied.
    Error code: 3
    Error message from server: Permission denied"

    Can anyone tell how to have the NAS326 allow read/write permission for those files???

  • lescarlson
    lescarlson Posts: 14
    First Comment Fourth Anniversary
     Freshman Member
    I got it....Never mind.
    The problem was login with 'username' as opposed to 'root'!

Consumer Product Help Center