We were hoping to use our Domain Controller as our webserver also and were
hoping to give FTP access to a few websites. Is it possible and why is it not
a good idea.
Thanks for your input thus far
Those kind of services (FTP and HTTP) are open to the web and makes you vulnerable to
hackers and Internet worms. You don't want to subject a Domain Controller to such possible
exploitation. It would NOT be in your best interest !
--
Dave
| We were hoping to use our Domain Controller as our webserver also and were
| hoping to give FTP access to a few websites. Is it possible and why is it not
| a good idea.
| Thanks for your input thus far
|
| "David H. Lipman" wrote:
|
| > I don't think it's a good idea to put it on a Domain controller.
| > I think it would be more secure to be on a workstation or member server.
| >
| > --
| > Dave
| >
| >
| >
| >
| > | > | What are the minimum security rights you need to setup and FTP user account
| > | on a windows 2000 domain controller?
| > |
| > | Thanks,
| > | Luke
| > |
| >
| >
| >
Windows' built-in FTP server uses domain authentication; ftp users must be
able to also log into your system. This is not secure.
I highly recommend a third-party FTP server, such as Serv-U from cat-soft.
You can allow domain users, or use an entirely different set of logins.
You can have read-only and write-only directories, and in ten years of
operation, only two security problems have been found - and each was fixed
the same day it was announced.