asked on

Azure AD connect to multiple forests

Hi,

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!

Mahesh

As far as I know, wherever you have same NetBIOS name, you cannot add the multiple domains

I don't see any problem with city.com, it should add as long as all AD ports are opened from azure ad connect to that domain DC (PDC)

Jozef Woo

ASKER

Hi Mahesh, thanks for your reply. Do you have any reference about the fact that having a duplicate NetBIOS is not allowed? I had been searching for that but I couldn't find any information about it.

SOLUTION

Mahesh

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

SOLUTION

Jozef Woo

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

ASKER CERTIFIED SOLUTION

Jozef Woo

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

Jozef Woo

ASKER

I found that the problem was related to AD Connect not being able to find the necessary SRV records in DNS. This wasn't mentioned in any of the suggested solutions or comments.