When you enable ssh, you also enable sftp. Use an FTP client that supports sftp such as filezilla and there ya go. I created the /home/<userid> direcotry so that the userid (I created durring the SSH creation process) account can log in. Another tip would be to move the /home directory to /shares/internal then create a symbolic to it. Use the command "ln -s /shares/internal/home /home" to create the link. This way any files you store in your home directory will be placed on the larger partition, not the smaller OS partition.
I don't want to be pedantic but transferring a plain binary file to the MBW with sftp goes at 570 KB/s, with ftp 5050 KB/s on my net … there ya go but on the slow lane.
since I have open this post [http://mybookworld.wikidot.com/forum/t-106390/vsftpd-able-to-connect-but-no-way-to-control-the-server], this post may contain an interesting answer.
Doe this mean that installing sftpd or other ftp server is actually not usefull at all!?
I case that your sftp coming with SSH activation is sufficient, how to manage this server … at least to get errors logging and other configuration capability?