The initial slide shows the ADT s environment which consists of a simulated is forest with to the main
trees a datum dot com and fabric in dot com.
The two child domains EU did a datum that comment is spear for breaking that comb are physically located
in the same city in Spain frequent resource share and exist between these two editors demands the parent
80 days demands a datum that comment for broken dot com exists in North American cities although transitive
trust relationships exist between all the aid it is domains in the ADT is forest no direct authentication
link exists between where you do it a datum that command is spear for broken dot com.
So let's review the slides on the first slide.
The slide depicts the authentication process that is required when a user from client computer seal
one wishes to access a file on file server D.
An arrow is shown from EU dot a datum dot com to ISP dot for brick and dot com on the second slide.
CLIENT 1 contact the local ADT as the main controller client 1 and this domain controller refers to
the 8 it is the main controller 2 That is next in line on the third slide the entity the main controller
2 referrals client 1 to 80 days domain controller 3 in four broken dot com on the fourth slide the 8
it is domain controller 3 referrals client 1 2 8 it is the main controller for an ISP that for broken
dot com on the fifth slide.
CLIENT 1 uses the ticket that ADT as the main controller for issued to contact files solver.
In is spelled out for broken dot com and on the 6 slide it is depicted as a shortcut trust that is established
between ISP dot for broken dot com and EU dot a datum that come with a shortcut trust established client
one receives a ticket from the local aid it is domain controller 1.
Now it can contact ADT as the main controller for in there is PD dot for broken dot com 80 days domain
and then receives a ticket to access file server D.
So in this scenario without the shortcut trust in place several communications must travel to North
American back the network link might not be fast or 100 percent reliable or it could be expensive.
Therefore the shortcut trust improves performance and more than one way.
So when you set up trusts between demands within the same forest across forests or with an external
the real information about this trust such as transit TvT and type is stored in active directory at
trusted domain object stores.
This information this domain object is created and stored in the system container.
In 80 years whenever you set up a trust how trusts enable users to access resources in a forest.
Let's recap the previous slides.
So when a user in a domain attempts to access a shared resource in another domain in the forest the
user's computer first contacts demand control or needs domain to request a session take it to the resource
because the resource is not in the user's domain.
The domain controller must determine whether a trust exists with a target domain.
The domain controller can use the trust domain object to verify that the trust exists.
However to access the resource the client computer must communicate with a domain controller in each
domain along the trust path.
The domain controller and the client computers domain refers the client computer to a domain controller
in the next domain along the trust path.
If that is not the domain where the resources located the domain controller refers the client computer
to a domain controller in the next domain.
Eventually the client computer is referred to a domain controller in the domain where the resource is
located and the client is issued a session ticket to access the resource.
The trust pass is a shorter pass through the trust hierarchy in a forest in which only the default trusts
are configured.
The trust passed does and goes up the demand tree to the forest root domain and then down the domain
tree to the Tajik domain.
If shortcut trusts are configured the trust path might be a single hop from the clan computer domain
to the domain that contains the resource.