IIS FTP

Troubleshoot

530 User cannot log in, home directory inaccessible.

To recap the items that you completed in this step, you configured FTP user isolation using the User name physical directory (enable global virtual directories) option. When using this mode of user isolation, all FTP user sessions are restricted to the physical directory with the same name of the FTP user account, and any global virtual directories that are created will apply to all users.

To create home directories for each user, you first need to create a physical directory under your FTP server's root folder that is named after your domain or named LocalUser for local user accounts. Next, you need to create a physical directory for each user account that will access your FTP site. The following table lists the home directory syntax for the authentication providers that ship with the FTP service:

# Anonymous users

%FtpRoot%\LocalUser\Public

# Local Windows user accounts
# (requires basic authentication)

%FtpRoot%\LocalUser\%UserName%

# Windows domain accounts
# (requires basic authentication)

%FtpRoot%\%UserDomain%\%UserName%

PASV Port

In the Data Channel Port Range box, type a range of port numbers (separated by a hyphen "5000-6000").

Type 0-0 to use the default port range specified in Windows TCP/IP settings.

Q1: "Data Channel Port Range" Grayed Out "0-0"

A1: Only can config on "Server Level"

Q2: FTP Passive Port Range not being honored

A2:

Actually, after you change the port range, you have to restart the "Microsoft FTP Service".

Using iisreset isn't sufficient, nor is clicking "Restart" at the server level in IIS Manager;

The OS-level service (ftpsvc) must be fully stopped and started.

net stop ftpsvc

net start ftpsvc