Single-server question (simple).

  • Thread starter Thread starter Traveler
  • Start date Start date
T

Traveler

Okay, not to get flamed here, but I have an elementary grasp on AD. I
understand the setup procedure, and have a few books to help me with
the setup, but none of them seem to answer a simple question.

First, my question:
When setting up AD, I will use it as the local dhcp server (disabling
the routers'), and setup a local DNS server. What I want to know; does
all internet/network traffic go through this server? I routinely
transfer several gigs between machines and a local network drive and I
think performance will suffer if it's all forced through one machine.

The following may or may not be pertinent :-)

My network background:
I have about a dozen computers and twice as many printers. They are
connected through local wall jacks and hubs/switches to a patch panel
with a large switch, then (for internet) through a router and a dsl
modem. Right now the router is the local dhcp server, and all computers
are part of a workgroup.

What is lacking:
New users and rights continually need to be updated and changed, and we
add or change printers on an almost weekly basis. This requires me to
set up each machine independently and its very time consuming. Not to
mention I miss a machine at times causing users to freak out.

What I want to do:
Set up a domain controller with active directory to facilitate (a)
single global setting(s) that will automatically be applied to all
machines. We already purchased Win2K Advanced Server and it's been
sitting in the back for a few years, but I could really use it now (I
think). The network runs just fine the way it is (except what I noted).
I just want the server to sit in the corner and authenticate users.

Thank you.
 
Unless you set the server up as a router, no traffic should be routed through
it. Being a DHCP and DNS server means it provides IP addresses to clients asking
for them and name resolution for clients configured to use the server for DNS.
 
If you are going to turn off the DHCP on the router, ensure that your new
DHCP scopes on the server match the previous scopes on your router. Or,
create all new scopes and update your routing tables accordingly. Also,
remember that if you have only one server acting as a DC and it goes down,
users won't be able to log in to the domain, only locally.
 
Back
Top