Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I have Active Directory set up on a Windows Server 2008 Amazon EC2 server. Its set up correctly I think, I never got any errors with it. Just to test that I got it all set up correctly, I have a Windows 7 Professional virtual machine set up on my network to join to AD. I set the VM to use the Active Directory box as its DNS server. I type in my domain to join it, but I get the following error:

DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "":

The query was for the SRV record for

The following domain controllers were identified by the query:

However no domain controllers could be contacted.

Common causes of this error include:

- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

It seems that I can talk to Active Directory, but when I'm trying to contact the Domain Controller, its giving a private IP to connect to, at least thats what I can make out of it. Here are some nslookup results.


Non-authoritative answer:


Address: and are CNAME's pointing to my EC2 box. Any idea what I need to do so that I can join my virtual machine to the EC2 Active Directory set up I have?


share|improve this question
up vote 1 down vote accepted

Did you enable all the necessary ports in the security group? See this post...

share|improve this answer
Yup, all of the ports necessary are opened. – Chiggins Feb 20 '11 at 9:08

You can't do that without VPN. Your EC2 instance is using private IP address within EC2. While you're trying to connect from an external machine to LAN. So the Workstation attempts to ping the LAN IP of the EC2 DC which it can't reach.

You need the workstation/server to be on public IPs both, or both in the same LAN, or VPN between workstation LAN/WAN and server LAN.

share|improve this answer
I have a VPN setup, but its still not joining :( – Chiggins Mar 31 '11 at 15:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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