Windows Server

dstein · Guest

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? 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?

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.

Any resources that somebody knows of, or any advice that you could give
would be greatly appreciated. Thanks in advance.

Jeff Cochran · Guest

On Sun, 9 Jan 2005 12:57:03 -0800, dstein
<dstein@discussions.microsoft.com> wrote:

Bill Grant · Guest

The only problem I can think of is DNS. Active Directory clients need to
use the local DNS server to find AD services. If your current setup is using
the DNS server at your ISP or using the router as a DNS proxy, you will need
to modify that.

Also make sure that you do not have DHCP running on both the router and
the server. You can use either, but not both.

"dstein" <dstein@discussions.microsoft.com> wrote in message
news:0123C9AA-A37A-40CC-9150-5E89B2A485B9@microsoft.com...

Brendan Saunders · Guest

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:

Brendan Saunders · Guest

That's why you use DNS forwarders on the server.

"Bill Grant" wrote:

dstein · Guest

Thanks to both of you. I appreciate the time you've taken to read and answer
my questions. I will have a chance to try your suggestions sometime tomorrow.

In the meantime, I've been reading a book to get as much background as
possible before I get started. I think I've got the concept of a domain, but
there is a few questions that have been on my mind. In the book (Mastering
Windows 2000 Server, Mark Minasi), the author walks through several example
scenarios for setting up a server. He makes the following "warning" each
time:

"Do not use the domain name win2ktest.com unless you are not connected to
the internet. If your network is or will ever be attached to the internet,
then either use a domain name that you have registered ... or a nonsensical
name that does not conflict with an already-registered name."

I've actually not tried some of the examples because I'm not sure how I
should approach something so simple as naming my domain! I want to create
and use a domain, but I don't want it exposed publicly to the whole internet
.... however, I *do* want to be able to access the internet on my workstations
and server. It seems to me that this would *have* to be possible, right?

I mean, theoretically, couldn't I name my domain microsoft.com? As long as
I do what is necessary to keep the domain "private"? So I guess my real
question here is, how do I create a domain that is "private", but whose
members can still access the internet?

And as long as I'm on the subject, is it possible for me to create a domain,
not register it, and gain access to it remotely by just ensuring that my new
domain is always "connected" to the internet?

If you read this far, I really do thank you for taking up your time. I'm
very interested in learning more about how this stuff works. The book has
been very helpful, but since these questions have come up, I've not been able
to move forward to other concepts. I look forward to hearing any answers you
may have.

Thank you again.

"Brendan Saunders" wrote:

	Windows Server Forum Index -> Networking	All times are GMT
Page 1 of 1