all groups > iis ftp > april 2005 >
You're in the

iis ftp

group:

IIS FTP in Longhorn; request of features


IIS FTP in Longhorn; request of features Miha
4/30/2005 4:56:19 PM
iis ftp:
I will write down few functions I would like to have in IIS in Longhorn:
- Option to ban IP
- Option to allow/deny file extensions
- Option to set upload/download limit
- Option to add user(and password for that user)
- Option to have gorups and put users in that group
(All users connected through that FTP could be represented as single user on
NTFS level, like IIS for Anonymous access)
- Option to add premissions for read, write, delete to every user
- Option to set FTP more easy to listen on 21 port for those behind firewall

And colud be more. I dont know, what is going on, but other ftp server have
this features for years. But IIS stil have just few features, old more the
me. Its time to include more features in IIS FTP. :)


Re: IIS FTP in Longhorn; request of features Bernard
5/1/2005 12:00:00 AM
[quoted text, click to view]

these are already in place and link to windows user database.

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/


[quoted text, click to view]

Re: IIS FTP in Longhorn; request of features jeff.nospam NO[at]SPAM zina.com
5/2/2005 12:00:00 AM
On Sat, 30 Apr 2005 16:56:19 -0700, "Miha"
[quoted text, click to view]

Already exists as part of the firewall and IP restrictions.

[quoted text, click to view]

For upload or download (or both)? You could work around this with
NTFS permissions and a bit of scripting if you desperately needed it.

[quoted text, click to view]

You mean by size? Quantity? Bandwidth? You can limit the size of a
user's folder using quotas, but not individual up/download limits.
And as far as most of the Microsoft target audience for the FTP
service goes, this is probably very low on the request list. For file
excahnge sites, especially home servers, this may be an issue, but not
for most organizations.

[quoted text, click to view]

These are all part of the basic Windows system and have been functions
available forever. In Server 2003 you also have user isolation you
can work with. You may wnat to look at:

HOW TO: Create a Secure FTP Directory that Uses Password
Authentication:
http://support.microsoft.com/?id=239120

How To Limit Access to a FTP Site in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816525

INFO: FTP Site Administration Documentation in IIS 6.0:
http://support.microsoft.com/default.aspx?scid=kb;en-us;814865

Hosting Multiple FTP Sites with FTP User Isolation
http://www.microsoft.com/resources/documentation/IIS/6/all/techref/en-us/iisRG_CFG_21.mspx

[quoted text, click to view]

You may need to explain this. FTP can be set for any port already,
and if you do nothing it's on 21/20 by default. Firewalls don't
change this function.

[quoted text, click to view]

Microsoft's FTP will never have all the features of third party
products. Someone from Microsoft *may* be able to comment on what's
AddThis Social Bookmark Button