RRinTetons
IS-IT--Management
This is mostly a "concept" question. If it's straight forward please point me to the doc's that cover this sort of stuff and I can probably go from there.
I have a Win2K Server (SP2) sitting in the Cisco PIX DMZ on our corporate network.
I want to have three web sites on it.
Site A should be accessible to both internal and external users (public) with no authentication. This site will contain ASP pages.
Site B should be accessible w/o further authentication to domain members when they hit it from their workstations within the corporate network, and with authentication when they hit it from outside. The users hitting it from the outside are not necessarily members of the company NT domain. This site will contain ASP and Perl cgi's.
Site C should always require authentication and it should be distinct from standard domain authentication. Again, some users hitting it from the outside will not be domain users. This site will contain ASP and Perl cgi's.
Direction?
I have a Win2K Server (SP2) sitting in the Cisco PIX DMZ on our corporate network.
I want to have three web sites on it.
Site A should be accessible to both internal and external users (public) with no authentication. This site will contain ASP pages.
Site B should be accessible w/o further authentication to domain members when they hit it from their workstations within the corporate network, and with authentication when they hit it from outside. The users hitting it from the outside are not necessarily members of the company NT domain. This site will contain ASP and Perl cgi's.
Site C should always require authentication and it should be distinct from standard domain authentication. Again, some users hitting it from the outside will not be domain users. This site will contain ASP and Perl cgi's.
Direction?