Server 2003 and DSL Router

Hi

I am setting up a small office system with Server 2003 and Client
PCs with Windows XP. I want to primarily use the Server 2003
as a file server and print server.

I am using a Linksys DSL Router as the gateway to the Internet. I
don't know much about Server 2003 but my questions are as follows:

i) If I set up AD on the Server, does the Server have to be the DHCP
Server?

ii) Should I disable the DHCP server on the Linksys router and let
the Server 2003 do it?

iii) If I do disable DHCP server on the Linksys box, how do all the
PCs know the address of the gateway?

iv) My installation is only 20 machines and I am not a public domain,
do I need my Server to have DNS enabled. All machines are at the same
domain. VERY simple network topology.

v) For simple file sharing, should I set up a DFS root?

Thanks for all your help. Sorry if all this info is in a FAQ
somewhere.

If you use Active Directory and you have only one server then yes you MUST
setup DHCP on the server in order for the domain to work correctly. Proper
dns configuration is critical in an AD domain. When you enable DHCP and
create a scope, the scope will give the client computers the IP address of
the default gateway. Your domain controller will provide ALL dns services
for the domain computers including internet name resolution by configuring
your domain controller to forward dns internet queries to your ISP dns
server. Definitely disable DHCP on the router if you are going to have an AD
domain. I have not used DFS enough to comment about it, though I doubt that
it will be that useful on a small network. See the links below about Active
Directory dns. Make sure that you assign a static IP address to the server
and point it to itself as it's preferred dns server in tcp/ip properties
BEFORE you run dcpromo on it to make it a domain controller. Also think
carefully about the domain name you want to use as it will be difficult to
change it at a later time. I suggest that you do not use a name currently
used on the internet. Many use .corp as mydomain.corp for their domain name.
The Windows 2003 Pocket Consultant is a great book to have around to
configure your domain/network for day to day stuff and Mark Minasi's
Mastering Windows 2003 Server is the book to get for in depth
learning/configuring of Windows 2003. --- Steve

http://support.microsoft.com/default...en-us%3B291382
http://support.microsoft.com/default...en-us%3B323380
http://www.bookpool.com/.x/in3mat9kp0/sm/0735613540

"John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hi
>
> I am setting up a small office system with Server 2003 and Client
> PCs with Windows XP. I want to primarily use the Server 2003
> as a file server and print server.
>
> I am using a Linksys DSL Router as the gateway to the Internet. I
> don't know much about Server 2003 but my questions are as follows:
>
> i) If I set up AD on the Server, does the Server have to be the DHCP
> Server?
>
> ii) Should I disable the DHCP server on the Linksys router and let
> the Server 2003 do it?
>
> iii) If I do disable DHCP server on the Linksys box, how do all the
> PCs know the address of the gateway?
>
> iv) My installation is only 20 machines and I am not a public domain,
> do I need my Server to have DNS enabled. All machines are at the same
> domain. VERY simple network topology.
>
> v) For simple file sharing, should I set up a DFS root?
>
> Thanks for all your help. Sorry if all this info is in a FAQ
> somewhere.