- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-InterdomainTrusts.xml
r414 r988 28 28 <indexterm><primary>ADS</primary></indexterm> 29 29 <indexterm><primary>LDAP-based</primary></indexterm> 30 Samba -3supports NT4-style domain trust relationships. This is a feature that many sites31 will want to use if they migrate to Samba -3from an NT4-style domain and do not want to30 Samba supports NT4-style domain trust relationships. This is a feature that many sites 31 will want to use if they migrate to Samba from an NT4-style domain and do not want to 32 32 adopt Active Directory or an LDAP-based authentication backend. This chapter explains 33 33 some 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-Samba34 possible for Samba to trust NT4 (and vice versa), as well as to create Samba-to-Samba 35 35 trusts. 36 36 </para> … … 75 75 <indexterm><primary>scalability</primary></indexterm> 76 76 <indexterm><primary>trust relationships</primary></indexterm> 77 Samba -3can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style77 Samba can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style 78 78 trust relationships. This imparts to Samba scalability similar to that with MS Windows NT4. 79 79 </para> … … 85 85 <indexterm><primary>interdomain trusts</primary></indexterm> 86 86 <indexterm><primary>ADS</primary></indexterm> 87 Given that Samba -3can function with a scalable backend authentication database such as LDAP, and given its87 Given that Samba can function with a scalable backend authentication database such as LDAP, and given its 88 88 ability to run in primary as well as backup domain control modes, the administrator would be well-advised to 89 89 consider alternatives to the use of interdomain trusts simply because, by the very nature of how trusts … … 166 166 Also, all inter-ADS domain trusts are transitive. In the case of the red, white, and blue domains, with 167 167 Windows 2000 and ADS, the red and blue domains can trust each other. This is an inherent feature of ADS 168 domains. Samba -3implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS168 domains. Samba implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS 169 169 security domains in similar manner to MS Windows NT4-style domains. 170 170 </para> … … 340 340 <indexterm><primary>between domains</primary></indexterm> 341 341 Each 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 -3domain. It can be clearly342 Windows NT4 server. However, the remote end could just as well be another Samba domain. It can be clearly 343 343 seen, after reading this document, that combining Samba-specific parts of what's written in the following 344 344 sections leads to trust between domains in a purely Samba environment. … … 591 591 592 592 <para> 593 It works with Samba -3and NT4 domains, and also with Samba-3 and Windows 200x ADS in mixed mode.593 It works with Samba and NT4 domains, and also with Samba-3 and Windows 200x ADS in mixed mode. 594 594 Both domain controllers, Samba and NT must have the same WINS server; otherwise, 595 595 the trust will never work.
Note:
See TracChangeset
for help on using the changeset viewer.