Suggested server roles for a small home network?

[wdbdesign]

I'm rebuilding my 2003 server after a MB failure, and I'm looking for some advice.

Currently the 2003 server machine acts as a dedicated web server. I've got a separate desktop machine running XP, and a laptop that connects wirelessly, also running XP. All machines are behind a wireless router / firewall. The web server will be hosting pages written in ASP.NET. I'd like to be able to remote desktop to the server, and to access the drives from another machine on the network. The server will NOT be running exchange server, nor acting as any other kind of mail server.

What are the necessary and recommended server roles for the server? Do I need to install active directory? Does it need to be a domain controller? Do I need a domain at all, or can the server (and desktop machine) simply be part of a workgroup?

Thanks a ton for any tips!

 

[lhuegele]

You want to be able to remote desktop to this server from WITHIN your own network or over the internet?

Personally, I run a server at home and went ahead and set-up my own little AD network. The server has AD, DNS, and IIS running on it. I let my Linksys router handle the DHCP side.

Are all your O/S's in the house the PRO versions?

 

[wdbdesign]

>> You want to be able to remote desktop to this server from WITHIN your own network or over the internet?

Within the network is fine. If I absolutely need to get to the server from outside the network I can always use logmein.com to access my desktop, and RD from there to the server.

>> Are all your O/S's in the house the PRO versions?

All XPs are Pro versions. Server 2003 is Standard.

>> The server has AD, DNS, and IIS running on it.

I'm a novice in these areas, but...

I don't think I need DNS. I typically have everything set up to use my ISP's. I use my registrar's nameservers to point the domain to my static IP.

I'm not sure about AD. Might I need AD for authentication with ASP.NET pages in the future? Do I need AD for anything else?

It looks like you're not running as a domain controller (unless that's implied by the DNS). Is there any reason for me to set up a domain?

Thanks!

 

[lhuegele]

Yes, I'm running 2 VM domain controllers on one box actually. It just gives me more control over my home network environment, that's all. I don't know the answer to your ASP.NET question though. I guess you could base it on your need for different permissions for different things.

My internal DNS only gives me better FQDN access to my other computers. It's not external.

You should be able to do what you want without creating an AD domain.

Good luck,