Click here for important information about Computing.net.

Solved Server 2008 / Win 7 Client / VMware

Tags:
Server
July 5, 2012 at 09:36:27
Specs: Windows Server 2008 RC2, AMD Athlon II X4 965
I'm doing the self-paced Training Kit for Microsoft Exam 70.685 and it says I have to have a server running Windows Server 2008 R2 Standard configured as a domain controller. As well as Two computers running Windows 7.

I've setup the server and clients in VMware Workstation and can successfully ping both 'machines' from each other.

However, I can't seem to get the clients to join the domain. It says it cannot contact the domain controller despite being able to ping both machines. I've attached a couple of screenshots. Anything obvious I'm missing? Just want to do the lessons and get on with the book!

Apologies if this is in the wrong forum, any pointers in the right direction would be great!

Server (2008): http://i.imgur.com/ah5Ch.jpg
Client (Win 7): http://i.imgur.com/b7a8a.jpg


See More: Server 2008 / Win 7 Client / VMware

Report •

✔ Best Answer
July 5, 2012 at 11:20:48
When you promoted the server to a DC it should have set up a DNS server. You now need to go into the network settings on the client and set the address of the server as the DNS server.

See in Thread ↓

#1
July 5, 2012 at 09:59:07
Odd you got it to ping.

Did you set all VM's to local network?

Hang up and live.


Report •

#2
July 5, 2012 at 10:01:10
Yep! Confusing the hell out of me.

First time using Active Directory so hoping I've set it up correctly


Report •

#3
July 5, 2012 at 10:12:15
1. Have you set up DHCP on the 2008 server? And is the Windows 7 VM getting it's IP setup from the 2008 server?

2. Is the Windows 7 machine using the 2008 server as it's DNS server?

#2, at least, is necessary for the domain to work properly.


Report •

Related Solutions
See More ↓

#4
July 5, 2012 at 10:15:59
I haven't, no. That's done by Add Roles in the Initial Configuration Tasks isn't it?

Report •

#5
July 5, 2012 at 10:39:05
DHCP is not compulsory, but the client must look to the server for DNS resolution. That's how it knows which computer is a DC.

Report •

#6
July 5, 2012 at 10:52:15
Thanks for your help. Is there a guide on how to set it up? Can't get my head round it all, which is why I'm doing these exams! :D

Report •

#7
July 5, 2012 at 11:20:48
✔ Best Answer
When you promoted the server to a DC it should have set up a DNS server. You now need to go into the network settings on the client and set the address of the server as the DNS server.

Report •

#8
July 7, 2012 at 18:45:04
Check the time settings on all systems, make sure they all have the same time within a couple minutes. Did you set your primary DNS server to your DC's IP address?

You need to have a DNS server running somewhere, most likely on your domain controller. Install that prior to installing Active Directory.

Tony


Report •
Start a discussion

Ask Question