Forgot to include the screenshot from my SOlidCP FTP setup.

Try setting read permissions for the SCPFtpUsers group to C:inetpubftproot

For this issue it's important what your using.

so for example if your using Filezilla --> It's important your filezilla user has access to the directories.

If your using IIS FTP, the most easy way is to let SolidCP set the default FTP site up for you (this should come with the right perms set).

Do note for basic hardening removing users group from disk level, creating administrator file access group with users (like solidcp server / administrators / filezilla ftp user, etc) -> with full perms, and adding network service + Local service accounts with read + execute permissions would be needed to properly harden your server.

Hi Marco,

thanks for the fast response.

1. the FTP Server is using Microsoft FTP through IIS
2. We just used the default FTP site setup

After the FTP role was installed on Windows 2012r2, I went into IIS --> default FTP and selected "FTP User Isolation", then in the dialog box i selected "User Name Directory"

The only other thing I did differently afterwards was I selected default FTP and then back to bindings and I added another ftp bind.  So the original binding to port 21 is there, then I added the same IP and made another port number 21345.

So in the end, the binding has port 21 and port 21345.

Not sure if that caused a problem or not, but when i started having issues with the FTP user, I removed the port 21345 binding and restarted FTP service.

Then I removed the FTP user from SolidCP and re-added a new user, but still have the same issue.

Not sure where to troubleshoot this one.