Windows 2003 Setup Domain Controller

October 21, 2010 at 18:14:49
Specs: Windows 2003 Server
First of all I am a nube...This is my home setup...

Setup:

Cable Broadband > Netgear WNDR3300 > 4 Laptops / 1 Desktop
> Dlink DAP-1522 >2 Desktops (one is Server 2003)

Now, I was wanting to setup the DHCP server on the Windows Server 2003 machine and turn off DHCP on the Netgear router, however I finally figured out that neither the Netgear or the Dlink support BOOTP (So it looks like that it out). If anyone knows of a way around this, please inform me :-).

Next, I have run through DCPROMO and have configured, it looks as though my DNS is configured properly and active directory is running fine. Here are a couple of things that I am wondering about.

1) Since the server is running on the network like it is connected shown above, shouldnt it work fine? Or do I need multiple nics into to make it run?

2) When I try to join another computer to the domain, it says the domain controller cannot be found.

3) When I go into my router and say for the DNS to point to the server, then in the DNS on the server I use the ISP's DNS servers for the forwarders, all my machines discontinue the ability to retrieve anything on the internet.

I am sure that I will have more, hoever this is predominent problems at this point.

I would be very gratefull for the information and any help anyone can give.

Thanks in advance,

Chris


See More: Windows 2003 Setup Domain Controller

Report •

#1
October 22, 2010 at 07:41:55
1) Is this entire network all using the same subnet? If yes, then clients should be able to reach the DC without trouble. However, the DC should have a static IP address, not one given out by DHCP.

2) Your issue here most likely is that all your clients are getting the TCP/IP settings from the DHCP server on the router and you haven't changed the settings on it yet. Ensure clients are getting the IP address of the DC as their DNS IP address. Default Gateway IP for them should remain the LAN IP of the router.

3) DNS is required to promote a server to a DC. I prefer to let dcpromo take care of the DNS. Typically, DNS will point at the IP of the DC and/or it's loopback (127.0.0.1). When finished promoting you then forward your DNS to that of your ISP so that requests outside the local zone get forwarded to the ISP's DNS server. Requests inside the local zone are handled by the DC.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
February 23, 2011 at 20:52:03
Make sure you setup the servers IP as a static IP rather than your DHCP server on your router assigning it an IP address. When you setyp a client, you have to make usre you use that same IP address you used for the static as the DNS server IP. One thing I cannot figure out is that I have setup a forwarder on my DNS (using opendns server) but when I use just the IP of my 2003 server, say a static IP of 192.168.1.109, I cannot resolve outside addresses unless I also add the open dns server IP to my list of DNS servers on the client machine...I thought I could just use the static IP address as DNS and if it didnt resolve the name it would forward it to the open dns servers via the forwarder configuration?! If i setup my DNS IP as just the 20003 server IP, I cannot resolve doamains like ebay.com, cnn.com, etc.

So I need to check the recursion option or something else I missed?


Report •

#3
February 23, 2011 at 21:46:06
1. you don't need multiple nics
2. common issue. either the server dns isn't configured properly or you are not pointing the workstation to the servers static ip for dns.

"When I go into my router and say for the DNS to point to the server"
wan or dhcp server? not wan or major mistake.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
February 24, 2011 at 01:10:10
In your OP you refer to BOOTP. Why would you need this?

Let the Windows server handle DHCP and DNS. It will need a fixed address (which, obviously, you exclude from the DHCP range). The clients will then use the Windows server for DNS. On that server (and nowhere else) you configure forwarding via an external DNS server (OpenDNS is fine) to resolve all queries that the Windows server can't resolve.

You can't use a DNS server on your router, or the OpenDNS servers, for your clients as those servers won't have the necessary entries for your Domain. When you set up Active Directory it automatically creates a number of DNS entries that are esential for the system to work.


Report •

Ask Question