IIS6 User Isolation FTP

[MichealC4]

thread931-1218500 is closed and I had some problems/questions.

I'm trying to set this up so that users can login with their credentials and see their directory (ala chroot/user isolation) on IIS6 and W2k3. Each time I try this, it tells me it cannot find the user's home directory. So in the above thread, I found to setup the directory structure. So my question is now how do I get the files they upload to their website? ie, C:\inetpub\ftproot\blah\user1 to C:\inetpub\

http://wwwroot\user1\.

I have a Linux background when it comes to mail servers, ftp servers, and webservers, so be gentle.

----------------------------
"Will work for bandwidth" - Thinkgeek T-shirt

 

[WhoKilledKenny]

Why are the clients using FTP? Are the clients web-designers that need to upload pages?
Is the Web-Server an intranet or Internet server?

Please explain the requirement from the users perspective and we'll see if someone can pipe up with a solution.

 

[MichealC4]

Yes, several websites are hosted on the server, and there are users that need FTP to upload (currently only one, the rest currently use Frontpage to upload, and to plan ahead expecting more users), I'd like to have this option setup correctly. This is an internet webserver. I "inherited" the server from someone else, so I'm not totally sure of the configuration of everything just yet.

----------------------------
"Will work for bandwidth" - Thinkgeek T-shirt

 

[WhoKilledKenny]

Here is the information you want to read up on...

http://www.microsoft.com/technet/pr...8ef-e3c5-456d-a8ca-7af4198819d4.mspx?mfr=true

Because this is an Internet server you should also look into some type of Secure FTP, as the username and password In IIS FTP is send clear text.

 

[MichealC4]

I've already read that, but that doesn't answer my question. How do I sync what's in the FTP directory with what the user wants in the web directory? In other words, they upload their web files, and those web files need to move from their ftp directory to their website directory.

----------------------------
"Will work for bandwidth" - Thinkgeek T-shirt

 

[WhoKilledKenny]

OK... here is how I do it depending on if the web-site currently exists or not.

Does not exist (new site) -
1. Create a local user account and password using Computer Management. Say username = CompanyContact
2. In the Root folder of my FTP site "d:\Inetpub\

http://wwwroot"

(this is were I set up my ftp root in IIS), is a folder called "LocalUser." This folder was manually created when I set up Isolation mode for FTP. In the LocalUser folder I manually create a new folder (assign NTFS Perms) that matches the name of the user account I created, folder name CompanyContact.
3. In IIS I create a new web-site and point the sites home directory to d:\Inetpub\

http://wwwroot\LocalUser\CompanyContact.

Set up proper permissions.

So with the set up, the client FTP's into the root of their web site and uploads changes. No sync required.

Web-site already exists -
1. You can set up your FTP like above and migrate the web-sites into each companies LocalUser directory.
-or-
2. Of you will have to set up FTP, Like you read, using the LocalUser Directory. Then Under the FTP site in IIS you will create new virtual directories that Point to the home directories of each web-site that you are hosting.
- After setting up VD's all users can access these directories, so you need to make permission changes on each one.
- Here is how the user would connect to the VD. They would FTP and logon with their user name. This will place them in their root folder, say C:\FTPRoot\LocalUser\CompanyContact. Then they would have to "CD" to the virtual directory, take note that doing an LS or DIR while logged into their FTP root folder does not show them the VD. They will have to know the name of the VD. User would CD to VD, say CD CompanySite. Then when they do a dir they will see their files and as long as perms are set correctly they will be able to upload changes.

I alway opt for option 1. and will tend to migrate web-sites when inheriting an IIS Server.

Hope that helps...

Here is another link for your documentation:

http://support.microsoft.com/?id=555018