A trust is a relationship established between two different domains that enables users in one domain to be authenticated by a domain controller in the other domain. There are different type of trust in Microsoft Active Directory domain such as External, Realm, Forest and shortcut. External trust is necessary when users of two different domains of two different business units wants to utilize resources such as printers and file server of trusted domains. This article can be applied in Windows Server 2003, Windows Server 2008/R2, Windows Server 2012/R2 and Windows Server 2016 domain using same principle written below.
Authentication Consideration
| Authentication Setting | Inter-forest Trust Type | Description |
| Domain-wide Authentication | External | Permits unrestricted access by any users. Default authentication setting for external trusts. |
| Forest-wide Authentication | Forest | Permits unrestricted access by any users. Default authentication setting for forest trusts. |
| Selective Authentication | External and Forest | Restricts access over an external. Authentication setting must be manually enabled. |
Administrative Privilege
To create trust you have to be a member of Domain Admins & Enterprise Admin in both Domains.
Transitive trusts
- Shortcut trust. A transitive trust between domains in the same domain tree or forest that is used to shorten the trust path in a large and complex domain tree or forest.
- Forest trust. A transitive trust between one forest root domain and another forest root domain.
- Realm trust. A transitive trust between an Active Directory domain and a Kerberos V5 realm.
Non-transitive trusts
- External trust. A non-transitive trust created between a Windows Server 2003 domain and Windows 2000 or Windows Server 2003 domain in another forest.
- Realm trust. A non-transitive trust between an Active Directory domain and a Kerberos V5 realm.
You have to fulfill few requirements before you can activate external trust. For example: Both domain controller must ping each other by IP address. If both domain controllers are placed in different subnet then proper routing is required. If there is a firewall between domain controllers then proper firewall rules should be in place allowing LDAP, DNS and resources port to be accessible from both sites. Forest and domain functional level must be Windows Server 2003 or later version.
Example:
DC1.DomainA.com IP address: 192.168.100.2
DC1.DomainB.com IP address: 192.168.200.2
Step1: Port requirement
If you are using MPLS/IP VPN/VPN make sure inbound and outbound routing are in correct order. If you have firewall between organisation make sure Active Directory ports are open in both sides. Further info on port requirement visit Active Directory and Active Directory Domain Services Port Requirements
Step2: Add DNS Record in TCP/IP Properties of Domain Controllers
Open TCP/IP Properties of DC1.DomainA.com and add IP address of DC1.DomainB.com in the secondary DNS record.
Open TCP/IP Properties of DC1.DomainB.com and add IP address of DC1.DomainA.com in the secondary DNS record.
Step3: Ping DomainA from DomainB and vice versa
Log on to each domain and ping each other by IP address. Resolve IP without any delay or timed out ping.
Step4: Test AD DS Ports
Telnet to port 389, 636 & 53 from both sides of domain to test whether you can access Active Directory & DNS
Step5: Health Check
Run a quick AD health check in both sides using this Link
Step6: Create PTR Record in both organisation
Add Reverse Lookup Zone of 192.168.200.2 into DC1.DomainA.com. To do this, Right Click on Reverse Lookup Zone>New Zone>Click Next>Primary Zone>Click Next>IPV4 reverse Lookup Zone>Type 192.168.200>Click Next>Finish.
Repeat the step to add 192.168.100.2 PTR into DC1.DomainB.com. To do this, Right Click on Reverse Lookup Zone>New Zone>Click Next>Primary Zone>Click Next>IPV4 reverse Lookup Zone>Type 192.168.100>Click Next>Finish.
Step7: Create Forward Lookup Zones in both organisation
In some DNS environment where DNS have constrained access (situation specific only), you may have to create Forward Lookup Zone for DomainA.com into DomainB.com and Forward Lookup Zone for DomainB.com into DomainA.com. But there is no harm creating a forward lookup zone in both sides as both forests are going to trust each other once trust is activated.
To do this, log on to DomainA.com >Open DNS Manager>Expand Forward Lookup Zone> Right click on Forward Lookup Zones>New Zones>primary Zones>Type FQDN of forest e.g. DomainB.com. >Select Default or select “To all domain controllers in this forest”> Type Zone Name DomainB.com>Allow Secure Dynamic Update>Follow the Wizard.
To do this, log on to DomainB.com >Open DNS Manager>Expand Forward Lookup Zone> Right click on Forward Lookup Zones>New Zones>primary Zones>Type FQDN of forest e.g. DomainA.com. >Select Default or select “To all domain controllers in this forest”> Type Zone Name DomainA.com>Allow Secure Dynamic Update>Follow the Wizard.
Step8: Create Host (A) record in both organisation
Create Host (A) record of Domain Controller of DomainA.com into Domain Controller of DomainB.com. Create Host (A) record of Domain Controller of DomainB.com into Domain Controller of DomainA.com. To do this Log on to DC1.DomainA.com>Right click on Forward Look Up Zone you created in step 7 which is DomainB.com>Click New Host (A)>Leave the Name Blank> Type IP Address of DC1.DomainB.com & Select Associated PTR Record> Click Add Host.
Repeat the Steps in DomainB.com. To do this log on to DC1.DomainB.com>Right click on Forward Look Up Zone you created in step7 which is DomainA.com>Click New Host (A)>Leave the Name Blank> Type IP Address of DC1.DomainA.com & Select Associated PTR Record> Click Add Host.
Step9: Add Name Server (NS) in both organisation
You must add Name Server of DC1.DomainA.com into the Name Servers Property of DC1.DomainB.com. Repeat the step to add Name Server of DC1.DomainB.com into the Name Servers Property of DC1.DomainA.com.
To do this log on to DC1.DomainA.com>Open DNS Manager>Right click on Forward Look Up Zone of DomainB.com>Click Properties>Click Name Servers Tab>Click Add>Type the IP Address of DC1.DomainB.com.
Repeat the Steps in DomainB.com. To do this log on to DC1.DomainB.com>Open DNS Manager>Right click on Forward Look Up Zone of DomainA.com>Click Properties>Click Name Servers Tab>Click Add>Type the IP address of DC1.DomainA.com.
Step10: Test DNS Record
Ping FQDN of DomainA.com from DomainB.com
Ping FQDN of DomainB.com from DomainA.com
Ping DC1.DomainA.com from DC1.DomainB.com
Ping DC1.DomainB.com from DC1.DomainA.com
Step11: Create External Trust
Example: One way trust allows users from DC1.DomainB.com (outgoing) get access into DC1.DomainA.com (incoming) but DC1.DomainA.com doesn’t get access to DC1.DomainB.com).
Note : if you want both sides get access to both sides then change that configure to two way trusts and set incoming and outgoing in both sides.
Creating incoming trust in DC1.DomainA.com
1. Open Active Directory Domains and Trusts.
2. In the console tree, right-click the domain for which you want to establish a trust, and then click Properties.
3. On the Trusts tab, click New Trust, and then click Next.
4. On the Trust Name page, type the Domain Name System (DNS) name (or NetBIOS name) of the external domain, and then click Next.
5. On the Trust Type page, click External trust, and then click Next.
6. On the Direction of Trust page, click One-way: incoming, and then click Next.
7. On the Sides of Trust page, click This domain only, and then click Next.
8. On the Trust Password page, type the trust password twice, and then click Next.
With the administrator of the other domain, agree on a secure channel password to be used in establishing the trust.
9. On the Trust Selections Complete page, review the results, and then click Next.
10. On the Trust Creation Complete page, review the results, and then click Next.
11. On the Confirm Incoming Trust page, do one of the following
- If you do not want to confirm this trust, click No, do not confirm the incoming trust
- If you want to confirm this trust, click Yes, confirm the incoming trust, and then supply the appropriate administrative credentials from the specified domain.
12. On the Completing the New Trust Wizard page, click Finish.
Creating outgoing trust in DC1.DomainB.com
1. Open Active Directory Domains and Trusts.
2. In the console tree, right-click the domain for which you want to establish a trust, and then click Properties.
3. On the Trusts tab, click New Trust, and then click Next.
4. On the Trust Name page, type the Domain Name System (DNS) name (or NetBIOS name) of the external domain, and then click Next.
5. On the Trust Type page, click External trust, and then click Next.
6. On the Direction of Trust page, click One-way: outgoing, and then click Next.
7. On the Sides of Trust page, click This domain only, and then click Next.
8. On the Outgoing Trust Authentication Level page, do one of the following, and then click Next:
- Click Domain-wide authentication.
- Click Selective authentication.
9. On the Trust Password page, type the trust password twice, and then click Next.
10. On the Trust Selections Complete page, review the results, and then click Next.
11. On the Trust Creation Complete page, review the results, and then click Next.
12. On the Confirm Outgoing Trust page, do one of the following:
- If you do not want to confirm this trust, click No, do not confirm the outgoing trust. Note that if you do not confirm the trust at this stage, the secure channel will not be established until the first time that the trust is used by users.
- If you want to confirm this trust, click Yes, confirm the outgoing trust, and then supply the appropriate administrative credentials from the specified domain.
13. On the Completing the New Trust Wizard page, click Finish.
Step12: Test a Trust Relation
- Virtualize two Windows clients
- Join them to DomainA and DomainB
- Create two test folders in DomainA and DomainB
- Share and assign permission to users of DomainA and DomainB for both folders.
- Log on to a Windows client in DomainA using credential of DomainB>Access folder of DomainA
- Log on to a Windows client in DomainB using credential of DomainA>Access folder of DomainB
This is great and very helpful – Thank you very much!!
LikeLike
I like this blog very much.
Please send me those topics via my mail address.
LikeLike
Such a nice article. Thank you very much. Keep writing more articles.
LikeLike