Computing.Net > Forums > Windows 2000 > IIS ftp-How do I give private home DIRs?

IIS ftp-How do I give private home DIRs?

Reply to Message Icon

Original Message
Name: Dave
Date: January 4, 2002 at 07:16:21 Pacific
Subject: IIS ftp-How do I give private home DIRs?
Comment:

I'm running Windows 2000 Advanced Server with IIS FTP server.

How can I set it up so that different FTP login accounts get their own (separate) FTP area? While it's easy to set up virutal directories and such, I can't seem to figure out how to segregate each user.

Help?


Report Offensive Message For Removal

Response Number 1
Name: Dan
Date: January 4, 2002 at 11:03:10 Pacific
Subject: IIS ftp-How do I give private home DIRs?
Reply: (edit)

Unfortunately in windows 2000 you cannot have users login into different directories. You can, however, have everyone log into one root directory and then have home directories from there. You would have to give the users read, read and execute and list folder contents only access to the root directory and then give the individual users full access to there home directory. It actually would be easier to just give the Everyone group access to the root directory and not bother with making a group (this is how we have it done on our servers for home directories). Another option, if you have the money, is to get a real ftp server program like G6 (www.gene6.com, 30 dollars (US)). This will allow you to set up individual home directories for users. I use it and it is very simple to use. Hope this helps.


Report Offensive Follow Up For Removal

Response Number 2
Name: David
Date: February 13, 2002 at 14:41:20 Pacific
Subject: IIS ftp-How do I give private home DIRs?
Reply: (edit)

Dan is incorrect; here is the way you should setup user FTP folders (this way when a user uses their login name and password, they are put into their OWN private folder!)

Step 1: Create a home folder for your user.

Typically, this will be a subfolder under a parent folder that is named exactly the same as the username. All users will need the right to Log on Locally. Of course, Admins should have full control of everything all the time :)

TIP: Do not set NTFS permissions yet. If you do, be sure the System account has access to the users' folder or you will get a 'stop sign" error when you try to create the Virtual Directory.

Step 2: Create a Virtual Directory and map the user's folder.

The trick here is that the Virtual Directory has to be the exact same name as the user. In this case, we create a folder called BartS and map it to FTPusers/BartS. Note that the directory name is case sensitive!

Step 3: Enable Write on the Virtual Directory

Unless this is a read-only FTP site, enable the write permission on the FTP snap in.

Step 4: Remove Anonymous authentication from the Virtual Directory.

Uncheck the "Allow only anonymous authentication" on the Security Acccounts tab. Now, when BartS logs on, he will be automatically placed in his user folder.

Step 5: Assign NTFS permissions.

For the parent folder of your users' folders, you can assign No Access to the anonymous account. Despite what some KB articles say, the user does not need permissions to the parent folder. The System account, however, does need access to this folder so Everyone, No Access is not a good idea. If the System account can't access the folder, you can have problems later when you go to make changes to the FTP server setup for the user.

For the users' folders, NTFS permissions Read and Write are typical. Execute permissions should be avoided. Remove Everyone from the access list and add the user's account. According to your policy, you may or may not include Administrators.

That's it! Now when users log on with FTP, they will be routed to their own FTP folder.

TIP: You can keep users from seeing folders for other users:
1. Point your FTP server to an empty root. Fine to use Inetpub/ftproot, just don't put anything in there or your users will see it.
2. Map your users' Virtual Folders to a location outside of the FTP server virtual root. By keeping your users' folders in the same parent folder outside of the virtual FTP root, when they go "up" in the directory tree from their personal folder, they will be magically transported to the empty FTProot.

WARNING. Password sent to the FTP service are sent in absolute cleartext. SSL can't be used and you can't use NTFS authentication. No good solution exists for this problem using native Microsoft FTP server.


Report Offensive Follow Up For Removal

Response Number 3
Name: Mike
Date: February 21, 2002 at 19:31:36 Pacific
Subject: IIS ftp-How do I give private home DIRs?
Reply: (edit)

I'm with Dan. You cannont do this using IIS 5 under Windows 2000. You can do it from IIS 4, though. The answer that you copied from http://www.iisanswers.com/Top10FAQ/t10-FTPuersfolder.htm was not for 2000.


Report Offensive Follow Up For Removal

Response Number 4
Name: Scott
Date: February 22, 2002 at 10:52:19 Pacific
Subject: IIS ftp-How do I give private home DIRs?
Reply: (edit)

Following David's instructions I just successfully set it up on Win2K. Why do you think you can't?


Report Offensive Follow Up For Removal







Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: IIS ftp-How do I give private home DIRs?

Comments:

 


  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 
Data Recovery Software