Link to home
Start Free TrialLog in
Avatar of Luis_Romero
Luis_Romero

asked on

Setup Domain Trust for internal networks fail - Unable to contact domain error

I have a primary domain, we will call it MM and a virtual domain, called MP. The MM domain is all physical and has been running with no issues. the MP domain is new, and is an attempt to split MM into 2, which is MP. I have a server running ESXi and I have 2 domain controllers running Server 2008 R2, MM domain is running Windows Server 2003. I installed the DNS, DHCP, and AD running. MP is running on a separate subnet, .2.1 and MM is running on .1.1. I can ping the MM domain, and MM can ping the MP domain with no problems. DNS entries were made on both sides (setup as Primary, which I think where the problem is) so the netbios names can be interpreted and pinged.

However, when I do the seemingly easy task of setting up the domain trusts using AD, I enter my MP domain into the fields, set it for Trust with a Windows domain, click next and it fails. The message states that the MP domain cannot be contact... But I can ping the domain, so where is the disconnect?
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Also you need to setup either conditional forwarder or secondary zone of both domains to each other so that they can identify each other and then you can establish trust
You can also use stub zones to accomplish this. They're easier to set up than secondaries, since you don't have to configure zone transfers.