Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

On a beefy server, I have a few Virtual Machines (VMs) running. On one of those, I have Domain Controller (DC) with a domain name (ex:SQL.AD.COM) running successfully. Now, I need to add the other VMs into this domain. How do I do that?

For AlwaysOn, all nodes must in a domain. So, for that to happen, all nodes need to be added to the domain created by the DC. When I go to My Computer >> Properties >> Computer Name >> Change Settings >> Computer Name (tab) >> Change >>

Add Computer to Doamin

I can change the computer name, but could not add the VM to the domain. What is missing?

This is the error I get: enter image description here I have the following network properties for each VM.

Domain Controller has 1 NIC

  1. First:
    • Name: AD
    • Type: Host-Only Adapter
    • Static IP Address (of VM): 200.201.202.1

What IP address settings do I need to configure for VM's to be able to join the domain? I have 3 nodes (VMs)

After @Phil comments, I removed the 200.201.xx.xx IP and added 192.168.1.x IP address pattern.

Thanks,
_UB

share|improve this question

closed as off topic by Jon Seigel, Mark Storey-Smith, dezso, Leigh Riffel, Marian Mar 5 '13 at 14:55

Questions on Database Administrators Stack Exchange are expected to relate to database administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
Can your server see (ping) the Domain Controller? Also, can it hit the DNS server? –  Thomas Stringer Feb 22 '13 at 1:24
    
It cannot ping either of them. DNS server? I do not remember configuring one. –  UB01 Feb 22 '13 at 1:29
2  
I believe a DNS server is a requirement for a domain. Either way, without seeing the DC a server won't be able to join the domain. –  Thomas Stringer Feb 22 '13 at 1:49
1  
200.201.202.1 is a proper internet routeable address. Did you mean to use that? If not, best to use 192.168.x.x, 10.x.x.x or 172.16.x.x as those are reserved for local use. Making sure your VM server software networking config aligns with all of this, obviously –  Phil Feb 22 '13 at 1:56
1  
In the settings of the network adapter, there is a place to put the IP Address of the DNS server. It's where you configure a static IP, subnet mask, etc. –  Thomas Stringer Feb 22 '13 at 2:03
show 4 more comments

1 Answer 1

up vote 0 down vote accepted

Finally after some reading more articles on Windows and AD Networking and speaking with abunch of people, this is what helped.

Settings on DC machine:

IP: 192.168.1.10
Subnetmask: 255.255.255.0
Gateway: (none)

Preferred DNS: 127.0.0.1
Alternate DNS: (none)

On Each VM:

IP: 192.168.1.11 (/12/13.../15 - on each node)
Subnetmask: 255.255.255.0
Gateway: (none)

Preferred DNS: 192.168.1.10 Alternate DNS: (none)

Restart the Network Adapter. BOOM !!

Now I can ping the DC and add them to the domain.

Why does it work now (but not before):

For DC: I made the DNS as loopback IP as preferred DNS (rather than its own IP - 192.168.1.10). This way it knows that the machine itself is the DNS.

For VMs: Gave them valid static IPs, rather than dynamic IP. Set the DNS to the DC (this was set correctly even before).

Glad I learnt something new,
_UB

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.