Beruflich Dokumente
Kultur Dokumente
exe
You can use nltest to:
Test trust relationships and the state of domain controller replication in a Windows
domain
Trust relationships are not transitive. For example, suppose Domain "X" trusts
Domain "Y", which in turn trusts Domain "Z". This does NOT imply Domain "X" trusts
Domain "Z". The reason for this is that the administrator in each domain must grant
explicit permission on either side of the trust relationship for it to take place.
Another form of trust relationship is sometimes referred to as an "implicit" trust. In a
single domain model, or in an environment where there are no "explicit" trust
relationships between any two domains, the "implicit" trust relationship is active
and functionally needed. This implicit trust exists between all computers running
Windows NT that are members of a domain and a domain controller in their domain.
Explicit trust relationships are established through User Manager For Domains.
Implicit trust relationships are established by becoming a member of a domain.
Nltest.exe can be used to test the trust relationship between a computer running
Windows NT that is a member of a domain and a domain controller where its
machine account resides. NLTEST can also verify the trust between the BDCs in a
domain and their PDC. In domains where an explicit trust has been defined, NLTEST
can test the trust relationship between all domain controllers in the trusting domain
and a domain controller in the trusted domain.
These sessions of communication are called Secure Channels and are used to
authenticate Windows NT machine accounts. They are also used to authenticate
User Accounts when a remote user connects to a network resource and the user
account exists in a trusted Domain. This is called Pass-Through Authentication, and
it allows a computer running Windows NT that has joined a domain to have access
to the User Account Database in its domain and in any Trusted Domains.
Nltest.exe can use the Browser Service to enumerate domain controllers. Therefore,
if browsing is not working correctly, Nltest.exe may produce inconsistent results.
The computer where Nltest.exe is run and those providing the browsing services
need to share the same protocols that are used by the domain controllers to carry
out their domain activity. In addition, the enumeration of the specified computer
and domain names depend on the status of name-resolution, such as WINS server
replication, IPX router configuration, or NetBEUI bridging.
All of these trust relationships, and domain synchronization, can be monitored,
tested, and verified by Nltest.exe.
Sample Output Obtained by Typing "NLTEST.EXE" Without the Quotes
C:\NTRESKIT>nltest
Usage: nltest [/OPTIONS]