


We checked and found NTFS and FTP default permissions to be ok and good. We started seeing issues where user isolation was not working and failing with “access denied” error. IIS Manager or ASP.NET custom authentication user accounts Local Windows user accounts (requires basic authentication) The following table lists the home directory syntax for the authentication providers that ship with the FTP service.

Next, you need to create a physical directory for each user account that will access your FTP site.

We created test FTP site with basic authentication enabled and created the folder structure required for User isolation with “username directory(disable global virtual directory) Recently I was working on a case where we wanted to setup FTP User level isolation.
