- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-ByExample/SBE-MakingHappyUsers.xml
r746 r988 364 364 The implementation of Samba BDCs necessitates the installation and configuration of LDAP. 365 365 For this site, you use OpenLDAP, the open source software LDAP server platform. Commercial 366 LDAP servers in current use with Samba -3include:366 LDAP servers in current use with Samba include: 367 367 </para> 368 368 … … 396 396 offerings, it requires that you manually edit the server configuration files and manually 397 397 initialize the LDAP directory database. OpenLDAP itself has only command-line tools to 398 help you to get OpenLDAP and Samba -3running as required, albeit with some learning curve challenges.398 help you to get OpenLDAP and Samba running as required, albeit with some learning curve challenges. 399 399 </para> 400 400 … … 448 448 tools and the creation of shell and Perl scripts a bit 449 449 challenging. OpenLDAP can be easily customized, though it includes 450 many ready-to-use schemas. Samba -3provides an OpenLDAP schema file450 many ready-to-use schemas. Samba provides an OpenLDAP schema file 451 451 that is required for use as a passdb backend. 452 452 </para> … … 454 454 <para> 455 455 <indexterm><primary>interoperability</primary></indexterm> 456 For those who are willing to brave the process of installing and configuring LDAP and Samba -3interoperability,456 For those who are willing to brave the process of installing and configuring LDAP and Samba interoperability, 457 457 there are a few nice Web-based tools that may help you to manage your users and groups more effectively. 458 458 The Web-based tools you might like to consider include the … … 520 520 server for UNIX system accounts as well as for Samba. From the OpenLDAP perspective, UNIX system 521 521 accounts are stored POSIX schema extensions. Samba provides its own schema to permit storage of account 522 attributes Samba needs. Samba -3can use the LDAP backend to store:522 attributes Samba needs. Samba can use the LDAP backend to store: 523 523 </para> 524 524 … … 540 540 <indexterm><primary>UID</primary></indexterm> 541 541 <indexterm><primary>nss_ldap</primary></indexterm> 542 The use of LDAP with Samba -3makes it necessary to store UNIX accounts as well as Windows Networking542 The use of LDAP with Samba makes it necessary to store UNIX accounts as well as Windows Networking 543 543 accounts in the LDAP backend. This implies the need to use the 544 544 <ulink url="http://www.padl.com/Contents/OpenSourceSoftware.html">PADL LDAP tools</ulink>. The resolution … … 858 858 859 859 <para> 860 This book is about Samba -3, so you can confine the printing style to just the smart860 This book is about Samba, so you can confine the printing style to just the smart 861 861 style of installation. Those interested in further information regarding intelligent 862 862 printing should review documentation on the Easy Software Products Web site. … … 1250 1250 1251 1251 <itemizedlist> 1252 <listitem><para>Samba -3PDC Server Configuration</para>1252 <listitem><para>Samba PDC Server Configuration</para> 1253 1253 <orderedlist> 1254 1254 <listitem><para>DHCP and DNS servers</para></listitem> 1255 1255 <listitem><para>OpenLDAP server</para></listitem> 1256 1256 <listitem><para>PAM and NSS client tools</para></listitem> 1257 <listitem><para>Samba -3PDC</para></listitem>1257 <listitem><para>Samba PDC</para></listitem> 1258 1258 <listitem><para>Idealx smbldap scripts</para></listitem> 1259 1259 <listitem><para>LDAP initialization</para></listitem> … … 1266 1266 </orderedlist> 1267 1267 </listitem> 1268 <listitem><para>Samba -3BDC Server Configuration</para>1268 <listitem><para>Samba BDC Server Configuration</para> 1269 1269 <orderedlist> 1270 1270 <listitem><para>DHCP and DNS servers</para></listitem> … … 1384 1384 1385 1385 <para> 1386 Samba -3and OpenLDAP will have a degree of interdependence that is unavoidable. The method1387 for bootstrapping the LDAP and Samba -3configuration is relatively straightforward. If you1386 Samba and OpenLDAP will have a degree of interdependence that is unavoidable. The method 1387 for bootstrapping the LDAP and Samba configuration is relatively straightforward. If you 1388 1388 follow these guidelines, the resulting system should work fine. 1389 1389 </para> … … 1782 1782 <indexterm><primary>secrets.tdb</primary></indexterm> 1783 1783 <indexterm><primary>smbpasswd</primary></indexterm> 1784 Samba -3communicates with the LDAP server. The password that it uses to1784 Samba communicates with the LDAP server. The password that it uses to 1785 1785 authenticate to the LDAP server must be stored in the <filename>secrets.tdb</filename> 1786 1786 file. Execute the following to create the new <filename>secrets.tdb</filename> files … … 1798 1798 <indexterm><primary>smbd</primary></indexterm> 1799 1799 <indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm> 1800 Samba -3generates a Windows Security Identifier (SID) only when <command>smbd</command>1800 Samba generates a Windows Security Identifier (SID) only when <command>smbd</command> 1801 1801 has been started. For this reason, you start Samba. After a few seconds delay, 1802 1802 execute: … … 1857 1857 1858 1858 <para> 1859 Your Samba -3PDC is now ready to communicate with the LDAP password backend. Let's get on with1859 Your Samba PDC is now ready to communicate with the LDAP password backend. Let's get on with 1860 1860 configuration of the LDAP server. 1861 1861 </para> … … 1926 1926 <para> 1927 1927 <indexterm><primary>Idealx</primary><secondary>smbldap-tools</secondary></indexterm> 1928 The Idealx scripts, or equivalent, are necessary to permit Samba -3to manage accounts1928 The Idealx scripts, or equivalent, are necessary to permit Samba to manage accounts 1929 1929 on the LDAP server. You have chosen the Idealx scripts because they are the best-known 1930 1930 LDAP configuration scripts. The use of these scripts will help avoid the necessity … … 2233 2233 2234 2234 <para> 2235 At this time, Samba -3requires that on a PDC all UNIX (POSIX) group accounts that are2235 At this time, Samba requires that on a PDC all UNIX (POSIX) group accounts that are 2236 2236 mapped (linked) to Windows domain group accounts must be in the LDAP database. It does not 2237 2237 hurt to have UNIX user and group accounts in both the system files as well as in the LDAP … … 2296 2296 <indexterm><primary>directory</primary><secondary>Computers container</secondary></indexterm> 2297 2297 In the following examples, as the LDAP database is initialized, we do create a container 2298 for Computer (machine) accounts. In the Samba -3&smb.conf; files, specific use is made2298 for Computer (machine) accounts. In the Samba &smb.conf; files, specific use is made 2299 2299 of the People container, not the Computers container, for domain member accounts. This is not a 2300 2300 mistake; it is a deliberate action that is necessitated by the fact that the resolution of … … 2673 2673 <indexterm><primary>ldapsam</primary></indexterm> 2674 2674 <indexterm><primary>pdbedit</primary></indexterm> 2675 The final validation step involves making certain that Samba -3can obtain the user2675 The final validation step involves making certain that Samba can obtain the user 2676 2676 accounts from the LDAP ldapsam passwd backend. Execute the following command as shown: 2677 2677 <screen> … … 2758 2758 <step><para> 2759 2759 The server you have so carefully built is now ready for another important step. You 2760 start the Samba -3 server and validate its operation. Execute the following to render all2760 start the Samba server and validate its operation. Execute the following to render all 2761 2761 the processes needed fully operative so that, on system reboot, they are automatically 2762 2762 started: … … 2801 2801 <step><para> 2802 2802 <indexterm><primary>smbclient</primary></indexterm> 2803 You may now check Samba -3operation as follows:2803 You may now check Samba operation as follows: 2804 2804 <screen> 2805 2805 &rootprompt; smbclient -L massive -U% … … 2859 2859 <para> 2860 2860 <indexterm><primary>CUPS</primary></indexterm> 2861 The configuration for Samba -3to enable CUPS raw-print-through printing has already been2861 The configuration for Samba to enable CUPS raw-print-through printing has already been 2862 2862 taken care of in the &smb.conf; file. The only preparation needed for <constant>smart</constant> 2863 printing to be possible involves creation of the directories in which Samba -3stores2863 printing to be possible involves creation of the directories in which Samba stores 2864 2864 Windows printing driver files. 2865 2865 </para> … … 2965 2965 2966 2966 <sect1 id="sbehap-bldg1"> 2967 <title>Samba -3BDC Configuration</title>2967 <title>Samba BDC Configuration</title> 2968 2968 2969 2969 <procedure> … … 3055 3055 <step><para> 3056 3056 <indexterm><primary>smbpasswd</primary></indexterm> 3057 You must now set the LDAP administrative password into the Samba -3<filename>secrets.tdb</filename>3057 You must now set the LDAP administrative password into the Samba <filename>secrets.tdb</filename> 3058 3058 file by executing this command: 3059 3059 <screen> … … 3066 3066 Now you must obtain the domain SID from the PDC and store it into the 3067 3067 <filename>secrets.tdb</filename> file also. This step is not necessary with an LDAP 3068 passdb backend because Samba -3 obtains the domain SID from the3068 passdb backend because Samba obtains the domain SID from the 3069 3069 sambaDomain object it automatically stores in the LDAP backend. It does not hurt to 3070 3070 add the SID to the <filename>secrets.tdb</filename>, and if you wish to do so, this … … 3075 3075 for Domain MEGANET2 in secrets.tdb 3076 3076 </screen> 3077 When configuring a Samba -3BDC that has an LDAP backend, there is no need to take3077 When configuring a Samba BDC that has an LDAP backend, there is no need to take 3078 3078 any special action to join it to the domain. However, winbind communicates with the 3079 3079 domain controller that is running on the localhost and must be able to authenticate, … … 3095 3095 <primary>pdbedit</primary> 3096 3096 </indexterm> 3097 Verify that user and group account resolution works via Samba -3tools as follows:3097 Verify that user and group account resolution works via Samba tools as follows: 3098 3098 <screen> 3099 3099 &rootprompt; pdbedit -L … … 3124 3124 <step><para> 3125 3125 The server you have so carefully built is now ready for another important step. Now 3126 start the Samba -3server and validate its operation. Execute the following to render all3126 start the Samba server and validate its operation. Execute the following to render all 3127 3127 the processes needed fully operative so that, upon system reboot, they are automatically 3128 3128 started: … … 3137 3137 &rootprompt; rcwinbind start 3138 3138 </screen> 3139 Samba -3should now be running and is ready for a quick test. But not quite yet!3139 Samba should now be running and is ready for a quick test. But not quite yet! 3140 3140 </para></step> 3141 3141
Note:
See TracChangeset
for help on using the changeset viewer.
