Windows Server 2003, IIS6, isolating users frustration

Ken, can't thank you enough. There was one little titbit in the first
article that I was missing that was ~precisely~ what I needed. For anybody
else following this thread, or who encounters this in the future:

1. The IIS5 method works in Windows 2003 Server.
2. One IP address can control multiple FTP folders, which are limited to the
user logging in.
3. (and this is the key point) The user has to have "list" access to the ftp
root, in additional to whatever access the user has to his own folder.

Excellent articles! Thank you again.

- Wm


--
William Morris
Product Development, Seritas LLC
Kansas City, Missouri

"Ken Schaefer" <kenREMOVE DeleteThis @THISadOpenStatic.com> wrote in message
news:%23ychj8EnEHA.3988@TK2MSFTNGP10.phx.gbl...
 > Hi,
 >
 > There are a couple of ways you can do this. You can still do it the old
IIS5
 > way, or you can use the other way that's available. It's all a little
 > confusing because some of the documentation out there isn't so good.
 >
 > This may help explain:
<font color=purple> > <a style='text-decoration: underline;' href="http://www.orcsweb.com/articles/mastering_iis_ftp.aspx</font" target="_blank">http://www.orcsweb.com/articles/mastering_iis_ftp.aspx</font</a>>
<font color=purple> > <a style='text-decoration: underline;' href="http://www.orcsweb.com/articles/mastering_iis_ftp2.aspx</font" target="_blank">http://www.orcsweb.com/articles/mastering_iis_ftp2.aspx</font</a>>
<font color=purple> > <a style='text-decoration: underline;' href="http://www.orcsweb.com/articles/mastering_iis_ftp3.aspx</font" target="_blank">http://www.orcsweb.com/articles/mastering_iis_ftp3.aspx</font</a>>
 >
 > Cheers
 > Ken
 >
 > "William Morris" <news.remove.this.and.the.dots DeleteThis @seamlyne.com> wrote in
 > message news:2qugc2F12fjhcU1@uni-berlin.de...
  > > We have a folder structure, developed under Win2K/IIS5, that looks about
  > > like this:
  > >
  > > c:\inetpub\wwwroot
  > > \OurApplication
  > > \ClientImages
  > > \ClientID1
  > > \ClientID2
  > > \DataUploads
  > > \ClientID3
  > > \ClientID4
  > >
  > > In IIS, it looks like this...
  > >
  > > OurFTPSites
  > > \ClientLogin1 (virtual - pointing to
  > > c:\inetpub\wwwroot\OurApplication\ClientImages\ClientID1)
  > > \ClientLogin2 (virtual - ditto\ClientID2)
  > > \ClientLogin3 (virtual - c:\inetpub\wwwroot\DataUploads\ClientID3)
  > > \ClientLogin4 (virtual - ditto\ClientID4)
  > >
  > > Under IIS5, by giving each of our users their own logins and virtual
  > > directories, they are locked in to their own folders but within the web
  > > tree
  > > so the web application/ASP files, scripting.FileSystemObject, and other
  > > programs can all get to the files.
  > >
  > > So, now we're getting ready to move to another server, Windows2003/IIS6.
  > > I've read all about isolating users, but it appears that we're being
  > > locked
  > > into a folder structure of "ftproot\LocalUser\username", which doesn't
  > > help.
  > > I've tried using the IIS5 method of virtual directories, but I get a
"User
  > > ClientLogin1 cannot log in, home directory inaccessible." Permissions
are
  > > set properly on the target folder, identical in every substantive way to
  > > our
  > > Win2K server.
  > >
  > > What's the answer here? Am I stuck with the folder structure Microsoft
  > > dictates? Seems like a HUGE step backwards.
  > >
  > > - Wm
  > >
  > > --
  > > William Morris
  > > Product Development, Seritas LLC
  > > Kansas City, Missouri
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Windows Server 2003, IIS6, isolating users frustration 

On Thu, 16 Sep 2004 16:54:17 -0500, "William Morris"
<news.remove.this.and.the.dots RemoveThis @seamlyne.com> wrote:

 >We have a folder structure, developed under Win2K/IIS5, that looks about
 >like this:
 >
 >c:\inetpub\wwwroot
 > \OurApplication
 > \ClientImages
 > \ClientID1
 > \ClientID2
 > \DataUploads
 > \ClientID3
 > \ClientID4
 >
 >In IIS, it looks like this...
 >
 >OurFTPSites
 > \ClientLogin1 (virtual - pointing to
 >c:\inetpub\wwwroot\OurApplication\ClientImages\ClientID1)
 > \ClientLogin2 (virtual - ditto\ClientID2)
 > \ClientLogin3 (virtual - c:\inetpub\wwwroot\DataUploads\ClientID3)
 > \ClientLogin4 (virtual - ditto\ClientID4)
 >
 >Under IIS5, by giving each of our users their own logins and virtual
 >directories, they are locked in to their own folders but within the web tree
 >so the web application/ASP files, scripting.FileSystemObject, and other
 >programs can all get to the files.
 >
 >So, now we're getting ready to move to another server, Windows2003/IIS6.
 >I've read all about isolating users, but it appears that we're being locked
 >into a folder structure of "ftproot\LocalUser\username", which doesn't help.

If you change your web root to match it works fine. Or use virtual
folders pointing to the web roots.

 >I've tried using the IIS5 method of virtual directories, but I get a "User
 >ClientLogin1 cannot log in, home directory inaccessible." Permissions are
 >set properly on the target folder, identical in every substantive way to our
 >Win2K server.

Still have to have the same structure, the virtual folder is in the
uer's root, you can't use it *as* the user's root.

 >What's the answer here? Am I stuck with the folder structure Microsoft
 >dictates?

Yep.

 >Seems like a HUGE step backwards.

So use a Non-Microsoft FTP server such as WFTPD.

Jeff<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Windows Server 2003, IIS6, isolating users frustration