<taoberly@mindspring.com> wrote in message
news:1186719622.799240.310500@g12g2000prg.googlegroups.com...
>I am setting up an Internet-accessible, password-protected FTP server
> for use by our customers, and as we're running Windows 2003 Server,
> decided to try IIS's FTP service first. Getting it up and running was
> fairly easy, but I have been frustrated that I can't seem to limit the
> accounts that can use the service, in the same way the "Remote Desktop
> Users" group limits who can use that connection method. Can someone
> tell me the exact criteria that lets an account authenticate in FTP?
> Is it simply everybody with a working local or domain login, or
> something else? I want to reduce the number
> logins that work, for obvious security reasons, and if this isn't a
> outright feature, am curious if there's still a trick to accomplish
> the same thing.
>
> Thanks for any feedback.
>
> Todd
>

<qbern...@hotmail.com.discuss> wrote:
> If it's a windows account, then it will be able to login remotely.
> to block specific access or only allow group of user.
>
> put all users in the an user group. then only allow the user group to have
> READ and etc permission on the ftp path.
> even if other users able to login but he/she will get access denied error.

<taoberly@mindspring.com> wrote in message
news:1186875066.101654.6550@d55g2000hsg.googlegroups.com...
> On Aug 10, 4:38 am, "Bernard Cheah [MVP]"
> <qbern...@hotmail.com.discuss> wrote:
>> If it's a windows account, then it will be able to login remotely.
>> to block specific access or only allow group of user.
>>
>> put all users in the an user group. then only allow the user group to
>> have
>> READ and etc permission on the ftp path.
>> even if other users able to login but he/she will get access denied
>> error.
>
> Thanks for the reply. I had a terrible time finding documentation
> that actually spelled this out. This is basically how it's configured
> now, but I'm still not too keen on the arrangement. Gotta think it
> over.
>
> Thanks,
>
> Todd
>