Re: Setting up Active Directory

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brendan Saunders (BrendanSaunders_at_discussions.microsoft.com)
Date: 01/09/05 

Date: Sun, 9 Jan 2005 15:59:02 -0800

Hey DStein

Much as I appreciate the value of reading up, and this is meant in no
disrespect at all to Jeff, exploring the server is a very good way to learn.
When I first created a domain in Win2K Server I had no experience at all and
barely understood the concept of a domain.

The "Set Up Your Server" page which displays by default when you first
startup your server contains a link to setup a Domain with Active Directory.
This starts the wizard to get everything started.

As for your internet access; Set up the DHCP service from the server setup
screen, create a scope (IP Address Range) (probably best to use 192.168.*.*).
 Exclude 192.168.*.1 and 192.168.*.2 from the scope and use these for your
router and server's static IP addresses. In your server's TCP/IP properties
assign it a static address that u excluded in your scope. You will need to
make sure that the router has a static IP address and is set as the default
gateway in the scope options. Set the DNS Server as the server's IP address
in the scope options.

Then setup DNS service, again from the same server setup screen, this pretty
much sets itself up, follow the wizards. In the server's TCP/IP properties,
manually enter the server's own IP address as it's DNS Server.

You will then need to access the admin interface of your router and note
down the DNS addresses specified there. In the DNS console windows select the
properties of the server -> Forwarders. Enter the DNS addresses as forwarders
to forward non-resolved DNS queries to your internet DNS.

These are the most basic setup tips. Going into any more detail would be an
immense task and reuire the MCSE that I haven't actually finished yet!!

Use TechNet and the forums, there are a lot of experienced ppl out there.

Good Luck

Brendan

"Jeff Cochran" wrote:

> On Sun, 9 Jan 2005 12:57:03 -0800, dstein
> <dstein@discussions.microsoft.com> wrote:
>
> >I have an existing home network that consists of two Windows XP Pro computers
> >and a cable modem (providing internet access) connected to a wireless router.
> > The XP computers are configured to use dynamic DHCP and the router acts as a
> >DHCP server.
> >
> >I now own a computer that I've installed Windows 2000 Server, but have not
> >set it up with any server services yet (DHCP, DNS, Active Directory, etc.),
> >because I don't know how to proceed.
> >
> >I would like to setup the new server as a domain controller running Active
> >Directory, but I don't want to change how my existing pc's access the
> >internet (through the wireless router running DHCP).
> >
> >My question is, can I create a domain, and run Active Directory for the
> >purpose of sharing resources (not internet) between my pc's?
>
> Yes.
>
> > How should I
> >setup the server so that I can basically use it as a file server, application
> >server, etc. without changing how I access the internet?
>
> Just set it up. The only key to accessing the internet is the Default
> Gateway setting in the workstation's TCP/IP settings.
>
> >I am a novice in the area of server operating systems. And I know that
> >running Active Directory on a Windows 2000 server on a domain is overkill for
> >my small home network. My main reason for doing this is for educational
> >purposes. I'd like to learn more about administering a network, and for me,
> >it's better to actually set something up than to just read about it.
>
> That's the best way to learn.
>
> >Any resources that somebody knows of, or any advice that you could give
> >would be greatly appreciated. Thanks in advance.
>
> Start with Microsoft and the white papers on Active Directory. A
> decent book may help, if you're already accomplished at server
> management the books aimed at the Active Directory MCSE exams would be
> ideal.
>
> Jeff
>

Relevant Pages

  • Re: How to configure for Two different IP subnets
    ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
    (microsoft.public.windows.server.networking)
  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... We have around 17 remote sites so using a DC for each would be expensive, and I can't see a benefit at the moment. ... also the DNS server. ... which includes the DNS. ... We really need a lot more info about the setup. ...
    (microsoft.public.windows.server.networking)
  • Re: Domain Controller Down
    ... I am guessing you are correct about the 'tweaking', as this was setup a long ... I don't know enough about how to setup DNS, but it looks to me like there is ... The Domain Name System name recommendations for Small Business Server 2000 ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Restoring Active Directory domain
    ... I believe you're right and the problem is in my DNS setup. ... on the new temp server, ... Unlimited Access, Anonymous Accounts, Uncensored Broadband Access ...
    (microsoft.public.win2000.active_directory)
  • Re: Restoring Active Directory domain
    ... Is that temp DC multihomed? ... I believe you're right and the problem is in my DNS setup. ... the new temp server, I get this: ...
    (microsoft.public.win2000.active_directory)