small IIS virtual server network model

[kanoz]

Im in the planning stages of setting up a Windows network for the purpose of running a small web hosting and design business.

The network will consist of one Windows 2k Server and two Win 2K workstations, a hardware firewall/router/dsl modem on a 1.5mb/728kb adsl connection with a static IP.

The server will be running IIS5 and some form of SMPT mail server (haven't decided yet). The IIS server will host multiple domain names using host headers. The mail server will have to be able to recieve email for multiple domains and forward mail to my clients' POP3 ISP email accounts.

I will be using zonedit.com to create zone files for the domains i'll be hosting, so i won't be running my own public dns servers. I will be hosting my own business's website on this server plus several sites belonging to my clients.

My questions are:

1. I am unable to decide or find information on whether I should install DNS integrated Active Directory and promote the webserver to a PDC for my internal network, or just use a workgroup. Is there any factors binding me to use an internal domain with this set up i have just explained?

2. Is there any security issues associated with having the PDC, webserver and email system running on the same box? If so, can anybody offer advise or any links on this subject?

3. What email software could I use to achieve the aims described above? I am thinking about using pegasus mail. My workstations use Outlook so it must be something compatible with outlook clients, and also able to forward mail to multiple domains. I am also contemplating Exchange server but don't really like the price tag.

4. If i were to create an internal domain, when configuring the servers suffix should i use mybusinessname.local or mybusinessname.com. mybusinessname.com is a registered domain but I kind of like the idea of keeping my public domain name and private network separate. Don't ask why, it just feels safer this way Any ideas or input?

I appreciate any help anybody can offer.

Cheers

[DVNT1]

1) from what you have mentioned, AD would not be very useful
2) yes, generically speaking, the more services on the computer the more potential exploits there are. On the otherhand it may be worth the risk in your situation
3) no RL experience with email other than Groupwise
4) I would not use a domain model in your situation but if there was reason to, I would keep it named differently from the public www domains you host.

[M_Six]

I highly recommend MailEnable for your email server. I have it running for three domains and it's been rock solid. The Professional version includes web and http mail as well as pop. The standard version is free and you can try the Pro version for 30 days. Has a nice anti-virus integration setup, too. Although you have to have your own anti-virus program.

[kanoz]

thanks for that. i've decided to set up a WORKGROUP as there doesn't appear to be any real reason to set up an internal domain so i may as well save myself the headaches of setting up AD. I installed and tested MailEnable last night and it worked great. i can set up multiple post offices for each domain, redirect mail and use it in conjunction with Outlook on the LAN.

does the AV integration only come with the Pro version?