So I'll admit I'm relatively new to the Domain Controller side of networking and probably set something up incorrectly, but here's my problem. I have a fresh install of Windows server 2003, ran dcpromo, setup a DHCP server with a route that points
to our router "192.168.1.1" as the default gateway, have the DNS on the router pointed to the DC and have turned off DHCP on my router. I have also forwarded a few ports to the DC, such as HTTP, DNS, FTP etc.. The DC is setup with a static IP and to point
at itself for a DNS server.
Here's my problem, the DHCP server works great. It assigns IP addresses to new clients and gives them a default gateway of 192.168.1.1, but I am unsure as to why the DNS server and/or active directory is not working. After a client PC receives an IP from
the DC, it is unable to resolve DNS i.e. I cant ping
www.google.com
but I can ping 8.8.8.8 or another IP address. I also cannot add any of my client machines to the domain, they say that they are unable to find any domain controllers, which is bizarre
because they are able to ping and receive an IP address from my DC's DHCP server.
I have followed several guides for setting up the DC step by step, but no matter how many times I've tried I keep running into the same problem. The DNS server on the DC does not seem to be working, or even connected to Active Directory. I do not know
if my problem lies with the way I setup my router of if I am missing some important step.
Thanks for the help, technical information is listed below:
Ipconfig /all output from DC:
Windows IP Configuration

Host Name . . . . . . . . . . . . : kermit
Primary Dns Suffix . . . . . . . : ecaeagles.org
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ecaeagles.org

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-11-43-C8-69-95
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1

Ipconfig /all output from client:
Windows IP Configuration

Host Name . . . . . . . . . . . . : eca1001
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ecaeagles.org
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-13-20-0C-3E-1C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.5
Lease Obtained. . . . . . . . . . : Thursday, June 14, 2012 4:25:27 PM
Lease Expires . . . . . . . . . . : Friday, June 22, 2012 4:25:27 PM

There is an amazing pack of free network admin tools. click here to download it

I ran nslookup on both a client machine and on the DC. Where is the DNS located in the DHCP server settings? Under scope options I have options 003 for router and 015 for a Domain name with the value of my domain, do I need to add another option? Or is it
elsewhere?

Thanks for the help,

here is the output of nslookup:
Client:
C:\Documents and Settings\llira.ECA1001>nslookup ecaeagles.org
*** Default servers are not available
Server: UnKnown
Address: 127.0.0.1

*** UnKnown can't find ecaeagles.org: No response from server

DC:
C:\Documents and Settings\Administrator.KERMIT.000>nslookup ecaeagles.org
Server: localhost
Address: 127.0.0.1

Name: ecaeagles.org
Address: 192.168.1.5

Need to support users over the internet? click here try our remote control online beta

Good afternoon!

I don't see a DNS entry in your ipconfig results. It may be a matter of making sure that the DHCP server is landing out the IP of the DC for DNS.
What result do you get from:
nslookup <YourDomainFQDN> (Ex: nslookup tiertwo.local)
C:\Users\jeff>nslookup tiertwo.local
Server: sbs2011
Address: 10.50.1.10

Name: tiertwo.local
Address: 10.50.1.10


The first entry returned is the DNS server providing results, and the second entry is the name result.
If you get a result that looks more like this, you have DNS issues.

C:\Users\jeff>nslookup tiertwo1.local
Server: sbs2011
Address: 10.50.1.10

*** sbs2011 can't find tiertwo1.local: Non-existent domain


Check the "DNS Servers" entry in your DHCP scope.

There is an amazing pack of free network admin tools. click here to download it

I ran nslookup on both a client machine and on the DC. Where is the DNS located in the DHCP server settings? Under scope options I have options 003 for router and 015 for a Domain name with the value of my domain, do I need to add another option? Or is it
elsewhere?

Thanks for the help,

here is the output of nslookup:
Client:
C:\Documents and Settings\llira.ECA1001>nslookup ecaeagles.org
*** Default servers are not available
Server: UnKnown
Address: 127.0.0.1

*** UnKnown can't find ecaeagles.org: No response from server

DC:
C:\Documents and Settings\Administrator.KERMIT.000>nslookup ecaeagles.org
Server: localhost
Address: 127.0.0.1

Name: ecaeagles.org
Address: 192.168.1.5

Need to support users over the internet? click here try our remote control online beta

Hello,
DNS servers are 006 in the DHCP scope options and DNS is MOST important in a domain.
Also it seems the workstation is NOT joined to the domain yet?Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog:
http://msmvps.com/blogs/mweber/


Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Need to support users over the internet? click here try our remote control online beta

Great! Adding option 006 fixed all of my issues. I couldn't add that machine to the domain because it was unable to see that there was a domain on the network since DNS was broken. I couldn't find option 006 since it was the next option in the list if
you scrolled down, I was so frustrated with this not working that I didn't notice the scroll bar... Thanks for the help I feel pretty dumb for not seeing that!

Need to support users over the internet? click here try our remote control online beta

Hello,
DNS servers are 006 in the DHCP scope options and DNS is MOST important in a domain.
Also it seems the workstation is NOT joined to the domain yet?Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog:
http://msmvps.com/blogs/mweber/


Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

There is an amazing pack of free network admin tools. click here to download it

Great! Adding option 006 fixed all of my issues. I couldn't add that machine to the domain because it was unable to see that there was a domain on the network since DNS was broken. I couldn't find option 006 since it was the next option in the list if
you scrolled down, I was so frustrated with this not working that I didn't notice the scroll bar... Thanks for the help I feel pretty dumb for not seeing that!

There is an amazing pack of free network admin tools. click here to download it

Glad to hear you're all set!

Need to support users over the internet? click here try our remote control online beta

Glad to hear you're all set!

Need to support users over the internet? click here try our remote control online beta