Active Directory

By trbleshooter ·
I have less than 20 users and setting up a domain(server 2003) from a workgroup. Is there a reason not to just leave the DHCP and DNS services with the router? I would really just like to use this as a fileserver and a DC for Active Directory. Is DHCP, DNS and fileserving to much for a single server?

Thanks in advance.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by ---TK--- In reply to Active Directory

You will be fine running AD, DNS, DHCP and a file server on one server.... However, if that server goes down, you screwed the pooch... for now I would only run AD and the file server on a single server... and leave the DNS and DHCP services with the router.... once your infrastructure gets larger (30+) I would think about adding a second server, to handle the other services...

Collapse -

You will need

by cmiller5400 In reply to Active Directory

You will need DNS on the domain controller. Active directory requires it. DHCP can stay with the router. You can configure the DNS server on the DC to forward to your router for all DNS lookups that it can't service.

Collapse -

I forgot about that....

by ---TK--- In reply to You will need

Active Directory's dependence on DNS...

Collapse -

Active Directory & Server roles

by Nimmo In reply to Active Directory

Having AD,DHCP,DNS, and also configure the server to be a file server isn't an issue, (take a look at SBS servers they host all services).

DHCP, DNS, & AD aren't resource hungry services they just service small requests from PC & other servers.

Just make sure your server has decent amount of RAM and fast drives (The gona get thrashed with 20 users accessing it for files etc.. You should also provide redundancy such as been in a RAID configuration).

Personally I think that you should put DHCP on the server because having the DHCP server on the router wont help much if the server goes down.

This is because the PC's will be getting DNS from the server therefore when the server goes down you wont be able to resolve hosts on the local netwrok or the internet anyway.

So unless the uses know the IP addresses of the sites they want to visit and the IP address of the server along with the full share path they isn't much point having DHCP on the router servicing the PC's lol.

Related Discussions

Related Forums