1

I'm trying to set up an domain in Azure AD Connect on a Workgroup computer. The challenge that we have is, we have a dedicated domain controller for the purpose of Azure AD Connect and the other domain controllers are in a non-routable network for AD Sync server (We chose not to install AD Connect on Domain Controller for various reasons). Sites & Services are configured properly but when we attempt to add the extra domain, we get the error "The Specified Domain does not exist or cannot be contacted."

Routes exists, firewall rules allow standard AD traffic along with dedicated AD Sync server's traffic as well. If I attempt to join the computer to the domain, I am prompted for credentials which I think would be successful if I click OK.

mutukrp
  • 31
  • 6
  • Hi, do you have a firewall between your workgroup computer and the DC? have you opened tcp/udp port135? this port is needed during the setup to bind to the AD forest. this link list all the ports needed: https://azure.microsoft.com/sv-se/documentation/articles/active-directory-aadconnect-ports/ – Michael Brown Apr 11 '16 at 18:18
  • Thanks Michael. The ports mentioned in the article are opened between the AD Connect server and only one domain controller. The other domain controllers are non-routable. – mutukrp Apr 12 '16 at 09:29

2 Answers2

0

Finally, we ended up upgrading the AD Connect version which resolved the issue. Appears to be a glitch in that particular version we had.

mutukrp
  • 31
  • 6
-2

Might be in the user name you're using: https://blog.kloud.com.au/2015/12/16/azure-ad-connect-the-specified-domain-does-not-exist-or-cannot-be-contacted-when-adding-an-untrusted-ad-forest/

Jos
  • 1
  • 1