"Mike T." <MikeT@discussions.microsoft.com> wrote in message
news:D9808F2C-B2E5-4BD3-A535-39A984ADE7E0@microsoft.com...
>I tried the suggestion below and it did not work for me, I get prompted to
> check the directory exists and try again.
>
> Any other suggestions?
>
> Mike
>
>
> "Bernard" wrote:
>
>> Create a virtual directory at the ftp site level, mapped it to the
>> physical
>> path, then control access with proper NTFS permissions.
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.microsoft.com/iis/
>> http://www.iiswebcastseries.com/
>> http://www.msmvps.com/bernard/
>>
>>
>> "msnews.microsoft.com" <brian@visionpro.com> wrote in message
>> news:eV4pR1gYFHA.3220@TK2MSFTNGP14.phx.gbl...
>> > Good morning,
>> >
>> > I'm using user isolation on my FTP server (not AD User Isolation) and
>> > for
>> > users that are local on the box it's working fine. I've got
>> > \ftproot\localuser\user and life is good. For AD users, it seems to be
>> > working, I've got \ftproot\<DOMAIN>\user and that works good.
>> >
>> > The problem that I'm encountering is that I need a bit more
>> > flexibility.
>> > Any user that's in AD (an employee) needs to have access to the entire
>> > FTP
>> > server from the real / (root) level. Any user that are local on the
>> > ftp
>> > machine (not in AD) need to be jailed into their home directory ...
>> > With
>> > one
>> > exception.
>> >
>> > The above is true with one minor exception .. I have a global
>> > \ftproot\Updates folder that any authenticated user should be able to
>> > read
>> > from and any authenticated AD user should be able to write to. How do
>> > I
>> > go
>> > about doing this? I'll also need to allow someway for my AD users to
>> > be
>> > able to write to the local users folders.
>> >
>> > Can someone help me out here?
>> >
>> > -brian
>> > brian at visionpro.com
>> >
>> >
>>
>>
>>