Ignore:
Timestamp:
Nov 24, 2016, 1:14:11 PM (9 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: update vendor to version 4.4.3

File:
1 edited

Legend:

Unmodified
Added
Removed
  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-InterdomainTrusts.xml

    r414 r988  
    2828<indexterm><primary>ADS</primary></indexterm>
    2929<indexterm><primary>LDAP-based</primary></indexterm>
    30 Samba-3 supports NT4-style domain trust relationships. This is a feature that many sites
    31 will want to use if they migrate to Samba-3 from an NT4-style domain and do not want to
     30Samba supports NT4-style domain trust relationships. This is a feature that many sites
     31will want to use if they migrate to Samba from an NT4-style domain and do not want to
    3232adopt Active Directory or an LDAP-based authentication backend. This chapter explains
    3333some background information regarding trust relationships and how to create them. It is now
    34 possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba-to-Samba
     34possible for Samba to trust NT4 (and vice versa), as well as to create Samba-to-Samba
    3535trusts.
    3636</para>
     
    7575<indexterm><primary>scalability</primary></indexterm>
    7676<indexterm><primary>trust relationships</primary></indexterm>
    77 Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style
     77Samba can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style
    7878trust relationships. This imparts to Samba scalability similar to that with MS Windows NT4.
    7979</para>
     
    8585<indexterm><primary>interdomain trusts</primary></indexterm>
    8686<indexterm><primary>ADS</primary></indexterm>
    87 Given that Samba-3 can function with a scalable backend authentication database such as LDAP, and given its
     87Given that Samba can function with a scalable backend authentication database such as LDAP, and given its
    8888ability to run in primary as well as backup domain control modes, the administrator would be well-advised to
    8989consider alternatives to the use of interdomain trusts simply because, by the very nature of how trusts
     
    166166Also, all inter-ADS domain trusts are transitive. In the case of the red, white, and blue domains, with
    167167Windows 2000 and ADS, the red and blue domains can trust each other. This is an inherent feature of ADS
    168 domains. Samba-3 implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS
     168domains. Samba implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS
    169169security domains in similar manner to MS Windows NT4-style domains.
    170170</para>
     
    340340<indexterm><primary>between domains</primary></indexterm>
    341341Each of the procedures described next assumes the peer domain in the trust relationship is controlled by a
    342 Windows NT4 server. However, the remote end could just as well be another Samba-3  domain. It can be clearly
     342Windows NT4 server. However, the remote end could just as well be another Samba  domain. It can be clearly
    343343seen, after reading this document, that combining Samba-specific parts of what's written in the following
    344344sections leads to trust between domains in a purely Samba environment.
     
    591591
    592592<para>
    593 It works with Samba-3  and NT4 domains, and also with Samba-3 and Windows 200x ADS in mixed mode.
     593It works with Samba  and NT4 domains, and also with Samba-3 and Windows 200x ADS in mixed mode.
    594594Both domain controllers, Samba and NT must have the same WINS server; otherwise,
    595595the trust will never work.
Note: See TracChangeset for help on using the changeset viewer.