+++ /dev/null
-<HTML
-><HEAD
-><TITLE
->OS2 Client HOWTO</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
-><BODY
-CLASS="ARTICLE"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="ARTICLE"
-><DIV
-CLASS="TITLEPAGE"
-><H1
-CLASS="TITLE"
-><A
-NAME="OS2"
->OS2 Client HOWTO</A
-></H1
-><HR></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3"
->FAQs</A
-></H1
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN5"
->How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</A
-></H2
-><P
->A more complete answer to this question can be
- found on <A
-HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html"
-TARGET="_top"
-> http://carol.wins.uva.nl/~leeuw/samba/warp.html</A
->.</P
-><P
->Basically, you need three components:</P
-><P
-></P
-><UL
-><LI
-><P
->The File and Print Client ('IBM Peer')
- </P
-></LI
-><LI
-><P
->TCP/IP ('Internet support')
- </P
-></LI
-><LI
-><P
->The "NetBIOS over TCP/IP" driver ('TCPBEUI')
- </P
-></LI
-></UL
-><P
->Installing the first two together with the base operating
- system on a blank system is explained in the Warp manual. If Warp
- has already been installed, but you now want to install the
- networking support, use the "Selective Install for Networking"
- object in the "System Setup" folder.</P
-><P
->Adding the "NetBIOS over TCP/IP" driver is not described
- in the manual and just barely in the online documentation. Start
- MPTS.EXE, click on OK, click on "Configure LAPS" and click
- on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line
- is then moved to 'Current Configuration'. Select that line,
- click on "Change number" and increase it from 0 to 1. Save this
- configuration.</P
-><P
->If the Samba server(s) is not on your local subnet, you
- can optionally add IP names and addresses of these servers
- to the "Names List", or specify a WINS server ('NetBIOS
- Nameserver' in IBM and RFC terminology). For Warp Connect you
- may need to download an update for 'IBM Peer' to bring it on
- the same level as Warp 4. See the webpage mentioned above.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H2
-CLASS="SECT2"
-><A
-NAME="AEN20"
->How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</A
-></H2
-><P
->You can use the free Microsoft LAN Manager 2.2c Client
- for OS/2 from
- <A
-HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"
-TARGET="_top"
-> ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A
->.
- See <A
-HREF="http://carol.wins.uva.nl/~leeuw/lanman.html"
-TARGET="_top"
-> http://carol.wins.uva.nl/~leeuw/lanman.html</A
-> for
- more information on how to install and use this client. In
- a nutshell, edit the file \OS2VER in the root directory of
- the OS/2 boot partition and add the lines:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> 20=setup.exe
- 20=netwksta.sys
- 20=netvdd.sys
- </PRE
-></P
-><P
->before you install the client. Also, don't use the
- included NE2000 driver because it is buggy. Try the NE2000
- or NS2000 driver from
- <A
-HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/"
-TARGET="_top"
-> ftp://ftp.cdrom.com/pub/os2/network/ndis/</A
-> instead.
- </P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H2
-CLASS="SECT2"
-><A
-NAME="AEN29"
->Are there any other issues when OS/2 (any version)
- is used as a client?</A
-></H2
-><P
->When you do a NET VIEW or use the "File and Print
- Client Resource Browser", no Samba servers show up. This can
- be fixed by a patch from <A
-HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html"
-TARGET="_top"
-> http://carol.wins.uva.nl/~leeuw/samba/fix.html</A
->.
- The patch will be included in a later version of Samba. It also
- fixes a couple of other problems, such as preserving long
- filenames when objects are dragged from the Workplace Shell
- to the Samba server. </P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H2
-CLASS="SECT2"
-><A
-NAME="AEN33"
->How do I get printer driver download working
- for OS/2 clients?</A
-></H2
-><P
->First, create a share called [PRINTDRV] that is
- world-readable. Copy your OS/2 driver files there. Note
- that the .EA_ files must still be separate, so you will need
- to use the original install files, and not copy an installed
- driver from an OS/2 system.</P
-><P
->Install the NT driver first for that printer. Then,
- add to your smb.conf a parameter, "os2 driver map =
- <TT
-CLASS="REPLACEABLE"
-><I
->filename</I
-></TT
->". Then, in the file
- specified by <TT
-CLASS="REPLACEABLE"
-><I
->filename</I
-></TT
->, map the
- name of the NT driver name to the OS/2 driver name as
- follows:</P
-><P
-><nt driver name> = <os2 driver
- name>.<device name>, e.g.:
- HP LaserJet 5L = LASERJET.HP LaserJet 5L</P
-><P
->You can have multiple drivers mapped in this file.</P
-><P
->If you only specify the OS/2 driver name, and not the
- device name, the first attempt to download the driver will
- actually download the files, but the OS/2 client will tell
- you the driver is not available. On the second attempt, it
- will work. This is fixed simply by adding the device name
- to the mapping, after which it will work on the first attempt.
- </P
-></DIV
-></DIV
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>SAMBA Project Documentation</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="NEXT"
+TITLE="How to Install and Test SAMBA"
+HREF="install.html"></HEAD
+><BODY
+CLASS="BOOK"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="BOOK"
+><A
+NAME="SAMBA-PROJECT-DOCUMENTATION"><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="SAMBA-PROJECT-DOCUMENTATION">SAMBA Project Documentation</H1
+><H3
+CLASS="AUTHOR"
+><A
+NAME="AEN4">SAMBA Team</H3
+><HR></DIV
+><H1
+><A
+NAME="AEN8">Abstract</H1
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Last Update</I
+></SPAN
+> : Thu Aug 15 12:48:45 CDT 2002</P
+><P
+>This book is a collection of HOWTOs added to Samba documentation over the years.
+I try to ensure that all are current, but sometimes the is a larger job
+than one person can maintain. The most recent version of this document
+can be found at <A
+HREF="http://www.samba.org/"
+TARGET="_top"
+>http://www.samba.org/</A
+>
+on the "Documentation" page. Please send updates to <A
+HREF="mailto:jerry@samba.org"
+TARGET="_top"
+>jerry@samba.org</A
+>.</P
+><P
+>This documentation is distributed under the GNU General Public License (GPL)
+version 2. A copy of the license is included with the Samba source
+distribution. A copy can be found on-line at <A
+HREF="http://www.fsf.org/licenses/gpl.txt"
+TARGET="_top"
+>http://www.fsf.org/licenses/gpl.txt</A
+></P
+><P
+>Cheers, jerry</P
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="install.html"
+>How to Install and Test SAMBA</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="install.html#AEN20"
+>Step 0: Read the man pages</A
+></DT
+><DT
+>1.2. <A
+HREF="install.html#AEN28"
+>Step 1: Building the Binaries</A
+></DT
+><DT
+>1.3. <A
+HREF="install.html#AEN56"
+>Step 2: The all important step</A
+></DT
+><DT
+>1.4. <A
+HREF="install.html#AEN60"
+>Step 3: Create the smb configuration file.</A
+></DT
+><DT
+>1.5. <A
+HREF="install.html#AEN74"
+>Step 4: Test your config file with
+ <B
+CLASS="COMMAND"
+>testparm</B
+></A
+></DT
+><DT
+>1.6. <A
+HREF="install.html#AEN80"
+>Step 5: Starting the smbd and nmbd</A
+></DT
+><DD
+><DL
+><DT
+>1.6.1. <A
+HREF="install.html#AEN90"
+>Step 5a: Starting from inetd.conf</A
+></DT
+><DT
+>1.6.2. <A
+HREF="install.html#AEN119"
+>Step 5b. Alternative: starting it as a daemon</A
+></DT
+></DL
+></DD
+><DT
+>1.7. <A
+HREF="install.html#AEN135"
+>Step 6: Try listing the shares available on your
+ server</A
+></DT
+><DT
+>1.8. <A
+HREF="install.html#AEN144"
+>Step 7: Try connecting with the unix client</A
+></DT
+><DT
+>1.9. <A
+HREF="install.html#AEN160"
+>Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</A
+></DT
+><DT
+>1.10. <A
+HREF="install.html#AEN174"
+>What If Things Don't Work?</A
+></DT
+><DD
+><DL
+><DT
+>1.10.1. <A
+HREF="install.html#AEN179"
+>Diagnosing Problems</A
+></DT
+><DT
+>1.10.2. <A
+HREF="install.html#AEN183"
+>Scope IDs</A
+></DT
+><DT
+>1.10.3. <A
+HREF="install.html#AEN186"
+>Choosing the Protocol Level</A
+></DT
+><DT
+>1.10.4. <A
+HREF="install.html#AEN195"
+>Printing from UNIX to a Client PC</A
+></DT
+><DT
+>1.10.5. <A
+HREF="install.html#AEN200"
+>Locking</A
+></DT
+><DT
+>1.10.6. <A
+HREF="install.html#AEN209"
+>Mapping Usernames</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>2. <A
+HREF="diagnosis.html"
+>Diagnosing your samba server</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="diagnosis.html#AEN223"
+>Introduction</A
+></DT
+><DT
+>2.2. <A
+HREF="diagnosis.html#AEN228"
+>Assumptions</A
+></DT
+><DT
+>2.3. <A
+HREF="diagnosis.html#AEN238"
+>Tests</A
+></DT
+><DD
+><DL
+><DT
+>2.3.1. <A
+HREF="diagnosis.html#AEN240"
+>Test 1</A
+></DT
+><DT
+>2.3.2. <A
+HREF="diagnosis.html#AEN246"
+>Test 2</A
+></DT
+><DT
+>2.3.3. <A
+HREF="diagnosis.html#AEN252"
+>Test 3</A
+></DT
+><DT
+>2.3.4. <A
+HREF="diagnosis.html#AEN267"
+>Test 4</A
+></DT
+><DT
+>2.3.5. <A
+HREF="diagnosis.html#AEN272"
+>Test 5</A
+></DT
+><DT
+>2.3.6. <A
+HREF="diagnosis.html#AEN278"
+>Test 6</A
+></DT
+><DT
+>2.3.7. <A
+HREF="diagnosis.html#AEN286"
+>Test 7</A
+></DT
+><DT
+>2.3.8. <A
+HREF="diagnosis.html#AEN312"
+>Test 8</A
+></DT
+><DT
+>2.3.9. <A
+HREF="diagnosis.html#AEN329"
+>Test 9</A
+></DT
+><DT
+>2.3.10. <A
+HREF="diagnosis.html#AEN334"
+>Test 10</A
+></DT
+><DT
+>2.3.11. <A
+HREF="diagnosis.html#AEN340"
+>Test 11</A
+></DT
+></DL
+></DD
+><DT
+>2.4. <A
+HREF="diagnosis.html#AEN345"
+>Still having troubles?</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="integrate-ms-networks.html"
+>Integrating MS Windows networks with Samba</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="integrate-ms-networks.html#AEN362"
+>Agenda</A
+></DT
+><DT
+>3.2. <A
+HREF="integrate-ms-networks.html#AEN384"
+>Name Resolution in a pure Unix/Linux world</A
+></DT
+><DD
+><DL
+><DT
+>3.2.1. <A
+HREF="integrate-ms-networks.html#AEN400"
+><TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></A
+></DT
+><DT
+>3.2.2. <A
+HREF="integrate-ms-networks.html#AEN416"
+><TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></A
+></DT
+><DT
+>3.2.3. <A
+HREF="integrate-ms-networks.html#AEN427"
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></A
+></DT
+><DT
+>3.2.4. <A
+HREF="integrate-ms-networks.html#AEN435"
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></A
+></DT
+></DL
+></DD
+><DT
+>3.3. <A
+HREF="integrate-ms-networks.html#AEN447"
+>Name resolution as used within MS Windows networking</A
+></DT
+><DD
+><DL
+><DT
+>3.3.1. <A
+HREF="integrate-ms-networks.html#AEN459"
+>The NetBIOS Name Cache</A
+></DT
+><DT
+>3.3.2. <A
+HREF="integrate-ms-networks.html#AEN464"
+>The LMHOSTS file</A
+></DT
+><DT
+>3.3.3. <A
+HREF="integrate-ms-networks.html#AEN472"
+>HOSTS file</A
+></DT
+><DT
+>3.3.4. <A
+HREF="integrate-ms-networks.html#AEN477"
+>DNS Lookup</A
+></DT
+><DT
+>3.3.5. <A
+HREF="integrate-ms-networks.html#AEN480"
+>WINS Lookup</A
+></DT
+></DL
+></DD
+><DT
+>3.4. <A
+HREF="integrate-ms-networks.html#AEN492"
+>How browsing functions and how to deploy stable and
+dependable browsing using Samba</A
+></DT
+><DT
+>3.5. <A
+HREF="integrate-ms-networks.html#AEN502"
+>MS Windows security options and how to configure
+Samba for seemless integration</A
+></DT
+><DD
+><DL
+><DT
+>3.5.1. <A
+HREF="integrate-ms-networks.html#AEN530"
+>Use MS Windows NT as an authentication server</A
+></DT
+><DT
+>3.5.2. <A
+HREF="integrate-ms-networks.html#AEN538"
+>Make Samba a member of an MS Windows NT security domain</A
+></DT
+><DT
+>3.5.3. <A
+HREF="integrate-ms-networks.html#AEN555"
+>Configure Samba as an authentication server</A
+></DT
+></DL
+></DD
+><DT
+>3.6. <A
+HREF="integrate-ms-networks.html#AEN572"
+>Conclusions</A
+></DT
+></DL
+></DD
+><DT
+>4. <A
+HREF="pam.html"
+>Configuring PAM for distributed but centrally
+managed authentication</A
+></DT
+><DD
+><DL
+><DT
+>4.1. <A
+HREF="pam.html#AEN593"
+>Samba and PAM</A
+></DT
+><DT
+>4.2. <A
+HREF="pam.html#AEN637"
+>Distributed Authentication</A
+></DT
+><DT
+>4.3. <A
+HREF="pam.html#AEN644"
+>PAM Configuration in smb.conf</A
+></DT
+></DL
+></DD
+><DT
+>5. <A
+HREF="msdfs.html"
+>Hosting a Microsoft Distributed File System tree on Samba</A
+></DT
+><DD
+><DL
+><DT
+>5.1. <A
+HREF="msdfs.html#AEN664"
+>Instructions</A
+></DT
+><DD
+><DL
+><DT
+>5.1.1. <A
+HREF="msdfs.html#AEN699"
+>Notes</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>6. <A
+HREF="unix-permissions.html"
+>UNIX Permission Bits and Windows NT Access Control Lists</A
+></DT
+><DD
+><DL
+><DT
+>6.1. <A
+HREF="unix-permissions.html#AEN719"
+>Viewing and changing UNIX permissions using the NT
+ security dialogs</A
+></DT
+><DT
+>6.2. <A
+HREF="unix-permissions.html#AEN728"
+>How to view file security on a Samba share</A
+></DT
+><DT
+>6.3. <A
+HREF="unix-permissions.html#AEN739"
+>Viewing file ownership</A
+></DT
+><DT
+>6.4. <A
+HREF="unix-permissions.html#AEN759"
+>Viewing file or directory permissions</A
+></DT
+><DD
+><DL
+><DT
+>6.4.1. <A
+HREF="unix-permissions.html#AEN774"
+>File Permissions</A
+></DT
+><DT
+>6.4.2. <A
+HREF="unix-permissions.html#AEN788"
+>Directory Permissions</A
+></DT
+></DL
+></DD
+><DT
+>6.5. <A
+HREF="unix-permissions.html#AEN795"
+>Modifying file or directory permissions</A
+></DT
+><DT
+>6.6. <A
+HREF="unix-permissions.html#AEN817"
+>Interaction with the standard Samba create mask
+ parameters</A
+></DT
+><DT
+>6.7. <A
+HREF="unix-permissions.html#AEN881"
+>Interaction with the standard Samba file attribute
+ mapping</A
+></DT
+></DL
+></DD
+><DT
+>7. <A
+HREF="printing.html"
+>Printing Support in Samba 2.2.x</A
+></DT
+><DD
+><DL
+><DT
+>7.1. <A
+HREF="printing.html#AEN902"
+>Introduction</A
+></DT
+><DT
+>7.2. <A
+HREF="printing.html#AEN924"
+>Configuration</A
+></DT
+><DD
+><DL
+><DT
+>7.2.1. <A
+HREF="printing.html#AEN935"
+>Creating [print$]</A
+></DT
+><DT
+>7.2.2. <A
+HREF="printing.html#AEN970"
+>Setting Drivers for Existing Printers</A
+></DT
+><DT
+>7.2.3. <A
+HREF="printing.html#AEN987"
+>Support a large number of printers</A
+></DT
+><DT
+>7.2.4. <A
+HREF="printing.html#AEN998"
+>Adding New Printers via the Windows NT APW</A
+></DT
+><DT
+>7.2.5. <A
+HREF="printing.html#AEN1028"
+>Samba and Printer Ports</A
+></DT
+></DL
+></DD
+><DT
+>7.3. <A
+HREF="printing.html#AEN1036"
+>The Imprints Toolset</A
+></DT
+><DD
+><DL
+><DT
+>7.3.1. <A
+HREF="printing.html#AEN1040"
+>What is Imprints?</A
+></DT
+><DT
+>7.3.2. <A
+HREF="printing.html#AEN1050"
+>Creating Printer Driver Packages</A
+></DT
+><DT
+>7.3.3. <A
+HREF="printing.html#AEN1053"
+>The Imprints server</A
+></DT
+><DT
+>7.3.4. <A
+HREF="printing.html#AEN1057"
+>The Installation Client</A
+></DT
+></DL
+></DD
+><DT
+>7.4. <A
+HREF="printing.html#AEN1079"
+><A
+NAME="MIGRATION"
+></A
+>Migration to from Samba 2.0.x to 2.2.x</A
+></DT
+></DL
+></DD
+><DT
+>8. <A
+HREF="printingdebug.html"
+>Debugging Printing Problems</A
+></DT
+><DD
+><DL
+><DT
+>8.1. <A
+HREF="printingdebug.html#AEN1125"
+>Introduction</A
+></DT
+><DT
+>8.2. <A
+HREF="printingdebug.html#AEN1141"
+>Debugging printer problems</A
+></DT
+><DT
+>8.3. <A
+HREF="printingdebug.html#AEN1150"
+>What printers do I have?</A
+></DT
+><DT
+>8.4. <A
+HREF="printingdebug.html#AEN1158"
+>Setting up printcap and print servers</A
+></DT
+><DT
+>8.5. <A
+HREF="printingdebug.html#AEN1186"
+>Job sent, no output</A
+></DT
+><DT
+>8.6. <A
+HREF="printingdebug.html#AEN1197"
+>Job sent, strange output</A
+></DT
+><DT
+>8.7. <A
+HREF="printingdebug.html#AEN1209"
+>Raw PostScript printed</A
+></DT
+><DT
+>8.8. <A
+HREF="printingdebug.html#AEN1212"
+>Advanced Printing</A
+></DT
+><DT
+>8.9. <A
+HREF="printingdebug.html#AEN1215"
+>Real debugging</A
+></DT
+></DL
+></DD
+><DT
+>9. <A
+HREF="securitylevels.html"
+>Security levels</A
+></DT
+><DD
+><DL
+><DT
+>9.1. <A
+HREF="securitylevels.html#AEN1228"
+>Introduction</A
+></DT
+><DT
+>9.2. <A
+HREF="securitylevels.html#AEN1239"
+>More complete description of security levels</A
+></DT
+></DL
+></DD
+><DT
+>10. <A
+HREF="domain-security.html"
+>security = domain in Samba 2.x</A
+></DT
+><DD
+><DL
+><DT
+>10.1. <A
+HREF="domain-security.html#AEN1272"
+>Joining an NT Domain with Samba 2.2</A
+></DT
+><DT
+>10.2. <A
+HREF="domain-security.html#AEN1336"
+>Samba and Windows 2000 Domains</A
+></DT
+><DT
+>10.3. <A
+HREF="domain-security.html#AEN1341"
+>Why is this better than security = server?</A
+></DT
+></DL
+></DD
+><DT
+>11. <A
+HREF="winbind.html"
+>Unified Logons between Windows NT and UNIX using Winbind</A
+></DT
+><DD
+><DL
+><DT
+>11.1. <A
+HREF="winbind.html#AEN1394"
+>Abstract</A
+></DT
+><DT
+>11.2. <A
+HREF="winbind.html#AEN1398"
+>Introduction</A
+></DT
+><DT
+>11.3. <A
+HREF="winbind.html#AEN1411"
+>What Winbind Provides</A
+></DT
+><DD
+><DL
+><DT
+>11.3.1. <A
+HREF="winbind.html#AEN1418"
+>Target Uses</A
+></DT
+></DL
+></DD
+><DT
+>11.4. <A
+HREF="winbind.html#AEN1422"
+>How Winbind Works</A
+></DT
+><DD
+><DL
+><DT
+>11.4.1. <A
+HREF="winbind.html#AEN1427"
+>Microsoft Remote Procedure Calls</A
+></DT
+><DT
+>11.4.2. <A
+HREF="winbind.html#AEN1431"
+>Name Service Switch</A
+></DT
+><DT
+>11.4.3. <A
+HREF="winbind.html#AEN1447"
+>Pluggable Authentication Modules</A
+></DT
+><DT
+>11.4.4. <A
+HREF="winbind.html#AEN1455"
+>User and Group ID Allocation</A
+></DT
+><DT
+>11.4.5. <A
+HREF="winbind.html#AEN1459"
+>Result Caching</A
+></DT
+></DL
+></DD
+><DT
+>11.5. <A
+HREF="winbind.html#AEN1462"
+>Installation and Configuration</A
+></DT
+><DD
+><DL
+><DT
+>11.5.1. <A
+HREF="winbind.html#AEN1469"
+>Introduction</A
+></DT
+><DT
+>11.5.2. <A
+HREF="winbind.html#AEN1482"
+>Requirements</A
+></DT
+><DT
+>11.5.3. <A
+HREF="winbind.html#AEN1496"
+>Testing Things Out</A
+></DT
+></DL
+></DD
+><DT
+>11.6. <A
+HREF="winbind.html#AEN1711"
+>Limitations</A
+></DT
+><DT
+>11.7. <A
+HREF="winbind.html#AEN1721"
+>Conclusion</A
+></DT
+></DL
+></DD
+><DT
+>12. <A
+HREF="samba-pdc.html"
+>How to Configure Samba 2.2 as a Primary Domain Controller</A
+></DT
+><DD
+><DL
+><DT
+>12.1. <A
+HREF="samba-pdc.html#AEN1741"
+>Prerequisite Reading</A
+></DT
+><DT
+>12.2. <A
+HREF="samba-pdc.html#AEN1747"
+>Background</A
+></DT
+><DT
+>12.3. <A
+HREF="samba-pdc.html#AEN1786"
+>Configuring the Samba Domain Controller</A
+></DT
+><DT
+>12.4. <A
+HREF="samba-pdc.html#AEN1829"
+>Creating Machine Trust Accounts and Joining Clients to the
+Domain</A
+></DT
+><DD
+><DL
+><DT
+>12.4.1. <A
+HREF="samba-pdc.html#AEN1848"
+>Manual Creation of Machine Trust Accounts</A
+></DT
+><DT
+>12.4.2. <A
+HREF="samba-pdc.html#AEN1883"
+>"On-the-Fly" Creation of Machine Trust Accounts</A
+></DT
+><DT
+>12.4.3. <A
+HREF="samba-pdc.html#AEN1892"
+>Joining the Client to the Domain</A
+></DT
+></DL
+></DD
+><DT
+>12.5. <A
+HREF="samba-pdc.html#AEN1907"
+>Common Problems and Errors</A
+></DT
+><DT
+>12.6. <A
+HREF="samba-pdc.html#AEN1955"
+>System Policies and Profiles</A
+></DT
+><DT
+>12.7. <A
+HREF="samba-pdc.html#AEN1999"
+>What other help can I get?</A
+></DT
+><DT
+>12.8. <A
+HREF="samba-pdc.html#AEN2113"
+>Domain Control for Windows 9x/ME</A
+></DT
+><DD
+><DL
+><DT
+>12.8.1. <A
+HREF="samba-pdc.html#AEN2139"
+>Configuration Instructions: Network Logons</A
+></DT
+><DT
+>12.8.2. <A
+HREF="samba-pdc.html#AEN2158"
+>Configuration Instructions: Setting up Roaming User Profiles</A
+></DT
+></DL
+></DD
+><DT
+>12.9. <A
+HREF="samba-pdc.html#AEN2251"
+>DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A
+></DT
+></DL
+></DD
+><DT
+>13. <A
+HREF="samba-bdc.html"
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A
+></DT
+><DD
+><DL
+><DT
+>13.1. <A
+HREF="samba-bdc.html#AEN2287"
+>Prerequisite Reading</A
+></DT
+><DT
+>13.2. <A
+HREF="samba-bdc.html#AEN2291"
+>Background</A
+></DT
+><DT
+>13.3. <A
+HREF="samba-bdc.html#AEN2299"
+>What qualifies a Domain Controller on the network?</A
+></DT
+><DD
+><DL
+><DT
+>13.3.1. <A
+HREF="samba-bdc.html#AEN2302"
+>How does a Workstation find its domain controller?</A
+></DT
+><DT
+>13.3.2. <A
+HREF="samba-bdc.html#AEN2305"
+>When is the PDC needed?</A
+></DT
+></DL
+></DD
+><DT
+>13.4. <A
+HREF="samba-bdc.html#AEN2308"
+>Can Samba be a Backup Domain Controller?</A
+></DT
+><DT
+>13.5. <A
+HREF="samba-bdc.html#AEN2312"
+>How do I set up a Samba BDC?</A
+></DT
+><DD
+><DL
+><DT
+>13.5.1. <A
+HREF="samba-bdc.html#AEN2329"
+>How do I replicate the smbpasswd file?</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>14. <A
+HREF="samba-ldap-howto.html"
+>Storing Samba's User/Machine Account information in an LDAP Directory</A
+></DT
+><DD
+><DL
+><DT
+>14.1. <A
+HREF="samba-ldap-howto.html#AEN2350"
+>Purpose</A
+></DT
+><DT
+>14.2. <A
+HREF="samba-ldap-howto.html#AEN2370"
+>Introduction</A
+></DT
+><DT
+>14.3. <A
+HREF="samba-ldap-howto.html#AEN2399"
+>Supported LDAP Servers</A
+></DT
+><DT
+>14.4. <A
+HREF="samba-ldap-howto.html#AEN2404"
+>Schema and Relationship to the RFC 2307 posixAccount</A
+></DT
+><DT
+>14.5. <A
+HREF="samba-ldap-howto.html#AEN2416"
+>Configuring Samba with LDAP</A
+></DT
+><DD
+><DL
+><DT
+>14.5.1. <A
+HREF="samba-ldap-howto.html#AEN2418"
+>OpenLDAP configuration</A
+></DT
+><DT
+>14.5.2. <A
+HREF="samba-ldap-howto.html#AEN2435"
+>Configuring Samba</A
+></DT
+></DL
+></DD
+><DT
+>14.6. <A
+HREF="samba-ldap-howto.html#AEN2463"
+>Accounts and Groups management</A
+></DT
+><DT
+>14.7. <A
+HREF="samba-ldap-howto.html#AEN2468"
+>Security and sambaAccount</A
+></DT
+><DT
+>14.8. <A
+HREF="samba-ldap-howto.html#AEN2488"
+>LDAP specials attributes for sambaAccounts</A
+></DT
+><DT
+>14.9. <A
+HREF="samba-ldap-howto.html#AEN2558"
+>Example LDIF Entries for a sambaAccount</A
+></DT
+><DT
+>14.10. <A
+HREF="samba-ldap-howto.html#AEN2566"
+>Comments</A
+></DT
+></DL
+></DD
+><DT
+>15. <A
+HREF="improved-browsing.html"
+>Improved browsing in samba</A
+></DT
+><DD
+><DL
+><DT
+>15.1. <A
+HREF="improved-browsing.html#AEN2577"
+>Overview of browsing</A
+></DT
+><DT
+>15.2. <A
+HREF="improved-browsing.html#AEN2581"
+>Browsing support in samba</A
+></DT
+><DT
+>15.3. <A
+HREF="improved-browsing.html#AEN2590"
+>Problem resolution</A
+></DT
+><DT
+>15.4. <A
+HREF="improved-browsing.html#AEN2597"
+>Browsing across subnets</A
+></DT
+><DD
+><DL
+><DT
+>15.4.1. <A
+HREF="improved-browsing.html#AEN2602"
+>How does cross subnet browsing work ?</A
+></DT
+></DL
+></DD
+><DT
+>15.5. <A
+HREF="improved-browsing.html#AEN2637"
+>Setting up a WINS server</A
+></DT
+><DT
+>15.6. <A
+HREF="improved-browsing.html#AEN2656"
+>Setting up Browsing in a WORKGROUP</A
+></DT
+><DT
+>15.7. <A
+HREF="improved-browsing.html#AEN2674"
+>Setting up Browsing in a DOMAIN</A
+></DT
+><DT
+>15.8. <A
+HREF="improved-browsing.html#AEN2684"
+>Forcing samba to be the master</A
+></DT
+><DT
+>15.9. <A
+HREF="improved-browsing.html#AEN2693"
+>Making samba the domain master</A
+></DT
+><DT
+>15.10. <A
+HREF="improved-browsing.html#AEN2711"
+>Note about broadcast addresses</A
+></DT
+><DT
+>15.11. <A
+HREF="improved-browsing.html#AEN2714"
+>Multiple interfaces</A
+></DT
+></DL
+></DD
+><DT
+>16. <A
+HREF="speed.html"
+>Samba performance issues</A
+></DT
+><DD
+><DL
+><DT
+>16.1. <A
+HREF="speed.html#AEN2732"
+>Comparisons</A
+></DT
+><DT
+>16.2. <A
+HREF="speed.html#AEN2738"
+>Oplocks</A
+></DT
+><DD
+><DL
+><DT
+>16.2.1. <A
+HREF="speed.html#AEN2740"
+>Overview</A
+></DT
+><DT
+>16.2.2. <A
+HREF="speed.html#AEN2748"
+>Level2 Oplocks</A
+></DT
+><DT
+>16.2.3. <A
+HREF="speed.html#AEN2754"
+>Old 'fake oplocks' option - deprecated</A
+></DT
+></DL
+></DD
+><DT
+>16.3. <A
+HREF="speed.html#AEN2758"
+>Socket options</A
+></DT
+><DT
+>16.4. <A
+HREF="speed.html#AEN2765"
+>Read size</A
+></DT
+><DT
+>16.5. <A
+HREF="speed.html#AEN2770"
+>Max xmit</A
+></DT
+><DT
+>16.6. <A
+HREF="speed.html#AEN2775"
+>Locking</A
+></DT
+><DT
+>16.7. <A
+HREF="speed.html#AEN2779"
+>Share modes</A
+></DT
+><DT
+>16.8. <A
+HREF="speed.html#AEN2784"
+>Log level</A
+></DT
+><DT
+>16.9. <A
+HREF="speed.html#AEN2787"
+>Wide lines</A
+></DT
+><DT
+>16.10. <A
+HREF="speed.html#AEN2790"
+>Read raw</A
+></DT
+><DT
+>16.11. <A
+HREF="speed.html#AEN2795"
+>Write raw</A
+></DT
+><DT
+>16.12. <A
+HREF="speed.html#AEN2799"
+>Read prediction</A
+></DT
+><DT
+>16.13. <A
+HREF="speed.html#AEN2806"
+>Memory mapping</A
+></DT
+><DT
+>16.14. <A
+HREF="speed.html#AEN2811"
+>Slow Clients</A
+></DT
+><DT
+>16.15. <A
+HREF="speed.html#AEN2815"
+>Slow Logins</A
+></DT
+><DT
+>16.16. <A
+HREF="speed.html#AEN2818"
+>Client tuning</A
+></DT
+><DT
+>16.17. <A
+HREF="speed.html#AEN2850"
+>My Results</A
+></DT
+></DL
+></DD
+><DT
+>17. <A
+HREF="other-clients.html"
+>Samba and other CIFS clients</A
+></DT
+><DD
+><DL
+><DT
+>17.1. <A
+HREF="other-clients.html#AEN2871"
+>Macintosh clients?</A
+></DT
+><DT
+>17.2. <A
+HREF="other-clients.html#AEN2880"
+>OS2 Client</A
+></DT
+><DD
+><DL
+><DT
+>17.2.1. <A
+HREF="other-clients.html#AEN2882"
+>How can I configure OS/2 Warp Connect or
+ OS/2 Warp 4 as a client for Samba?</A
+></DT
+><DT
+>17.2.2. <A
+HREF="other-clients.html#AEN2897"
+>How can I configure OS/2 Warp 3 (not Connect),
+ OS/2 1.2, 1.3 or 2.x for Samba?</A
+></DT
+><DT
+>17.2.3. <A
+HREF="other-clients.html#AEN2906"
+>Are there any other issues when OS/2 (any version)
+ is used as a client?</A
+></DT
+><DT
+>17.2.4. <A
+HREF="other-clients.html#AEN2910"
+>How do I get printer driver download working
+ for OS/2 clients?</A
+></DT
+></DL
+></DD
+><DT
+>17.3. <A
+HREF="other-clients.html#AEN2920"
+>Windows for Workgroups</A
+></DT
+><DD
+><DL
+><DT
+>17.3.1. <A
+HREF="other-clients.html#AEN2922"
+>Use latest TCP/IP stack from Microsoft</A
+></DT
+><DT
+>17.3.2. <A
+HREF="other-clients.html#AEN2927"
+>Delete .pwl files after password change</A
+></DT
+><DT
+>17.3.3. <A
+HREF="other-clients.html#AEN2932"
+>Configure WfW password handling</A
+></DT
+><DT
+>17.3.4. <A
+HREF="other-clients.html#AEN2936"
+>Case handling of passwords</A
+></DT
+></DL
+></DD
+><DT
+>17.4. <A
+HREF="other-clients.html#AEN2941"
+>Windows '95/'98</A
+></DT
+><DT
+>17.5. <A
+HREF="other-clients.html#AEN2957"
+>Windows 2000 Service Pack 2</A
+></DT
+></DL
+></DD
+><DT
+>18. <A
+HREF="cvs-access.html"
+>HOWTO Access Samba source code via CVS</A
+></DT
+><DD
+><DL
+><DT
+>18.1. <A
+HREF="cvs-access.html#AEN2981"
+>Introduction</A
+></DT
+><DT
+>18.2. <A
+HREF="cvs-access.html#AEN2986"
+>CVS Access to samba.org</A
+></DT
+><DD
+><DL
+><DT
+>18.2.1. <A
+HREF="cvs-access.html#AEN2989"
+>Access via CVSweb</A
+></DT
+><DT
+>18.2.2. <A
+HREF="cvs-access.html#AEN2994"
+>Access via cvs</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>19. <A
+HREF="bugreport.html"
+>Reporting Bugs</A
+></DT
+><DD
+><DL
+><DT
+>19.1. <A
+HREF="bugreport.html#AEN3029"
+>Introduction</A
+></DT
+><DT
+>19.2. <A
+HREF="bugreport.html#AEN3036"
+>General info</A
+></DT
+><DT
+>19.3. <A
+HREF="bugreport.html#AEN3042"
+>Debug levels</A
+></DT
+><DT
+>19.4. <A
+HREF="bugreport.html#AEN3059"
+>Internal errors</A
+></DT
+><DT
+>19.5. <A
+HREF="bugreport.html#AEN3069"
+>Attaching to a running process</A
+></DT
+><DT
+>19.6. <A
+HREF="bugreport.html#AEN3072"
+>Patches</A
+></DT
+></DL
+></DD
+><DT
+>20. <A
+HREF="groupmapping.html"
+>Group mapping HOWTO</A
+></DT
+><DT
+>21. <A
+HREF="portability.html"
+>Portability</A
+></DT
+><DD
+><DL
+><DT
+>21.1. <A
+HREF="portability.html#AEN3119"
+>HPUX</A
+></DT
+><DT
+>21.2. <A
+HREF="portability.html#AEN3124"
+>SCO Unix</A
+></DT
+><DT
+>21.3. <A
+HREF="portability.html#AEN3128"
+>DNIX</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to Install and Test SAMBA</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Reporting Bugs</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="HOWTO Access Samba source code via CVS"
+HREF="cvs-access.html"><LINK
+REL="NEXT"
+TITLE="Group mapping HOWTO"
+HREF="groupmapping.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="BUGREPORT"
->Reporting Bugs</A
-></H1
-><HR></DIV
+NAME="BUGREPORT">Chapter 19. Reporting Bugs</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Introduction</A
-></H1
+NAME="AEN3029">19.1. Introduction</H1
><P
>The email address for bug reports is samba@samba.org</P
><P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN10"
->General info</A
-></H1
+NAME="AEN3036">19.2. General info</H1
><P
>Before submitting a bug report check your config for silly
errors. Look in your log files for obvious messages that tell you that
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN16"
->Debug levels</A
-></H1
+NAME="AEN3042">19.3. Debug levels</H1
><P
>If the bug has anything to do with Samba behaving incorrectly as a
server (like refusing to open a file) then the log files will probably
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN33"
->Internal errors</A
-></H1
+NAME="AEN3059">19.4. Internal errors</H1
><P
>If you get a "INTERNAL ERROR" message in your log files it means that
Samba got an unexpected signal while running. It is probably a
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN43"
->Attaching to a running process</A
-></H1
+NAME="AEN3069">19.5. Attaching to a running process</H1
><P
>Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN46"
->Patches</A
-></H1
+NAME="AEN3072">19.6. Patches</H1
><P
>The best sort of bug report is one that includes a fix! If you send us
patches please use <B
exactly what version you used. </P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>HOWTO Access Samba source code via CVS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Group mapping HOWTO</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>HOWTO Access Samba source code via CVS</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba and other CIFS clients"
+HREF="other-clients.html"><LINK
+REL="NEXT"
+TITLE="Reporting Bugs"
+HREF="bugreport.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="other-clients.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="bugreport.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="CVS-ACCESS"
->HOWTO Access Samba source code via CVS</A
-></H1
-><HR></DIV
+NAME="CVS-ACCESS">Chapter 18. HOWTO Access Samba source code via CVS</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Introduction</A
-></H1
+NAME="AEN2981">18.1. Introduction</H1
><P
>Samba is developed in an open environment. Developers use CVS
(Concurrent Versioning System) to "checkin" (also known as
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN8"
->CVS Access to samba.org</A
-></H1
+NAME="AEN2986">18.2. CVS Access to samba.org</H1
><P
>The machine samba.org runs a publicly accessible CVS
repository for access to the source code of several packages,
accessing the CVS server on this host.</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN11"
->Access via CVSweb</A
-></H2
+NAME="AEN2989">18.2.1. Access via CVSweb</H2
><P
>You can access the source code via your
favourite WWW browser. This allows you to access the contents of
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN16"
->Access via cvs</A
-></H2
+NAME="AEN2994">18.2.2. Access via cvs</H2
><P
>You can also access the source code via a
normal cvs client. This gives you much more control over you can
></DIV
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="other-clients.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="bugreport.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba and other CIFS clients</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Reporting Bugs</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Diagnosing your samba server</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="How to Install and Test SAMBA"
+HREF="install.html"><LINK
+REL="NEXT"
+TITLE="Integrating MS Windows networks with Samba"
+HREF="integrate-ms-networks.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="install.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="DIAGNOSIS"
->Diagnosing your samba server</A
-></H1
-><HR></DIV
+NAME="DIAGNOSIS">Chapter 2. Diagnosing your samba server</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Introduction</A
-></H1
+NAME="AEN223">2.1. Introduction</H1
><P
>This file contains a list of tests you can perform to validate your
Samba server. It also tells you what the likely cause of the problem
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN8"
->Assumptions</A
-></H1
+NAME="AEN228">2.2. Assumptions</H1
><P
>In all of the tests I assume you have a Samba server called BIGSERVER
and a PC called ACLIENT both in workgroup TESTGROUP. I also assume the
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN18"
->Tests</A
-></H1
+NAME="AEN238">2.3. Tests</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN20"
->Test 1</A
-></H2
+NAME="AEN240">2.3.1. Test 1</H2
><P
>In the directory in which you store your smb.conf file, run the command
"testparm smb.conf". If it reports any errors then your smb.conf
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN26"
->Test 2</A
-></H2
+NAME="AEN246">2.3.2. Test 2</H2
><P
>Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
the unix box. If you don't get a valid response then your TCP/IP
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN32"
->Test 3</A
-></H2
+NAME="AEN252">2.3.3. Test 3</H2
><P
>Run the command "smbclient -L BIGSERVER" on the unix box. You
should get a list of available shares back. </P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN47"
->Test 4</A
-></H2
+NAME="AEN267">2.3.4. Test 4</H2
><P
>Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
IP address of your Samba server back.</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN52"
->Test 5</A
-></H2
+NAME="AEN272">2.3.5. Test 5</H2
><P
>run the command <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN58"
->Test 6</A
-></H2
+NAME="AEN278">2.3.6. Test 6</H2
><P
>Run the command <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN66"
->Test 7</A
-></H2
+NAME="AEN286">2.3.7. Test 7</H2
><P
>Run the command <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN92"
->Test 8</A
-></H2
+NAME="AEN312">2.3.8. Test 8</H2
><P
>On the PC type the command <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN109"
->Test 9</A
-></H2
+NAME="AEN329">2.3.9. Test 9</H2
><P
>Run the command <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN114"
->Test 10</A
-></H2
+NAME="AEN334">2.3.10. Test 10</H2
><P
>Run the command <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN120"
->Test 11</A
-></H2
+NAME="AEN340">2.3.11. Test 11</H2
><P
>From file manager try to browse the server. Your samba server should
appear in the browse list of your local workgroup (or the one you
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN125"
->Still having troubles?</A
-></H1
+NAME="AEN345">2.4. Still having troubles?</H1
><P
>Try the mailing list or newsgroup, or use the ethereal utility to
sniff the problem. The official samba mailing list can be reached at
>Also look at the other docs in the Samba package!</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>How to Install and Test SAMBA</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Integrating MS Windows networks with Samba</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>security = domain in Samba 2.x</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Security levels"
+HREF="securitylevels.html"><LINK
+REL="NEXT"
+TITLE="Unified Logons between Windows NT and UNIX using Winbind"
+HREF="winbind.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="winbind.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="DOMAIN-SECURITY"
->security = domain in Samba 2.x</A
-></H1
-><HR></DIV
+NAME="DOMAIN-SECURITY">Chapter 10. security = domain in Samba 2.x</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Joining an NT Domain with Samba 2.2</A
-></H1
+NAME="AEN1272">10.1. Joining an NT Domain with Samba 2.2</H1
><P
>Assume you have a Samba 2.x server with a NetBIOS name of
<TT
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN67"
->Samba and Windows 2000 Domains</A
-></H1
+NAME="AEN1336">10.2. Samba and Windows 2000 Domains</H1
><P
>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
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN72"
->Why is this better than security = server?</A
-></H1
+NAME="AEN1341">10.3. Why is this better than security = server?</H1
><P
>Currently, domain security in Samba doesn't free you from
having to create local Unix users to represent the users attaching
user is authenticated, making a Samba server truly plug and play
in an NT domain environment. Watch for this code soon.</P
><P
+><SPAN
+CLASS="emphasis"
><I
CLASS="EMPHASIS"
>NOTE:</I
+></SPAN
> Much of the text of this document
was first published in the Web magazine <A
HREF="http://www.linuxworld.com"
>.</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="winbind.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Security levels</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Unified Logons between Windows NT and UNIX using Winbind</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Group mapping HOWTO</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Reporting Bugs"
+HREF="bugreport.html"><LINK
+REL="NEXT"
+TITLE="Portability"
+HREF="portability.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="bugreport.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="portability.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="GROUPMAPPING">Chapter 20. Group mapping HOWTO</H1
+><P
+>
+Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
+current method (likely to change) to manage the groups is a new command called
+<B
+CLASS="COMMAND"
+>smbgroupedit</B
+>.</P
+><P
+>The first immediate reason to use the group mapping on a PDC, is that
+the <B
+CLASS="COMMAND"
+>domain admin group</B
+> of <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> is
+now gone. This parameter was used to give the listed users local admin rights
+on their workstations. It was some magic stuff that simply worked but didn't
+scale very well for complex setups.</P
+><P
+>Let me explain how it works on NT/W2K, to have this magic fade away.
+When installing NT/W2K on a computer, the installer program creates some users
+and groups. Notably the 'Administrators' group, and gives to that group some
+privileges like the ability to change the date and time or to kill any process
+(or close too) running on the local machine. The 'Administrator' user is a
+member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
+group privileges. If a 'joe' user is created and become a member of the
+'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.</P
+><P
+>When a NT/W2K machine is joined to a domain, during that phase, the "Domain
+Administrators' group of the PDC is added to the 'Administrators' group of the
+workstation. Every members of the 'Domain Administrators' group 'inherit' the
+rights of the 'Administrators' group when logging on the workstation.</P
+><P
+>You are now wondering how to make some of your samba PDC users members of the
+'Domain Administrators' ? That's really easy.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>create a unix group (usually in <TT
+CLASS="FILENAME"
+>/etc/group</TT
+>), let's call it domadm</P
+></LI
+><LI
+><P
+>add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in <TT
+CLASS="FILENAME"
+>/etc/group</TT
+> will look like:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>domadm:x:502:joe,john,mary</PRE
+></P
+></LI
+><LI
+><P
+>Map this domadm group to the <B
+CLASS="COMMAND"
+>domain admins</B
+> group by running the command:</P
+><P
+><B
+CLASS="COMMAND"
+>smbgroupedit -c "Domain Admins" -u domadm</B
+></P
+></LI
+></OL
+><P
+>You're set, joe, john and mary are domain administrators !</P
+><P
+>Like the Domain Admins group, you can map any arbitrary Unix group to any NT
+group. You can also make any Unix group a domain group. For example, on a domain
+member machine (an NT/W2K or a samba server running winbind), you would like to
+give access to a certain directory to some users who are member of a group on
+your samba PDC. Flag that group as a domain group by running:</P
+><P
+><B
+CLASS="COMMAND"
+>smbgroupedit -a unixgroup -td</B
+></P
+><P
+>You can list the various groups in the mapping database like this</P
+><P
+><B
+CLASS="COMMAND"
+>smbgroupedit -v</B
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="bugreport.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="portability.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Reporting Bugs</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Portability</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Improved browsing in samba</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
+HREF="samba-ldap-howto.html"><LINK
+REL="NEXT"
+TITLE="Samba performance issues"
+HREF="speed.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-ldap-howto.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="speed.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="IMPROVED-BROWSING"
->Improved browsing in samba</A
-></H1
-><HR></DIV
+NAME="IMPROVED-BROWSING">Chapter 15. Improved browsing in samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Overview of browsing</A
-></H1
+NAME="AEN2577">15.1. Overview of browsing</H1
><P
>SMB networking provides a mechanism by which clients can access a list
of machines in a network, a so-called "browse list". This list
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN7"
->Browsing support in samba</A
-></H1
+NAME="AEN2581">15.2. Browsing support in samba</H1
><P
>Samba now fully supports browsing. The browsing is supported by nmbd
and is also controlled by options in the smb.conf file (see smb.conf(5)).</P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN16"
->Problem resolution</A
-></H1
+NAME="AEN2590">15.3. Problem resolution</H1
><P
>If something doesn't work then hopefully the log.nmb file will help
you track down the problem. Try a debug level of 2 or 3 for finding
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN23"
->Browsing across subnets</A
-></H1
+NAME="AEN2597">15.4. Browsing across subnets</H1
><P
>With the release of Samba 1.9.17(alpha1 and above) Samba has been
updated to enable it to support the replication of browse lists
settings) for Samba this is in the smb.conf file.</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN28"
->How does cross subnet browsing work ?</A
-></H2
+NAME="AEN2602">15.4.1. How does cross subnet browsing work ?</H2
><P
>Cross subnet browsing is a complicated dance, containing multiple
moving parts. It has taken Microsoft several years to get the code
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN63"
->Setting up a WINS server</A
-></H1
+NAME="AEN2637">15.5. Setting up a WINS server</H1
><P
>Either a Samba machine or a Windows NT Server machine may be set up
as a WINS server. To set a Samba machine to be a WINS server you must
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN82"
->Setting up Browsing in a WORKGROUP</A
-></H1
+NAME="AEN2656">15.6. Setting up Browsing in a WORKGROUP</H1
><P
>To set up cross subnet browsing on a network containing machines
in up to be in a WORKGROUP, not an NT Domain you need to set up one
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN100"
->Setting up Browsing in a DOMAIN</A
-></H1
+NAME="AEN2674">15.7. Setting up Browsing in a DOMAIN</H1
><P
>If you are adding Samba servers to a Windows NT Domain then
you must not set up a Samba server as a domain master browser.
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN110"
->Forcing samba to be the master</A
-></H1
+NAME="AEN2684">15.8. Forcing samba to be the master</H1
><P
>Who becomes the "master browser" is determined by an election process
using broadcasts. Each election packet contains a number of parameters
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN119"
->Making samba the domain master</A
-></H1
+NAME="AEN2693">15.9. Making samba the domain master</H1
><P
>The domain master is responsible for collating the browse lists of
multiple subnets so that browsing can occur between subnets. You can
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN137"
->Note about broadcast addresses</A
-></H1
+NAME="AEN2711">15.10. Note about broadcast addresses</H1
><P
>If your network uses a "0" based broadcast address (for example if it
ends in a 0) then you will strike problems. Windows for Workgroups
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN140"
->Multiple interfaces</A
-></H1
+NAME="AEN2714">15.11. Multiple interfaces</H1
><P
>Samba now supports machines with multiple network interfaces. If you
have multiple interfaces then you will need to use the "interfaces"
option in smb.conf to configure them. See smb.conf(5) for details.</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-ldap-howto.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="speed.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Storing Samba's User/Machine Account information in an LDAP Directory</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Samba performance issues</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>How to Install and Test SAMBA</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="NEXT"
+TITLE="Diagnosing your samba server"
+HREF="diagnosis.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="diagnosis.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="INSTALL"
->How to Install and Test SAMBA</A
-></H1
-><HR></DIV
+NAME="INSTALL">Chapter 1. How to Install and Test SAMBA</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Step 0: Read the man pages</A
-></H1
+NAME="AEN20">1.1. Step 0: Read the man pages</H1
><P
>The man pages distributed with SAMBA contain
lots of useful info that will help to get you started.
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN11"
->Step 1: Building the Binaries</A
-></H1
+NAME="AEN28">1.2. Step 1: Building the Binaries</H1
><P
>To do this, first run the program <B
CLASS="COMMAND"
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN39"
->Step 2: The all important step</A
-></H1
+NAME="AEN56">1.3. Step 2: The all important step</H1
><P
>At this stage you must fetch yourself a
coffee or other drink you find stimulating. Getting the rest
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN43"
->Step 3: Create the smb configuration file.</A
-></H1
+NAME="AEN60">1.4. Step 3: Create the smb configuration file.</H1
><P
>There are sample configuration files in the examples
subdirectory in the distribution. I suggest you read them
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN57"
->Step 4: Test your config file with
+NAME="AEN74">1.5. Step 4: Test your config file with
<B
CLASS="COMMAND"
>testparm</B
-></A
></H1
><P
>It's important that you test the validity of your
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN63"
->Step 5: Starting the smbd and nmbd</A
-></H1
+NAME="AEN80">1.6. Step 5: Starting the smbd and nmbd</H1
><P
>You must choose to start smbd and nmbd either
as daemons or from <B
request.</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN73"
->Step 5a: Starting from inetd.conf</A
-></H2
+NAME="AEN90">1.6.1. Step 5a: Starting from inetd.conf</H2
><P
>NOTE; The following will be different if
you use NIS or NIS+ to distributed services maps.</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN102"
->Step 5b. Alternative: starting it as a daemon</A
-></H2
+NAME="AEN119">1.6.2. Step 5b. Alternative: starting it as a daemon</H2
><P
>To start the server as a daemon you should create
a script something like this one, perhaps calling
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN118"
->Step 6: Try listing the shares available on your
- server</A
-></H1
+NAME="AEN135">1.7. Step 6: Try listing the shares available on your
+ server</H1
><P
><TT
CLASS="PROMPT"
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN127"
->Step 7: Try connecting with the unix client</A
-></H1
+NAME="AEN144">1.8. Step 7: Try connecting with the unix client</H1
><P
><TT
CLASS="PROMPT"
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN143"
->Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</A
-></H1
+NAME="AEN160">1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</H1
><P
>Try mounting disks. eg:</P
><P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN157"
->What If Things Don't Work?</A
-></H1
+NAME="AEN174">1.10. What If Things Don't Work?</H1
><P
>If nothing works and you start to think "who wrote
this pile of trash" then I suggest you do step 2 again (and
easier. </P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN162"
->Diagnosing Problems</A
-></H2
+NAME="AEN179">1.10.1. Diagnosing Problems</H2
><P
>If you have installation problems then go to
<TT
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN166"
->Scope IDs</A
-></H2
+NAME="AEN183">1.10.2. Scope IDs</H2
><P
>By default Samba uses a blank scope ID. This means
all your windows boxes must also have a blank scope ID.
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN169"
->Choosing the Protocol Level</A
-></H2
+NAME="AEN186">1.10.3. Choosing the Protocol Level</H2
><P
>The SMB protocol has many dialects. Currently
Samba supports 5, called CORE, COREPLUS, LANMAN1,
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN178"
->Printing from UNIX to a Client PC</A
-></H2
+NAME="AEN195">1.10.4. Printing from UNIX to a Client PC</H2
><P
>To use a printer that is available via a smb-based
- server from a unix host you will need to compile the
+ server from a unix host with LPR you will need to compile the
smbclient program. You then need to install the script
"smbprint". Read the instruction in smbprint for more details.
</P
><P
>There is also a SYSV style script that does much
the same thing called smbprint.sysv. It contains instructions.</P
+><P
+>See the CUPS manual for information about setting up
+ printing from a unix host with CUPS to a smb-based server. </P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN182"
->Locking</A
-></H2
+NAME="AEN200">1.10.5. Locking</H2
><P
>One area which sometimes causes trouble is locking.</P
><P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN191"
->Mapping Usernames</A
-></H2
+NAME="AEN209">1.10.6. Mapping Usernames</H2
><P
>If you have different usernames on the PCs and
the unix server then take a look at the "username map" option.
></DIV
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="diagnosis.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>SAMBA Project Documentation</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Diagnosing your samba server</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Integrating MS Windows networks with Samba</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Diagnosing your samba server"
+HREF="diagnosis.html"><LINK
+REL="NEXT"
+TITLE="Configuring PAM for distributed but centrally
+managed authentication"
+HREF="pam.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="diagnosis.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="pam.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="INTEGRATE-MS-NETWORKS"
->Integrating MS Windows networks with Samba</A
-></H1
-><HR></DIV
+NAME="INTEGRATE-MS-NETWORKS">Chapter 3. Integrating MS Windows networks with Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Agenda</A
-></H1
+NAME="AEN362">3.1. Agenda</H1
><P
>To identify the key functional mechanisms of MS Windows networking
to enable the deployment of Samba as a means of extending and/or
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN25"
->Name Resolution in a pure Unix/Linux world</A
-></H1
+NAME="AEN384">3.2. Name Resolution in a pure Unix/Linux world</H1
><P
>The key configuration files covered in this section are:</P
><P
></UL
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN41"
-><TT
+NAME="AEN400">3.2.1. <TT
CLASS="FILENAME"
>/etc/hosts</TT
-></A
></H2
><P
>Contains a static list of IP Addresses and names.
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN57"
-><TT
+NAME="AEN416">3.2.2. <TT
CLASS="FILENAME"
>/etc/resolv.conf</TT
-></A
></H2
><P
>This file tells the name resolution libraries:</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN68"
-><TT
+NAME="AEN427">3.2.3. <TT
CLASS="FILENAME"
>/etc/host.conf</TT
-></A
></H2
><P
><TT
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN76"
-><TT
+NAME="AEN435">3.2.4. <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
-></A
></H2
><P
>This file controls the actual name resolution targets. The
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN88"
->Name resolution as used within MS Windows networking</A
-></H1
+NAME="AEN447">3.3. Name resolution as used within MS Windows networking</H1
><P
>MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
limited to this area.</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN100"
->The NetBIOS Name Cache</A
-></H2
+NAME="AEN459">3.3.1. The NetBIOS Name Cache</H2
><P
>All MS Windows machines employ an in memory buffer in which is
stored the NetBIOS names and IP addresses for all external
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN105"
->The LMHOSTS file</A
-></H2
+NAME="AEN464">3.3.2. The LMHOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or
2000 in <TT
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN113"
->HOSTS file</A
-></H2
+NAME="AEN472">3.3.3. HOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or 2000 in
<TT
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN118"
->DNS Lookup</A
-></H2
+NAME="AEN477">3.3.4. DNS Lookup</H2
><P
>This capability is configured in the TCP/IP setup area in the network
configuration facility. If enabled an elaborate name resolution sequence
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN121"
->WINS Lookup</A
-></H2
+NAME="AEN480">3.3.5. WINS Lookup</H2
><P
>A WINS (Windows Internet Name Server) service is the equivaent of the
rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN133"
->How browsing functions and how to deploy stable and
-dependable browsing using Samba</A
-></H1
+NAME="AEN492">3.4. How browsing functions and how to deploy stable and
+dependable browsing using Samba</H1
><P
>As stated above, MS Windows machines register their NetBIOS names
(i.e.: the machine name for each service type in operation) on start
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN143"
->MS Windows security options and how to configure
-Samba for seemless integration</A
-></H1
+NAME="AEN502">3.5. MS Windows security options and how to configure
+Samba for seemless integration</H1
><P
>MS Windows clients may use encrypted passwords as part of a
challenege/response authentication model (a.k.a. NTLMv1) or
>password level</I
></TT
> must be set to the maximum
-number of upper case letter which <I
+number of upper case letter which <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>could</I
+></SPAN
> appear
is a password. Note that is the server OS uses the traditional
DES version of crypt(), then a <TT
for support of encrypted passwords:</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN171"
->Use MS Windows NT as an authentication server</A
-></H2
+NAME="AEN530">3.5.1. Use MS Windows NT as an authentication server</H2
><P
>This method involves the additions of the following parameters
in the smb.conf file:</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN179"
->Make Samba a member of an MS Windows NT security domain</A
-></H2
+NAME="AEN538">3.5.2. Make Samba a member of an MS Windows NT security domain</H2
><P
>This method involves additon of the following paramters in the smb.conf file:</P
><P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN196"
->Configure Samba as an authentication server</A
-></H2
+NAME="AEN555">3.5.3. Configure Samba as an authentication server</H2
><P
>This mode of authentication demands that there be on the
Unix/Linux system both a Unix style account as well as an
machine. The following structure is required.</P
><DIV
CLASS="SECT3"
-><HR><H3
+><H3
CLASS="SECT3"
><A
-NAME="AEN203"
->Users</A
-></H3
+NAME="AEN562">3.5.3.1. Users</H3
><P
>A user account that may provide a home directory should be
created. The following Linux system commands are typical of
></DIV
><DIV
CLASS="SECT3"
-><HR><H3
+><H3
CLASS="SECT3"
><A
-NAME="AEN208"
->MS Windows NT Machine Accounts</A
-></H3
+NAME="AEN567">3.5.3.2. MS Windows NT Machine Accounts</H3
><P
>These are required only when Samba is used as a domain
controller. Refer to the Samba-PDC-HOWTO for more details.</P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN213"
->Conclusions</A
-></H1
+NAME="AEN572">3.6. Conclusions</H1
><P
>Samba provides a flexible means to operate as...</P
><P
></UL
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="diagnosis.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="pam.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Diagnosing your samba server</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Configuring PAM for distributed but centrally
+managed authentication</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Hosting a Microsoft Distributed File System tree on Samba</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Configuring PAM for distributed but centrally
+managed authentication"
+HREF="pam.html"><LINK
+REL="NEXT"
+TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
+HREF="unix-permissions.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="pam.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="MSDFS"
->Hosting a Microsoft Distributed File System tree on Samba</A
-></H1
-><HR></DIV
+NAME="MSDFS">Chapter 5. Hosting a Microsoft Distributed File System tree on Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Instructions</A
-></H1
+NAME="AEN664">5.1. Instructions</H1
><P
>The Distributed File System (or Dfs) provides a means of
separating the logical view of files and directories that users
takes users directly to the appropriate shares on the network.</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN38"
->Notes</A
-></H2
+NAME="AEN699">5.1.1. Notes</H2
><P
></P
><UL
></DIV
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="pam.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Configuring PAM for distributed but centrally
+managed authentication</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>UNIX Permission Bits and Windows NT Access Control Lists</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Samba and other CIFS clients</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba performance issues"
+HREF="speed.html"><LINK
+REL="NEXT"
+TITLE="HOWTO Access Samba source code via CVS"
+HREF="cvs-access.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="speed.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="OTHER-CLIENTS">Chapter 17. Samba and other CIFS clients</H1
+><P
+>This chapter contains client-specific information.</P
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2871">17.1. Macintosh clients?</H1
+><P
+>Yes. <A
+HREF="http://www.thursby.com/"
+TARGET="_top"
+>Thursby</A
+> now have a CIFS Client / Server called DAVE - see</P
+><P
+>They test it against Windows 95, Windows NT and samba for
+compatibility issues. At the time of writing, DAVE was at version
+1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
+the Thursby web site (the speed of finder copies has been greatly
+enhanced, and there are bug-fixes included).</P
+><P
+>
+Alternatives - There are two free implementations of AppleTalk for
+several kinds of UNIX machnes, and several more commercial ones.
+These products allow you to run file services and print services
+natively to Macintosh users, with no additional support required on
+the Macintosh. The two free omplementations are
+<A
+HREF="http://www.umich.edu/~rsug/netatalk/"
+TARGET="_top"
+>Netatalk</A
+>, and
+<A
+HREF="http://www.cs.mu.oz.au/appletalk/atalk.html"
+TARGET="_top"
+>CAP</A
+>.
+What Samba offers MS
+Windows users, these packages offer to Macs. For more info on these
+packages, Samba, and Linux (and other UNIX-based systems) see
+<A
+HREF="http://www.eats.com/linux_mac_win.html"
+TARGET="_top"
+>http://www.eats.com/linux_mac_win.html</A
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2880">17.2. OS2 Client</H1
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2882">17.2.1. How can I configure OS/2 Warp Connect or
+ OS/2 Warp 4 as a client for Samba?</H2
+><P
+>A more complete answer to this question can be
+ found on <A
+HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html"
+TARGET="_top"
+> http://carol.wins.uva.nl/~leeuw/samba/warp.html</A
+>.</P
+><P
+>Basically, you need three components:</P
+><P
+></P
+><UL
+><LI
+><P
+>The File and Print Client ('IBM Peer')
+ </P
+></LI
+><LI
+><P
+>TCP/IP ('Internet support')
+ </P
+></LI
+><LI
+><P
+>The "NetBIOS over TCP/IP" driver ('TCPBEUI')
+ </P
+></LI
+></UL
+><P
+>Installing the first two together with the base operating
+ system on a blank system is explained in the Warp manual. If Warp
+ has already been installed, but you now want to install the
+ networking support, use the "Selective Install for Networking"
+ object in the "System Setup" folder.</P
+><P
+>Adding the "NetBIOS over TCP/IP" driver is not described
+ in the manual and just barely in the online documentation. Start
+ MPTS.EXE, click on OK, click on "Configure LAPS" and click
+ on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line
+ is then moved to 'Current Configuration'. Select that line,
+ click on "Change number" and increase it from 0 to 1. Save this
+ configuration.</P
+><P
+>If the Samba server(s) is not on your local subnet, you
+ can optionally add IP names and addresses of these servers
+ to the "Names List", or specify a WINS server ('NetBIOS
+ Nameserver' in IBM and RFC terminology). For Warp Connect you
+ may need to download an update for 'IBM Peer' to bring it on
+ the same level as Warp 4. See the webpage mentioned above.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2897">17.2.2. How can I configure OS/2 Warp 3 (not Connect),
+ OS/2 1.2, 1.3 or 2.x for Samba?</H2
+><P
+>You can use the free Microsoft LAN Manager 2.2c Client
+ for OS/2 from
+ <A
+HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"
+TARGET="_top"
+> ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A
+>.
+ See <A
+HREF="http://carol.wins.uva.nl/~leeuw/lanman.html"
+TARGET="_top"
+> http://carol.wins.uva.nl/~leeuw/lanman.html</A
+> for
+ more information on how to install and use this client. In
+ a nutshell, edit the file \OS2VER in the root directory of
+ the OS/2 boot partition and add the lines:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> 20=setup.exe
+ 20=netwksta.sys
+ 20=netvdd.sys
+ </PRE
+></P
+><P
+>before you install the client. Also, don't use the
+ included NE2000 driver because it is buggy. Try the NE2000
+ or NS2000 driver from
+ <A
+HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/"
+TARGET="_top"
+> ftp://ftp.cdrom.com/pub/os2/network/ndis/</A
+> instead.
+ </P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2906">17.2.3. Are there any other issues when OS/2 (any version)
+ is used as a client?</H2
+><P
+>When you do a NET VIEW or use the "File and Print
+ Client Resource Browser", no Samba servers show up. This can
+ be fixed by a patch from <A
+HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html"
+TARGET="_top"
+> http://carol.wins.uva.nl/~leeuw/samba/fix.html</A
+>.
+ The patch will be included in a later version of Samba. It also
+ fixes a couple of other problems, such as preserving long
+ filenames when objects are dragged from the Workplace Shell
+ to the Samba server. </P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2910">17.2.4. How do I get printer driver download working
+ for OS/2 clients?</H2
+><P
+>First, create a share called [PRINTDRV] that is
+ world-readable. Copy your OS/2 driver files there. Note
+ that the .EA_ files must still be separate, so you will need
+ to use the original install files, and not copy an installed
+ driver from an OS/2 system.</P
+><P
+>Install the NT driver first for that printer. Then,
+ add to your smb.conf a parameter, os2 driver map =
+ <TT
+CLASS="REPLACEABLE"
+><I
+>filename</I
+></TT
+>". Then, in the file
+ specified by <TT
+CLASS="REPLACEABLE"
+><I
+>filename</I
+></TT
+>, map the
+ name of the NT driver name to the OS/2 driver name as
+ follows:</P
+><P
+><B
+CLASS="COMMAND"
+>nt driver name = os2 "driver
+ name"."device name"</B
+>, e.g.:
+ HP LaserJet 5L = LASERJET.HP LaserJet 5L</P
+><P
+>You can have multiple drivers mapped in this file.</P
+><P
+>If you only specify the OS/2 driver name, and not the
+ device name, the first attempt to download the driver will
+ actually download the files, but the OS/2 client will tell
+ you the driver is not available. On the second attempt, it
+ will work. This is fixed simply by adding the device name
+ to the mapping, after which it will work on the first attempt.
+ </P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2920">17.3. Windows for Workgroups</H1
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2922">17.3.1. Use latest TCP/IP stack from Microsoft</H2
+><P
+>Use the latest TCP/IP stack from microsoft if you use Windows
+for workgroups.</P
+><P
+>The early TCP/IP stacks had lots of bugs.</P
+><P
+>
+Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
+VxD drivers. The latest release can be found on their ftp site at
+ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
+There is an update.txt file there that describes the problems that were
+fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386,
+WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2927">17.3.2. Delete .pwl files after password change</H2
+><P
+>WfWg does a lousy job with passwords. I find that if I change my
+password on either the unix box or the PC the safest thing to do is to
+delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.</P
+><P
+>
+If you don't do this you may find that WfWg remembers and uses the old
+password, even if you told it a new one.</P
+><P
+>
+Often WfWg will totally ignore a password you give it in a dialog box.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2932">17.3.3. Configure WfW password handling</H2
+><P
+>There is a program call admincfg.exe
+on the last disk (disk 8) of the WFW 3.11 disk set. To install it
+type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon
+for it via the "Progam Manager" "New" Menu. This program allows you
+to control how WFW handles passwords. ie disable Password Caching etc
+for use with <B
+CLASS="COMMAND"
+>security = user</B
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2936">17.3.4. Case handling of passwords</H2
+><P
+>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+> information on <B
+CLASS="COMMAND"
+>password level</B
+> to specify what characters samba should try to uppercase when checking.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2941">17.4. Windows '95/'98</H1
+><P
+>When using Windows 95 OEM SR2 the following updates are recommended where Samba
+is being used. Please NOTE that the above change will affect you once these
+updates have been installed.</P
+><P
+>
+There are more updates than the ones mentioned here. You are referred to the
+Microsoft Web site for all currently available updates to your specific version
+of Windows 95.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Kernel Update: KRNLUPD.EXE</P
+></LI
+><LI
+><P
+>Ping Fix: PINGUPD.EXE</P
+></LI
+><LI
+><P
+>RPC Update: RPCRTUPD.EXE</P
+></LI
+><LI
+><P
+>TCP/IP Update: VIPUPD.EXE</P
+></LI
+><LI
+><P
+>Redirector Update: VRDRUPD.EXE</P
+></LI
+></OL
+><P
+>Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This
+fix may stop your machine from hanging for an extended period when exiting
+OutLook and you may also notice a significant speedup when accessing network
+neighborhood services.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2957">17.5. Windows 2000 Service Pack 2</H1
+><P
+>
+There are several annoyances with Windows 2000 SP2. One of which
+only appears when using a Samba server to host user profiles
+to Windows 2000 SP2 clients in a Windows domain. This assumes
+that Samba is a member of the domain, but the problem will
+likely occur if it is not.</P
+><P
+>
+In order to server profiles successfully to Windows 2000 SP2
+clients (when not operating as a PDC), Samba must have
+<B
+CLASS="COMMAND"
+>nt acl support = no</B
+>
+added to the file share which houses the roaming profiles.
+If this is not done, then the Windows 2000 SP2 client will
+complain about not being able to access the profile (Access
+Denied) and create multiple copies of it on disk (DOMAIN.user.001,
+DOMAIN.user.002, etc...). See the
+<A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+> man page
+for more details on this option. Also note that the
+<B
+CLASS="COMMAND"
+>nt acl support</B
+> parameter was formally a global parameter in
+releases prior to Samba 2.2.2.</P
+><P
+>
+The following is a minimal profile share:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [profile]
+ path = /export/profile
+ create mask = 0600
+ directory mask = 0700
+ nt acl support = no
+ read only = no</PRE
+></P
+><P
+>The reason for this bug is that the Win2k SP2 client copies
+the security descriptor for the profile which contains
+the Samba server's SID, and not the domain SID. The client
+compares the SID for SAMBA\user and realizes it is
+different that the one assigned to DOMAIN\user. Hence the reason
+for the "access denied" message.</P
+><P
+>By disabling the <B
+CLASS="COMMAND"
+>nt acl support</B
+> parameter, Samba will send
+the Win2k client a response to the QuerySecurityDescriptor
+trans2 call which causes the client to set a default ACL
+for the profile. This default ACL includes </P
+><P
+><B
+CLASS="COMMAND"
+>DOMAIN\user "Full Control"</B
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE : This bug does not occur when using winbind to
+create accounts on the Samba host for Domain users.</I
+></SPAN
+></P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="speed.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba performance issues</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>HOWTO Access Samba source code via CVS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
managed authentication</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Integrating MS Windows networks with Samba"
+HREF="integrate-ms-networks.html"><LINK
+REL="NEXT"
+TITLE="Hosting a Microsoft Distributed File System tree on Samba"
+HREF="msdfs.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="msdfs.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="PAM"
->Configuring PAM for distributed but centrally
-managed authentication</A
-></H1
-><HR></DIV
+NAME="PAM">Chapter 4. Configuring PAM for distributed but centrally
+managed authentication</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Samba and PAM</A
-></H1
+NAME="AEN593">4.1. Samba and PAM</H1
><P
>A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
></P
><P
>Note: PAM allows stacking of authentication mechanisms. It is
-also possible to pass information obtained within on PAM module through
+also possible to pass information obtained within one PAM module through
to the next module in the PAM stack. Please refer to the documentation for
your particular system implementation for details regarding the specific
capabilities of PAM in this environment. Some Linux implmentations also
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN47"
->Distributed Authentication</A
-></H1
+NAME="AEN637">4.2. Distributed Authentication</H1
><P
>The astute administrator will realize from this that the
combination of <TT
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN54"
->PAM Configuration in smb.conf</A
-></H1
+NAME="AEN644">4.3. PAM Configuration in smb.conf</H1
><P
>There is an option in smb.conf called <A
HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
></P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="msdfs.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Integrating MS Windows networks with Samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Hosting a Microsoft Distributed File System tree on Samba</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Portability</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Group mapping HOWTO"
+HREF="groupmapping.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+> </TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="PORTABILITY">Chapter 21. Portability</H1
+><P
+>Samba works on a wide range of platforms but the interface all the
+platforms provide is not always compatible. This chapter contains
+platform-specific information about compiling and using samba.</P
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3119">21.1. HPUX</H1
+><P
+>HP's implementation of supplementary groups is, er, non-standard (for
+hysterical reasons). There are two group files, /etc/group and
+/etc/logingroup; the system maps UIDs to numbers using the former, but
+initgroups() reads the latter. Most system admins who know the ropes
+symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons
+too stupid to go into here). initgroups() will complain if one of the
+groups you're in in /etc/logingroup has what it considers to be an invalid
+ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think)
+60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody'
+GIDs.</P
+><P
+>If you encounter this problem, make sure that the programs that are failing
+to initgroups() be run as users not in any groups with GIDs outside the
+allowed range.</P
+><P
+>This is documented in the HP manual pages under setgroups(2) and passwd(4).</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3124">21.2. SCO Unix</H1
+><P
+>
+If you run an old version of SCO Unix then you may need to get important
+TCP/IP patches for Samba to work correctly. Without the patch, you may
+encounter corrupt data transfers using samba.</P
+><P
+>The patch you need is UOD385 Connection Drivers SLS. It is available from
+SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z).</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3128">21.3. DNIX</H1
+><P
+>DNIX has a problem with seteuid() and setegid(). These routines are
+needed for Samba to work correctly, but they were left out of the DNIX
+C library for some reason.</P
+><P
+>For this reason Samba by default defines the macro NO_EID in the DNIX
+section of includes.h. This works around the problem in a limited way,
+but it is far from ideal, some things still won't work right.</P
+><P
+>
+To fix the problem properly you need to assemble the following two
+functions and then either add them to your C library or link them into
+Samba.</P
+><P
+>
+put this in the file <TT
+CLASS="FILENAME"
+>setegid.s</TT
+>:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> .globl _setegid
+_setegid:
+ moveq #47,d0
+ movl #100,a0
+ moveq #1,d1
+ movl 4(sp),a1
+ trap #9
+ bccs 1$
+ jmp cerror
+1$:
+ clrl d0
+ rts</PRE
+></P
+><P
+>put this in the file <TT
+CLASS="FILENAME"
+>seteuid.s</TT
+>:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> .globl _seteuid
+_seteuid:
+ moveq #47,d0
+ movl #100,a0
+ moveq #0,d1
+ movl 4(sp),a1
+ trap #9
+ bccs 1$
+ jmp cerror
+1$:
+ clrl d0
+ rts</PRE
+></P
+><P
+>after creating the above files you then assemble them using</P
+><P
+><B
+CLASS="COMMAND"
+>as seteuid.s</B
+></P
+><P
+><B
+CLASS="COMMAND"
+>as setegid.s</B
+></P
+><P
+>that should produce the files <TT
+CLASS="FILENAME"
+>seteuid.o</TT
+> and
+<TT
+CLASS="FILENAME"
+>setegid.o</TT
+></P
+><P
+>then you need to add these to the LIBSM line in the DNIX section of
+the Samba Makefile. Your LIBSM line will then look something like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>LIBSM = setegid.o seteuid.o -ln</PRE
+></P
+><P
+>
+You should then remove the line:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#define NO_EID</PRE
+></P
+><P
+>from the DNIX section of <TT
+CLASS="FILENAME"
+>includes.h</TT
+></P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+> </TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Group mapping HOWTO</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+> </TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Printing Support in Samba 2.2.x</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
+HREF="unix-permissions.html"><LINK
+REL="NEXT"
+TITLE="Debugging Printing Problems"
+HREF="printingdebug.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="printingdebug.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="PRINTING"
->Printing Support in Samba 2.2.x</A
-></H1
-><HR></DIV
+NAME="PRINTING">Chapter 7. Printing Support in Samba 2.2.x</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Introduction</A
-></H1
+NAME="AEN902">7.1. Introduction</H1
><P
>Beginning with the 2.2.0 release, Samba supports
the native Windows NT printing mechanisms implemented via
spooled files. They are utilized entirely by the clients.</P
><P
>The following MS KB article, may be of some help if you are dealing with
-Windows 2000 clients: <I
+Windows 2000 clients: <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>How to Add Printers with No User
Interaction in Windows 2000</I
+></SPAN
></P
><P
><A
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN25"
->Configuration</A
-></H1
+NAME="AEN924">7.2. Configuration</H1
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
><B
>[print$] vs. [printer$]</B
-></TD
+></TH
></TR
><TR
><TD
+> </TD
+><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>Previous versions of Samba recommended using a share named [printer$].
This name was taken from the printer$ service created by Windows 9x
> parameter, are being deprecated and should not
be used in new installations. For more information on this change,
you should refer to the <A
-HREF="#MIGRATION"
+HREF="printing.html#MIGRATION"
>Migration section</A
>
of this document.</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN36"
->Creating [print$]</A
-></H2
+NAME="AEN935">7.2.1. Creating [print$]</H2
><P
>In order to support the uploading of printer driver
files, you must first configure a file share named [print$].
an account on the Samba host, then this is a non-issue.</P
><DIV
CLASS="NOTE"
-><BLOCKQUOTE
-CLASS="NOTE"
><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
><B
->Author's Note: </B
+>Author's Note</B
+></TH
+></TR
+><TR
+><TD
+> </TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
>The non-issue is that if all your Windows NT users are guaranteed to be
authenticated by the Samba server (such as a domain member server and the NT
user has already been validated by the Domain Controller in
> in the [global] section as well. Make sure
you understand what this parameter does before using it
though. --jerry</P
-></BLOCKQUOTE
+></TD
+></TR
+></TABLE
></DIV
><P
>In order for a Windows NT print server to support
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
><B
>ATTENTION! REQUIRED PERMISSIONS</B
-></TD
+></TH
></TR
><TR
><TD
+> </TD
+><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>In order to currently add a new driver to you Samba host,
one of two conditions must hold true:</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN71"
->Setting Drivers for Existing Printers</A
-></H2
+NAME="AEN970">7.2.2. Setting Drivers for Existing Printers</H2
><P
>The initial listing of printers in the Samba host's
Printers folder will have no real printer driver assigned
to them. By default, in Samba 2.2.0 this driver name was set to
-<I
+<SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</I
+></SPAN
>.
Later versions changed this to a NULL string to allow the use
tof the local Add Printer Wizard on NT/2000 clients.
which has this default driver assigned will result in
the error message:</P
><P
+><SPAN
+CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Device settings cannot be displayed. The driver
for the specified printer is not installed, only spooler
properties will be displayed. Do you want to install the
driver now?</I
+></SPAN
></P
><P
>Click "No" in the error dialog and you will be presented with
-the printer properties window. The way assign a driver to a
+the printer properties window. The way to assign a driver to a
printer is to either</P
><P
></P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN88"
->Support a large number of printers</A
-></H2
+NAME="AEN987">7.2.3. Support a large number of printers</H2
><P
>One issue that has arisen during the development
phase of Samba 2.2 is the need to support driver downloads for
100's of printers. Using the Windows NT APW is somewhat
-awkward to say the least. If more than one printer is using the
+awkward to say the list. If more than one printer are using the
same driver, the <A
HREF="rpcclient.1.html"
TARGET="_top"
setdriver command</B
></A
> can be used to set the driver
-associated with an installed driver. The following is an example
+associated with an installed driver. The following is example
of how this could be accomplished:</P
><P
><PRE
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN99"
->Adding New Printers via the Windows NT APW</A
-></H2
+NAME="AEN998">7.2.4. Adding New Printers via the Windows NT APW</H2
><P
>By default, Samba offers all printer shares defined in <TT
CLASS="FILENAME"
>smb.conf</TT
>
-in the "Printers..." folder. Also in this folder is the Windows NT
+in the "Printers..." folder. Also existing in this folder is the Windows NT
Add Printer Wizard icon. The APW will be show only if</P
><P
></P
>add printer
command</I
></TT
-> and reparse the <TT
+> and reparse to the <TT
CLASS="FILENAME"
>smb.conf</TT
>
></A
> for removing entries from the "Printers..."
folder.</P
+><P
+>The following is an example <A
+HREF="smb.conf.5.html#ADDPRINTERCOMMAN"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>add printer command</I
+></TT
+></A
+> script. It adds the appropriate entries to <TT
+CLASS="FILENAME"
+>/etc/printcap.local</TT
+> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>#!/bin/sh
+
+# Script to insert a new printer entry into printcap.local
+#
+# $1, printer name, used as the descriptive name
+# $2, share name, used as the printer name for Linux
+# $3, port name
+# $4, driver name
+# $5, location, used for the device file of the printer
+# $6, win9x location
+
+#
+# Make sure we use the location that RedHat uses for local printer defs
+PRINTCAP=/etc/printcap.local
+DATE=`date +%Y%m%d-%H%M%S`
+LP=lp
+RESTART="service lpd restart"
+
+# Keep a copy
+cp $PRINTCAP $PRINTCAP.$DATE
+# Add the printer to $PRINTCAP
+echo "" >> $PRINTCAP
+echo "$2|$1:\\" >> $PRINTCAP
+echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP
+echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP
+echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP
+
+touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+
+mkdir /var/spool/lpd/$2
+chmod 700 /var/spool/lpd/$2
+chown $LP /var/spool/lpd/$2
+#echo $1 >> "/usr/local/samba/var/print/$5.prn"
+#echo $2 >> "/usr/local/samba/var/print/$5.prn"
+#echo $3 >> "/usr/local/samba/var/print/$5.prn"
+#echo $4 >> "/usr/local/samba/var/print/$5.prn"
+#echo $5 >> "/usr/local/samba/var/print/$5.prn"
+#echo $6 >> "/usr/local/samba/var/print/$5.prn"
+$RESTART >> "/usr/local/samba/var/print/$5.prn"
+# Not sure if this is needed
+touch /usr/local/samba/lib/smb.conf
+#
+# You need to return a value, but I am not sure what it means.
+#
+echo "Done"
+exit 0</PRE
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN124"
->Samba and Printer Ports</A
-></H2
+NAME="AEN1028">7.2.5. Samba and Printer Ports</H2
><P
>Windows NT/2000 print servers associate a port with each printer. These normally
take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
concept of ports associated with a printer. By default, only one printer port,
-named "Samba Printer Port", exists on a system. Samba does not really need a port in
+named "Samba Printer Port", exists on a system. Samba does not really a port in
order to print, rather it is a requirement of Windows clients. </P
><P
>Note that Samba does not support the concept of "Printer Pooling" internally
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN132"
->The Imprints Toolset</A
-></H1
+NAME="AEN1036">7.3. The Imprints Toolset</H1
><P
>The Imprints tool set provides a UNIX equivalent of the
Windows NT Add Printer Wizard. For complete information, please
only provide a brief introduction to the features of Imprints.</P
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN136"
->What is Imprints?</A
-></H2
+NAME="AEN1040">7.3.1. What is Imprints?</H2
><P
>Imprints is a collection of tools for supporting the goals
of</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN146"
->Creating Printer Driver Packages</A
-></H2
+NAME="AEN1050">7.3.2. Creating Printer Driver Packages</H2
><P
>The process of creating printer driver packages is beyond
the scope of this document (refer to Imprints.txt also included
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN149"
->The Imprints server</A
-></H2
+NAME="AEN1053">7.3.3. The Imprints server</H2
><P
>The Imprints server is really a database server that
may be queried via standard HTTP mechanisms. Each printer
downloading of the package. Each package is digitally signed
via GnuPG which can be used to verify that package downloaded
is actually the one referred in the Imprints database. It is
- <I
+ <SPAN
+CLASS="emphasis"
+><I
CLASS="EMPHASIS"
>not</I
+></SPAN
> recommended that this security check
be disabled.</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN153"
->The Installation Client</A
-></H2
+NAME="AEN1057">7.3.4. The Installation Client</H2
><P
>More information regarding the Imprints installation client
is available in the <TT
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN175"
-><A
+NAME="AEN1079">7.4. <A
NAME="MIGRATION"
></A
->Migration to from Samba 2.0.x to 2.2.x</A
-></H1
+>Migration to from Samba 2.0.x to 2.2.x</H1
><P
>Given that printer driver management has changed (we hope improved) in
2.2 over prior releases, migration from an existing setup to 2.2 can
></P
><TABLE
CLASS="WARNING"
-BORDER="1"
WIDTH="100%"
+BORDER="0"
><TR
><TD
+WIDTH="25"
ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
><B
>Achtung!</B
-></TD
+></TH
></TR
><TR
><TD
+> </TD
+><TD
ALIGN="LEFT"
+VALIGN="TOP"
><P
>The following <TT
CLASS="FILENAME"
>use client driver</I
></TT
>). Both of
-these options are described in the smb.conf(5) man page and are
+these options are described in the smb.coinf(5) man page and are
disabled by default.</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="printingdebug.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>UNIX Permission Bits and Windows NT Access Control Lists</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Debugging Printing Problems</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
->
+>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Debugging Printing Problems</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Printing Support in Samba 2.2.x"
+HREF="printing.html"><LINK
+REL="NEXT"
+TITLE="Security levels"
+HREF="securitylevels.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="printing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="PRINTING_DEBUG"
->Debugging Printing Problems</A
-></H1
-><HR></DIV
+NAME="PRINTINGDEBUG">Chapter 8. Debugging Printing Problems</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Introduction</A
-></H1
+NAME="AEN1125">8.1. Introduction</H1
><P
>This is a short description of how to debug printing problems with
Samba. This describes how to debug problems with printing from a SMB
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN19"
->Debugging printer problems</A
-></H1
+NAME="AEN1141">8.2. Debugging printer problems</H1
><P
>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN28"
->What printers do I have?</A
-></H1
+NAME="AEN1150">8.3. What printers do I have?</H1
><P
>You can use the 'testprns' program to check to see if the printer
name you are using is recognized by Samba. For example, you can
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN36"
->Setting up printcap and print servers</A
-></H1
+NAME="AEN1158">8.4. Setting up printcap and print servers</H1
><P
>You may need to set up some printcaps for your Samba system to use.
It is strongly recommended that you use the facilities provided by
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN64"
->Job sent, no output</A
-></H1
+NAME="AEN1186">8.5. Job sent, no output</H1
><P
>This is the most frustrating part of printing. You may have sent the
job, verified that the job was forwarded, set up a wrapper around
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN75"
->Job sent, strange output</A
-></H1
+NAME="AEN1197">8.6. Job sent, strange output</H1
><P
>Once you have the job printing, you can then start worrying about
making it print nicely.</P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN87"
->Raw PostScript printed</A
-></H1
+NAME="AEN1209">8.7. Raw PostScript printed</H1
><P
>This is a problem that is usually caused by either the print spooling
system putting information at the start of the print job that makes
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN90"
->Advanced Printing</A
-></H1
+NAME="AEN1212">8.8. Advanced Printing</H1
><P
>Note that you can do some pretty magic things by using your
imagination with the "print command" option and some shell scripts.
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN93"
->Real debugging</A
-></H1
+NAME="AEN1215">8.9. Real debugging</H1
><P
>If the above debug tips don't help, then maybe you need to bring in
the bug guns, system tracing. See Tracing.txt in this directory.</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="printing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Printing Support in Samba 2.2.x</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Security levels</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="How to Configure Samba 2.2 as a Primary Domain Controller"
+HREF="samba-pdc.html"><LINK
+REL="NEXT"
+TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
+HREF="samba-ldap-howto.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="samba-ldap-howto.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="SAMBA-BDC">Chapter 13. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2287">13.1. Prerequisite Reading</H1
+><P
+>Before you continue reading in this chapter, please make sure
+that you are comfortable with configuring a Samba PDC
+as described in the <A
+HREF="Samba-PDC-HOWTO.html"
+TARGET="_top"
+>Samba-PDC-HOWTO</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2291">13.2. Background</H1
+><P
+>What is a Domain Controller? It is a machine that is able to answer
+logon requests from workstations in a Windows NT Domain. Whenever a
+user logs into a Windows NT Workstation, the workstation connects to a
+Domain Controller and asks him whether the username and password the
+user typed in is correct. The Domain Controller replies with a lot of
+information about the user, for example the place where the users
+profile is stored, the users full name of the user. All this
+information is stored in the NT user database, the so-called SAM.</P
+><P
+>There are two kinds of Domain Controller in a NT 4 compatible Domain:
+A Primary Domain Controller (PDC) and one or more Backup Domain
+Controllers (BDC). The PDC contains the master copy of the
+SAM. Whenever the SAM has to change, for example when a user changes
+his password, this change has to be done on the PDC. A Backup Domain
+Controller is a machine that maintains a read-only copy of the
+SAM. This way it is able to reply to logon requests and authenticate
+users in case the PDC is not available. During this time no changes to
+the SAM are possible. Whenever changes to the SAM are done on the PDC,
+all BDC receive the changes from the PDC.</P
+><P
+>Since version 2.2 Samba officially supports domain logons for all
+current Windows Clients, including Windows 2000 and XP. This text
+assumes the domain to be named SAMBA. To be able to act as a PDC, some
+parameters in the [global]-section of the smb.conf have to be set:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>workgroup = SAMBA
+domain master = yes
+domain logons = yes</PRE
+></P
+><P
+>Several other things like a [homes] and a [netlogon] share also may be
+set along with settings for the profile path, the users home drive and
+others. This will not be covered in this document.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2299">13.3. What qualifies a Domain Controller on the network?</H1
+><P
+>Every machine that is a Domain Controller for the domain SAMBA has to
+register the NetBIOS group name SAMBA#1c with the WINS server and/or
+by broadcast on the local network. The PDC also registers the unique
+NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
+normally reserved for the domain master browser, a role that has
+nothing to do with anything related to authentication, but the
+Microsoft Domain implementation requires the domain master browser to
+be on the same machine as the PDC.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2302">13.3.1. How does a Workstation find its domain controller?</H2
+><P
+>A NT workstation in the domain SAMBA that wants a local user to be
+authenticated has to find the domain controller for SAMBA. It does
+this by doing a NetBIOS name query for the group name SAMBA#1c. It
+assumes that each of the machines it gets back from the queries is a
+domain controller and can answer logon requests. To not open security
+holes both the workstation and the selected (TODO: How is the DC
+chosen) domain controller authenticate each other. After that the
+workstation sends the user's credentials (his name and password) to
+the domain controller, asking for approval.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2305">13.3.2. When is the PDC needed?</H2
+><P
+>Whenever a user wants to change his password, this has to be done on
+the PDC. To find the PDC, the workstation does a NetBIOS name query
+for SAMBA#1b, assuming this machine maintains the master copy of the
+SAM. The workstation contacts the PDC, both mutually authenticate and
+the password change is done.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2308">13.4. Can Samba be a Backup Domain Controller?</H1
+><P
+>With version 2.2, no. The native NT SAM replication protocols have
+not yet been fully implemented. The Samba Team is working on
+understanding and implementing the protocols, but this work has not
+been finished for version 2.2.</P
+><P
+>Can I get the benefits of a BDC with Samba? Yes. The main reason for
+implementing a BDC is availability. If the PDC is a Samba machine,
+a second Samba machine can be set up to
+service logon requests whenever the PDC is down.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2312">13.5. How do I set up a Samba BDC?</H1
+><P
+>Several things have to be done:</P
+><P
+></P
+><UL
+><LI
+><P
+>The domain SID has to be the same on the PDC and the BDC. This used to
+be stored in the file private/MACHINE.SID. This file is not created
+anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
+stored in the file private/secrets.tdb. Simply copying the secrets.tdb
+from the PDC to the BDC does not work, as the BDC would
+generate a new SID for itself and override the domain SID with this
+new BDC SID.</P
+><P
+>To retrieve the domain SID from the PDC or an existing BDC and store it in the
+secrets.tdb, execute 'net rpc getsid' on the BDC.</P
+></LI
+><LI
+><P
+>The Unix user database has to be synchronized from the PDC to the
+BDC. This means that both the /etc/passwd and /etc/group have to be
+replicated from the PDC to the BDC. This can be done manually
+whenever changes are made, or the PDC is set up as a NIS master
+server and the BDC as a NIS slave server. To set up the BDC as a
+mere NIS client would not be enough, as the BDC would not be able to
+access its user database in case of a PDC failure.</P
+></LI
+><LI
+><P
+>The Samba password database in the file private/smbpasswd has to be
+replicated from the PDC to the BDC. This is a bit tricky, see the
+next section.</P
+></LI
+><LI
+><P
+>Any netlogon share has to be replicated from the PDC to the
+BDC. This can be done manually whenever login scripts are changed,
+or it can be done automatically together with the smbpasswd
+synchronization.</P
+></LI
+></UL
+><P
+>Finally, the BDC has to be found by the workstations. This can be done
+by setting</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>workgroup = samba
+domain master = no
+domain logons = yes</PRE
+></P
+><P
+>in the [global]-section of the smb.conf of the BDC. This makes the BDC
+only register the name SAMBA#1c with the WINS server. This is no
+problem as the name SAMBA#1c is a NetBIOS group name that is meant to
+be registered by more than one machine. The parameter 'domain master =
+no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
+name is reserved for the Primary Domain Controller.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2329">13.5.1. How do I replicate the smbpasswd file?</H2
+><P
+>Replication of the smbpasswd file is sensitive. It has to be done
+whenever changes to the SAM are made. Every user's password change is
+done in the smbpasswd file and has to be replicated to the BDC. So
+replicating the smbpasswd file very often is necessary.</P
+><P
+>As the smbpasswd file contains plain text password equivalents, it
+must not be sent unencrypted over the wire. The best way to set up
+smbpasswd replication from the PDC to the BDC is to use the utility
+rsync. rsync can use ssh as a transport. ssh itself can be set up to
+accept *only* rsync transfer without requiring the user to type a
+password.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="samba-ldap-howto.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>How to Configure Samba 2.2 as a Primary Domain Controller</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Storing Samba's User/Machine Account information in an LDAP Directory</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Storing Samba's User/Machine Account information in an LDAP Directory</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain"
+HREF="samba-bdc.html"><LINK
+REL="NEXT"
+TITLE="Improved browsing in samba"
+HREF="improved-browsing.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-bdc.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="SAMBA-LDAP-HOWTO"
->Storing Samba's User/Machine Account information in an LDAP Directory</A
-></H1
-><HR></DIV
+NAME="SAMBA-LDAP-HOWTO">Chapter 14. Storing Samba's User/Machine Account information in an LDAP Directory</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Purpose</A
-></H1
+NAME="AEN2350">14.1. Purpose</H1
><P
>This document describes how to use an LDAP directory for storing Samba user
account information traditionally stored in the smbpasswd(5) file. It is
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN23"
->Introduction</A
-></H1
+NAME="AEN2370">14.2. Introduction</H1
><P
>Traditionally, when configuring <A
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN52"
->Supported LDAP Servers</A
-></H1
+NAME="AEN2399">14.3. Supported LDAP Servers</H1
><P
>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP
2.0 server and client libraries. The same code should be able to work with
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN57"
->Schema and Relationship to the RFC 2307 posixAccount</A
-></H1
+NAME="AEN2404">14.4. Schema and Relationship to the RFC 2307 posixAccount</H1
><P
>Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
<TT
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN69"
->Configuring Samba with LDAP</A
-></H1
+NAME="AEN2416">14.5. Configuring Samba with LDAP</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN71"
->OpenLDAP configuration</A
-></H2
+NAME="AEN2418">14.5.1. OpenLDAP configuration</H2
><P
>To include support for the sambaAccount object in an OpenLDAP directory
server, first copy the samba.schema file to slapd's configuration directory.</P
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN88"
->Configuring Samba</A
-></H2
+NAME="AEN2435">14.5.2. Configuring Samba</H2
><P
>The following parameters are available in smb.conf only with <TT
CLASS="PARAMETER"
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN116"
->Accounts and Groups management</A
-></H1
+NAME="AEN2463">14.6. Accounts and Groups management</H1
><P
>As users accounts are managed thru the sambaAccount objectclass, you should
modify you existing administration tools to deal with sambaAccount attributes.</P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN121"
->Security and sambaAccount</A
-></H1
+NAME="AEN2468">14.7. Security and sambaAccount</H1
><P
>There are two important points to remember when discussing the security
of sambaAccount entries in the directory.</P
><UL
><LI
><P
+><SPAN
+CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Never</I
+></SPAN
> retrieve the lmPassword or
ntPassword attribute values over an unencrypted LDAP session.</P
></LI
><LI
><P
+><SPAN
+CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Never</I
+></SPAN
> allow non-admin users to
view the lmPassword or ntPassword attribute values.</P
></LI
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN141"
->LDAP specials attributes for sambaAccounts</A
-></H1
+NAME="AEN2488">14.8. LDAP specials attributes for sambaAccounts</H1
><P
>The sambaAccount objectclass is composed of the following attributes:</P
><P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN211"
->Example LDIF Entries for a sambaAccount</A
-></H1
+NAME="AEN2558">14.9. Example LDIF Entries for a sambaAccount</H1
><P
>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
><P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN219"
->Comments</A
-></H1
+NAME="AEN2566">14.10. Comments</H1
><P
>Please mail all comments regarding this HOWTO to <A
HREF="mailto:jerry@samba.org"
last updated to reflect the Samba 2.2.3 release. </P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-bdc.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Improved browsing in samba</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Security levels</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Debugging Printing Problems"
+HREF="printingdebug.html"><LINK
+REL="NEXT"
+TITLE="security = domain in Samba 2.x"
+HREF="domain-security.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="printingdebug.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="domain-security.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="SECURITY_LEVELS"
->Security levels</A
-></H1
-><HR></DIV
+NAME="SECURITYLEVELS">Chapter 9. Security levels</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Introduction</A
-></H1
+NAME="AEN1228">9.1. Introduction</H1
><P
>Samba supports the following options to the global smb.conf parameter</P
><P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN14"
->More complete description of security levels</A
-></H1
+NAME="AEN1239">9.2. More complete description of security levels</H1
><P
>A SMB server tells the client at startup what "security level" it is
running. There are two options "share level" and "user level". Which
schemes by which the two could be kept in sync.</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="printingdebug.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="domain-security.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Debugging Printing Problems</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>security = domain in Samba 2.x</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Samba performance issues</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Improved browsing in samba"
+HREF="improved-browsing.html"><LINK
+REL="NEXT"
+TITLE="Samba and other CIFS clients"
+HREF="other-clients.html"></HEAD
><BODY
-CLASS="ARTICLE"
+CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
-CLASS="ARTICLE"
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="other-clients.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
><DIV
-CLASS="TITLEPAGE"
+CLASS="CHAPTER"
><H1
-CLASS="TITLE"
><A
-NAME="SPEED"
->Samba performance issues</A
-></H1
-><HR></DIV
+NAME="SPEED">Chapter 16. Samba performance issues</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3"
->Comparisons</A
-></H1
+NAME="AEN2732">16.1. Comparisons</H1
><P
>The Samba server uses TCP to talk to the client. Thus if you are
trying to see if it performs well you should really compare it to
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN9"
->Oplocks</A
-></H1
+NAME="AEN2738">16.2. Oplocks</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN11"
->Overview</A
-></H2
+NAME="AEN2740">16.2.1. Overview</H2
><P
>Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN19"
->Level2 Oplocks</A
-></H2
+NAME="AEN2748">16.2.2. Level2 Oplocks</H2
><P
>With Samba 2.0.5 a new capability - level2 (read only) oplocks is
supported (although the option is off by default - see the smb.conf
></DIV
><DIV
CLASS="SECT2"
-><HR><H2
+><H2
CLASS="SECT2"
><A
-NAME="AEN25"
->Old 'fake oplocks' option - deprecated</A
-></H2
+NAME="AEN2754">16.2.3. Old 'fake oplocks' option - deprecated</H2
><P
>Samba can also fake oplocks, by granting a oplock whenever a client
asks for one. This is controlled using the smb.conf option "fake
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN29"
->Socket options</A
-></H1
+NAME="AEN2758">16.3. Socket options</H1
><P
>There are a number of socket options that can greatly affect the
performance of a TCP based server like Samba.</P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN36"
->Read size</A
-></H1
+NAME="AEN2765">16.4. Read size</H1
><P
>The option "read size" affects the overlap of disk reads/writes with
network reads/writes. If the amount of data being transferred in
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN41"
->Max xmit</A
-></H1
+NAME="AEN2770">16.5. Max xmit</H1
><P
>At startup the client and server negotiate a "maximum transmit" size,
which limits the size of nearly all SMB commands. You can set the
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN46"
->Locking</A
-></H1
+NAME="AEN2775">16.6. Locking</H1
><P
>By default Samba does not implement strict locking on each read/write
call (although it did in previous versions). If you enable strict
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN50"
->Share modes</A
-></H1
+NAME="AEN2779">16.7. Share modes</H1
><P
>Some people find that opening files is very slow. This is often
because of the "share modes" code needed to fully implement the dos
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN55"
->Log level</A
-></H1
+NAME="AEN2784">16.8. Log level</H1
><P
>If you set the log level (also known as "debug level") higher than 2
then you may suffer a large drop in performance. This is because the
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN58"
->Wide lines</A
-></H1
+NAME="AEN2787">16.9. Wide lines</H1
><P
>The "wide links" option is now enabled by default, but if you disable
it (for better security) then you may suffer a performance hit in
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN61"
->Read raw</A
-></H1
+NAME="AEN2790">16.10. Read raw</H1
><P
>The "read raw" operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN66"
->Write raw</A
-></H1
+NAME="AEN2795">16.11. Write raw</H1
><P
>The "write raw" operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN70"
->Read prediction</A
-></H1
+NAME="AEN2799">16.12. Read prediction</H1
><P
>Samba can do read prediction on some of the SMB commands. Read
prediction means that Samba reads some extra data on the last file it
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN77"
->Memory mapping</A
-></H1
+NAME="AEN2806">16.13. Memory mapping</H1
><P
>Samba supports reading files via memory mapping them. One some
machines this can give a large boost to performance, on others it
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN82"
->Slow Clients</A
-></H1
+NAME="AEN2811">16.14. Slow Clients</H1
><P
>One person has reported that setting the protocol to COREPLUS rather
than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN86"
->Slow Logins</A
-></H1
+NAME="AEN2815">16.15. Slow Logins</H1
><P
>Slow logins are almost always due to the password checking time. Using
the lowest practical "password level" will improve things a lot. You
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN89"
->Client tuning</A
-></H1
+NAME="AEN2818">16.16. Client tuning</H1
><P
>Often a speed problem can be traced to the client. The client (for
example Windows for Workgroups) can often be tuned for better TCP
></DIV
><DIV
CLASS="SECT1"
-><HR><H1
+><H1
CLASS="SECT1"
><A
-NAME="AEN121"
->My Results</A
-></H1
+NAME="AEN2850">16.17. My Results</H1
><P
>Some people want to see real numbers in a document like this, so here
they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b
here someday ...</P
></DIV
></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="other-clients.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Improved browsing in samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Samba and other CIFS clients</TD
+></TR
+></TABLE
+></DIV
></BODY
></HTML
>
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>UNIX Permission Bits and Windows NT Access Control Lists</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="Samba-HOWTO.html"><LINK
+REL="PREVIOUS"
+TITLE="Hosting a Microsoft Distributed File System tree on Samba"
+HREF="msdfs.html"><LINK
+REL="NEXT"
+TITLE="Printing Support in Samba 2.2.x"
+HREF="printing.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="msdfs.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="printing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="UNIX-PERMISSIONS">Chapter 6. UNIX Permission Bits and Windows NT Access Control Lists</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN719">6.1. Viewing and changing UNIX permissions using the NT
+ security dialogs</H1
+><P
+>New in the Samba 2.0.4 release is the ability for Windows
+ NT clients to use their native security settings dialog box to
+ view and modify the underlying UNIX permissions.</P
+><P
+>Note that this ability is careful not to compromise
+ the security of the UNIX host Samba is running on, and
+ still obeys all the file permission rules that a Samba
+ administrator can set.</P
+><P
+>In Samba 2.0.4 and above the default value of the
+ parameter <A
+HREF="smb.conf.5.html#NTACLSUPPORT"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> nt acl support</I
+></TT
+></A
+> has been changed from
+ <TT
+CLASS="CONSTANT"
+>false</TT
+> to <TT
+CLASS="CONSTANT"
+>true</TT
+>, so
+ manipulation of permissions is turned on by default.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN728">6.2. How to view file security on a Samba share</H1
+><P
+>From an NT 4.0 client, single-click with the right
+ mouse button on any file or directory in a Samba mounted
+ drive letter or UNC path. When the menu pops-up, click
+ on the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Properties</I
+></SPAN
+> entry at the bottom of
+ the menu. This brings up the normal file properties dialog
+ box, but with Samba 2.0.4 this will have a new tab along the top
+ marked <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Security</I
+></SPAN
+>. Click on this tab and you
+ will see three buttons, <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Permissions</I
+></SPAN
+>,
+ <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Auditing</I
+></SPAN
+>, and <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Ownership</I
+></SPAN
+>.
+ The <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Auditing</I
+></SPAN
+> button will cause either
+ an error message <SPAN
+CLASS="ERRORNAME"
+>A requested privilege is not held
+ by the client</SPAN
+> to appear if the user is not the
+ NT Administrator, or a dialog which is intended to allow an
+ Administrator to add auditing requirements to a file if the
+ user is logged on as the NT Administrator. This dialog is
+ non-functional with a Samba share at this time, as the only
+ useful button, the <B
+CLASS="COMMAND"
+>Add</B
+> button will not currently
+ allow a list of users to be seen.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN739">6.3. Viewing file ownership</H1
+><P
+>Clicking on the <B
+CLASS="COMMAND"
+>"Ownership"</B
+> button
+ brings up a dialog box telling you who owns the given file. The
+ owner name will be of the form :</P
+><P
+><B
+CLASS="COMMAND"
+>"SERVER\user (Long name)"</B
+></P
+><P
+>Where <TT
+CLASS="REPLACEABLE"
+><I
+>SERVER</I
+></TT
+> is the NetBIOS name of
+ the Samba server, <TT
+CLASS="REPLACEABLE"
+><I
+>user</I
+></TT
+> is the user name of
+ the UNIX user who owns the file, and <TT
+CLASS="REPLACEABLE"
+><I
+>(Long name)</I
+></TT
+>
+ is the descriptive string identifying the user (normally found in the
+ GECOS field of the UNIX password database). Click on the <B
+CLASS="COMMAND"
+>Close
+ </B
+> button to remove this dialog.</P
+><P
+>If the parameter <TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+>
+ is set to <TT
+CLASS="CONSTANT"
+>false</TT
+> then the file owner will
+ be shown as the NT user <B
+CLASS="COMMAND"
+>"Everyone"</B
+>.</P
+><P
+>The <B
+CLASS="COMMAND"
+>Take Ownership</B
+> button will not allow
+ you to change the ownership of this file to yourself (clicking on
+ it will display a dialog box complaining that the user you are
+ currently logged onto the NT client cannot be found). The reason
+ for this is that changing the ownership of a file is a privileged
+ operation in UNIX, available only to the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>root</I
+></SPAN
+>
+ user. As clicking on this button causes NT to attempt to change
+ the ownership of a file to the current user logged into the NT
+ client this will not work with Samba at this time.</P
+><P
+>There is an NT chown command that will work with Samba
+ and allow a user with Administrator privilege connected
+ to a Samba 2.0.4 server as root to change the ownership of
+ files on both a local NTFS filesystem or remote mounted NTFS
+ or Samba drive. This is available as part of the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Seclib
+ </I
+></SPAN
+> NT security library written by Jeremy Allison of
+ the Samba Team, available from the main Samba ftp site.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN759">6.4. Viewing file or directory permissions</H1
+><P
+>The third button is the <B
+CLASS="COMMAND"
+>"Permissions"</B
+>
+ button. Clicking on this brings up a dialog box that shows both
+ the permissions and the UNIX owner of the file or directory.
+ The owner is displayed in the form :</P
+><P
+><B
+CLASS="COMMAND"
+>"SERVER\user (Long name)"</B
+></P
+><P
+>Where <TT
+CLASS="REPLACEABLE"
+><I
+>SERVER</I
+></TT
+> is the NetBIOS name of
+ the Samba server, <TT
+CLASS="REPLACEABLE"
+><I
+>user</I
+></TT
+> is the user name of
+ the UNIX user who owns the file, and <TT
+CLASS="REPLACEABLE"
+><I
+>(Long name)</I
+></TT
+>
+ is the descriptive string identifying the user (normally found in the
+ GECOS field of the UNIX password database).</P
+><P
+>If the parameter <TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+>
+ is set to <TT
+CLASS="CONSTANT"
+>false</TT
+> then the file owner will
+ be shown as the NT user <B
+CLASS="COMMAND"
+>"Everyone"</B
+> and the
+ permissions will be shown as NT "Full Control".</P
+><P
+>The permissions field is displayed differently for files
+ and directories, so I'll describe the way file permissions
+ are displayed first.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN774">6.4.1. File Permissions</H2
+><P
+>The standard UNIX user/group/world triple and
+ the corresponding "read", "write", "execute" permissions
+ triples are mapped by Samba into a three element NT ACL
+ with the 'r', 'w', and 'x' bits mapped into the corresponding
+ NT permissions. The UNIX world permissions are mapped into
+ the global NT group <B
+CLASS="COMMAND"
+>Everyone</B
+>, followed
+ by the list of permissions allowed for UNIX world. The UNIX
+ owner and group permissions are displayed as an NT
+ <B
+CLASS="COMMAND"
+>user</B
+> icon and an NT <B
+CLASS="COMMAND"
+>local
+ group</B
+> icon respectively followed by the list
+ of permissions allowed for the UNIX user and group.</P
+><P
+>As many UNIX permission sets don't map into common
+ NT names such as <B
+CLASS="COMMAND"
+>"read"</B
+>, <B
+CLASS="COMMAND"
+> "change"</B
+> or <B
+CLASS="COMMAND"
+>"full control"</B
+> then
+ usually the permissions will be prefixed by the words <B
+CLASS="COMMAND"
+> "Special Access"</B
+> in the NT display list.</P
+><P
+>But what happens if the file has no permissions allowed
+ for a particular UNIX user group or world component ? In order
+ to allow "no permissions" to be seen and modified then Samba
+ overloads the NT <B
+CLASS="COMMAND"
+>"Take Ownership"</B
+> ACL attribute
+ (which has no meaning in UNIX) and reports a component with
+ no permissions as having the NT <B
+CLASS="COMMAND"
+>"O"</B
+> bit set.
+ This was chosen of course to make it look like a zero, meaning
+ zero permissions. More details on the decision behind this will
+ be given below.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN788">6.4.2. Directory Permissions</H2
+><P
+>Directories on an NT NTFS file system have two
+ different sets of permissions. The first set of permissions
+ is the ACL set on the directory itself, this is usually displayed
+ in the first set of parentheses in the normal <B
+CLASS="COMMAND"
+>"RW"</B
+>
+ NT style. This first set of permissions is created by Samba in
+ exactly the same way as normal file permissions are, described
+ above, and is displayed in the same way.</P
+><P
+>The second set of directory permissions has no real meaning
+ in the UNIX permissions world and represents the <B
+CLASS="COMMAND"
+> "inherited"</B
+> permissions that any file created within
+ this directory would inherit.</P
+><P
+>Samba synthesises these inherited permissions for NT by
+ returning as an NT ACL the UNIX permission mode that a new file
+ created by Samba on this share would receive.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN795">6.5. Modifying file or directory permissions</H1
+><P
+>Modifying file and directory permissions is as simple
+ as changing the displayed permissions in the dialog box, and
+ clicking the <B
+CLASS="COMMAND"
+>OK</B
+> button. However, there are
+ limitations that a user needs to be aware of, and also interactions
+ with the standard Samba permission masks and mapping of DOS
+ attributes that need to also be taken into account.</P
+><P
+>If the parameter <TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+>
+ is set to <TT
+CLASS="CONSTANT"
+>false</TT
+> then any attempt to set
+ security permissions will fail with an <B
+CLASS="COMMAND"
+>"Access Denied"
+ </B
+> message.</P
+><P
+>The first thing to note is that the <B
+CLASS="COMMAND"
+>"Add"</B
+>
+ button will not return a list of users in Samba 2.0.4 (it will give
+ an error message of <B
+CLASS="COMMAND"
+>"The remote procedure call failed
+ and did not execute"</B
+>). This means that you can only
+ manipulate the current user/group/world permissions listed in
+ the dialog box. This actually works quite well as these are the
+ only permissions that UNIX actually has.</P
+><P
+>If a permission triple (either user, group, or world)
+ is removed from the list of permissions in the NT dialog box,
+ then when the <B
+CLASS="COMMAND"
+>"OK"</B
+> button is pressed it will
+ be applied as "no permissions" on the UNIX side. If you then
+ view the permissions again the "no permissions" entry will appear
+ as the NT <B
+CLASS="COMMAND"
+>"O"</B
+> flag, as described above. This
+ allows you to add permissions back to a file or directory once
+ you have removed them from a triple component.</P
+><P
+>As UNIX supports only the "r", "w" and "x" bits of
+ an NT ACL then if other NT security attributes such as "Delete
+ access" are selected then they will be ignored when applied on
+ the Samba server.</P
+><P
+>When setting permissions on a directory the second
+ set of permissions (in the second set of parentheses) is
+ by default applied to all files within that directory. If this
+ is not what you want you must uncheck the <B
+CLASS="COMMAND"
+>"Replace
+ permissions on existing files"</B
+> checkbox in the NT
+ dialog before clicking <B
+CLASS="COMMAND"
+>"OK"</B
+>.</P
+><P
+>If you wish to remove all permissions from a
+ user/group/world component then you may either highlight the
+ component and click the <B
+CLASS="COMMAND"
+>"Remove"</B
+> button,
+ or set the component to only have the special <B
+CLASS="COMMAND"
+>"Take
+ Ownership"</B
+> permission (displayed as <B
+CLASS="COMMAND"
+>"O"
+ </B
+>) highlighted.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN817">6.6. Interaction with the standard Samba create mask
+ parameters</H1
+><P
+>Note that with Samba 2.0.5 there are four new parameters
+ to control this interaction. These are :</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>directory security mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force directory security mode</I
+></TT
+></P
+><P
+>Once a user clicks <B
+CLASS="COMMAND"
+>"OK"</B
+> to apply the
+ permissions Samba maps the given permissions into a user/group/world
+ r/w/x triple set, and then will check the changed permissions for a
+ file against the bits set in the <A
+HREF="smb.conf.5.html#SECURITYMASK"
+TARGET="_top"
+>
+ <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></A
+> parameter. Any bits that
+ were changed that are not set to '1' in this parameter are left alone
+ in the file permissions.</P
+><P
+>Essentially, zero bits in the <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+>
+ mask may be treated as a set of bits the user is <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not</I
+></SPAN
+>
+ allowed to change, and one bits are those the user is allowed to change.
+ </P
+><P
+>If not set explicitly this parameter is set to the same value as
+ the <A
+HREF="smb.conf.5.html#CREATEMASK"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>create mask
+ </I
+></TT
+></A
+> parameter to provide compatibility with Samba 2.0.4
+ where this permission change facility was introduced. To allow a user to
+ modify all the user/group/world permissions on a file, set this parameter
+ to 0777.</P
+><P
+>Next Samba checks the changed permissions for a file against
+ the bits set in the <A
+HREF="smb.conf.5.html#FORCESECURITYMODE"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>force security mode</I
+></TT
+></A
+> parameter. Any bits
+ that were changed that correspond to bits set to '1' in this parameter
+ are forced to be set.</P
+><P
+>Essentially, bits set in the <TT
+CLASS="PARAMETER"
+><I
+>force security mode
+ </I
+></TT
+> parameter may be treated as a set of bits that, when
+ modifying security on a file, the user has always set to be 'on'.</P
+><P
+>If not set explicitly this parameter is set to the same value
+ as the <A
+HREF="smb.conf.5.html#FORCECREATEMODE"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ create mode</I
+></TT
+></A
+> parameter to provide compatibility
+ with Samba 2.0.4 where the permission change facility was introduced.
+ To allow a user to modify all the user/group/world permissions on a file
+ with no restrictions set this parameter to 000.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>force
+ security mode</I
+></TT
+> parameters are applied to the change
+ request in that order.</P
+><P
+>For a directory Samba will perform the same operations as
+ described above for a file except using the parameter <TT
+CLASS="PARAMETER"
+><I
+> directory security mask</I
+></TT
+> instead of <TT
+CLASS="PARAMETER"
+><I
+>security
+ mask</I
+></TT
+>, and <TT
+CLASS="PARAMETER"
+><I
+>force directory security mode
+ </I
+></TT
+> parameter instead of <TT
+CLASS="PARAMETER"
+><I
+>force security mode
+ </I
+></TT
+>.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>directory security mask</I
+></TT
+> parameter
+ by default is set to the same value as the <TT
+CLASS="PARAMETER"
+><I
+>directory mask
+ </I
+></TT
+> parameter and the <TT
+CLASS="PARAMETER"
+><I
+>force directory security
+ mode</I
+></TT
+> parameter by default is set to the same value as
+ the <TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+> parameter to provide
+ compatibility with Samba 2.0.4 where the permission change facility
+ was introduced.</P
+><P
+>In this way Samba enforces the permission restrictions that
+ an administrator can set on a Samba share, whilst still allowing users
+ to modify the permission bits within that restriction.</P
+><P
+>If you want to set up a share that allows users full control
+ in modifying the permission bits on their files and directories and
+ doesn't force any particular bits to be set 'on', then set the following
+ parameters in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+></A
+> file in that share specific section :</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>security mask = 0777</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode = 0</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>directory security mask = 0777</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force directory security mode = 0</I
+></TT
+></P
+><P
+>As described, in Samba 2.0.4 the parameters :</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>directory mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+></P
+><P
+>were used instead of the parameters discussed here.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN881">6.7. Interaction with the standard Samba file attribute
+ mapping</H1
+><P
+>Samba maps some of the DOS attribute bits (such as "read
+ only") into the UNIX permissions of a file. This means there can
+ be a conflict between the permission bits set via the security
+ dialog and the permission bits set by the file attribute mapping.
+ </P
+><P
+>One way this can show up is if a file has no UNIX read access
+ for the owner it will show up as "read only" in the standard
+ file attributes tabbed dialog. Unfortunately this dialog is
+ the same one that contains the security info in another tab.</P
+><P
+>What this can mean is that if the owner changes the permissions
+ to allow themselves read access using the security dialog, clicks
+ <B
+CLASS="COMMAND"
+>"OK"</B
+> to get back to the standard attributes tab
+ dialog, and then clicks <B
+CLASS="COMMAND"
+>"OK"</B
+> on that dialog, then
+ NT will set the file permissions back to read-only (as that is what
+ the attributes still say in the dialog). This means that after setting
+ permissions and clicking <B
+CLASS="COMMAND"
+>"OK"</B
+> to get back to the
+ attributes dialog you should always hit <B
+CLASS="COMMAND"
+>"Cancel"</B
+>
+ rather than <B
+CLASS="COMMAND"
+>"OK"</B
+> to ensure that your changes
+ are not overridden.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="msdfs.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="Samba-HOWTO.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="printing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Hosting a Microsoft Distributed File System tree on Samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+> </TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Printing Support in Samba 2.2.x</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
git.samba.org / tprouty / samba.git / commitdiff