From a84f1e7535b64dcfb1f274097cf947d0ad6fd1ec Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Thu, 16 Jan 2003 02:21:51 +0000 Subject: regenerate docs (This used to be commit 2215dc37e26bec17eb971e7b54818622a9bb5b97) --- docs/htmldocs/winbind.html | 119 ++++++++++++--------------------------------- 1 file changed, 31 insertions(+), 88 deletions(-) (limited to 'docs/htmldocs/winbind.html') diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index df5a59f771..1558512a61 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -5,7 +5,8 @@ >Unified Logons between Windows NT and UNIX using Winbind

Chapter 16. Unified Logons between Windows NT and UNIX using Winbind

Chapter 15. Unified Logons between Windows NT and UNIX using Winbind

16.1. Abstract

15.1. Abstract

Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -107,9 +104,7 @@ CLASS="SECT1" >

16.2. Introduction

15.2. Introduction

It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -161,9 +156,7 @@ CLASS="SECT1" >

16.3. What Winbind Provides

15.3. What Winbind Provides

Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once @@ -203,9 +196,7 @@ CLASS="SECT2" >

16.3.1. Target Uses

15.3.1. Target Uses

Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -227,9 +218,7 @@ CLASS="SECT1" >

16.4. How Winbind Works

15.4. How Winbind Works

The winbind system is designed around a client/server architecture. A long running

16.4.1. Microsoft Remote Procedure Calls

15.4.1. Microsoft Remote Procedure Calls

Over the last two years, efforts have been underway by various Samba Team members to decode various aspects of @@ -273,9 +260,7 @@ CLASS="SECT2" >

16.4.2. Name Service Switch

15.4.2. Name Service Switch

The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system @@ -353,9 +338,7 @@ CLASS="SECT2" >

16.4.3. Pluggable Authentication Modules

15.4.3. Pluggable Authentication Modules

Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -402,9 +385,7 @@ CLASS="SECT2" >

16.4.4. User and Group ID Allocation

15.4.4. User and Group ID Allocation

When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is @@ -428,9 +409,7 @@ CLASS="SECT2" >

16.4.5. Result Caching

15.4.5. Result Caching

An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind @@ -451,9 +430,7 @@ CLASS="SECT1" >

16.5. Installation and Configuration

15.5. Installation and Configuration

Many thanks to John Trostel

16.5.1. Introduction

15.5.1. Introduction

This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access @@ -537,9 +512,7 @@ CLASS="SECT2" >

16.5.2. Requirements

15.5.2. Requirements

If you have a samba configuration file that you are currently using...

16.5.3. Testing Things Out

15.5.3. Testing Things Out

Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all

16.5.3.1. Configure and compile SAMBA

15.5.3.1. Configure and compile SAMBA

The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon @@ -718,9 +687,7 @@ CLASS="SECT3" >

16.5.3.2. Configure 15.5.3.2. Configure nsswitch.conf and the @@ -823,9 +790,7 @@ CLASS="SECT3" >

16.5.3.3. Configure smb.conf

15.5.3.3. Configure smb.conf

Several parameters are needed in the smb.conf file to control the behavior of

16.5.3.4. Join the SAMBA server to the PDC domain

15.5.3.4. Join the SAMBA server to the PDC domain

Enter the following command to make the SAMBA server join the PDC domain, where

16.5.3.5. Start up the winbindd daemon and test it!

15.5.3.5. Start up the winbindd daemon and test it!

Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of @@ -1067,17 +1028,13 @@ CLASS="SECT3" >

16.5.3.6. Fix the init.d startup scripts

15.5.3.6. Fix the init.d startup scripts

16.5.3.6.1. Linux

15.5.3.6.1. Linux

The

16.5.3.6.2. Solaris

15.5.3.6.2. Solaris

On solaris, you need to modify the

16.5.3.6.3. Restarting

15.5.3.6.3. Restarting

If you restart the

16.5.3.7. Configure Winbind and PAM

15.5.3.7. Configure Winbind and PAM

If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other @@ -1324,9 +1275,7 @@ CLASS="SECT4" >

16.5.3.7.1. Linux/FreeBSD-specific PAM configuration

15.5.3.7.1. Linux/FreeBSD-specific PAM configuration

The

16.5.3.7.2. Solaris-specific configuration

15.5.3.7.2. Solaris-specific configuration

The /etc/pam.conf needs to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes @@ -1540,9 +1487,7 @@ CLASS="SECT1" >

16.6. Limitations

15.6. Limitations

Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -1581,9 +1526,7 @@ CLASS="SECT1" >

16.7. Conclusion

15.7. Conclusion

The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate -- cgit