0

I'm trying to set up Azure AD Connect with a sync from 3 forests to 1 tenant. However, I'm struggling to add the forests in the AD Connect wizard.

I'm working with the following domains:

intranet.city.com with Netbios name "INTRANET" intranet.pdwxcity.com with Netbios name "INTRANET" city.com with Netbios name "CITY"

In the "Connect your directories" page, I was able to add the "parent" (company owning the tenant) domain intranet.city.com but I couldn't add the other domains. All the required ports are open. I am getting the following errors (depending on the format of the credentials; Netbios name, full domain name, UPN, etc):

The provided user was not found in the directory. Specify a valid domain account OR The specified forest does not exist or cannot be contacted OR The specified domain does not exist or cannot be contacted

Any idea what the problem could be? Is the fact that they have similar Netbios or top level domains a problem?

Please note that I am working with the hosts file for name resolution to the other domains. I don't know if this is a problem or not.

Thanks a lot for the help!

0

Sounds like a name resolution issue to me. What entries do you have in your host file? why aren't you using DNS? you need to be able to resolve the SRV records of the domains you want to connect to. Can the server you have installed Azure AD Connect on resolve those records? what DNS Server is it using?

  • Hi Michael Brown, thank you for your reply. In the hosts file I have added the domain name and the domain controller of the intranet.pdwxcity.com domain. The city.com domain controllers are resolvable through DNS (using the DC/DNS of intranet.city.com - where the AD Connect server is installed). How can I check if the SRV records can be resolved? – Jozef Woo Apr 11 '17 at 16:59
  • If there is separate DNS server in each forest, then on the DNS server the AD Connect is using, you can add Conditional Forwarders for other two forests/domains. You can refer to the following article for Conditional Forwarder. technet.microsoft.com/en-us/library/… – Andy Liu - MSFT Apr 12 '17 at 8:20
  • @Jozef: just to check if the issue has been resolved. – Andy Liu - MSFT Apr 19 '17 at 9:48
  • Hi Andy, thanks for the follow-up. It hasn't been resolved yet. Will know for sure if it's resolved on the 3th of May. In the mean time I can say that I'm also convinced now that it's a DNS issue and that configuring forwarders will probably resolve it. I will update this thread as soon as I've implemented the forwarders. Thanks again! – Jozef Woo Apr 20 '17 at 17:42
0

The problem has been solved by manually creating SRV records for the other domains. DNS forwarders were not in place because of some particular setup at the customer.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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