Need to setup FTP Sites on a server that uses Host Headers for the websites

Ok, here is what I've done:

Folder Structure:
E:\
E:\website1\wwwroot
E:\website2\wwwroot
E:\website3\wwwroot

Under IIS:
New FTP Site
Description: MyServer FTP Sites
IP Address: 216.xxx.xxx.135
TCP Port: 21
Isolate Users
Path: E:\

Under MyServer FTP Sites
New Virtual Directory
Alias: website1
Path: e:\website1\wwwroot
Permissions: Read

Users defined:
website1, password: password, full control of e:\website1\wwwroot

When trying to FTP using ftp.website1.com, user name: website1, password: password, I get the following error:

530 User zaicomllc cannot log in, home directory inaccessible.

I think this is because I don't have a Folder setup for the user website1.

Remember, ultimately I want to have multiple websites using the same IP Address and Port Number using Host Headers.  I want the FTP Sites for each website to be isolated from the other sites.

ok,

1) ftp server root.

do you really want to make the ftp server root at E:\ ?  it is not usually good practice to put it on a disk root - it would be better something like "E:\ftproot"

2) 530 User zaicomllc cannot log in, home directory inaccessible.

you mean there is no physical directory e:\zaicomllc\wwwroot?  Then make one.  Also, make the permissions 'write' - else they will be able to view the contents, but they can't upload anything.

Also, make sure that the 'zaicomllc' user has write access to the 'e:\zaicomllc\wwwroot' folder, AND read access to the ftp root (e.g. 'E:\ftproot')

3) Remember, ultimately I want to have multiple websites using the same IP Address and Port Number using Host Headers.

The ftp protocol dos not support host headers, so you will need to use the same ftp server for all users.  You can use dns to point the different domains to the same IP address though, and so make the ftp login banner reasonably generic, and they will not know the difference.

Regards,  Mike.

1) ftp server root
The only folders on the e: drive are the websites.  If I take your suggestion, I would have the following folder structure:
e:\
e:\ftproot
e:\ftproot\website1\wwwroot
e:\ftproot\website2\wwwroot
e:\ftproot\website3\wwwroot

2) 530 User zaicomllc cannot log in, home directory inaccessible
My mistake, the error read 530 User website1 cannot log in, home directory inaccessible
There is a e:\website1\wwwroot folder that has Read access only right now.
The website1 user has Read/Write access to e:\website1\wwwroot folder.

I'll try moving everything into e:\ftproot folder.

I created a folder on E: called FTPRoot.  Under FTPRoot I put another folder Test.  The structure looks like this:
e:\
e:\ftproot
e:\ftproot\test

Created a test user which has read access on e:\ftproot and read/write access on e:\ftproot\test.

I deleted the FTPsite and created a new one and specified do not isolate users.  Assigned the default directory to e:\ftproot.  I created a virtual directory called test and assigned the default directory to e:\ftproot\test.  Under this configuration, I was able to successfully FTP into the site.

Next, I deleted the virtual directory and FTPSite.  I created a new one and specified isolate users.  Assigned the default directory to e:\ftproot.  I created a virtual directory called test and assigned the default directory to e:\ftproot\test.  Under this configuration, I cannot access the FTP site.  I get the

530 User test cannot log in, home directory inaccessible.

I also accessed the IIS configuration, chose the Virtual Directory Test and clicked on Browse.  It asks for a user name and password.  When I enter test and the password I still get the error.  I can't even use the Administrator account.

Any other suggestions?

Increasing points because this is becoming time critical.

OK, what kind of user isolation - standard or AD?  I suspect that you will want the former (i.e. NOT Active Directory).

Perhaps there is a problem with conflict between the physical directory and virtual directory.

I suggest a structure more like this:

e:\
e:\ftproot (everyone:read only)
e:\websites (administrator access only)
e:\websites\test (user test: read/write)

create an ftp site, set the root to 'e:\ftproot'
under that ftp server, create a virtual directory called 'test' physical path 'e:\websites\test'

Cheers.

Used standard isolation not AD.

Used your configuration and still get the home directory is inaccessible

This is so frustrating.  It seems like I've done everything my IIS 6.0 Administrators Guide has told me to do along with your suggestions but I still can't get this to work.

is this server a domain controller by any chance?  the ftp user requires "log on locally" rights in security policy.

Cheers.

the server is not a domain controller.  the users group is in the log on locally security policy.  the ftp user is in the users group.