Unable to Connect to Domain Controller

I am setting up a virtual environment to host Project Server 2010 beta.  Using VirtualBox I created a domain controller, SQL server and application / web server.  All 3 machines are running windows server 2008 r2.   When I try to connect the SQL or application / web servers to the domain controller I get the following error  "An attempt to resolve the DNS name of a domain controller in the domain being joined has failed."  I am able to ping both clients to the domain contolller and vica versa using both ip addresses and names.  Can you shed some light on this.  
moronid1Asked:
Who is Participating?
 
NetExpert-WarszawaConnect With a Mentor Commented:
It should be (just example - can be different):

DC:
IP: 192.168.101.1
netmask: 255.255.255.0
DNS: 192.168.101.1
name: dc.name.of.domain

SQL:
IP: 192.168.101.2
netmask: 255.255.255.0
DNS: 192.168.101.1
name: sql.name.of.domain

web:
IP: 192.168.101.3
netmask: 255.255.255.0
DNS: 192.168.101.1
name: web.name.of.domain

What is important above is:
IP addresses have all the first three numbers common
IP addresses have the fourth number different
DNS server is set to DC IP address
a domain name for all computers is the same and is a name of your ad domain.

After restarting all servers see a DNS console on DC. You should find your domain in forward zones. There must be some ad records there. Could you give a screen shot please?
0
 
NetExpert-WarszawaCommented:
The SQL server and the web server need to have DNS server set to an IP address of DC. Do they have it?
0
 
elawadCommented:
do the regular nslookup DCname  from either the SQL server or the web server and see th results if it resolves the coorect ip address of the domain controller or you get an error.  by doing this you can see also if your resolving the ip address through the correct DNS at your domain or you have DNS error.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
moronid1Author Commented:
I set the client servers "Preferred DNS server address" to the DC ip.  Same error when trying to add clients to domain.
0
 
moronid1Author Commented:
Run "nslookup DC" and got the following message:
DNS request timed out.
        timeout was 2 seconds
Server:  Unknown
Address: 169.254.232.176
*** UnKnown can't find DC:  Server failed.
0
 
NetExpert-WarszawaCommented:
169.254.232.176 this is APIPA address. Set all computers to some (the same) IP network.

What is an output when you run it on DC?
0
 
moronid1Author Commented:
I'm sorry for not having network engineering experience.  I installed AD and it installed DNS.  I didn't setup a static ip address on the DC.  I let the install do wth work.  The 169.254.232.176 was what the install assigned to the DC.  Should I assign a static ip to the DC such as 192.168.101.1?  Also I ran the nslookup DC on the DC and go the following:
DNS request timed out
        timeout was 2 seconds
Server:  UnKnown
Address:  ::1
*** UnKnown can't find DC:  Non-existant domain

Thanks so much for your help.  I am under a deadline to get Project Server 2010 installed on the VM.
0
 
NetExpert-WarszawaCommented:
First of all, set "Preferred DNS server address" on DC too. It must register itself (and active directory records) with a DNS.

It will be much easier if you set IP addresses. Now you have no guarantee that after restart the same addresses remain.
0
 
moronid1Author Commented:
So you are suggesting that I set the DC to a static ip?  So, I will use 192.168.101.1.  Do I need to set the SQL server (client) to a static ip as well?  If so, what number should I use?  Thanks.
0
 
moronid1Author Commented:
I set the DNS on the DC as the ip of the DC.  I also verified that the SQL box has the same ip as the prefereded DSN.  Still got the same error with trying to connect the SQL server to the domain.  Thanks.
0
 
moronid1Author Commented:
It am connected!  Thanks so much for the lesson on AD.  I struggled so much with this I will never forget what you taught me on the use of static ip addresses.  Now I can get on with installing Project Server 2010.  Thanks again, Moroni
0
 
moronid1Author Commented:
Very knowledgeable and good at transferring knowledge!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.