IIS Server Security, Pro's & Con's...

Hello all,

Before I get to babbling on, please feel free to correct
me if I'm wrong at any point, and please forgive the
massive long post for such a simple queery!

I'm in the process of designing the infrastructure for
when we move to Win2k network/domain.
I'm not very experianced in IIS and was looking for some
advice.
One problem is our current NT Domain name is no longer
relevant to the company, and so we want to tidy it up from
a user perspective (logging on from internet). So our
upgrade strategy includes moving to a new domain name of
fashion.com. Unfortunatly NT/2k logon uses netbios for
domain names, so our users would still have to use our old
domain name. What I did discover is if IIS sits on a
Domain Controller then there's no need no put a domain
name in when logging on. However whilst having a quick
browse through the jungle that is Microsoft.com I came
across a statement that IIS and DC on the same box can
cause replication issues, and put a heavy load on the
server.

Now to the point.
There are a few ways of implementing IIS, but what are the
pros and cons of having IIS sat on Domain Controller, or a
member server, or in a different forest etc???
Are there any standard practices you could reccommend?

Thanks for reading all this, any help is appreciated!

Matt.

Is your primary concern the ability for user to logon without typing the
domain? If so, just set the default domain ...
http://support.microsoft.com/?kbid=168908

--
Tom Kaminski IIS MVP
http://www.iistoolshed.com/ - tools , scripts, and utilities for running IIS
http://mvp.support.microsoft.com/
http://www.microsoft.com/windowsserver2003/community/centers/iis/

Agreed. Putting IIS onto a domain controller might be acceptable IF you are
a small organization with not a lot of money for extra servers, and the
server is not visible from the Internet, and keeping the server secure from
internal users is not a big concern for you.

On Mon, 27 Oct 2003 04:47:15 -0800, "Matt Rowe"



Pros - Not really any. Cons - Plenty. From the replication issues
you mention, to the security aspect of running under a domain account
and so on.


IIS on a stand-alone server, outside the firewall, for external
access. A separate internal IIS for intranet use. VPN's if users
need to connect from outside.

Oh, and fashion.com is taken.

Jeff

Agreed, though there are some organizations [think churches, non-profits,
small home offices, dentists offices, etc.] that may want to share files or
information via HTTP and can't afford $1500. MS Small Business Server is
relatively popular, even though [if I understand correctly] a typical SBS
configuration puts the firewall, email server and domain controller on the
same single server.

Give me a call, I think I know how to sort this ou

From http://www.developmentnow.com/g/91_2003_10_0_0_363853/Pros-Cons--.ht

Posted via DevelopmentNow.com Group
http://www.developmentnow.com