From 2a85f0cf33f303e091ce6f6bea7b7a072cd81c14 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 15 Jan 2003 22:29:27 +0000 Subject: syncing docs with HEAD (This used to be commit d8fe70c3b4be548244e9d7b7ea533e64232df001) --- docs/htmldocs/domain-security.html | 47 ++++++++++++++++++++++---------------- 1 file changed, 27 insertions(+), 20 deletions(-) (limited to 'docs/htmldocs/domain-security.html') diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html index 8273525710..1a10767235 100644 --- a/docs/htmldocs/domain-security.html +++ b/docs/htmldocs/domain-security.html @@ -2,19 +2,22 @@ security = domain in Samba 2.xSamba as a NT4 domain memberPrevNextChapter 9. security = domain in Samba 2.xChapter 10. Samba as a NT4 domain member

9.1. Joining an NT Domain with Samba 2.2

10.1. Joining an NT Domain with Samba 2.2

Assume you have a Samba 2.x server with a NetBIOS name of

9.2. Samba and Windows 2000 Domains

10.2. Samba and Windows 2000 Domains

Many people have asked regarding the state of Samba's ability to participate in -a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows +a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows 2000 domain operating in mixed or native mode.

There is much confusion between the circumstances that require a "mixed" mode @@ -333,9 +336,9 @@ CLASS="SECT1" >

9.3. Why is this better than security = server?

10.3. Why is this better than security = server?

Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching @@ -435,7 +438,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevNextSecurity levelsSamba as a ADS domain member UpUnified Logons between Windows NT and UNIX using WinbindOptional configuration