4 >SAMBA Project Documentation</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
18 NAME="SAMBA-PROJECT-DOCUMENTATION"
25 NAME="SAMBA-PROJECT-DOCUMENTATION"
26 >SAMBA Project Documentation</A
43 > : Tue Jul 31 15:58:03 CDT 2001</P
45 >This book is a collection of HOWTOs added to Samba documentation over the years.
46 I try to ensure that all are current, but sometimes the is a larger job
47 than one person can maintain. The most recent version of this document
49 HREF="http://www.samba.org/"
51 >http://www.samba.org/</A
53 on the "Documentation" page. Please send updates to <A
54 HREF="mailto:jerry@samba.org"
70 >How to Install and Test SAMBA</A
77 >Step 0: Read the man pages</A
82 >Step 1: Building the Binaries</A
87 >Step 2: The all important step</A
92 >Step 3: Create the smb configuration file.</A
97 >Step 4: Test your config file with
106 >Step 5: Starting the smbd and nmbd</A
113 >Step 5a: Starting from inetd.conf</A
118 >Step 5b. Alternative: starting it as a daemon</A
125 >Step 6: Try listing the shares available on your
131 >Step 7: Try connecting with the unix client</A
136 >Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
137 Win2k, OS/2, etc... client</A
142 >What If Things Don't Work?</A
149 >Diagnosing Problems</A
159 >Choosing the Protocol Level</A
164 >Printing from UNIX to a Client PC</A
174 >Mapping Usernames</A
179 >Other Character Sets</A
187 HREF="#INTEGRATE-MS-NETWORKS"
188 >Integrating MS Windows networks with Samba</A
200 >Name Resolution in a pure Unix/Linux world</A
217 >/etc/resolv.conf</TT
233 >/etc/nsswitch.conf</TT
241 >Name resolution as used within MS Windows networking</A
248 >The NetBIOS Name Cache</A
275 >How browsing functions and how to deploy stable and
276 dependable browsing using Samba</A
281 >MS Windows security options and how to configure
282 Samba for seemless integration</A
289 >Use MS Windows NT as an authentication server</A
294 >Make Samba a member of an MS Windows NT security domain</A
299 >Configure Samba as an authentication server</A
311 >MS Windows NT Machine Accounts</A
327 >Configuring PAM for distributed but centrally
328 managed authentication</A
340 >Distributed Authentication</A
345 >PAM Configuration in smb.conf</A
352 >Hosting a Microsoft Distributed File System tree on Samba</A
374 HREF="#UNIX-PERMISSIONS"
375 >UNIX Permission Bits and Windows NT Access Control Lists</A
382 >Viewing and changing UNIX permissions using the NT
388 >How to view file security on a Samba share</A
393 >Viewing file ownership</A
398 >Viewing file or directory permissions</A
410 >Directory Permissions</A
417 >Modifying file or directory permissions</A
422 >Interaction with the standard Samba create mask
428 >Interaction with the standard Samba file attribute
436 >Printing Support in Samba 2.2.x</A
455 >Creating [print$]</A
460 >Setting Drivers for Existing Printers</A
465 >Support a large number of printers</A
470 >Adding New Printers via the Windows NT APW</A
475 >Samba and Printer Ports</A
482 >The Imprints Toolset</A
489 >What is Imprints?</A
494 >Creating Printer Driver Packages</A
499 >The Imprints server</A
504 >The Installation Client</A
514 >Migration to from Samba 2.0.x to 2.2.x</A
520 HREF="#DOMAIN-SECURITY"
521 >security = domain in Samba 2.x</A
528 >Joining an NT Domain with Samba 2.2</A
533 >Samba and Windows 2000 Domains</A
538 >Why is this better than security = server?</A
545 >How to Configure Samba 2.2 as a Primary Domain Controller</A
552 >Prerequisite Reading</A
562 >Configuring the Samba Domain Controller</A
567 >Creating Machine Trust Accounts and Joining Clients to the
575 >Manual Creation of Machine Trust Accounts</A
580 >"On-the-Fly" Creation of Machine Trust Accounts</A
585 >Joining the Client to the Domain</A
592 >Common Problems and Errors</A
597 >System Policies and Profiles</A
602 >What other help can I get?</A
607 >Domain Control for Windows 9x/ME</A
614 >Configuration Instructions: Network Logons</A
619 >Configuration Instructions: Setting up Roaming User Profiles</A
626 >Windows NT Configuration</A
631 >Windows 9X Configuration</A
636 >Win9X and WinNT Configuration</A
641 >Windows 9X Profile Setup</A
646 >Windows NT Workstation 4.0</A
651 >Windows NT Server</A
656 >Sharing Profiles between W95 and NT Workstation 4.0</A
665 >DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A
671 HREF="#SAMBA-LDAP-HOWTO"
672 >Storing Samba's User/Machine Account information in an LDAP Directory</A
689 >Supported LDAP Servers</A
694 >Schema and Relationship to the RFC 2307 posixAccount</A
699 >smb.conf LDAP parameters</A
704 >Security and sambaAccount</A
714 >Example LDIF Entries for a sambaAccount</A
726 >Unified Logons between Windows NT and UNIX using Winbind</A
743 >What Winbind Provides</A
757 >How Winbind Works</A
764 >Microsoft Remote Procedure Calls</A
769 >Name Service Switch</A
774 >Pluggable Authentication Modules</A
779 >User and Group ID Allocation</A
791 >Installation and Configuration</A
808 >Testing Things Out</A
815 >Configure and compile SAMBA</A
829 >Configure smb.conf</A
834 >Join the SAMBA server to the PDC domain</A
839 >Start up the winbindd daemon and test it!</A
846 >/etc/rc.d/init.d/smb</TT
852 >Configure Winbind and PAM</A
887 >How can I configure OS/2 Warp Connect or
888 OS/2 Warp 4 as a client for Samba?</A
893 >How can I configure OS/2 Warp 3 (not Connect),
894 OS/2 1.2, 1.3 or 2.x for Samba?</A
899 >Are there any other issues when OS/2 (any version)
900 is used as a client?</A
905 >How do I get printer driver download working
915 >HOWTO Access Samba source code via CVS</A
927 >CVS Access to samba.org</A
934 >Access via CVSweb</A
957 >Chapter 1. How to Install and Test SAMBA</A
965 >1.1. Step 0: Read the man pages</A
968 >The man pages distributed with SAMBA contain
969 lots of useful info that will help to get you started.
970 If you don't know how to read man pages then try
979 >nroff -man smbd.8 | more
984 >Other sources of information are pointed to
985 by the Samba web site,<A
986 HREF="http://www.samba.org/"
988 > http://www.samba.org</A
997 >1.2. Step 1: Building the Binaries</A
1000 >To do this, first run the program <B
1004 > in the source directory. This should automatically
1005 configure Samba for your operating system. If you have unusual
1006 needs then you may wish to run</P
1019 >first to see what special options you can enable.
1032 >will create the binaries. Once it's successfully
1033 compiled you can use </P
1045 >to install the binaries and manual pages. You can
1046 separately install the binaries and/or man pages using</P
1072 >Note that if you are upgrading for a previous version
1073 of Samba you might like to know that the old versions of
1074 the binaries will be renamed with a ".old" extension. You
1075 can go back to the previous version with</P
1088 >if you find this version a disaster!</P
1096 >1.3. Step 2: The all important step</A
1099 >At this stage you must fetch yourself a
1100 coffee or other drink you find stimulating. Getting the rest
1101 of the install right can sometimes be tricky, so you will
1102 probably need it.</P
1104 >If you have installed samba before then you can skip
1113 >1.4. Step 3: Create the smb configuration file.</A
1116 >There are sample configuration files in the examples
1117 subdirectory in the distribution. I suggest you read them
1118 carefully so you can see how the options go together in
1119 practice. See the man page for all the options.</P
1121 >The simplest useful configuration file would be
1122 something like this:</P
1131 CLASS="PROGRAMLISTING"
1144 >which would allow connections by anyone with an
1145 account on the server, using either their login name or
1146 "homes" as the service name. (Note that I also set the
1147 workgroup that Samba is part of. See BROWSING.txt for details)</P
1156 > file. You need to create it
1159 >Make sure you put the smb.conf file in the same place
1160 you specified in the<TT
1163 > (the default is to
1166 >/usr/local/samba/lib/</TT
1169 >For more information about security settings for the
1170 [homes] share please refer to the document UNIX_SECURITY.txt.</P
1178 >1.5. Step 4: Test your config file with
1185 >It's important that you test the validity of your
1189 > file using the testparm program.
1190 If testparm runs OK then it will list the loaded services. If
1191 not it will give an error message.</P
1193 >Make sure it runs OK and that the services look
1194 reasonable before proceeding. </P
1202 >1.6. Step 5: Starting the smbd and nmbd</A
1205 >You must choose to start smbd and nmbd either
1206 as daemons or from <B
1210 to do both! Either you can put them in <TT
1213 > and have them started on demand
1217 >, or you can start them as
1218 daemons either from the command line or in <TT
1221 >. See the man pages for details
1222 on the command line options. Take particular care to read
1223 the bit about what user you need to be in order to start
1224 Samba. In many cases you must be root.</P
1226 >The main advantage of starting <B
1233 > as a daemon is that they will
1234 respond slightly more quickly to an initial connection
1235 request. This is, however, unlikely to be a problem.</P
1242 >1.6.1. Step 5a: Starting from inetd.conf</A
1245 >NOTE; The following will be different if
1246 you use NIS or NIS+ to distributed services maps.</P
1252 What is defined at port 139/tcp. If nothing is defined
1253 then add a line like this:</P
1258 >netbios-ssn 139/tcp</B
1262 >similarly for 137/udp you should have an entry like:</P
1267 >netbios-ns 137/udp</B
1273 >/etc/inetd.conf</TT
1275 and add two lines something like this:</P
1284 CLASS="PROGRAMLISTING"
1285 > netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
1286 netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd
1293 >The exact syntax of <TT
1295 >/etc/inetd.conf</TT
1297 varies between unixes. Look at the other entries in inetd.conf
1300 >NOTE: Some unixes already have entries like netbios_ns
1301 (note the underscore) in <TT
1305 You must either edit <TT
1311 >/etc/inetd.conf</TT
1312 > to make them consistent.</P
1314 >NOTE: On many systems you may need to use the
1315 "interfaces" option in smb.conf to specify the IP address
1316 and netmask of your interfaces. Run <B
1320 as root if you don't know what the broadcast is for your
1324 > tries to determine it at run
1325 time, but fails on some unixes. See the section on "testing nmbd"
1326 for a method of finding if you need to do this.</P
1328 >!!!WARNING!!! Many unixes only accept around 5
1329 parameters on the command line in <TT
1333 This means you shouldn't use spaces between the options and
1334 arguments, or you should use a script, and start the script
1343 >, perhaps just send
1344 it a HUP. If you have installed an earlier version of <B
1347 > then you may need to kill nmbd as well.</P
1355 >1.6.2. Step 5b. Alternative: starting it as a daemon</A
1358 >To start the server as a daemon you should create
1359 a script something like this one, perhaps calling
1372 CLASS="PROGRAMLISTING"
1374 /usr/local/samba/bin/smbd -D
1375 /usr/local/samba/bin/nmbd -D
1382 >then make it executable with <B
1388 >You can then run <B
1392 hand or execute it from <TT
1398 >To kill it send a kill signal to the processes
1407 >NOTE: If you use the SVR4 style init system then
1408 you may like to look at the <TT
1410 >examples/svr4-startup</TT
1412 script to make Samba fit into that system.</P
1421 >1.7. Step 6: Try listing the shares available on your
1441 >Your should get back a list of shares available on
1442 your server. If you don't then something is incorrectly setup.
1443 Note that this method can also be used to see what shares
1444 are available on other LanManager clients (such as WfWg).</P
1446 >If you choose user level security then you may find
1447 that Samba requests a password before it will list the shares.
1451 > man page for details. (you
1452 can force it to list the shares without a password by
1453 adding the option -U% to the command line. This will not work
1454 with non-Samba servers)</P
1462 >1.8. Step 7: Try connecting with the unix client</A
1474 > //yourhostname/aservice</I
1486 would be the name of the host where you installed <B
1495 any service you have defined in the <TT
1499 file. Try your user name if you just have a [homes] section
1505 >For example if your unix host is bambi and your login
1506 name is fred you would type:</P
1514 >smbclient //bambi/fred
1525 >1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
1526 Win2k, OS/2, etc... client</A
1529 >Try mounting disks. eg:</P
1533 >C:\WINDOWS\> </TT
1537 >net use d: \\servername\service
1542 >Try printing. eg:</P
1546 >C:\WINDOWS\> </TT
1551 \\servername\spoolservice</B
1557 >C:\WINDOWS\> </TT
1566 >Celebrate, or send me a bug report!</P
1574 >1.10. What If Things Don't Work?</A
1577 >If nothing works and you start to think "who wrote
1578 this pile of trash" then I suggest you do step 2 again (and
1579 again) till you calm down.</P
1581 >Then you might read the file DIAGNOSIS.txt and the
1582 FAQ. If you are still stuck then try the mailing list or
1583 newsgroup (look in the README for details). Samba has been
1584 successfully installed at thousands of sites worldwide, so maybe
1585 someone else has hit your problem and has overcome it. You could
1586 also use the WWW site to scan back issues of the samba-digest.</P
1588 >When you fix the problem PLEASE send me some updates to the
1589 documentation (or source code) so that the next person will find it
1597 >1.10.1. Diagnosing Problems</A
1600 >If you have installation problems then go to
1604 > to try to find the
1613 >1.10.2. Scope IDs</A
1616 >By default Samba uses a blank scope ID. This means
1617 all your windows boxes must also have a blank scope ID.
1618 If you really want to use a non-blank scope ID then you will
1619 need to use the -i <scope> option to nmbd, smbd, and
1620 smbclient. All your PCs will need to have the same setting for
1621 this to work. I do not recommend scope IDs.</P
1629 >1.10.3. Choosing the Protocol Level</A
1632 >The SMB protocol has many dialects. Currently
1633 Samba supports 5, called CORE, COREPLUS, LANMAN1,
1636 >You can choose what maximum protocol to support
1640 > file. The default is
1641 NT1 and that is the best for the vast majority of sites.</P
1643 >In older versions of Samba you may have found it
1644 necessary to use COREPLUS. The limitations that led to
1645 this have mostly been fixed. It is now less likely that you
1646 will want to use less than LANMAN1. The only remaining advantage
1647 of COREPLUS is that for some obscure reason WfWg preserves
1648 the case of passwords in this protocol, whereas under LANMAN1,
1649 LANMAN2 or NT1 it uppercases all passwords before sending them,
1650 forcing you to use the "password level=" option in some cases.</P
1652 >The main advantage of LANMAN2 and NT1 is support for
1653 long filenames with some clients (eg: smbclient, Windows NT
1656 >See the smb.conf(5) manual page for more details.</P
1658 >Note: To support print queue reporting you may find
1659 that you have to use TCP/IP as the default protocol under
1660 WfWg. For some reason if you leave Netbeui as the default
1661 it may break the print queue reporting on some systems.
1662 It is presumably a WfWg bug.</P
1670 >1.10.4. Printing from UNIX to a Client PC</A
1673 >To use a printer that is available via a smb-based
1674 server from a unix host you will need to compile the
1675 smbclient program. You then need to install the script
1676 "smbprint". Read the instruction in smbprint for more details.
1679 >There is also a SYSV style script that does much
1680 the same thing called smbprint.sysv. It contains instructions.</P
1691 >One area which sometimes causes trouble is locking.</P
1693 >There are two types of locking which need to be
1694 performed by a SMB server. The first is "record locking"
1695 which allows a client to lock a range of bytes in a open file.
1696 The second is the "deny modes" that are specified when a file
1699 >Record locking semantics under Unix is very
1700 different from record locking under Windows. Versions
1701 of Samba before 2.2 have tried to use the native
1702 fcntl() unix system call to implement proper record
1703 locking between different Samba clients. This can not
1704 be fully correct due to several reasons. The simplest
1705 is the fact that a Windows client is allowed to lock a
1706 byte range up to 2^32 or 2^64, depending on the client
1707 OS. The unix locking only supports byte ranges up to
1708 2^31. So it is not possible to correctly satisfy a
1709 lock request above 2^31. There are many more
1710 differences, too many to be listed here.</P
1712 >Samba 2.2 and above implements record locking
1713 completely independent of the underlying unix
1714 system. If a byte range lock that the client requests
1715 happens to fall into the range 0-2^31, Samba hands
1716 this request down to the Unix system. All other locks
1717 can not be seen by unix anyway.</P
1719 >Strictly a SMB server should check for locks before
1720 every read and write call on a file. Unfortunately with the
1721 way fcntl() works this can be slow and may overstress the
1722 rpc.lockd. It is also almost always unnecessary as clients
1723 are supposed to independently make locking calls before reads
1724 and writes anyway if locking is important to them. By default
1725 Samba only makes locking calls when explicitly asked
1726 to by a client, but if you set "strict locking = yes" then it will
1727 make lock checking calls on every read and write. </P
1729 >You can also disable by range locking completely
1730 using "locking = no". This is useful for those shares that
1731 don't support locking or don't need it (such as cdroms). In
1732 this case Samba fakes the return codes of locking calls to
1733 tell clients that everything is OK.</P
1735 >The second class of locking is the "deny modes". These
1736 are set by an application when it opens a file to determine
1737 what types of access should be allowed simultaneously with
1738 its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE
1739 or DENY_ALL. There are also special compatibility modes called
1740 DENY_FCB and DENY_DOS.</P
1742 >You can disable share modes using "share modes = no".
1743 This may be useful on a heavily loaded server as the share
1744 modes code is very slow. See also the FAST_SHARE_MODES
1745 option in the Makefile for a way to do full share modes
1746 very fast using shared memory (if your OS supports it).</P
1754 >1.10.6. Mapping Usernames</A
1757 >If you have different usernames on the PCs and
1758 the unix server then take a look at the "username map" option.
1759 See the smb.conf man page for details.</P
1767 >1.10.7. Other Character Sets</A
1770 >If you have problems using filenames with accented
1771 characters in them (like the German, French or Scandinavian
1772 character sets) then I recommend you look at the "valid chars"
1773 option in smb.conf and also take a look at the validchars
1774 package in the examples directory.</P
1782 NAME="INTEGRATE-MS-NETWORKS"
1783 >Chapter 2. Integrating MS Windows networks with Samba</A
1794 >To identify the key functional mechanisms of MS Windows networking
1795 to enable the deployment of Samba as a means of extending and/or
1796 replacing MS Windows NT/2000 technology.</P
1798 >We will examine:</P
1805 >Name resolution in a pure Unix/Linux TCP/IP
1811 >Name resolution as used within MS Windows
1817 >How browsing functions and how to deploy stable
1818 and dependable browsing using Samba
1823 >MS Windows security options and how to
1824 configure Samba for seemless integration
1829 >Configuration of Samba as:</P
1836 >A stand-alone server</P
1840 >An MS Windows NT 3.x/4.0 security domain member
1845 >An alternative to an MS Windows NT 3.x/4.0 Domain Controller
1858 >2.2. Name Resolution in a pure Unix/Linux world</A
1861 >The key configuration files covered in this section are:</P
1876 >/etc/resolv.conf</TT
1890 >/etc/nsswitch.conf</TT
1906 >Contains a static list of IP Addresses and names.
1916 CLASS="PROGRAMLISTING"
1917 > 127.0.0.1 localhost localhost.localdomain
1918 192.168.1.1 bigbox.caldera.com bigbox alias4box</PRE
1928 name resolution mechanism so that uses do not need to remember
1931 >Network packets that are sent over the physical network transport
1932 layer communicate not via IP addresses but rather using the Media
1933 Access Control address, or MAC address. IP Addresses are currently
1934 32 bits in length and are typically presented as four (4) decimal
1935 numbers that are separated by a dot (or period). eg: 168.192.1.1</P
1937 >MAC Addresses use 48 bits (or 6 bytes) and are typically represented
1938 as two digit hexadecimal numbers separated by colons. eg:
1939 40:8e:0a:12:34:56</P
1941 >Every network interfrace must have an MAC address. Associated with
1942 a MAC address there may be one or more IP addresses. There is NO
1943 relationship between an IP address and a MAC address, all such assignments
1944 are arbitary or discretionary in nature. At the most basic level all
1945 network communications takes place using MAC addressing. Since MAC
1946 addresses must be globally unique, and generally remains fixed for
1947 any particular interface, the assignment of an IP address makes sense
1948 from a network management perspective. More than one IP address can
1949 be assigned per MAC address. One address must be the primary IP address,
1950 this is the address that will be returned in the ARP reply.</P
1952 >When a user or a process wants to communicate with another machine
1953 the protocol implementation ensures that the "machine name" or "host
1954 name" is resolved to an IP address in a manner that is controlled
1955 by the TCP/IP configuration control files. The file
1959 > is one such file.</P
1961 >When the IP address of the destination interface has been
1962 determined a protocol called ARP/RARP isused to identify
1963 the MAC address of the target interface. ARP stands for Address
1964 Resolution Protocol, and is a broadcast oriented method that
1965 uses UDP (User Datagram Protocol) to send a request to all
1966 interfaces on the local network segment using the all 1's MAC
1967 address. Network interfaces are programmed to respond to two
1968 MAC addresses only; their own unique address and the address
1969 ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will
1970 contain the MAC address and the primary IP address for each
1976 > file is foundational to all
1977 Unix/Linux TCP/IP installations and as a minumum will contain
1978 the localhost and local network interface IP addresses and the
1979 primary names by which they are known within the local machine.
1980 This file helps to prime the pump so that a basic level of name
1981 resolution can exist before any other method of name resolution
1982 becomes available.</P
1992 >/etc/resolv.conf</TT
1996 >This file tells the name resolution libraries:</P
2002 >The name of the domain to which the machine
2008 >The name(s) of any domains that should be
2009 automatically searched when trying to resolve unqualified
2010 host names to their IP address
2015 >The name or IP address of available Domain
2016 Name Servers that may be asked to perform name to address
2037 > is the primary means by
2038 which the setting in /etc/resolv.conf may be affected. It is a
2039 critical configuration file. This file controls the order by
2040 which name resolution may procede. The typical structure is:</P
2049 CLASS="PROGRAMLISTING"
2057 >then both addresses should be returned. Please refer to the
2058 man page for host.conf for further details.</P
2068 >/etc/nsswitch.conf</TT
2072 >This file controls the actual name resolution targets. The
2073 file typically has resolver object specifications as follows:</P
2082 CLASS="PROGRAMLISTING"
2083 > # /etc/nsswitch.conf
2085 # Name Service Switch configuration file.
2089 # Alternative entries for password authentication are:
2090 # passwd: compat files nis ldap winbind
2094 hosts: files nis dns
2095 # Alternative entries for host name resolution are:
2096 # hosts: files dns nis nis+ hesoid db compat ldap wins
2097 networks: nis files dns
2100 protocols: nis files
2102 services: nis files</PRE
2108 >Of course, each of these mechanisms requires that the appropriate
2109 facilities and/or services are correctly configured.</P
2111 >It should be noted that unless a network request/message must be
2112 sent, TCP/IP networks are silent. All TCP/IP communications assumes a
2113 principal of speaking only when necessary.</P
2115 >Samba version 2.2.0 will add Linux support for extensions to
2116 the name service switch infrastructure so that linux clients will
2117 be able to obtain resolution of MS Windows NetBIOS names to IP
2118 Addresses. To gain this functionality Samba needs to be compiled
2119 with appropriate arguments to the make command (ie: <B
2122 nsswitch/libnss_wins.so</B
2123 >). The resulting library should
2124 then be installed in the <TT
2128 the "wins" parameter needs to be added to the "hosts:" line in
2131 >/etc/nsswitch.conf</TT
2132 > file. At this point it
2133 will be possible to ping any MS Windows machine by it's NetBIOS
2134 machine name, so long as that machine is within the workgroup to
2135 which both the samba machine and the MS Windows machine belong.</P
2144 >2.3. Name resolution as used within MS Windows networking</A
2147 >MS Windows networking is predicated about the name each machine
2148 is given. This name is known variously (and inconsistently) as
2149 the "computer name", "machine name", "networking name", "netbios name",
2150 "SMB name". All terms mean the same thing with the exception of
2151 "netbios name" which can apply also to the name of the workgroup or the
2152 domain name. The terms "workgroup" and "domain" are really just a
2153 simply name with which the machine is associated. All NetBIOS names
2154 are exactly 16 characters in length. The 16th character is reserved.
2155 It is used to store a one byte value that indicates service level
2156 information for the NetBIOS name that is registered. A NetBIOS machine
2157 name is therefore registered for each service type that is provided by
2158 the client/server.</P
2160 >The following are typical NetBIOS name/service type registrations:</P
2169 CLASS="PROGRAMLISTING"
2170 > Unique NetBIOS Names:
2171 MACHINENAME<00> = Server Service is running on MACHINENAME
2172 MACHINENAME<03> = Generic Machine Name (NetBIOS name)
2173 MACHINENAME<20> = LanMan Server service is running on MACHINENAME
2174 WORKGROUP<1b> = Domain Master Browser
2177 WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
2178 WORKGROUP<1c> = Domain Controllers / Netlogon Servers
2179 WORKGROUP<1d> = Local Master Browsers
2180 WORKGROUP<1e> = Internet Name Resolvers</PRE
2186 >It should be noted that all NetBIOS machines register their own
2187 names as per the above. This is in vast contrast to TCP/IP
2188 installations where traditionally the system administrator will
2189 determine in the /etc/hosts or in the DNS database what names
2190 are associated with each IP address.</P
2192 >One further point of clarification should be noted, the <TT
2196 file and the DNS records do not provide the NetBIOS name type information
2197 that MS Windows clients depend on to locate the type of service that may
2198 be needed. An example of this is what happens when an MS Windows client
2199 wants to locate a domain logon server. It find this service and the IP
2200 address of a server that provides it by performing a lookup (via a
2201 NetBIOS broadcast) for enumeration of all machines that have
2202 registered the name type *<1c>. A logon request is then sent to each
2203 IP address that is returned in the enumerated list of IP addresses. Which
2204 ever machine first replies then ends up providing the logon services.</P
2206 >The name "workgroup" or "domain" really can be confusing since these
2207 have the added significance of indicating what is the security
2208 architecture of the MS Windows network. The term "workgroup" indicates
2209 that the primary nature of the network environment is that of a
2210 peer-to-peer design. In a WORKGROUP all machines are responsible for
2211 their own security, and generally such security is limited to use of
2212 just a password (known as SHARE MORE security). In most situations
2213 with peer-to-peer networking the users who control their own machines
2214 will simply opt to have no security at all. It is possible to have
2215 USER MODE security in a WORKGROUP environment, thus requiring use
2216 of a user name and a matching password.</P
2218 >MS Windows networking is thus predetermined to use machine names
2219 for all local and remote machine message passing. The protocol used is
2220 called Server Message Block (SMB) and this is implemented using
2221 the NetBIOS protocol (Network Basic Input Output System). NetBIOS can
2222 be encapsulated using LLC (Logical Link Control) protocol - in which case
2223 the resulting protocol is called NetBEUI (Network Basic Extended User
2224 Interface). NetBIOS can also be run over IPX (Internetworking Packet
2225 Exchange) protocol as used by Novell NetWare, and it can be run
2226 over TCP/IP protocols - in which case the resulting protocol is called
2227 NBT or NetBT, the NetBIOS over TCP/IP.</P
2229 >MS Windows machines use a complex array of name resolution mechanisms.
2230 Since we are primarily concerned with TCP/IP this demonstration is
2231 limited to this area.</P
2238 >2.3.1. The NetBIOS Name Cache</A
2241 >All MS Windows machines employ an in memory buffer in which is
2242 stored the NetBIOS names and their IP addresses for all external
2243 machines that that the local machine has communicated with over the
2244 past 10-15 minutes. It is more efficient to obtain an IP address
2245 for a machine from the local cache than it is to go through all the
2246 configured name resolution mechanisms.</P
2248 >If a machine whose name is in the local name cache has been shut
2249 down before the name had been expired and flushed from the cache, then
2250 an attempt to exchange a message with that machine will be subject
2251 to time-out delays. ie: It's name is in the cache, so a name resolution
2252 lookup will succeed, but the machine can not respond. This can be
2253 frustrating for users - but it is a characteristic of the protocol.</P
2255 >The MS Windows utility that allows examination of the NetBIOS
2256 name cache is called "nbtstat". The Samba equivalent of this
2257 is called "nmblookup".</P
2265 >2.3.2. The LMHOSTS file</A
2268 >This file is usually located in MS Windows NT 4.0 or
2271 >C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
2273 the IP Address and the machine name in matched pairs. The
2277 > file performs NetBIOS name
2278 to IP address mapping oriented.</P
2280 >It typically looks like:</P
2289 CLASS="PROGRAMLISTING"
2290 > # Copyright (c) 1998 Microsoft Corp.
2292 # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
2293 # over TCP/IP) stack for Windows98
2295 # This file contains the mappings of IP addresses to NT computernames
2296 # (NetBIOS) names. Each entry should be kept on an individual line.
2297 # The IP address should be placed in the first column followed by the
2298 # corresponding computername. The address and the comptername
2299 # should be separated by at least one space or tab. The "#" character
2300 # is generally used to denote the start of a comment (see the exceptions
2303 # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
2304 # files and offers the following extensions:
2307 # #DOM:<domain>
2308 # #INCLUDE <filename>
2311 # \0xnn (non-printing character support)
2313 # Following any entry in the file with the characters "#PRE" will cause
2314 # the entry to be preloaded into the name cache. By default, entries are
2315 # not preloaded, but are parsed only after dynamic name resolution fails.
2317 # Following an entry with the "#DOM:<domain>" tag will associate the
2318 # entry with the domain specified by <domain>. This affects how the
2319 # browser and logon services behave in TCP/IP environments. To preload
2320 # the host name associated with #DOM entry, it is necessary to also add a
2321 # #PRE to the line. The <domain> is always preloaded although it will not
2322 # be shown when the name cache is viewed.
2324 # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
2325 # software to seek the specified <filename> and parse it as if it were
2326 # local. <filename> is generally a UNC-based name, allowing a
2327 # centralized lmhosts file to be maintained on a server.
2328 # It is ALWAYS necessary to provide a mapping for the IP address of the
2329 # server prior to the #INCLUDE. This mapping must use the #PRE directive.
2330 # In addtion the share "public" in the example below must be in the
2331 # LanManServer list of "NullSessionShares" in order for client machines to
2332 # be able to read the lmhosts file successfully. This key is under
2333 # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
2334 # in the registry. Simply add "public" to the list found there.
2336 # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
2337 # statements to be grouped together. Any single successful include
2338 # will cause the group to succeed.
2340 # Finally, non-printing characters can be embedded in mappings by
2341 # first surrounding the NetBIOS name in quotations, then using the
2342 # \0xnn notation to specify a hex value for a non-printing character.
2344 # The following example illustrates all of these extensions:
2346 # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
2347 # 102.54.94.102 "appname \0x14" #special app server
2348 # 102.54.94.123 popular #PRE #source server
2349 # 102.54.94.117 localsrv #PRE #needed for the include
2352 # #INCLUDE \\localsrv\public\lmhosts
2353 # #INCLUDE \\rhino\public\lmhosts
2356 # In the above example, the "appname" server contains a special
2357 # character in its name, the "popular" and "localsrv" server names are
2358 # preloaded, and the "rhino" server name is specified so it can be used
2359 # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
2360 # system is unavailable.
2362 # Note that the whole file is parsed including comments on each lookup,
2363 # so keeping the number of comments to a minimum will improve performance.
2364 # Therefore it is not advisable to simply add lmhosts file entries onto the
2365 # end of this file.</PRE
2377 >2.3.3. HOSTS file</A
2380 >This file is usually located in MS Windows NT 4.0 or 2000 in
2383 >C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
2385 the IP Address and the IP hostname in matched pairs. It can be
2386 used by the name resolution infrastructure in MS Windows, depending
2387 on how the TCP/IP environment is configured. This file is in
2388 every way the equivalent of the Unix/Linux <TT
2399 >2.3.4. DNS Lookup</A
2402 >This capability is configured in the TCP/IP setup area in the network
2403 configuration facility. If enabled an elaborate name resolution sequence
2404 is followed the precise nature of which isdependant on what the NetBIOS
2405 Node Type parameter is configured to. A Node Type of 0 means use
2406 NetBIOS broadcast (over UDP broadcast) is first used if the name
2407 that is the subject of a name lookup is not found in the NetBIOS name
2408 cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to
2409 Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
2410 WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
2419 >2.3.5. WINS Lookup</A
2422 >A WINS (Windows Internet Name Server) service is the equivaent of the
2423 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
2424 the names and IP addresses that are registered by a Windows client
2425 if the TCP/IP setup has been given at least one WINS Server IP Address.</P
2427 >To configure Samba to be a WINS server the following parameter needs
2428 to be added to the <TT
2440 CLASS="PROGRAMLISTING"
2441 > wins support = Yes</PRE
2447 >To configure Samba to use a WINS server the following parameters are
2448 needed in the smb.conf file:</P
2457 CLASS="PROGRAMLISTING"
2459 wins server = xxx.xxx.xxx.xxx</PRE
2471 of the WINS server.</P
2480 >2.4. How browsing functions and how to deploy stable and
2481 dependable browsing using Samba</A
2484 >As stated above, MS Windows machines register their NetBIOS names
2485 (ie: the machine name for each service type in operation) on start
2486 up. Also, as stated above, the exact method by which this name registration
2487 takes place is determined by whether or not the MS Windows client/server
2488 has been given a WINS server address, whether or not LMHOSTS lookup
2489 is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P
2491 >In the case where there is no WINS server all name registrations as
2492 well as name lookups are done by UDP broadcast. This isolates name
2493 resolution to the local subnet, unless LMHOSTS is used to list all
2494 names and IP addresses. In such situations Samba provides a means by
2495 which the samba server name may be forcibly injected into the browse
2496 list of a remote MS Windows network (using the "remote announce" parameter).</P
2498 >Where a WINS server is used, the MS Windows client will use UDP
2499 unicast to register with the WINS server. Such packets can be routed
2500 and thus WINS allows name resolution to function across routed networks.</P
2502 >During the startup process an election will take place to create a
2503 local master browser if one does not already exist. On each NetBIOS network
2504 one machine will be elected to function as the domain master browser. This
2505 domain browsing has nothing to do with MS security domain control.
2506 Instead, the domain master browser serves the role of contacting each local
2507 master browser (found by asking WINS or from LMHOSTS) and exchanging browse
2508 list contents. This way every master browser will eventually obtain a complete
2509 list of all machines that are on the network. Every 11-15 minutes an election
2510 is held to determine which machine will be the master browser. By nature of
2511 the election criteria used, the machine with the highest uptime, or the
2512 most senior protocol version, or other criteria, will win the election
2513 as domain master browser.</P
2515 >Clients wishing to browse the network make use of this list, but also depend
2516 on the availability of correct name resolution to the respective IP
2517 address/addresses. </P
2519 >Any configuration that breaks name resolution and/or browsing intrinsics
2520 will annoy users because they will have to put up with protracted
2521 inability to use the network services.</P
2523 >Samba supports a feature that allows forced synchonisation
2524 of browse lists across routed networks using the "remote
2525 browse sync" parameter in the smb.conf file. This causes Samba
2526 to contact the local master browser on a remote network and
2527 to request browse list synchronisation. This effectively bridges
2528 two networks that are separated by routers. The two remote
2529 networks may use either broadcast based name resolution or WINS
2530 based name resolution, but it should be noted that the "remote
2531 browse sync" parameter provides browse list synchronisation - and
2532 that is distinct from name to address resolution, in other
2533 words, for cross subnet browsing to function correctly it is
2534 essential that a name to address resolution mechanism be provided.
2535 This mechanism could be via DNS, <TT
2547 >2.5. MS Windows security options and how to configure
2548 Samba for seemless integration</A
2551 >MS Windows clients may use encrypted passwords as part of a
2552 challenege/response authentication model (a.k.a. NTLMv1) or
2553 alone, or clear text strings for simple password based
2554 authentication. It should be realized that with the SMB
2555 protocol the password is passed over the network either
2556 in plain text or encrypted, but not both in the same
2557 authentication requets.</P
2559 >When encrypted passwords are used a password that has been
2560 entered by the user is encrypted in two ways:</P
2566 >An MD4 hash of the UNICODE of the password
2567 string. This is known as the NT hash.
2572 >The password is converted to upper case,
2573 and then padded or trucated to 14 bytes. This string is
2574 then appended with 5 bytes of NULL characters and split to
2575 form two 56 bit DES keys to encrypt a "magic" 8 byte value.
2576 The resulting 16 bytes for the LanMan hash.
2581 >You should refer to the <A
2582 HREF="ENCRYPTION.html"
2584 >Password Encryption</A
2585 > chapter in this HOWTO collection
2586 for more details on the inner workings</P
2588 >MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x
2589 and version 4.0 pre-service pack 3 will use either mode of
2590 password authentication. All versions of MS Windows that follow
2591 these versions no longer support plain text passwords by default.</P
2593 >MS Windows clients have a habit of dropping network mappings that
2594 have been idle for 10 minutes or longer. When the user attempts to
2595 use the mapped drive connection that has been dropped the SMB protocol
2596 has a mechanism by which the connection can be re-established using
2597 a cached copy of the password.</P
2599 >When Microsoft changed the default password mode, they dropped support for
2600 caching of the plain text password. This means that when the registry
2601 parameter is changed to re-enable use of plain text passwords it appears to
2602 work, but when a dropped mapping attempts to revalidate it will fail if
2603 the remote authentication server does not support encrypted passwords.
2604 This means that it is definitely not a good idea to re-enable plain text
2605 password support in such clients.</P
2607 >The following parameters can be used to work around the
2608 issue of Windows 9x client upper casing usernames and
2609 password before transmitting them to the SMB server
2610 when using clear text authentication.</P
2619 CLASS="PROGRAMLISTING"
2621 HREF="smb.conf.5.html#PASSWORDLEVEL"
2631 HREF="smb.conf.5.html#USERNAMELEVEL"
2645 >By default Samba will lower case the username before attempting
2646 to lookup the user in the database of local system accounts.
2647 Because UNIX usernames conventionally only contain lower case
2654 is rarely even needed.</P
2656 >However, password on UNIX systems often make use of mixed case
2657 characters. This means that in order for a user on a Windows 9x
2658 client to connect to a Samba server using clear text authentication,
2664 > must be set to the maximum
2665 number of upper case letter which <EM
2668 is a password. Note that is the server OS uses the traditional
2669 DES version of crypt(), then a <TT
2675 of 8 will result in case insensitive passwords as seen from Windows
2676 users. This will also result in longer login times as Samba
2677 hash to compute the permutations of the password string and
2678 try them one by one until a match is located (or all combinations fail).</P
2680 >The best option to adopt is to enable support for encrypted passwords
2681 where ever Samba is used. There are three configuration possibilities
2682 for support of encrypted passwords:</P
2689 >2.5.1. Use MS Windows NT as an authentication server</A
2692 >This method involves the additions of the following parameters
2693 in the smb.conf file:</P
2702 CLASS="PROGRAMLISTING"
2703 > encrypt passwords = Yes
2705 password server = "NetBIOS_name_of_PDC"</PRE
2711 >There are two ways of identifying whether or not a username and
2712 password pair was valid or not. One uses the reply information provided
2713 as part of the authentication messaging process, the other uses
2714 just and error code.</P
2716 >The down-side of this mode of configuration is the fact that
2717 for security reasons Samba will send the password server a bogus
2718 username and a bogus password and if the remote server fails to
2719 reject the username and password pair then an alternative mode
2720 of identification of validation is used. Where a site uses password
2721 lock out after a certain number of failed authentication attempts
2722 this will result in user lockouts.</P
2724 >Use of this mode of authentication does require there to be
2725 a standard Unix account for the user, this account can be blocked
2726 to prevent logons by other than MS Windows clients.</P
2734 >2.5.2. Make Samba a member of an MS Windows NT security domain</A
2737 >This method involves additon of the following paramters in the smb.conf file:</P
2746 CLASS="PROGRAMLISTING"
2747 > encrypt passwords = Yes
2749 workgroup = "name of NT domain"
2750 password server = *</PRE
2756 >The use of the "*" argument to "password server" will cause samba
2757 to locate the domain controller in a way analogous to the way
2758 this is done within MS Windows NT.</P
2760 >In order for this method to work the Samba server needs to join the
2761 MS Windows NT security domain. This is done as follows:</P
2767 >On the MS Windows NT domain controller using
2768 the Server Manager add a machine account for the Samba server.
2773 >Next, on the Linux system execute:
2776 >smbpasswd -r PDC_NAME -j DOMAIN_NAME</B
2782 >Use of this mode of authentication does require there to be
2783 a standard Unix account for the user in order to assign
2784 a uid once the account has been authenticated by the remote
2785 Windows DC. This account can be blocked to prevent logons by
2786 other than MS Windows clients by things such as setting an invalid
2792 >An alternative to assigning UIDs to Windows users on a
2793 Samba member server is presented in the <A
2796 >Winbind Overview</A
2798 this HOWTO collection.</P
2806 >2.5.3. Configure Samba as an authentication server</A
2809 >This mode of authentication demands that there be on the
2810 Unix/Linux system both a Unix style account as well as and
2811 smbpasswd entry for the user. The Unix system account can be
2812 locked if required as only the encrypted password will be
2813 used for SMB client authentication.</P
2815 >This method involves addition of the following parameters to
2816 the smb.conf file:</P
2825 CLASS="PROGRAMLISTING"
2826 >## please refer to the Samba PDC HOWTO chapter later in
2827 ## this collection for more details
2829 encrypt passwords = Yes
2832 ; an OS level of 33 or more is recommended
2836 path = /somewhare/in/file/system
2837 read only = yes</PRE
2843 >in order for this method to work a Unix system account needs
2844 to be created for each user, as well as for each MS Windows NT/2000
2845 machine. The following structure is required.</P
2855 >A user account that may provide a home directory should be
2856 created. The following Linux system commands are typical of
2857 the procedure for creating an account.</P
2866 CLASS="PROGRAMLISTING"
2867 > # useradd -s /bin/bash -d /home/"userid" -m "userid"
2869 Enter Password: <pw>
2871 # smbpasswd -a "userid"
2872 Enter Password: <pw></PRE
2884 >2.5.3.2. MS Windows NT Machine Accounts</A
2887 >These are required only when Samba is used as a domain
2888 controller. Refer to the Samba-PDC-HOWTO for more details.</P
2897 CLASS="PROGRAMLISTING"
2898 > # useradd -s /bin/false -d /dev/null "machine_name"\$
2899 # passwd -l "machine_name"\$
2900 # smbpasswd -a -m "machine_name"</PRE
2914 >2.6. Conclusions</A
2917 >Samba provides a flexible means to operate as...</P
2923 >A Stand-alone server - No special action is needed
2924 other than to create user accounts. Stand-alone servers do NOT
2925 provide network logon services, meaning that machines that use this
2926 server do NOT perform a domain logon but instead make use only of
2927 the MS Windows logon which is local to the MS Windows
2933 >An MS Windows NT 3.x/4.0 security domain member.
2938 >An alternative to an MS Windows NT 3.x/4.0
2950 >Chapter 3. Configuring PAM for distributed but centrally
2951 managed authentication</A
2959 >3.1. Samba and PAM</A
2962 >A number of Unix systems (eg: Sun Solaris), as well as the
2963 xxxxBSD family and Linux, now utilize the Pluggable Authentication
2964 Modules (PAM) facility to provide all authentication,
2965 authorization and resource control services. Prior to the
2966 introduction of PAM, a decision to use an alternative to
2967 the system password database (<TT
2971 would require the provision of alternatives for all programs that provide
2972 security services. Such a choice would involve provision of
2973 alternatives to such programs as: <B
2985 >PAM provides a mechanism that disconnects these security programs
2986 from the underlying authentication/authorization infrastructure.
2987 PAM is configured either through one file <TT
2991 or by editing individual files that are located in <TT
2996 >The following is an example <TT
2998 >/etc/pam.d/login</TT
2999 > configuration file.
3000 This example had all options been uncommented is probably not usable
3001 as it stacks many conditions before allowing successful completion
3002 of the login process. Essentially all conditions can be disabled
3003 by commenting them out except the calls to <TT
3015 CLASS="PROGRAMLISTING"
3017 # The PAM configuration file for the `login' service
3019 auth required pam_securetty.so
3020 auth required pam_nologin.so
3021 # auth required pam_dialup.so
3022 # auth optional pam_mail.so
3023 auth required pam_pwdb.so shadow md5
3024 # account requisite pam_time.so
3025 account required pam_pwdb.so
3026 session required pam_pwdb.so
3027 # session optional pam_lastlog.so
3028 # password required pam_cracklib.so retry=3
3029 password required pam_pwdb.so shadow md5</PRE
3035 >PAM allows use of replacable modules. Those available on a
3036 sample system include:</P
3045 CLASS="PROGRAMLISTING"
3046 >$ /bin/ls /lib/security
3047 pam_access.so pam_ftp.so pam_limits.so
3048 pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
3049 pam_cracklib.so pam_group.so pam_listfile.so
3050 pam_nologin.so pam_rootok.so pam_tally.so
3051 pam_deny.so pam_issue.so pam_mail.so
3052 pam_permit.so pam_securetty.so pam_time.so
3053 pam_dialup.so pam_lastlog.so pam_mkhomedir.so
3054 pam_pwdb.so pam_shells.so pam_unix.so
3055 pam_env.so pam_ldap.so pam_motd.so
3056 pam_radius.so pam_smbpass.so pam_unix_acct.so
3057 pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
3058 pam_userdb.so pam_warn.so pam_unix_session.so</PRE
3064 >The following example for the login program replaces the use of
3068 > module which uses the system
3069 password database (<TT
3083 > which uses the Samba
3084 database which contains the Microsoft MD4 encrypted password
3085 hashes. This database is stored in either
3088 >/usr/local/samba/private/smbpasswd</TT
3092 >/etc/samba/smbpasswd</TT
3096 >/etc/samba.d/smbpasswd</TT
3098 Samba implementation for your Unix/Linux system. The
3102 > module is provided by
3103 Samba version 2.2.1 or later. It can be compiled by specifying the
3106 >--with-pam_smbpass</B
3107 > options when running Samba's
3111 > script. For more information
3115 > module, see the documentation
3118 >source/pam_smbpass</TT
3119 > directory of the Samba
3120 source distribution.</P
3129 CLASS="PROGRAMLISTING"
3131 # The PAM configuration file for the `login' service
3133 auth required pam_smbpass.so nodelay
3134 account required pam_smbpass.so nodelay
3135 session required pam_smbpass.so nodelay
3136 password required pam_smbpass.so nodelay</PRE
3142 >The following is the PAM configuration file for a particular
3143 Linux system. The default condition uses <TT
3155 CLASS="PROGRAMLISTING"
3157 # The PAM configuration file for the `samba' service
3159 auth required /lib/security/pam_pwdb.so nullok nodelay shadow audit
3160 account required /lib/security/pam_pwdb.so audit nodelay
3161 session required /lib/security/pam_pwdb.so nodelay
3162 password required /lib/security/pam_pwdb.so shadow md5</PRE
3168 >In the following example the decision has been made to use the
3169 smbpasswd database even for basic samba authentication. Such a
3170 decision could also be made for the passwd program and would
3171 thus allow the smbpasswd passwords to be changed using the passwd
3181 CLASS="PROGRAMLISTING"
3183 # The PAM configuration file for the `samba' service
3185 auth required /lib/security/pam_smbpass.so nodelay
3186 account required /lib/security/pam_pwdb.so audit nodelay
3187 session required /lib/security/pam_pwdb.so nodelay
3188 password required /lib/security/pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE
3194 >Note: PAM allows stacking of authentication mechanisms. It is
3195 also possible to pass information obtained within on PAM module through
3196 to the next module in the PAM stack. Please refer to the documentation for
3197 your particular system implementation for details regarding the specific
3198 capabilities of PAM in this environment. Some Linux implmentations also
3202 > module that allows all
3203 authentication to be configured in a single central file. The
3207 > method has some very devoted followers
3208 on the basis that it allows for easier administration. As with all issues in
3209 life though, every decision makes trade-offs, so you may want examine the
3210 PAM documentation for further helpful information.</P
3218 >3.2. Distributed Authentication</A
3221 >The astute administrator will realize from this that the
3234 HREF="http://rsync.samba.org/"
3236 >http://rsync.samba.org/</A
3238 will allow the establishment of a centrally managed, distributed
3239 user/password database that can also be used by all
3240 PAM (eg: Linux) aware programs and applications. This arrangement
3241 can have particularly potent advantages compared with the
3242 use of Microsoft Active Directory Service (ADS) in so far as
3243 reduction of wide area network authentication traffic.</P
3251 >3.3. PAM Configuration in smb.conf</A
3254 >There is an option in smb.conf called <A
3255 HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
3257 >obey pam restrictions</A
3259 The following is from the on-line help for this option in SWAT;</P
3261 >When Samba 2.2 is configure to enable PAM support (i.e.
3265 >), this parameter will
3266 control whether or not Samba should obey PAM's account
3267 and session management directives. The default behavior
3268 is to use PAM for clear text authentication only and to
3269 ignore any account or session management. Note that Samba always
3270 ignores PAM for authentication in the case of
3272 HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
3274 >encrypt passwords = yes</A
3276 The reason is that PAM modules cannot support the challenge/response
3277 authentication mechanism needed in the presence of SMB
3278 password encryption. </P
3282 >obey pam restrictions = no</B
3291 >Chapter 4. Hosting a Microsoft Distributed File System tree on Samba</A
3299 >4.1. Instructions</A
3302 >The Distributed File System (or Dfs) provides a means of
3303 separating the logical view of files and directories that users
3304 see from the actual physical locations of these resources on the
3305 network. It allows for higher availability, smoother storage expansion,
3306 load balancing etc. For more information about Dfs, refer to <A
3307 HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
3309 > Microsoft documentation</A
3312 >This document explains how to host a Dfs tree on a Unix
3313 machine (for Dfs-aware clients to browse) using Samba.</P
3315 >To enable SMB-based DFS for Samba, configure it with the
3321 > option. Once built, a
3322 Samba server can be made a Dfs server by setting the global
3324 HREF="smb.conf.5.html#HOSTMSDFS"
3332 > parameter in the <TT
3336 > file. You designate a share as a Dfs root using the share
3338 HREF="smb.conf.5.html#MSDFSROOT"
3346 > parameter. A Dfs root directory on
3347 Samba hosts Dfs links in the form of symbolic links that point
3348 to other servers. For example, a symbolic link
3351 >junction->msdfs:storage1\share1</TT
3353 the share directory acts as the Dfs junction. When Dfs-aware
3354 clients attempt to access the junction link, they are redirected
3355 to the storage location (in this case, \\storage1\share1).</P
3357 >Dfs trees on Samba work with all Dfs-aware clients ranging
3358 from Windows 95 to 2000.</P
3360 >Here's an example of setting up a Dfs tree on a Samba
3370 CLASS="PROGRAMLISTING"
3371 ># The smb.conf file:
3373 netbios name = SAMBA
3377 path = /export/dfsroot
3385 >In the /export/dfsroot directory we set up our dfs links to
3386 other servers on the network.</P
3394 >cd /export/dfsroot</B
3404 >chown root /export/dfsroot</B
3414 >chmod 755 /export/dfsroot</B
3424 >ln -s msdfs:storageA\\shareA linka</B
3434 >ln -s msdfs:serverB\\share,serverC\\share linkb</B
3438 >You should set up the permissions and ownership of
3439 the directory acting as the Dfs root such that only designated
3440 users can create, delete or modify the msdfs links. Also note
3441 that symlink names should be all lowercase. This limitation exists
3442 to have Samba avoid trying all the case combinations to get at
3443 the link name. Finally set up the symbolic links to point to the
3444 network shares you want, and start Samba.</P
3446 >Users on Dfs-aware clients can now browse the Dfs tree
3447 on the Samba server at \\samba\dfs. Accessing
3448 links linka or linkb (which appear as directories to the client)
3449 takes users directly to the appropriate shares on the network.</P
3463 >Windows clients need to be rebooted
3464 if a previously mounted non-dfs share is made a dfs
3465 root or vice versa. A better way is to introduce a
3466 new share and make it the dfs root.</P
3470 >Currently there's a restriction that msdfs
3471 symlink names should all be lowercase.</P
3475 >For security purposes, the directory
3476 acting as the root of the Dfs tree should have ownership
3477 and permissions set so that only designated users can
3478 modify the symbolic links in the directory.</P
3488 NAME="UNIX-PERMISSIONS"
3489 >Chapter 5. UNIX Permission Bits and Windows NT Access Control Lists</A
3497 >5.1. Viewing and changing UNIX permissions using the NT
3501 >New in the Samba 2.0.4 release is the ability for Windows
3502 NT clients to use their native security settings dialog box to
3503 view and modify the underlying UNIX permissions.</P
3505 >Note that this ability is careful not to compromise
3506 the security of the UNIX host Samba is running on, and
3507 still obeys all the file permission rules that a Samba
3508 administrator can set.</P
3510 >In Samba 2.0.4 and above the default value of the
3512 HREF="smb.conf.5.html#NTACLSUPPORT"
3520 > has been changed from
3528 manipulation of permissions is turned on by default.</P
3536 >5.2. How to view file security on a Samba share</A
3539 >From an NT 4.0 client, single-click with the right
3540 mouse button on any file or directory in a Samba mounted
3541 drive letter or UNC path. When the menu pops-up, click
3544 > entry at the bottom of
3545 the menu. This brings up the normal file properties dialog
3546 box, but with Samba 2.0.4 this will have a new tab along the top
3549 >. Click on this tab and you
3550 will see three buttons, <EM
3560 > button will cause either
3561 an error message <SPAN
3563 >A requested privilege is not held
3565 > to appear if the user is not the
3566 NT Administrator, or a dialog which is intended to allow an
3567 Administrator to add auditing requirements to a file if the
3568 user is logged on as the NT Administrator. This dialog is
3569 non-functional with a Samba share at this time, as the only
3570 useful button, the <B
3573 > button will not currently
3574 allow a list of users to be seen.</P
3582 >5.3. Viewing file ownership</A
3589 brings up a dialog box telling you who owns the given file. The
3590 owner name will be of the form :</P
3594 >"SERVER\user (Long name)"</B
3602 > is the NetBIOS name of
3603 the Samba server, <TT
3608 > is the user name of
3609 the UNIX user who owns the file, and <TT
3615 is the descriptive string identifying the user (normally found in the
3616 GECOS field of the UNIX password database). Click on the <B
3620 > button to remove this dialog.</P
3622 >If the parameter <TT
3631 > then the file owner will
3632 be shown as the NT user <B
3640 > button will not allow
3641 you to change the ownership of this file to yourself (clicking on
3642 it will display a dialog box complaining that the user you are
3643 currently logged onto the NT client cannot be found). The reason
3644 for this is that changing the ownership of a file is a privileged
3645 operation in UNIX, available only to the <EM
3648 user. As clicking on this button causes NT to attempt to change
3649 the ownership of a file to the current user logged into the NT
3650 client this will not work with Samba at this time.</P
3652 >There is an NT chown command that will work with Samba
3653 and allow a user with Administrator privilege connected
3654 to a Samba 2.0.4 server as root to change the ownership of
3655 files on both a local NTFS filesystem or remote mounted NTFS
3656 or Samba drive. This is available as part of the <EM
3659 > NT security library written by Jeremy Allison of
3660 the Samba Team, available from the main Samba ftp site.</P
3668 >5.4. Viewing file or directory permissions</A
3671 >The third button is the <B
3675 button. Clicking on this brings up a dialog box that shows both
3676 the permissions and the UNIX owner of the file or directory.
3677 The owner is displayed in the form :</P
3681 >"SERVER\user (Long name)"</B
3689 > is the NetBIOS name of
3690 the Samba server, <TT
3695 > is the user name of
3696 the UNIX user who owns the file, and <TT
3702 is the descriptive string identifying the user (normally found in the
3703 GECOS field of the UNIX password database).</P
3705 >If the parameter <TT
3714 > then the file owner will
3715 be shown as the NT user <B
3719 permissions will be shown as NT "Full Control".</P
3721 >The permissions field is displayed differently for files
3722 and directories, so I'll describe the way file permissions
3723 are displayed first.</P
3730 >5.4.1. File Permissions</A
3733 >The standard UNIX user/group/world triple and
3734 the corresponding "read", "write", "execute" permissions
3735 triples are mapped by Samba into a three element NT ACL
3736 with the 'r', 'w', and 'x' bits mapped into the corresponding
3737 NT permissions. The UNIX world permissions are mapped into
3738 the global NT group <B
3742 by the list of permissions allowed for UNIX world. The UNIX
3743 owner and group permissions are displayed as an NT
3751 > icon respectively followed by the list
3752 of permissions allowed for the UNIX user and group.</P
3754 >As many UNIX permission sets don't map into common
3765 usually the permissions will be prefixed by the words <B
3767 > "Special Access"</B
3768 > in the NT display list.</P
3770 >But what happens if the file has no permissions allowed
3771 for a particular UNIX user group or world component ? In order
3772 to allow "no permissions" to be seen and modified then Samba
3775 >"Take Ownership"</B
3777 (which has no meaning in UNIX) and reports a component with
3778 no permissions as having the NT <B
3782 This was chosen of course to make it look like a zero, meaning
3783 zero permissions. More details on the decision behind this will
3792 >5.4.2. Directory Permissions</A
3795 >Directories on an NT NTFS file system have two
3796 different sets of permissions. The first set of permissions
3797 is the ACL set on the directory itself, this is usually displayed
3798 in the first set of parentheses in the normal <B
3802 NT style. This first set of permissions is created by Samba in
3803 exactly the same way as normal file permissions are, described
3804 above, and is displayed in the same way.</P
3806 >The second set of directory permissions has no real meaning
3807 in the UNIX permissions world and represents the <B
3810 > permissions that any file created within
3811 this directory would inherit.</P
3813 >Samba synthesises these inherited permissions for NT by
3814 returning as an NT ACL the UNIX permission mode that a new file
3815 created by Samba on this share would receive.</P
3824 >5.5. Modifying file or directory permissions</A
3827 >Modifying file and directory permissions is as simple
3828 as changing the displayed permissions in the dialog box, and
3832 > button. However, there are
3833 limitations that a user needs to be aware of, and also interactions
3834 with the standard Samba permission masks and mapping of DOS
3835 attributes that need to also be taken into account.</P
3837 >If the parameter <TT
3846 > then any attempt to set
3847 security permissions will fail with an <B
3853 >The first thing to note is that the <B
3857 button will not return a list of users in Samba 2.0.4 (it will give
3858 an error message of <B
3860 >"The remote procedure call failed
3861 and did not execute"</B
3862 >). This means that you can only
3863 manipulate the current user/group/world permissions listed in
3864 the dialog box. This actually works quite well as these are the
3865 only permissions that UNIX actually has.</P
3867 >If a permission triple (either user, group, or world)
3868 is removed from the list of permissions in the NT dialog box,
3872 > button is pressed it will
3873 be applied as "no permissions" on the UNIX side. If you then
3874 view the permissions again the "no permissions" entry will appear
3878 > flag, as described above. This
3879 allows you to add permissions back to a file or directory once
3880 you have removed them from a triple component.</P
3882 >As UNIX supports only the "r", "w" and "x" bits of
3883 an NT ACL then if other NT security attributes such as "Delete
3884 access" are selected then they will be ignored when applied on
3885 the Samba server.</P
3887 >When setting permissions on a directory the second
3888 set of permissions (in the second set of parentheses) is
3889 by default applied to all files within that directory. If this
3890 is not what you want you must uncheck the <B
3893 permissions on existing files"</B
3894 > checkbox in the NT
3895 dialog before clicking <B
3900 >If you wish to remove all permissions from a
3901 user/group/world component then you may either highlight the
3902 component and click the <B
3906 or set the component to only have the special <B
3910 > permission (displayed as <B
3922 >5.6. Interaction with the standard Samba create mask
3926 >Note that with Samba 2.0.5 there are four new parameters
3927 to control this interaction. These are :</P
3939 >force security mode</I
3946 >directory security mask</I
3953 >force directory security mode</I
3957 >Once a user clicks <B
3961 permissions Samba maps the given permissions into a user/group/world
3962 r/w/x triple set, and then will check the changed permissions for a
3963 file against the bits set in the <A
3964 HREF="smb.conf.5.html#SECURITYMASK"
3973 > parameter. Any bits that
3974 were changed that are not set to '1' in this parameter are left alone
3975 in the file permissions.</P
3977 >Essentially, zero bits in the <TT
3983 mask may be treated as a set of bits the user is <EM
3986 allowed to change, and one bits are those the user is allowed to change.
3989 >If not set explicitly this parameter is set to the same value as
3991 HREF="smb.conf.5.html#CREATEMASK"
4000 > parameter to provide compatibility with Samba 2.0.4
4001 where this permission change facility was introduced. To allow a user to
4002 modify all the user/group/world permissions on a file, set this parameter
4005 >Next Samba checks the changed permissions for a file against
4006 the bits set in the <A
4007 HREF="smb.conf.5.html#FORCESECURITYMODE"
4012 >force security mode</I
4015 > parameter. Any bits
4016 that were changed that correspond to bits set to '1' in this parameter
4017 are forced to be set.</P
4019 >Essentially, bits set in the <TT
4022 >force security mode
4025 > parameter may be treated as a set of bits that, when
4026 modifying security on a file, the user has always set to be 'on'.</P
4028 >If not set explicitly this parameter is set to the same value
4030 HREF="smb.conf.5.html#FORCECREATEMODE"
4039 > parameter to provide compatibility
4040 with Samba 2.0.4 where the permission change facility was introduced.
4041 To allow a user to modify all the user/group/world permissions on a file
4042 with no restrictions set this parameter to 000.</P
4055 > parameters are applied to the change
4056 request in that order.</P
4058 >For a directory Samba will perform the same operations as
4059 described above for a file except using the parameter <TT
4062 > directory security mask</I
4073 >force directory security mode
4076 > parameter instead of <TT
4079 >force security mode
4087 >directory security mask</I
4090 by default is set to the same value as the <TT
4096 > parameter and the <TT
4099 >force directory security
4102 > parameter by default is set to the same value as
4106 >force directory mode</I
4108 > parameter to provide
4109 compatibility with Samba 2.0.4 where the permission change facility
4112 >In this way Samba enforces the permission restrictions that
4113 an administrator can set on a Samba share, whilst still allowing users
4114 to modify the permission bits within that restriction.</P
4116 >If you want to set up a share that allows users full control
4117 in modifying the permission bits on their files and directories and
4118 doesn't force any particular bits to be set 'on', then set the following
4119 parameters in the <A
4120 HREF="smb.conf.5.html"
4127 > file in that share specific section :</P
4132 >security mask = 0777</I
4139 >force security mode = 0</I
4146 >directory security mask = 0777</I
4153 >force directory security mode = 0</I
4157 >As described, in Samba 2.0.4 the parameters :</P
4169 >force create mode</I
4183 >force directory mode</I
4187 >were used instead of the parameters discussed here.</P
4195 >5.7. Interaction with the standard Samba file attribute
4199 >Samba maps some of the DOS attribute bits (such as "read
4200 only") into the UNIX permissions of a file. This means there can
4201 be a conflict between the permission bits set via the security
4202 dialog and the permission bits set by the file attribute mapping.
4205 >One way this can show up is if a file has no UNIX read access
4206 for the owner it will show up as "read only" in the standard
4207 file attributes tabbed dialog. Unfortunately this dialog is
4208 the same one that contains the security info in another tab.</P
4210 >What this can mean is that if the owner changes the permissions
4211 to allow themselves read access using the security dialog, clicks
4215 > to get back to the standard attributes tab
4216 dialog, and then clicks <B
4219 > on that dialog, then
4220 NT will set the file permissions back to read-only (as that is what
4221 the attributes still say in the dialog). This means that after setting
4222 permissions and clicking <B
4225 > to get back to the
4226 attributes dialog you should always hit <B
4233 > to ensure that your changes
4234 are not overridden.</P
4242 >Chapter 6. Printing Support in Samba 2.2.x</A
4250 >6.1. Introduction</A
4253 >Beginning with the 2.2.0 release, Samba supports
4254 the native Windows NT printing mechanisms implemented via
4255 MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of
4256 Samba only supported LanMan printing calls.</P
4258 >The additional functionality provided by the new
4259 SPOOLSS support includes:</P
4265 >Support for downloading printer driver
4266 files to Windows 95/98/NT/2000 clients upon demand.
4271 >Uploading of printer drivers via the
4272 Windows NT Add Printer Wizard (APW) or the
4273 Imprints tool set (refer to <A
4274 HREF="http://imprints.sourceforge.net"
4276 >http://imprints.sourceforge.net</A
4282 >Support for the native MS-RPC printing
4283 calls such as StartDocPrinter, EnumJobs(), etc... (See
4284 the MSDN documentation at <A
4285 HREF="http://msdn.microsoft.com/"
4287 >http://msdn.microsoft.com/</A
4289 for more information on the Win32 printing API)
4294 >Support for NT Access Control Lists (ACL)
4295 on printer objects</P
4299 >Improved support for printer queue manipulation
4300 through the use of an internal databases for spooled job
4305 >There has been some initial confusion about what all this means
4306 and whether or not it is a requirement for printer drivers to be
4307 installed on a Samba host in order to support printing from Windows
4308 clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients
4309 require that the Samba server possess a valid driver for the printer.
4310 This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients
4311 can use the local APW for installing drivers to be used with a Samba
4312 served printer. This is the same behavior exhibited by Windows 9x clients.
4313 As a side note, Samba does not use these drivers in any way to process
4314 spooled files. They are utilized entirely by the clients.</P
4316 >The following MS KB article, may be of some help if you are dealing with
4317 Windows 2000 clients: <EM
4318 >How to Add Printers with No User
4319 Interaction in Windows 2000</EM
4323 HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP"
4325 >http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A
4334 >6.2. Configuration</A
4348 >[print$] vs. [printer$]</B
4355 >Previous versions of Samba recommended using a share named [printer$].
4356 This name was taken from the printer$ service created by Windows 9x
4357 clients when a printer was shared. Windows 9x printer servers always have
4358 a printer$ service which provides read-only access via no
4359 password in order to support printer driver downloads.</P
4361 >However, the initial implementation allowed for a
4365 >printer driver location</I
4368 to be used on a per share basis to specify the location of
4369 the driver files associated with that printer. Another
4376 a means of defining the printer driver name to be sent to
4379 >These parameters, including <TT
4385 > parameter, are being depreciated and should not
4386 be used in new installations. For more information on this change,
4387 you should refer to the <A
4389 >Migration section</A
4391 of this document.</P
4402 >6.2.1. Creating [print$]</A
4405 >In order to support the uploading of printer driver
4406 files, you must first configure a file share named [print$].
4407 The name of this share is hard coded in Samba's internals so
4408 the name is very important (print$ is the service used by
4409 Windows NT print servers to provide support for printer driver
4412 >You should modify the server's smb.conf file to add the global
4413 parameters and to create the
4414 following file share (of course, some of the parameter values,
4415 such as 'path' are arbitrary and should be replaced with
4416 appropriate values for your site):</P
4425 CLASS="PROGRAMLISTING"
4427 ; members of the ntadmin group should be able
4428 ; to add drivers and set printer properties
4429 ; root is implicitly a 'printer admin'
4430 printer admin = @ntadmin
4433 path = /usr/local/samba/printers
4437 ; since this share is configured as read only, then we need
4438 ; a 'write list'. Check the file system permissions to make
4439 ; sure this account can copy files to the share. If this
4440 ; is setup to a non-root account, then it should also exist
4441 ; as a 'printer admin'
4442 write list = @ntadmin,root</PRE
4449 HREF="smb.conf.5.html#WRITELIST"
4457 > is used to allow administrative
4458 level user accounts to have write access in order to update files
4459 on the share. See the <A
4460 HREF="smb.conf.5.html"
4464 > for more information on configuring file shares.</P
4466 >The requirement for <A
4467 HREF="smb.conf.5.html#GUESTOK"
4474 > depends upon how your
4475 site is configured. If users will be guaranteed to have
4476 an account on the Samba host, then this is a non-issue.</P
4484 >The non-issue is that if all your Windows NT users are guaranteed to be
4485 authenticated by the Samba server (such as a domain member server and the NT
4486 user has already been validated by the Domain Controller in
4487 order to logon to the Windows NT console), then guest access
4488 is not necessary. Of course, in a workgroup environment where
4489 you just want to be able to print without worrying about
4490 silly accounts and security, then configure the share for
4491 guest access. You'll probably want to add <A
4492 HREF="smb.conf.5.html#MAPTOGUEST"
4496 >map to guest = Bad User</B
4498 > in the [global] section as well. Make sure
4499 you understand what this parameter does before using it
4504 >In order for a Windows NT print server to support
4505 the downloading of driver files by multiple client architectures,
4506 it must create subdirectories within the [print$] service
4507 which correspond to each of the supported client architectures.
4508 Samba follows this model as well.</P
4510 >Next create the directory tree below the [print$] share
4511 for each architecture you wish to support.</P
4520 CLASS="PROGRAMLISTING"
4522 |-W32X86 ; "Windows NT x86"
4523 |-WIN40 ; "Windows 95/98"
4524 |-W32ALPHA ; "Windows NT Alpha_AXP"
4525 |-W32MIPS ; "Windows NT R4000"
4526 |-W32PPC ; "Windows NT PowerPC"</PRE
4543 >ATTENTION! REQUIRED PERMISSIONS</B
4550 >In order to currently add a new driver to you Samba host,
4551 one of two conditions must hold true:</P
4557 >The account used to connect to the Samba host
4558 must have a uid of 0 (i.e. a root account)</P
4562 >The account used to connect to the Samba host
4563 must be a member of the <A
4564 HREF="smb.conf.5.html#PRINTERADMIN"
4577 >Of course, the connected account must still possess access
4578 to add files to the subdirectories beneath [print$]. Remember
4579 that all file shares are set to 'read only' by default.</P
4585 >Once you have created the required [print$] service and
4586 associated subdirectories, simply log onto the Samba server using
4593 from a Windows NT 4.0 client. Navigate to the "Printers" folder
4594 on the Samba server. You should see an initial listing of printers
4595 that matches the printer shares defined on your Samba host.</P
4603 >6.2.2. Setting Drivers for Existing Printers</A
4606 >The initial listing of printers in the Samba host's
4607 Printers folder will have no real printer driver assigned
4608 to them. By default, in Samba 2.2.0 this driver name was set to
4610 >NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</EM
4612 Later versions changed this to a NULL string to allow the use
4613 tof the local Add Printer Wizard on NT/2000 clients.
4614 Attempting to view the printer properties for a printer
4615 which has this default driver assigned will result in
4616 the error message:</P
4619 >Device settings cannot be displayed. The driver
4620 for the specified printer is not installed, only spooler
4621 properties will be displayed. Do you want to install the
4625 >Click "No" in the error dialog and you will be presented with
4626 the printer properties window. The way assign a driver to a
4627 printer is to either</P
4633 >Use the "New Driver..." button to install
4634 a new printer driver, or</P
4638 >Select a driver from the popup list of
4639 installed drivers. Initially this list will be empty.</P
4643 >If you wish to install printer drivers for client
4644 operating systems other than "Windows NT x86", you will need
4645 to use the "Sharing" tab of the printer properties dialog.</P
4647 >Assuming you have connected with a root account, you
4648 will also be able modify other printer properties such as
4649 ACLs and device settings using this dialog box.</P
4651 >A few closing comments for this section, it is possible
4652 on a Windows NT print server to have printers
4653 listed in the Printers folder which are not shared. Samba does
4654 not make this distinction. By definition, the only printers of
4655 which Samba is aware are those which are specified as shares in
4661 >Another interesting side note is that Windows NT clients do
4662 not use the SMB printer share, but rather can print directly
4663 to any printer on another Windows NT host using MS-RPC. This
4664 of course assumes that the printing client has the necessary
4665 privileges on the remote host serving the printer. The default
4666 permissions assigned by Windows NT to a printer gives the "Print"
4667 permissions to the "Everyone" well-known group.</P
4675 >6.2.3. Support a large number of printers</A
4678 >One issue that has arisen during the development
4679 phase of Samba 2.2 is the need to support driver downloads for
4680 100's of printers. Using the Windows NT APW is somewhat
4681 awkward to say the list. If more than one printer are using the
4683 HREF="rpcclient.1.html"
4688 setdriver command</B
4690 > can be used to set the driver
4691 associated with an installed driver. The following is example
4692 of how this could be accomplished:</P
4701 CLASS="PROGRAMLISTING"
4706 >rpcclient pogo -U root%secret -c "enumdrivers"
4707 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
4710 Printer Driver Info 1:
4711 Driver Name: [HP LaserJet 4000 Series PS]
4713 Printer Driver Info 1:
4714 Driver Name: [HP LaserJet 2100 Series PS]
4716 Printer Driver Info 1:
4717 Driver Name: [HP LaserJet 4Si/4SiMX PS]
4722 >rpcclient pogo -U root%secret -c "enumprinters"
4723 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
4725 name:[\\POGO\hp-print]
4726 description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
4732 >rpcclient pogo -U root%secret \
4736 > -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
4737 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
4738 Successfully set hp-print to driver HP LaserJet 4000 Series PS.</PRE
4750 >6.2.4. Adding New Printers via the Windows NT APW</A
4753 >By default, Samba offers all printer shares defined in <TT
4757 in the "Printers..." folder. Also existing in this folder is the Windows NT
4758 Add Printer Wizard icon. The APW will be show only if</P
4764 >The connected user is able to successfully
4765 execute an OpenPrinterEx(\\server) with administrative
4766 privileges (i.e. root or <TT
4777 HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD"
4783 add printer wizard = yes</I
4791 >In order to be able to use the APW to successfully add a printer to a Samba
4793 HREF="smb.conf.5.html#ADDPRINTERCOMMAND"
4802 > must have a defined value. The program
4803 hook must successfully add the printer to the system (i.e.
4807 > or appropriate files) and
4813 >When using the APW from a client, if the named printer share does
4817 > will execute the <TT
4823 > and reparse to the <TT
4827 to attempt to locate the new printer share. If the share is still not defined,
4828 an error of "Access Denied" is returned to the client. Note that the
4832 >add printer program</I
4834 > is executed under the context
4835 of the connected user, not necessarily a root account.</P
4837 >There is a complementing <A
4838 HREF="smb.conf.5.html#DELETEPRINTERCOMMAND"
4847 > for removing entries from the "Printers..."
4856 >6.2.5. Samba and Printer Ports</A
4859 >Windows NT/2000 print servers associate a port with each printer. These normally
4860 take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
4861 concept of ports associated with a printer. By default, only one printer port,
4862 named "Samba Printer Port", exists on a system. Samba does not really a port in
4863 order to print, rather it is a requirement of Windows clients. </P
4865 >Note that Samba does not support the concept of "Printer Pooling" internally
4866 either. This is when a logical printer is assigned to multiple ports as
4867 a form of load balancing or fail over.</P
4869 >If you require that multiple ports be defined for some reason,
4874 HREF="smb.conf.5.html#ENUMPORTSCOMMAND"
4883 > which can be used to define an external program
4884 that generates a listing of ports on a system.</P
4893 >6.3. The Imprints Toolset</A
4896 >The Imprints tool set provides a UNIX equivalent of the
4897 Windows NT Add Printer Wizard. For complete information, please
4898 refer to the Imprints web site at <A
4899 HREF="http://imprints.sourceforge.net/"
4901 > http://imprints.sourceforge.net/</A
4902 > as well as the documentation
4903 included with the imprints source distribution. This section will
4904 only provide a brief introduction to the features of Imprints.</P
4911 >6.3.1. What is Imprints?</A
4914 >Imprints is a collection of tools for supporting the goals
4921 >Providing a central repository information
4922 regarding Windows NT and 95/98 printer driver packages</P
4926 >Providing the tools necessary for creating
4927 the Imprints printer driver packages.</P
4931 >Providing an installation client which
4932 will obtain and install printer drivers on remote Samba
4933 and Windows NT 4 print servers.</P
4943 >6.3.2. Creating Printer Driver Packages</A
4946 >The process of creating printer driver packages is beyond
4947 the scope of this document (refer to Imprints.txt also included
4948 with the Samba distribution for more information). In short,
4949 an Imprints driver package is a gzipped tarball containing the
4950 driver files, related INF files, and a control file needed by the
4951 installation client.</P
4959 >6.3.3. The Imprints server</A
4962 >The Imprints server is really a database server that
4963 may be queried via standard HTTP mechanisms. Each printer
4964 entry in the database has an associated URL for the actual
4965 downloading of the package. Each package is digitally signed
4966 via GnuPG which can be used to verify that package downloaded
4967 is actually the one referred in the Imprints database. It is
4970 > recommended that this security check
4979 >6.3.4. The Installation Client</A
4982 >More information regarding the Imprints installation client
4983 is available in the <TT
4985 >Imprints-Client-HOWTO.ps</TT
4987 file included with the imprints source package.</P
4989 >The Imprints installation client comes in two forms.</P
4995 >a set of command line Perl scripts</P
4999 >a GTK+ based graphical interface to
5000 the command line perl scripts</P
5004 >The installation client (in both forms) provides a means
5005 of querying the Imprints database server for a matching
5006 list of known printer model names as well as a means to
5007 download and install the drivers on remote Samba and Windows
5008 NT print servers.</P
5010 >The basic installation process is in four steps and
5011 perl code is wrapped around <B
5027 CLASS="PROGRAMLISTING"
5029 foreach (supported architecture for a given driver)
5031 1. rpcclient: Get the appropriate upload directory
5032 on the remote server
5033 2. smbclient: Upload the driver files
5034 3. rpcclient: Issues an AddPrinterDriver() MS-RPC
5037 4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually
5038 create the printer</PRE
5044 >One of the problems encountered when implementing
5045 the Imprints tool set was the name space issues between
5046 various supported client architectures. For example, Windows
5047 NT includes a driver named "Apple LaserWriter II NTX v51.8"
5048 and Windows 95 calls its version of this driver "Apple
5049 LaserWriter II NTX"</P
5051 >The problem is how to know what client drivers have
5052 been uploaded for a printer. As astute reader will remember
5053 that the Windows NT Printer Properties dialog only includes
5054 space for one printer driver name. A quick look in the
5055 Windows NT 4.0 system registry at</P
5059 >HKLM\System\CurrentControlSet\Control\Print\Environment
5063 >will reveal that Windows NT always uses the NT driver
5064 name. This is ok as Windows NT always requires that at least
5065 the Windows NT version of the printer driver is present.
5066 However, Samba does not have the requirement internally.
5067 Therefore, how can you use the NT driver name if is has not
5068 already been installed?</P
5070 >The way of sidestepping this limitation is to require
5071 that all Imprints printer driver packages include both the Intel
5072 Windows NT and 95/98 printer drivers and that NT driver is
5085 >Migration to from Samba 2.0.x to 2.2.x</A
5088 >Given that printer driver management has changed (we hope improved) in
5089 2.2 over prior releases, migration from an existing setup to 2.2 can
5090 follow several paths. Here are the possible scenarios for
5097 >If you do not desire the new Windows NT
5098 print driver support, nothing needs to be done.
5099 All existing parameters work the same.</P
5103 >If you want to take advantage of NT printer
5104 driver support but do not want to migrate the
5105 9x drivers to the new setup, the leave the existing
5109 > file. When smbd attempts
5111 9x driver for the printer in the TDB and fails it
5112 will drop down to using the printers.def (and all
5113 associated parameters). The <B
5117 tool will also remain for backwards compatibility but will
5118 be removed in the next major release.</P
5122 >If you install a Windows 9x driver for a printer
5123 on your Samba host (in the printing TDB), this information will
5124 take precedence and the three old printing parameters
5125 will be ignored (including print driver location).</P
5129 >If you want to migrate an existing <TT
5133 file into the new setup, the current only solution is to use the Windows
5134 NT APW to install the NT drivers and the 9x drivers. This can be scripted
5142 Imprints installation client at <A
5143 HREF="http://imprints.sourceforge.net/"
5145 >http://imprints.sourceforge.net/</A
5173 > parameters are considered to
5174 be deprecated and will be removed soon. Do not use them in new
5184 >printer driver file (G)</I
5194 >printer driver (S)</I
5204 >printer driver location (S)</I
5215 >The have been two new parameters add in Samba 2.2.2 to for
5216 better support of Samba 2.0.x backwards capability (<TT
5222 >) and for using local printers drivers on Windows
5223 NT/2000 clients (<TT
5226 >use client driver</I
5229 these options are described in the smb.coinf(5) man page and are
5230 disabled by default.</P
5237 NAME="DOMAIN-SECURITY"
5238 >Chapter 7. security = domain in Samba 2.x</A
5246 >7.1. Joining an NT Domain with Samba 2.2</A
5249 >Assume you have a Samba 2.x server with a NetBIOS name of
5253 > and are joining an NT domain called
5257 >, which has a PDC with a NetBIOS name
5261 > and two backup domain controllers
5262 with NetBIOS names <TT
5271 >In order to join the domain, first stop all Samba daemons
5272 and run the command:</P
5280 >smbpasswd -j DOM -r DOMPDC
5284 >Administrator%password</I
5290 >as we are joining the domain DOM and the PDC for that domain
5291 (the only machine that has write access to the domain SAM database)
5295 >Administrator%password</I
5298 the login name and password for an account which has the necessary
5299 privilege to add machines to the domain. If this is successful
5300 you will see the message:</P
5303 CLASS="COMPUTEROUTPUT"
5304 >smbpasswd: Joined domain DOM.</TT
5308 >in your terminal window. See the <A
5309 HREF="smbpasswd.8.html"
5312 > man page for more details.</P
5314 >There is existing development code to join a domain
5315 without having to create the machine trust account on the PDC
5316 beforehand. This code will hopefully be available soon
5317 in release branches as well.</P
5319 >This command goes through the machine account password
5320 change protocol, then writes the new (random) machine account
5321 password for this Samba server into a file in the same directory
5322 in which an smbpasswd file would be stored - normally :</P
5326 >/usr/local/samba/private</TT
5329 >In Samba 2.0.x, the filename looks like this:</P
5336 ><NT DOMAIN NAME></I
5350 > suffix stands for machine account
5351 password file. So in our example above, the file would be called:</P
5358 >In Samba 2.2, this file has been replaced with a TDB
5359 (Trivial Database) file named <TT
5365 >This file is created and owned by root and is not
5366 readable by any other user. It is the key to the domain-level
5367 security for your system, and should be treated as carefully
5368 as a shadow password file.</P
5370 >Now, before restarting the Samba daemons you must
5372 HREF="smb.conf.5.html"
5379 > file to tell Samba it should now use domain security.</P
5381 >Change (or add) your <A
5382 HREF="smb.conf.5.html#SECURITY"
5390 > line in the [global] section
5391 of your smb.conf to read:</P
5395 >security = domain</B
5399 HREF="smb.conf.5.html#WORKGROUP"
5407 > line in the [global] section to read: </P
5414 >as this is the name of the domain we are joining. </P
5416 >You must also have the parameter <A
5417 HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
5422 >encrypt passwords</I
5429 > in order for your users to authenticate to the NT PDC.</P
5431 >Finally, add (or modify) a <A
5432 HREF="smb.conf.5.html#PASSWORDSERVER"
5437 >password server =</I
5440 > line in the [global]
5441 section to read: </P
5445 >password server = DOMPDC DOMBDC1 DOMBDC2</B
5448 >These are the primary and backup domain controllers Samba
5449 will attempt to contact in order to authenticate users. Samba will
5450 try to contact each of these servers in order, so you may want to
5451 rearrange this list in order to spread out the authentication load
5452 among domain controllers.</P
5454 >Alternatively, if you want smbd to automatically determine
5455 the list of Domain controllers to use for authentication, you may
5456 set this line to be :</P
5460 >password server = *</B
5463 >This method, which was introduced in Samba 2.0.6,
5464 allows Samba to use exactly the same mechanism that NT does. This
5465 method either broadcasts or uses a WINS database in order to
5466 find domain controllers to authenticate against.</P
5468 >Finally, restart your Samba daemons and get ready for
5469 clients to begin using domain security!</P
5477 >7.2. Samba and Windows 2000 Domains</A
5480 >Many people have asked regarding the state of Samba's ability to participate in
5481 a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows
5482 2000 domain operating in mixed or native mode.</P
5484 >There is much confusion between the circumstances that require a "mixed" mode
5485 Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode
5486 Win2k domain controller is only needed if Windows NT BDCs must exist in the same
5487 domain. By default, a Win2k DC in "native" mode will still support
5488 NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and
5489 NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server.</P
5491 >The steps for adding a Samba 2.2 host to a Win2k domain are the same as those
5492 for adding a Samba server to a Windows NT 4.0 domain. The only exception is that
5493 the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and
5494 Computers" MMC (Microsoft Management Console) plugin.</P
5502 >7.3. Why is this better than security = server?</A
5505 >Currently, domain security in Samba doesn't free you from
5506 having to create local Unix users to represent the users attaching
5507 to your server. This means that if domain user <TT
5511 > attaches to your domain security Samba server, there needs
5512 to be a local Unix user fred to represent that user in the Unix
5513 filesystem. This is very similar to the older Samba security mode
5515 HREF="smb.conf.5.html#SECURITYEQUALSSERVER"
5517 >security = server</A
5519 where Samba would pass through the authentication request to a Windows
5520 NT server in the same way as a Windows 95 or Windows 98 server would.
5523 >Please refer to the <A
5528 > for information on a system to automatically
5529 assign UNIX uids and gids to Windows NT Domain users and groups.
5530 This code is available in development branches only at the moment,
5531 but will be moved to release branches soon.</P
5533 >The advantage to domain-level security is that the
5534 authentication in domain-level security is passed down the authenticated
5535 RPC channel in exactly the same way that an NT server would do it. This
5536 means Samba servers now participate in domain trust relationships in
5537 exactly the same way NT servers do (i.e., you can add Samba servers into
5538 a resource domain and have the authentication passed on from a resource
5539 domain PDC to an account domain PDC.</P
5541 >In addition, with <B
5543 >security = server</B
5545 daemon on a server has to keep a connection open to the
5546 authenticating server for as long as that daemon lasts. This can drain
5547 the connection resources on a Microsoft NT server and cause it to run
5548 out of available connections. With <B
5550 >security = domain</B
5552 however, the Samba daemons connect to the PDC/BDC only for as long
5553 as is necessary to authenticate the user, and then drop the connection,
5554 thus conserving PDC connection resources.</P
5556 >And finally, acting in the same manner as an NT server
5557 authenticating to a PDC means that as part of the authentication
5558 reply, the Samba server gets the user identification information such
5559 as the user SID, the list of NT groups the user belongs to, etc. All
5560 this information will allow Samba to be extended in the future into
5561 a mode the developers currently call appliance mode. In this mode,
5562 no local Unix users will be necessary, and Samba will generate Unix
5563 uids and gids from the information passed back from the PDC when a
5564 user is authenticated, making a Samba server truly plug and play
5565 in an NT domain environment. Watch for this code soon.</P
5569 > Much of the text of this document
5570 was first published in the Web magazine <A
5571 HREF="http://www.linuxworld.com"
5576 HREF="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html"
5588 >Chapter 8. How to Configure Samba 2.2 as a Primary Domain Controller</A
5596 >8.1. Prerequisite Reading</A
5599 >Before you continue reading in this chapter, please make sure
5600 that you are comfortable with configuring basic files services
5601 in smb.conf and how to enable and administer password
5602 encryption in Samba. Theses two topics are covered in the
5604 HREF="smb.conf.5.html"
5612 HREF="ENCRYPTION.html"
5614 >Encryption chapter</A
5616 of this HOWTO Collection.</P
5635 > This document is a combination
5636 of David Bannon's "Samba 2.2 PDC HOWTO" and "Samba NT Domain FAQ".
5637 Both documents are superseded by this one.</P
5641 >Versions of Samba prior to release 2.2 had marginal capabilities to act
5642 as a Windows NT 4.0 Primary Domain Controller
5644 (PDC). With Samba 2.2.0, we are proud to announce official support for
5645 Windows NT 4.0-style domain logons from Windows NT 4.0 and Windows
5646 2000 clients. This article outlines the steps
5647 necessary for configuring Samba as a PDC. It is necessary to have a
5648 working Samba server prior to implementing the PDC functionality. If
5649 you have not followed the steps outlined in <A
5650 HREF="UNIX_INSTALL.html"
5652 > UNIX_INSTALL.html</A
5654 that your server is configured correctly before proceeding. Another
5655 good resource in the <A
5656 HREF="smb.conf.5.html"
5660 >. The following functionality should work in 2.2:</P
5666 > domain logons for Windows NT 4.0/2000 clients.
5671 > placing a Windows 9x client in user level security
5676 > retrieving a list of users and groups from a Samba PDC to
5677 Windows 9x/NT/2000 clients
5682 > roving (roaming) user profiles
5687 > Windows NT 4.0-style system policies
5692 >The following pieces of functionality are not included in the 2.2 release:</P
5698 > Windows NT 4 domain trusts
5703 > SAM replication with Windows NT 4.0 Domain Controllers
5704 (i.e. a Samba PDC and a Windows NT BDC or vice versa)
5709 > Adding users via the User Manager for Domains
5714 > Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
5720 >Please note that Windows 9x clients are not true members of a domain
5721 for reasons outlined in this article. Therefore the protocol for
5722 support Windows 9x-style domain logons is completely different
5723 from NT4 domain logons and has been officially supported for some
5726 >Implementing a Samba PDC can basically be divided into 2 broad
5734 > Configuring the Samba PDC
5739 > Creating machine trust accounts and joining clients
5745 >There are other minor details such as user profiles, system
5746 policies, etc... However, these are not necessarily specific
5747 to a Samba PDC as much as they are related to Windows NT networking
5748 concepts. They will be mentioned only briefly here.</P
5756 >8.3. Configuring the Samba Domain Controller</A
5759 >The first step in creating a working Samba PDC is to
5760 understand the parameters necessary in smb.conf. I will not
5761 attempt to re-explain the parameters here as they are more that
5762 adequately covered in <A
5763 HREF="smb.conf.5.html"
5767 >. For convenience, the parameters have been
5768 linked with the actual smb.conf description.</P
5770 >Here is an example <TT
5773 > for acting as a PDC:</P
5782 CLASS="PROGRAMLISTING"
5784 ; Basic server settings
5786 HREF="smb.conf.5.html#NETBIOSNAME"
5796 HREF="smb.conf.5.html#WORKGROUP"
5806 ; we should act as the domain and local master browser
5808 HREF="smb.conf.5.html#OSLEVEL"
5813 HREF="smb.conf.5.html#PERFERREDMASTER"
5815 >preferred master</A
5818 HREF="smb.conf.5.html#DOMAINMASTER"
5823 HREF="smb.conf.5.html#LOCALMASTER"
5828 ; security settings (must user security = user)
5830 HREF="smb.conf.5.html#SECURITYEQUALSUSER"
5835 ; encrypted passwords are a requirement for a PDC
5837 HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
5839 >encrypt passwords</A
5842 ; support domain logons
5844 HREF="smb.conf.5.html#DOMAINLOGONS"
5849 ; where to store user profiles?
5851 HREF="smb.conf.5.html#LOGONPATH"
5854 > = \\%N\profiles\%u
5856 ; where is a user's home directory and where should it
5859 HREF="smb.conf.5.html#LOGONDRIVE"
5864 HREF="smb.conf.5.html#LOGONHOME"
5869 ; specify a generic logon script for all users
5870 ; this is a relative **DOS** path to the [netlogon] share
5872 HREF="smb.conf.5.html#LOGONSCRIPT"
5877 ; necessary share for domain controller
5880 HREF="smb.conf.5.html#PATH"
5883 > = /usr/local/samba/lib/netlogon
5885 HREF="smb.conf.5.html#READONLY"
5890 HREF="smb.conf.5.html#WRITELIST"
5900 ; share for storing user profiles
5903 HREF="smb.conf.5.html#PATH"
5906 > = /export/smb/ntprofile
5908 HREF="smb.conf.5.html#READONLY"
5913 HREF="smb.conf.5.html#CREATEMASK"
5918 HREF="smb.conf.5.html#DIRECTORYMASK"
5927 >There are a couple of points to emphasize in the above configuration.</P
5933 > Encrypted passwords must be enabled. For more details on how
5934 to do this, refer to <A
5935 HREF="ENCRYPTION.html"
5943 > The server must support domain logons and a
5952 > The server must be the domain master browser in order for Windows
5953 client to locate the server as a DC. Please refer to the various
5954 Network Browsing documentation included with this distribution for
5960 >As Samba 2.2 does not offer a complete implementation of group mapping
5961 between Windows NT groups and Unix groups (this is really quite
5962 complicated to explain in a short space), you should refer to the
5964 HREF="smb.conf.5.html#DOMAINADMINGROUP"
5968 > smb.conf parameter for information of creating "Domain
5969 Admins" style accounts.</P
5977 >8.4. Creating Machine Trust Accounts and Joining Clients to the
5981 >A machine trust account is a Samba account that is used to
5982 authenticate a client machine (rather than a user) to the Samba
5983 server. In Windows terminology, this is known as a "Computer
5986 >The password of a machine trust account acts as the shared secret for
5987 secure communication with the Domain Controller. This is a security
5988 feature to prevent an unauthorized machine with the same NetBIOS name
5989 from joining the domain and gaining access to domain user/group
5990 accounts. Windows NT and 2000 clients use machine trust accounts, but
5991 Windows 9x clients do not. Hence, a Windows 9x client is never a true
5992 member of a domain because it does not possess a machine trust
5993 account, and thus has no shared secret with the domain controller.</P
5995 >A Windows PDC stores each machine trust account in the Windows
5996 Registry. A Samba PDC, however, stores each machine trust account
5997 in two parts, as follows:
6004 >A Samba account, stored in the same location as user
6005 LanMan and NT password hashes (currently
6009 >). The Samba account
6010 possesses and uses only the NT password hash.</P
6014 >A corresponding Unix account, typically stored in
6018 >. (Future releases will alleviate the need to
6027 >There are two ways to create machine trust accounts:</P
6033 > Manual creation. Both the Samba and corresponding
6034 Unix account are created by hand.</P
6038 > "On-the-fly" creation. The Samba machine trust
6039 account is automatically created by Samba at the time the client
6040 is joined to the domain. (For security, this is the
6041 recommended method.) The corresponding Unix account may be
6042 created automatically or manually. </P
6051 >8.4.1. Manual Creation of Machine Trust Accounts</A
6054 >The first step in manually creating a machine trust account is to
6055 manually create the corresponding Unix account in
6059 >. This can be done using
6063 > or other 'add user' command that is normally
6064 used to create new Unix accounts. The following is an example for a
6065 Linux based Samba server:</P
6072 >/usr/sbin/useradd -g 100 -d /dev/null -c <TT
6102 > entry will list the machine name
6103 with a "$" appended, won't have a password, will have a null shell and no
6104 home directory. For example a machine named 'doppy' would have an
6108 > entry like this:</P
6117 CLASS="PROGRAMLISTING"
6118 >doppy$:x:505:501:<TT
6121 >machine_nickname</I
6123 >:/dev/null:/bin/false</PRE
6132 >machine_nickname</I
6135 descriptive name for the client, i.e., BasementComputer.
6141 > absolutely must be the NetBIOS
6142 name of the client to be joined to the domain. The "$" must be
6143 appended to the NetBIOS name of the client or Samba will not recognize
6144 this as a machine trust account.</P
6146 >Now that the corresponding Unix account has been created, the next step is to create
6147 the Samba account for the client containing the well-known initial
6148 machine trust account password. This can be done using the <A
6149 HREF="smbpasswd.8.html"
6163 >smbpasswd -a -m <TT
6176 > is the machine's NetBIOS
6177 name. The RID of the new machine account is generated from the UID of
6178 the corresponding Unix account.</P
6191 >Join the client to the domain immediately</B
6198 > Manually creating a machine trust account using this method is the
6199 equivalent of creating a machine trust account on a Windows NT PDC using
6200 the "Server Manager". From the time at which the account is created
6201 to the time which the client joins the domain and changes the password,
6202 your domain is vulnerable to an intruder joining your domain using a
6203 a machine with the same NetBIOS name. A PDC inherently trusts
6204 members of the domain and will serve out a large degree of user
6205 information to such clients. You have been warned!
6218 >8.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
6221 >The second (and recommended) way of creating machine trust accounts is
6222 simply to allow the Samba server to create them as needed when the client
6223 is joined to the domain. </P
6225 >Since each Samba machine trust account requires a corresponding
6226 Unix account, a method for automatically creating the
6227 Unix account is usually supplied; this requires configuration of the
6229 HREF="smb.conf.5.html#ADDUSERSCRIPT"
6237 method is not required, however; corresponding Unix accounts may also
6238 be created manually.</P
6240 >Below is an example for a RedHat 6.2 Linux system.</P
6249 CLASS="PROGRAMLISTING"
6251 # <...remainder of parameters...>
6252 add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE
6264 >8.4.3. Joining the Client to the Domain</A
6267 >The procedure for joining a client to the domain varies with the
6268 version of Windows.</P
6278 > When the user elects to join the client to a domain, Windows prompts for
6279 an account and password that is privileged to join the domain. A
6280 Samba administrative account (i.e., a Samba account that has root
6281 privileges on the Samba server) must be entered here; the
6282 operation will fail if an ordinary user account is given.
6283 The password for this account should be
6284 set to a different password than the associated
6288 > entry, for security
6291 >The session key of the Samba administrative account acts as an
6292 encryption key for setting the password of the machine trust
6293 account. The machine trust account will be created on-the-fly, or
6294 updated if it already exists.</P
6302 > If the machine trust account was created manually, on the
6303 Identification Changes menu enter the domain name, but do not
6304 check the box "Create a Computer Account in the Domain." In this case,
6305 the existing machine trust account is used to join the machine to
6308 > If the machine trust account is to be created
6309 on-the-fly, on the Identification Changes menu enter the domain
6310 name, and check the box "Create a Computer Account in the Domain." In
6311 this case, joining the domain proceeds as above for Windows 2000
6312 (i.e., you must supply a Samba administrative account when
6324 >8.5. Common Problems and Errors</A
6334 >I cannot include a '$' in a machine name.</EM
6338 > A 'machine name' in (typically) <TT
6342 of the machine name with a '$' appended. FreeBSD (and other BSD
6343 systems?) won't create a user with a '$' in their name.
6346 > The problem is only in the program used to make the entry, once
6347 made, it works perfectly. So create a user without the '$' and
6351 > to edit the entry, adding the '$'. Or create
6352 the whole entry with vipw if you like, make sure you use a
6359 >I get told "You already have a connection to the Domain...."
6360 or "Cannot join domain, the credentials supplied conflict with an
6361 existing set.." when creating a machine trust account.</EM
6365 > This happens if you try to create a machine trust account from the
6366 machine itself and already have a connection (e.g. mapped drive)
6367 to a share (or IPC$) on the Samba PDC. The following command
6368 will remove all network drive connections:
6380 > Further, if the machine is a already a 'member of a workgroup' that
6381 is the same name as the domain you are joining (bad idea) you will
6382 get this message. Change the workgroup name to something else, it
6383 does not matter what, reboot, and try again.
6389 >The system can not log you on (C000019B)....</EM
6393 >I joined the domain successfully but after upgrading
6394 to a newer version of the Samba code I get the message, "The system
6395 can not log you on (C000019B), Please try a gain or consult your
6396 system administrator" when attempting to logon.
6399 > This occurs when the domain SID stored in
6402 >private/WORKGROUP.SID</TT
6404 changed. For example, you remove the file and <B
6408 creates a new one. Or you are swapping back and forth between
6409 versions 2.0.7, TNG and the HEAD branch code (not recommended). The
6410 only way to correct the problem is to restore the original domain
6411 SID or remove the domain client from the domain and rejoin.
6417 >The machine trust account for this computer either does not
6418 exist or is not accessible.</EM
6422 > When I try to join the domain I get the message "The machine account
6423 for this computer either does not exist or is not accessible". What's
6427 > This problem is caused by the PDC not having a suitable machine trust account.
6428 If you are using the <TT
6434 accounts then this would indicate that it has not worked. Ensure the domain
6435 admin user system is working.
6438 > Alternatively if you are creating account entries manually then they
6439 have not been created correctly. Make sure that you have the entry
6440 correct for the machine trust account in smbpasswd file on the Samba PDC.
6441 If you added the account using an editor rather than using the smbpasswd
6442 utility, make sure that the account name is the machine NetBIOS name
6443 with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
6444 in both /etc/passwd and the smbpasswd file. Some people have reported
6445 that inconsistent subnet masks between the Samba server and the NT
6446 client have caused this problem. Make sure that these are consistent
6447 for both client and server.
6453 >When I attempt to login to a Samba Domain from a NT4/W2K workstation,
6454 I get a message about my account being disabled.</EM
6458 > This problem is caused by a PAM related bug in Samba 2.2.0. This bug is
6459 fixed in 2.2.1. Other symptoms could be unaccessible shares on
6460 NT/W2K member servers in the domain or the following error in your smbd.log:
6461 passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user%
6464 > At first be ensure to enable the useraccounts with <B
6468 >, this is normally done, when you create an account.
6471 > In order to work around this problem in 2.2.0, configure the
6480 >/etc/pam.d/samba</TT
6491 CLASS="PROGRAMLISTING"
6492 > account required pam_permit.so
6499 > If you want to remain backward compatibility to samba 2.0.x use
6503 >, it's also possible to use
6507 >. There are some bugs if you try to
6511 >, if you need this, be ensure to use
6512 the most recent version of this file.
6523 >8.6. System Policies and Profiles</A
6526 >Much of the information necessary to implement System Policies and
6527 Roving User Profiles in a Samba domain is the same as that for
6528 implementing these same items in a Windows NT 4.0 domain.
6529 You should read the white paper <A
6530 HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp"
6533 Profiles and Policies in Windows NT 4.0</A
6534 > available from Microsoft.</P
6536 >Here are some additional details:</P
6543 >What about Windows NT Policy Editor?</EM
6547 > To create or edit <TT
6551 the NT Server Policy Editor, <B
6555 is included with NT Server but <EM
6556 >not NT Workstation</EM
6558 There is a Policy Editor on a NTws
6559 but it is not suitable for creating <EM
6560 >Domain Policies</EM
6562 Further, although the Windows 95
6563 Policy Editor can be installed on an NT Workstation/Server, it will not
6564 work with NT policies because the registry key that are set by the policy templates.
6565 However, the files from the NT Server will run happily enough on an NTws.
6568 >poledit.exe, common.adm</TT
6573 to put the two *.adm files in <TT
6577 the binary will look for them unless told otherwise. Note also that that
6578 directory is 'hidden'.
6581 > The Windows NT policy editor is also included with the Service Pack 3 (and
6582 later) for Windows NT 4.0. Extract the files using <B
6584 >servicepackname /x</B
6589 > for service pack 6a. The policy editor,
6593 > and the associated template files (*.adm) should
6594 be extracted as well. It is also possible to downloaded the policy template
6595 files for Office97 and get a copy of the policy editor. Another possible
6596 location is with the Zero Administration Kit available for download from Microsoft.
6602 >Can Win95 do Policies?</EM
6606 > Install the group policy handler for Win9x to pick up group
6607 policies. Look on the Win98 CD in <TT
6609 >\tools\reskit\netadmin\poledit</TT
6611 Install group policies on a Win9x client by double-clicking
6615 >. Log off and on again a couple of
6616 times and see if Win98 picks up group policies. Unfortunately this needs
6617 to be done on every Win9x machine that uses group policies....
6620 > If group policies don't work one reports suggests getting the updated
6621 (read: working) grouppol.dll for Windows 9x. The group list is grabbed
6628 >How do I get 'User Manager' and 'Server Manager'</EM
6632 > Since I don't need to buy an NT Server CD now, how do I get
6633 the 'User Manager for Domains', the 'Server Manager'?
6636 > Microsoft distributes a version of these tools called nexus for
6637 installation on Windows 95 systems. The tools set includes
6648 >User Manager for Domains</P
6656 > Click here to download the archived file <A
6657 HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
6659 >ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
6663 > The Windows NT 4.0 version of the 'User Manager for
6664 Domains' and 'Server Manager' are available from Microsoft via ftp
6666 HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
6668 >ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
6680 >8.7. What other help can I get?</A
6683 >There are many sources of information available in the form
6684 of mailing lists, RFC's and documentation. The docs that come
6685 with the samba distribution contain very good explanations of
6686 general SMB topics such as browsing.</P
6693 >What are some diagnostics tools I can use to debug the domain logon
6694 process and where can I find them?</EM
6698 > One of the best diagnostic tools for debugging problems is Samba itself.
6699 You can use the -d option for both smbd and nmbd to specify what
6700 'debug level' at which to run. See the man pages on smbd, nmbd and
6701 smb.conf for more information on debugging options. The debug
6702 level can range from 1 (the default) to 10 (100 for debugging passwords).
6705 > Another helpful method of debugging is to compile samba using the
6709 > flag. This will include debug
6710 information in the binaries and allow you to attach gdb to the
6711 running smbd / nmbd process. In order to attach gdb to an smbd
6712 process for an NT workstation, first get the workstation to make the
6713 connection. Pressing ctrl-alt-delete and going down to the domain box
6714 is sufficient (at least, on the first time you join the domain) to
6715 generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
6716 maintains an open connection, and therefore there will be an smbd
6717 process running (assuming that you haven't set a really short smbd
6718 idle timeout) So, in between pressing ctrl alt delete, and actually
6719 typing in your password, you can gdb attach and continue.
6722 > Some useful samba commands worth investigating:
6729 >testparam | more</P
6733 >smbclient -L //{netbios name of server}</P
6737 > An SMB enabled version of tcpdump is available from
6739 HREF="http://www.tcpdump.org/"
6741 >http://www.tcpdup.org/</A
6743 Ethereal, another good packet sniffer for Unix and Win32
6744 hosts, can be downloaded from <A
6745 HREF="http://www.ethereal.com/"
6747 >http://www.ethereal.com</A
6751 > For tracing things on the Microsoft Windows NT, Network Monitor
6752 (aka. netmon) is available on the Microsoft Developer Network CD's,
6753 the Windows NT Server install CD and the SMS CD's. The version of
6754 netmon that ships with SMS allows for dumping packets between any two
6755 computers (i.e. placing the network interface in promiscuous mode).
6756 The version on the NT Server install CD will only allow monitoring
6757 of network traffic directed to the local NT box and broadcasts on the
6758 local subnet. Be aware that Ethereal can read and write netmon
6765 >How do I install 'Network Monitor' on an NT Workstation
6766 or a Windows 9x box?</EM
6770 > Installing netmon on an NT workstation requires a couple
6771 of steps. The following are for installing Netmon V4.00.349, which comes
6772 with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
6773 Workstation 4.0. The process should be similar for other version of
6774 Windows NT / Netmon. You will need both the Microsoft Windows
6775 NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
6778 > Initially you will need to install 'Network Monitor Tools and Agent'
6779 on the NT Server. To do this
6786 >Goto Start - Settings - Control Panel -
6787 Network - Services - Add </P
6791 >Select the 'Network Monitor Tools and Agent' and
6796 >Click 'OK' on the Network Control Panel.
6801 >Insert the Windows NT Server 4.0 install CD
6806 > At this point the Netmon files should exist in
6809 >%SYSTEMROOT%\System32\netmon\*.*</TT
6811 Two subdirectories exist as well, <TT
6815 which contains the necessary DLL's for parsing the netmon packet
6822 > In order to install the Netmon tools on an NT Workstation, you will
6823 first need to install the 'Network Monitor Agent' from the Workstation
6831 >Goto Start - Settings - Control Panel -
6832 Network - Services - Add</P
6836 >Select the 'Network Monitor Agent' and click
6841 >Click 'OK' on the Network Control Panel.
6846 >Insert the Windows NT Workstation 4.0 install
6847 CD when prompted.</P
6851 > Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
6852 to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
6853 permissions as you deem appropriate for your site. You will need
6854 administrative rights on the NT box to run netmon.
6857 > To install Netmon on a Windows 9x box install the network monitor agent
6858 from the Windows 9x CD (\admin\nettools\netmon). There is a readme
6859 file located with the netmon driver files on the CD if you need
6860 information on how to do this. Copy the files from a working
6861 Netmon installation.
6866 > The following is a list if helpful URLs and other links:
6873 >Home of Samba site <A
6874 HREF="http://samba.org"
6876 > http://samba.org</A
6877 >. We have a mirror near you !</P
6884 on the Samba mirrors might mention your problem. If so,
6885 it might mean that the developers are working on it.</P
6889 >See how Scott Merrill simulates a BDC behavior at
6891 HREF="http://www.skippy.net/linux/smb-howto.html"
6893 > http://www.skippy.net/linux/smb-howto.html</A
6898 >Although 2.0.7 has almost had its day as a PDC, David Bannon will
6899 keep the 2.0.7 PDC pages at <A
6900 HREF="http://bioserve.latrobe.edu.au/samba"
6902 > http://bioserve.latrobe.edu.au/samba</A
6903 > going for a while yet.</P
6907 >Misc links to CIFS information
6909 HREF="http://samba.org/cifs/"
6911 >http://samba.org/cifs/</A
6916 >NT Domains for Unix <A
6917 HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
6919 > http://mailhost.cb1.com/~lkcl/ntdom/</A
6924 >FTP site for older SMB specs:
6926 HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
6928 > ftp://ftp.microsoft.com/developr/drg/CIFS/</A
6940 >How do I get help from the mailing lists?</EM
6944 > There are a number of Samba related mailing lists. Go to <A
6945 HREF="http://samba.org"
6947 >http://samba.org</A
6948 >, click on your nearest mirror
6949 and then click on <B
6952 > and then click on <B
6954 > Samba related mailing lists</B
6958 > For questions relating to Samba TNG go to
6960 HREF="http://www.samba-tng.org/"
6962 >http://www.samba-tng.org/</A
6964 It has been requested that you don't post questions about Samba-TNG to the
6965 main stream Samba lists.</P
6967 > If you post a message to one of the lists please observe the following guide lines :
6974 > Always remember that the developers are volunteers, they are
6975 not paid and they never guarantee to produce a particular feature at
6976 a particular time. Any time lines are 'best guess' and nothing more.
6981 > Always mention what version of samba you are using and what
6982 operating system its running under. You should probably list the
6983 relevant sections of your smb.conf file, at least the options
6984 in [global] that affect PDC support.</P
6988 >In addition to the version, if you obtained Samba via
6989 CVS mention the date when you last checked it out.</P
6993 > Try and make your question clear and brief, lots of long,
6994 convoluted questions get deleted before they are completely read !
6995 Don't post html encoded messages (if you can select colour or font
7000 > If you run one of those nifty 'I'm on holidays' things when
7001 you are away, make sure its configured to not answer mailing lists.
7006 > Don't cross post. Work out which is the best list to post to
7007 and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
7008 Many people active on the lists subscribe to more
7009 than one list and get annoyed to see the same message two or more times.
7010 Often someone will see a message and thinking it would be better dealt
7011 with on another, will forward it on for you.</P
7015 >You might include <EM
7018 log files written at a debug level set to as much as 20.
7019 Please don't send the entire log but enough to give the context of the
7024 >(Possibly) If you have a complete netmon trace ( from the opening of
7025 the pipe to the error ) you can send the *.CAP file as well.</P
7029 >Please think carefully before attaching a document to an email.
7030 Consider pasting the relevant parts into the body of the message. The samba
7031 mailing lists go to a huge number of people, do they all need a copy of your
7032 smb.conf in their attach directory?</P
7039 >How do I get off the mailing lists?</EM
7043 >To have your name removed from a samba mailing list, go to the
7044 same place you went to to get on it. Go to <A
7045 HREF="http://lists.samba.org/"
7047 >http://lists.samba.org</A
7049 click on your nearest mirror and then click on <B
7055 > Samba related mailing lists</B
7058 HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
7064 > Please don't post messages to the list asking to be removed, you will just
7065 be referred to the above address (unless that process failed in some way...)
7076 >8.8. Domain Control for Windows 9x/ME</A
7085 >The following section contains much of the original
7086 DOMAIN.txt file previously included with Samba. Much of
7087 the material is based on what went into the book <EM
7089 Edition, Using Samba</EM
7090 >, by Richard Sharpe.</P
7094 >A domain and a workgroup are exactly the same thing in terms of network
7095 browsing. The difference is that a distributable authentication
7096 database is associated with a domain, for secure login access to a
7097 network. Also, different access rights can be granted to users if they
7098 successfully authenticate against a domain logon server (NT server and
7099 other systems based on NT server support this, as does at least Samba TNG now).</P
7101 >The SMB client logging on to a domain has an expectation that every other
7102 server in the domain should accept the same authentication information.
7103 Network browsing functionality of domains and workgroups is
7104 identical and is explained in BROWSING.txt. It should be noted, that browsing
7105 is totally orthogonal to logon support.</P
7107 >Issues related to the single-logon network model are discussed in this
7108 section. Samba supports domain logons, network logon scripts, and user
7109 profiles for MS Windows for workgroups and MS Windows 9X/ME clients
7110 which will be the focus of this section.</P
7112 >When an SMB client in a domain wishes to logon it broadcast requests for a
7113 logon server. The first one to reply gets the job, and validates its
7114 password using whatever mechanism the Samba administrator has installed.
7115 It is possible (but very stupid) to create a domain where the user
7116 database is not shared between servers, i.e. they are effectively workgroup
7117 servers advertising themselves as participating in a domain. This
7118 demonstrates how authentication is quite different from but closely
7119 involved with domains.</P
7121 >Using these features you can make your clients verify their logon via
7122 the Samba server; make clients run a batch file when they logon to
7123 the network and download their preferences, desktop and start menu.</P
7125 >Before launching into the configuration instructions, it is
7126 worthwhile lookingat how a Windows 9x/ME client performs a logon:</P
7133 > The client broadcasts (to the IP broadcast address of the subnet it is in)
7134 a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the
7135 NetBIOS layer. The client chooses the first response it receives, which
7136 contains the NetBIOS name of the logon server to use in the format of
7142 > The client then connects to that server, logs on (does an SMBsessetupX) and
7143 then connects to the IPC$ share (using an SMBtconX).
7148 > The client then does a NetWkstaUserLogon request, which retrieves the name
7149 of the user's logon script.
7154 > The client then connects to the NetLogon share and searches for this
7155 and if it is found and can be read, is retrieved and executed by the client.
7156 After this, the client disconnects from the NetLogon share.
7161 > The client then sends a NetUserGetInfo request to the server, to retrieve
7162 the user's home share, which is used to search for profiles. Since the
7163 response to the NetUserGetInfo request does not contain much more
7164 the user's home share, profiles for Win9X clients MUST reside in the user
7170 > The client then connects to the user's home share and searches for the
7171 user's profile. As it turns out, you can specify the user's home share as
7172 a sharename and path. For example, \\server\fred\.profile.
7173 If the profiles are found, they are implemented.
7178 > The client then disconnects from the user's home share, and reconnects to
7179 the NetLogon share and looks for CONFIG.POL, the policies file. If this is
7180 found, it is read and implemented.
7190 >8.8.1. Configuration Instructions: Network Logons</A
7193 >The main difference between a PDC and a Windows 9x logon
7194 server configuration is that</P
7200 >Password encryption is not required for a Windows 9x logon server.</P
7204 >Windows 9x/ME clients do not possess machine trust accounts.</P
7208 >Therefore, a Samba PDC will also act as a Windows 9x logon
7222 >security mode and master browsers</B
7229 >There are a few comments to make in order to tie up some
7230 loose ends. There has been much debate over the issue of whether
7231 or not it is ok to configure Samba as a Domain Controller in security
7232 modes other than <TT
7235 >. The only security mode
7236 which will not work due to technical reasons is <TT
7247 mode security is really just a variation on SMB user level security.</P
7249 >Actually, this issue is also closely tied to the debate on whether
7250 or not Samba must be the domain master browser for its workgroup
7251 when operating as a DC. While it may technically be possible
7252 to configure a server as such (after all, browsing and domain logons
7253 are two distinctly different functions), it is not a good idea to
7254 so. You should remember that the DC must register the DOMAIN#1b NetBIOS
7255 name. This is the name used by Windows clients to locate the DC.
7256 Windows clients do not distinguish between the DC and the DMB.
7257 For this reason, it is very wise to configure the Samba DC as the DMB.</P
7259 >Now back to the issue of configuring a Samba DC to use a mode other
7260 than "security = user". If a Samba host is configured to use
7261 another SMB server or DC in order to validate user connection
7262 requests, then it is a fact that some other machine on the network
7263 (the "password server") knows more about user than the Samba host.
7264 99% of the time, this other host is a domain controller. Now
7265 in order to operate in domain mode security, the "workgroup" parameter
7266 must be set to the name of the Windows NT domain (which already
7267 has a domain controller, right?)</P
7269 >Therefore configuring a Samba box as a DC for a domain that
7270 already by definition has a PDC is asking for trouble.
7271 Therefore, you should always configure the Samba DC to be the DMB
7284 >8.8.2. Configuration Instructions: Setting up Roaming User Profiles</A
7307 > Roaming profiles support is different
7308 for Win9X and WinNT.</P
7314 >Before discussing how to configure roaming profiles, it is useful to see how
7315 Win9X and WinNT clients implement these features.</P
7317 >Win9X clients send a NetUserGetInfo request to the server to get the user's
7318 profiles location. However, the response does not have room for a separate
7319 profiles location field, only the user's home share. This means that Win9X
7320 profiles are restricted to being in the user's home directory.</P
7322 >WinNT clients send a NetSAMLogon RPC request, which contains many fields,
7323 including a separate field for the location of the user's profiles.
7324 This means that support for profiles is different for Win9X and WinNT.</P
7331 >8.8.2.1. Windows NT Configuration</A
7334 >To support WinNT clients, in the [global] section of smb.conf set the
7335 following (for example):</P
7344 CLASS="PROGRAMLISTING"
7345 >logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE
7351 >The default for this option is \\%N\%U\profile, namely
7352 \\sambaserver\username\profile. The \\N%\%U service is created
7353 automatically by the [homes] service.
7354 If you are using a samba server for the profiles, you _must_ make the
7355 share specified in the logon path browseable. </P
7363 >[lkcl 26aug96 - we have discovered a problem where Windows clients can
7364 maintain a connection to the [homes] share in between logins. The
7365 [homes] share must NOT therefore be used in a profile path.]</P
7375 >8.8.2.2. Windows 9X Configuration</A
7378 >To support Win9X clients, you must use the "logon home" parameter. Samba has
7379 now been fixed so that "net use/home" now works as well, and it, too, relies
7380 on the "logon home" parameter.</P
7382 >By using the logon home parameter, you are restricted to putting Win9X
7383 profiles in the user's home directory. But wait! There is a trick you
7384 can use. If you set the following in the [global] section of your
7394 CLASS="PROGRAMLISTING"
7395 >logon home = \\%L\%U\.profiles</PRE
7401 >then your Win9X clients will dutifully put their clients in a subdirectory
7402 of your home directory called .profiles (thus making them hidden).</P
7404 >Not only that, but 'net use/home' will also work, because of a feature in
7405 Win9X. It removes any directory stuff off the end of the home directory area
7406 and only uses the server and share portion. That is, it looks like you
7407 specified \\%L\%U for "logon home".</P
7415 >8.8.2.3. Win9X and WinNT Configuration</A
7418 >You can support profiles for both Win9X and WinNT clients by setting both the
7419 "logon home" and "logon path" parameters. For example:</P
7428 CLASS="PROGRAMLISTING"
7429 >logon home = \\%L\%U\.profiles
7430 logon path = \\%L\profiles\%U</PRE
7442 >I have not checked what 'net use /home' does on NT when "logon home" is
7453 >8.8.2.4. Windows 9X Profile Setup</A
7456 >When a user first logs in on Windows 9X, the file user.DAT is created,
7457 as are folders "Start Menu", "Desktop", "Programs" and "Nethood".
7458 These directories and their contents will be merged with the local
7459 versions stored in c:\windows\profiles\username on subsequent logins,
7460 taking the most recent from each. You will need to use the [global]
7461 options "preserve case = yes", "short preserve case = yes" and
7462 "case sensitive = no" in order to maintain capital letters in shortcuts
7463 in any of the profile folders.</P
7465 >The user.DAT file contains all the user's preferences. If you wish to
7466 enforce a set of preferences, rename their user.DAT file to user.MAN,
7467 and deny them write access to this file.</P
7474 > On the Windows 95 machine, go to Control Panel | Passwords and
7475 select the User Profiles tab. Select the required level of
7476 roaming preferences. Press OK, but do _not_ allow the computer
7482 > On the Windows 95 machine, go to Control Panel | Network |
7483 Client for Microsoft Networks | Preferences. Select 'Log on to
7484 NT Domain'. Then, ensure that the Primary Logon is 'Client for
7485 Microsoft Networks'. Press OK, and this time allow the computer
7491 >Under Windows 95, Profiles are downloaded from the Primary Logon.
7492 If you have the Primary Logon as 'Client for Novell Networks', then
7493 the profiles and logon script will be downloaded from your Novell
7494 Server. If you have the Primary Logon as 'Windows Logon', then the
7495 profiles will be loaded from the local machine - a bit against the
7496 concept of roaming profiles, if you ask me.</P
7498 >You will now find that the Microsoft Networks Login box contains
7499 [user, password, domain] instead of just [user, password]. Type in
7500 the samba server's domain name (or any other domain known to exist,
7501 but bear in mind that the user will be authenticated against this
7502 domain and profiles downloaded from it, if that domain logon server
7503 supports it), user name and user's password.</P
7505 >Once the user has been successfully validated, the Windows 95 machine
7506 will inform you that 'The user has not logged on before' and asks you
7507 if you wish to save the user's preferences? Select 'yes'.</P
7509 >Once the Windows 95 client comes up with the desktop, you should be able
7510 to examine the contents of the directory specified in the "logon path"
7511 on the samba server and verify that the "Desktop", "Start Menu",
7512 "Programs" and "Nethood" folders have been created.</P
7514 >These folders will be cached locally on the client, and updated when
7515 the user logs off (if you haven't made them read-only by then :-).
7516 You will find that if the user creates further folders or short-cuts,
7517 that the client will merge the profile contents downloaded with the
7518 contents of the profile directory already on the local client, taking
7519 the newest folders and short-cuts from each set.</P
7521 >If you have made the folders / files read-only on the samba server,
7522 then you will get errors from the w95 machine on logon and logout, as
7523 it attempts to merge the local and the remote profile. Basically, if
7524 you have any errors reported by the w95 machine, check the Unix file
7525 permissions and ownership rights on the profile directory contents,
7526 on the samba server.</P
7528 >If you have problems creating user profiles, you can reset the user's
7529 local desktop cache, as shown below. When this user then next logs in,
7530 they will be told that they are logging in "for the first time".</P
7537 > instead of logging in under the [user, password, domain] dialog,
7543 > run the regedit.exe program, and look in:
7546 > HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
7549 > you will find an entry, for each user, of ProfilePath. Note the
7550 contents of this key (likely to be c:\windows\profiles\username),
7551 then delete the key ProfilePath for the required user.
7554 > [Exit the registry editor].
7561 > - before deleting the contents of the
7563 the ProfilePath (this is likely to be c:\windows\profiles\username),
7564 ask them if they have any important files stored on their desktop
7565 or in their start menu. delete the contents of the directory
7566 ProfilePath (making a backup if any of the files are needed).
7569 > This will have the effect of removing the local (read-only hidden
7570 system file) user.DAT in their profile directory, as well as the
7571 local "desktop", "nethood", "start menu" and "programs" folders.
7576 > search for the user's .PWL password-caching file in the c:\windows
7577 directory, and delete it.
7582 > log off the windows 95 client.
7587 > check the contents of the profile path (see "logon path" described
7588 above), and delete the user.DAT or user.MAN file for the user,
7589 making a backup if required.
7594 >If all else fails, increase samba's debug log levels to between 3 and 10,
7595 and / or run a packet trace program such as tcpdump or netmon.exe, and
7596 look for any error reports.</P
7598 >If you have access to an NT server, then first set up roaming profiles
7599 and / or netlogons on the NT server. Make a packet trace, or examine
7600 the example packet traces provided with NT server, and see what the
7601 differences are with the equivalent samba trace.</P
7609 >8.8.2.5. Windows NT Workstation 4.0</A
7612 >When a user first logs in to a Windows NT Workstation, the profile
7613 NTuser.DAT is created. The profile location can be now specified
7614 through the "logon path" parameter. </P
7622 >[lkcl 10aug97 - i tried setting the path to
7623 \\samba-server\homes\profile, and discovered that this fails because
7624 a background process maintains the connection to the [homes] share
7625 which does _not_ close down in between user logins. you have to
7626 have \\samba-server\%L\profile, where user is the username created
7627 from the [homes] share].</P
7631 >There is a parameter that is now available for use with NT Profiles:
7632 "logon drive". This should be set to "h:" or any other drive, and
7633 should be used in conjunction with the new "logon home" parameter.</P
7635 >The entry for the NT 4.0 profile is a _directory_ not a file. The NT
7636 help on profiles mentions that a directory is also created with a .PDS
7637 extension. The user, while logging in, must have write permission to
7638 create the full profile path (and the folder with the .PDS extension)
7639 [lkcl 10aug97 - i found that the creation of the .PDS directory failed,
7640 and had to create these manually for each user, with a shell script.
7641 also, i presume, but have not tested, that the full profile path must
7642 be browseable just as it is for w95, due to the manner in which they
7643 attempt to create the full profile path: test existence of each path
7644 component; create path component].</P
7646 >In the profile directory, NT creates more folders than 95. It creates
7647 "Application Data" and others, as well as "Desktop", "Nethood",
7648 "Start Menu" and "Programs". The profile itself is stored in a file
7649 NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
7650 its purpose is currently unknown.</P
7652 >You can use the System Control Panel to copy a local profile onto
7653 a samba server (see NT Help on profiles: it is also capable of firing
7654 up the correct location in the System Control Panel for you). The
7655 NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
7656 turns a profile into a mandatory one.</P
7664 >[lkcl 10aug97 - i notice that NT Workstation tells me that it is
7665 downloading a profile from a slow link. whether this is actually the
7666 case, or whether there is some configuration issue, as yet unknown,
7667 that makes NT Workstation _think_ that the link is a slow one is a
7668 matter to be resolved].</P
7670 >[lkcl 20aug97 - after samba digest correspondence, one user found, and
7671 another confirmed, that profiles cannot be loaded from a samba server
7672 unless "security = user" and "encrypt passwords = yes" (see the file
7673 ENCRYPTION.txt) or "security = server" and "password server = ip.address.
7674 of.yourNTserver" are used. Either of these options will allow the NT
7675 workstation to access the samba server using LAN manager encrypted
7676 passwords, without the user intervention normally required by NT
7677 workstation for clear-text passwords].</P
7679 >[lkcl 25aug97 - more comments received about NT profiles: the case of
7680 the profile _matters_. the file _must_ be called NTuser.DAT or, for
7681 a mandatory profile, NTuser.MAN].</P
7691 >8.8.2.6. Windows NT Server</A
7694 >There is nothing to stop you specifying any path that you like for the
7695 location of users' profiles. Therefore, you could specify that the
7696 profile be stored on a samba server, or any other SMB server, as long as
7697 that SMB server supports encrypted passwords.</P
7705 >8.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A
7719 >Potentially outdated or incorrect material follows</B
7726 >I think this is all bogus, but have not deleted it. (Richard Sharpe)</P
7732 >The default logon path is \\%N\U%. NT Workstation will attempt to create
7733 a directory "\\samba-server\username.PDS" if you specify the logon path
7734 as "\\samba-server\username" with the NT User Manager. Therefore, you
7735 will need to specify (for example) "\\samba-server\username\profile".
7736 NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which
7737 is more likely to succeed.</P
7739 >If you then want to share the same Start Menu / Desktop with W95, you will
7740 need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97
7741 this has its drawbacks: i created a shortcut to telnet.exe, which attempts
7742 to run from the c:\winnt\system32 directory. this directory is obviously
7743 unlikely to exist on a Win95-only host].</P
7745 > If you have this set up correctly, you will find separate user.DAT and
7746 NTuser.DAT files in the same profile directory.</P
7754 >[lkcl 25aug97 - there are some issues to resolve with downloading of
7755 NT profiles, probably to do with time/date stamps. i have found that
7756 NTuser.DAT is never updated on the workstation after the first time that
7757 it is copied to the local workstation profile directory. this is in
7758 contrast to w95, where it _does_ transfer / update profiles correctly].</P
7770 >8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A
7784 >Possibly Outdated Material</B
7791 > This appendix was originally authored by John H Terpstra of
7792 the Samba Team and is included here for posterity.
7802 The term "Domain Controller" and those related to it refer to one specific
7803 method of authentication that can underly an SMB domain. Domain Controllers
7804 prior to Windows NT Server 3.1 were sold by various companies and based on
7805 private extensions to the LAN Manager 2.1 protocol. Windows NT introduced
7806 Microsoft-specific ways of distributing the user authentication database.
7807 See DOMAIN.txt for examples of how Samba can participate in or create
7808 SMB domains based on shared authentication database schemes other than the
7811 >Windows NT Server can be installed as either a plain file and print server
7812 (WORKGROUP workstation or server) or as a server that participates in Domain
7813 Control (DOMAIN member, Primary Domain controller or Backup Domain controller).
7814 The same is true for OS/2 Warp Server, Digital Pathworks and other similar
7815 products, all of which can participate in Domain Control along with Windows NT.</P
7817 >To many people these terms can be confusing, so let's try to clear the air.</P
7819 >Every Windows NT system (workstation or server) has a registry database.
7820 The registry contains entries that describe the initialization information
7821 for all services (the equivalent of Unix Daemons) that run within the Windows
7822 NT environment. The registry also contains entries that tell application
7823 software where to find dynamically loadable libraries that they depend upon.
7824 In fact, the registry contains entries that describes everything that anything
7825 may need to know to interact with the rest of the system.</P
7827 >The registry files can be located on any Windows NT machine by opening a
7828 command prompt and typing:</P
7833 > dir %SystemRoot%\System32\config</P
7835 >The environment variable %SystemRoot% value can be obtained by typing:</P
7840 >echo %SystemRoot%</P
7842 >The active parts of the registry that you may want to be familiar with are
7843 the files called: default, system, software, sam and security.</P
7845 >In a domain environment, Microsoft Windows NT domain controllers participate
7846 in replication of the SAM and SECURITY files so that all controllers within
7847 the domain have an exactly identical copy of each.</P
7849 >The Microsoft Windows NT system is structured within a security model that
7850 says that all applications and services must authenticate themselves before
7851 they can obtain permission from the security manager to do what they set out
7854 >The Windows NT User database also resides within the registry. This part of
7855 the registry contains the user's security identifier, home directory, group
7856 memberships, desktop profile, and so on.</P
7858 >Every Windows NT system (workstation as well as server) will have its own
7859 registry. Windows NT Servers that participate in Domain Security control
7860 have a database that they share in common - thus they do NOT own an
7861 independent full registry database of their own, as do Workstations and
7864 >The User database is called the SAM (Security Access Manager) database and
7865 is used for all user authentication as well as for authentication of inter-
7866 process authentication (i.e. to ensure that the service action a user has
7867 requested is permitted within the limits of that user's privileges).</P
7869 >The Samba team have produced a utility that can dump the Windows NT SAM into
7870 smbpasswd format: see ENCRYPTION.txt for information on smbpasswd and
7871 /pub/samba/pwdump on your nearest Samba mirror for the utility. This
7872 facility is useful but cannot be easily used to implement SAM replication
7873 to Samba systems.</P
7875 >Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers
7876 can participate in a Domain security system that is controlled by Windows NT
7877 servers that have been correctly configured. Almost every domain will have
7878 ONE Primary Domain Controller (PDC). It is desirable that each domain will
7879 have at least one Backup Domain Controller (BDC).</P
7881 >The PDC and BDCs then participate in replication of the SAM database so that
7882 each Domain Controlling participant will have an up to date SAM component
7883 within its registry.</P
7890 NAME="SAMBA-LDAP-HOWTO"
7891 >Chapter 9. Storing Samba's User/Machine Account information in an LDAP Directory</A
7902 >This document describes how to use an LDAP directory for storing Samba user
7903 account information normally stored in the smbpasswd(5) file. It is
7904 assumed that the reader already has a basic understanding of LDAP concepts
7905 and has a working directory server already installed. For more information
7906 on LDAP architectures and Directories, please refer to the following sites.</P
7913 HREF="http://www.openldap.org/"
7915 >http://www.openldap.org/</A
7920 >iPlanet Directory Server - <A
7921 HREF="http://iplanet.netscape.com/directory"
7923 >http://iplanet.netscape.com/directory</A
7929 HREF="http://www.ora.com/"
7931 >O'Reilly Publishing</A
7933 a guide to LDAP for System Administrators which has a planned release date of
7934 early summer, 2002.</P
7936 >It may also be helpful to supplement the reading of the HOWTO with
7938 HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-2_2-howto.html"
7940 >Samba-PDC-LDAP-HOWTO</A
7942 maintained by Ignacio Coupeau.</P
7950 >9.2. Introduction</A
7953 >Traditionally, when configuring <A
7954 HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
7961 > file, user account
7962 information such as username, LM/NT password hashes, password change times, and account
7963 flags have been stored in the <TT
7966 > file. There are several
7967 disadvantages to this approach for sites with very large numbers of users (counted
7968 in the thousands).</P
7970 >The first is that all lookups must be performed sequentially. Given that
7971 there are approximately two lookups per domain logon (one for a normal
7972 session connection such as when mapping a network drive or printer), this
7973 is non-optimal. What is needed is an indexed approach such as is used in
7976 >The second problem is that administrators who desired to replicate a
7977 smbpasswd file to more than one Samba server were left to use external
7985 and wrote custom, in-house scripts.</P
7987 >And finally, the amount of information which is stored in an
7988 smbpasswd entry leaves no room for additional attributes such as
7989 a home directory, password expiration time, or even a Relative
7990 Identified (RID).</P
7992 >As a result of these defeciencies, a more robust means of storing user attributes
7993 used by smbd was developed. The API which defines access to user accounts
7994 is referred to as the samdb interface (previously this was called the passdb
7995 API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support
7996 for a samdb backend (e.g. <TT
8007 >) requires compile time support.</P
8009 >When compiling Samba to include the <TT
8015 option, smbd (and associated tools) will store and lookup user accounts in
8016 an LDAP directory. In reality, this is very easy to understand. If you are
8017 comfortable with using an smbpasswd file, simply replace "smbpasswd" with
8018 "LDAP directory" in all the documentation.</P
8020 >There are a few points to stress about what the <TT
8026 does not provide. The LDAP support referred to in the this documentation does not
8033 >A means of retrieving user account information from
8034 an Windows 2000 Active Directory server.</P
8038 >A means of replacing /etc/passwd.</P
8042 >The second item can be accomplished by using LDAP NSS and PAM modules. LGPL
8043 versions of these libraries can be obtained from PADL Software
8045 HREF="http://www.padl.com/"
8047 >http://www.padl.com/</A
8049 the details of configuring these packages are beyond the scope of this document.</P
8057 >9.3. Supported LDAP Servers</A
8060 >The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP
8061 2.0 server and client libraries. The same code should be able to work with
8062 Netscape's Directory Server and client SDK. However, due to lack of testing
8063 so far, there are bound to be compile errors and bugs. These should not be
8064 hard to fix. If you are so inclined, please be sure to forward all patches to
8066 HREF="samba-patches@samba.org"
8068 >samba-patches@samba.org</A
8071 HREF="jerry@samba.org"
8082 >9.4. Schema and Relationship to the RFC 2307 posixAccount</A
8085 >Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
8088 >examples/LDAP/samba.schema</TT
8089 >. (Note that this schema
8090 file has been modified since the experimental support initially included
8091 in 2.2.2). The sambaAccount objectclass is given here:</P
8100 CLASS="PROGRAMLISTING"
8101 >objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
8102 DESC 'Samba Account'
8104 MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
8105 logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
8106 displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
8107 description $ userWorkstations $ primaryGroupID ))</PRE
8113 >The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are
8114 owned by the Samba Team and as such is legal to be openly published.
8115 If you translate the schema to be used with Netscape DS, please
8116 submit the modified schema file as a patch to <A
8117 HREF="jerry@samba.org"
8122 >Just as the smbpasswd file is mean to store information which supplements a
8126 > entry, so is the sambaAccount object
8127 meant to supplement the UNIX user account information. A sambaAccount is a
8131 > objectclass so it can be stored individually
8132 in the directory. However, there are several fields (e.g. uid) which overlap
8133 with the posixAccount objectclass outlined in RFC2307. This is by design.</P
8135 >In order to store all user account information (UNIX and Samba) in the directory,
8136 it is necessary to use the sambaAccount and posixAccount objectclasses in
8137 combination. However, smbd will still obtain the user's UNIX account
8138 information via the standard C library calls (e.g. getpwnam(), et. al.).
8139 This means that the Samba server must also have the LDAP NSS library installed
8140 and functioning correctly. This division of information makes it possible to
8141 store all Samba account information in LDAP, but still maintain UNIX account
8142 information in NIS while the network is transitioning to a full LDAP infrastructure.</P
8144 >To include support for the sambaAccount object in an OpenLDAP directory
8145 server, first copy the samba.schema file to slapd's configuration directory.</P
8152 >cp samba.schema /etc/openldap/schema/</B
8155 >Next, include the <TT
8162 The sambaAccount object contains two attributes which depend upon other schema
8163 files. The 'uid' attribute is defined in <TT
8167 the 'displayName' attribute is defined in the <TT
8169 >inetorgperson.schema</TT
8171 file. Bother of these must be included before the <TT
8183 CLASS="PROGRAMLISTING"
8184 >## /etc/openldap/slapd.conf
8186 ## schema files (core.schema is required by default)
8187 include /etc/openldap/schema/core.schema
8189 ## needed for sambaAccount
8190 include /etc/openldap/schema/cosine.schema
8191 include /etc/openldap/schema/inetorgperson.schema
8192 include /etc/openldap/schema/samba.schema
8194 ## uncomment this line if you want to support the RFC2307 (NIS) schema
8195 ## include /etc/openldap/schema/nis.schema
8209 >9.5. smb.conf LDAP parameters</A
8212 >The following parameters are available in smb.conf only with <TT
8218 was included with compiling Samba.</P
8225 HREF="smb.conf.5.html#LDAPSSL"
8233 HREF="smb.conf.5.html#LDAPSERVER"
8241 HREF="smb.conf.5.html#LDAPADMINDN"
8249 HREF="smb.conf.5.html#LDAPSUFFIX"
8257 HREF="smb.conf.5.html#LDAPFILTER"
8265 HREF="smb.conf.5.html#LDAPPORT"
8272 >These are described in the <A
8273 HREF="smb.conf.5.html"
8277 page and so will not be repeated here. However, a sample smb.conf file for
8278 use with an LDAP directory could appear as</P
8287 CLASS="PROGRAMLISTING"
8288 >## /usr/local/samba/lib/smb.conf
8291 encrypt passwords = yes
8293 netbios name = TASHTEGO
8296 # ldap related parameters
8298 # define the DN to use when binding to the directory servers
8299 # The password for this DN is not stored in smb.conf. Rather it
8300 # must be set by using 'smbpasswd -w <TT
8306 # passphrase in the secrets.tdb file. If the "ldap admin dn" values
8307 # changes, this password will need to be reset.
8308 ldap admin dn = "cn=Manager,dc=samba,dc=org"
8310 # specify the LDAP server's hostname (defaults to locahost)
8311 ldap server = ahab.samba.org
8313 # Define the SSL option when connecting to the directory
8314 # ('off', 'start tls', or 'on' (default))
8315 ldap ssl = start tls
8317 # define the port to use in the LDAP session (defaults to 636 when
8321 # specify the base DN to use when searching the directory
8322 ldap suffix = "ou=people,dc=samba,dc=org"
8324 # generally the default ldap search filter is ok
8325 # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"</PRE
8337 >9.6. Security and sambaAccount</A
8340 >There are two important points to remember when discussing the security
8341 of sambaAccount entries in the directory.</P
8349 > retrieve the lmPassword or
8350 ntPassword attribute values over an unencrypted LDAP session.</P
8356 > allow non-admin users to
8357 view the lmPassword or ntPassword attribute values.</P
8361 >These password hashes are clear text equivalents and can be used to impersonate
8362 the user without deriving the original clear text strings.</P
8364 >To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
8365 to require an encrypted session (<B
8369 the default port of 636
8370 when contacting the directory server. When using an OpenLDAP 2.0 server, it
8371 is possible to use the use the StartTLS LDAP extended operation in the place of
8372 LDAPS. In either case, you are strongly discouraged to disable this security
8378 >The second security precaution is to prevent non-administrative users from
8379 harvesting password hashes from the directory. This can be done using the
8380 following ACL in <TT
8392 CLASS="PROGRAMLISTING"
8393 >## allow users to update their own password, but not to browse others
8394 access to attrs=userPassword,lmPassword,ntPassword
8402 >You may of course, add in write access to administrative DN's as necessary.</P
8413 >There are currently four sambaAccount attributes which map directly onto
8423 >smbHome -> "logon home"</P
8427 >profilePath -> "logon path"</P
8431 >homeDrive -> "logon drive"</P
8435 >scriptPath -> "logon script"</P
8439 >First of all, these parameters are only used when Samba is acting as a
8440 PDC or a domain (refer to the <A
8441 HREF="Samba-PDC-HOWTO.html"
8445 for details on how to configure Samba as a Primary Domain Controller).
8446 Furthermore, these attributes are only stored with the sambaAccount entry if
8447 the values are non-default values. For example, assume TASHTEGO has now been
8448 configured as a PDC and that <B
8450 >logon home = \\%L\%u</B
8455 > file. When a user named "becky" logons to the domain,
8461 > string is expanded to \\TASHTEGO\becky.</P
8463 >If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org",
8464 this value is used. However, if this attribute does not exist, then the value
8470 > parameter is used in its place. Samba
8471 will only write the attribute value to the directory entry is the value is
8472 something other than the default (e.g. \\MOBY\becky).</P
8480 >9.8. Example LDIF Entries for a sambaAccount</A
8483 >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
8492 CLASS="PROGRAMLISTING"
8493 >dn: uid=guest2, ou=people,dc=plainjoe,dc=org
8494 ntPassword: 878D8014606CDA29677A44EFA1353FC7
8495 pwdMustChange: 2147483647
8496 primaryGroupID: 1201
8497 lmPassword: 552902031BEDE9EFAAD3B435B51404EE
8498 pwdLastSet: 1010179124
8500 objectClass: sambaAccount
8502 kickoffTime: 2147483647
8504 logoffTime: 2147483647
8506 pwdCanChange: 0</PRE
8512 >The following is an LDIF entry for using both the sambaAccount and
8513 posixAccount objectclasses:</P
8522 CLASS="PROGRAMLISTING"
8523 >dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
8525 displayName: Gerald Carter
8526 lmPassword: 552902031BEDE9EFAAD3B435B51404EE
8527 primaryGroupID: 1201
8528 objectClass: posixAccount
8529 objectClass: sambaAccount
8531 userPassword: {crypt}BpM2ej8Rkzogo
8535 loginShell: /bin/bash
8536 logoffTime: 2147483647
8538 kickoffTime: 2147483647
8539 pwdLastSet: 1010179230
8541 homeDirectory: /home/tashtego/gcarter
8543 pwdMustChange: 2147483647
8544 ntPassword: 878D8014606CDA29677A44EFA1353FC7</PRE
8559 >Please mail all comments regarding this HOWTO to <A
8560 HREF="mailto:jerry@samba.org"
8563 >. This documents was
8564 last updated to reflect the Samba 2.2.3 release. </P
8572 >Chapter 10. Unified Logons between Windows NT and UNIX using Winbind</A
8583 >Integration of UNIX and Microsoft Windows NT through
8584 a unified logon has been considered a "holy grail" in heterogeneous
8585 computing environments for a long time. We present
8588 >, a component of the Samba suite
8589 of programs as a solution to the unified logon problem. Winbind
8590 uses a UNIX implementation
8591 of Microsoft RPC calls, Pluggable Authentication Modules, and the Name
8592 Service Switch to allow Windows NT domain users to appear and operate
8593 as UNIX users on a UNIX machine. This paper describes the winbind
8594 system, explaining the functionality it provides, how it is configured,
8595 and how it works internally.</P
8603 >10.2. Introduction</A
8606 >It is well known that UNIX and Microsoft Windows NT have
8607 different models for representing user and group information and
8608 use different technologies for implementing them. This fact has
8609 made it difficult to integrate the two systems in a satisfactory
8612 >One common solution in use today has been to create
8613 identically named user accounts on both the UNIX and Windows systems
8614 and use the Samba suite of programs to provide file and print services
8615 between the two. This solution is far from perfect however, as
8616 adding and deleting users on both sets of machines becomes a chore
8617 and two sets of passwords are required both of which
8618 can lead to synchronization problems between the UNIX and Windows
8619 systems and confusion for users.</P
8621 >We divide the unified logon problem for UNIX machines into
8622 three smaller problems:</P
8628 >Obtaining Windows NT user and group information
8633 >Authenticating Windows NT users
8638 >Password changing for Windows NT users
8643 >Ideally, a prospective solution to the unified logon problem
8644 would satisfy all the above components without duplication of
8645 information on the UNIX machines and without creating additional
8646 tasks for the system administrator when maintaining users and
8647 groups on either system. The winbind system provides a simple
8648 and elegant solution to all three components of the unified logon
8657 >10.3. What Winbind Provides</A
8660 >Winbind unifies UNIX and Windows NT account management by
8661 allowing a UNIX box to become a full member of a NT domain. Once
8662 this is done the UNIX box will see NT users and groups as if
8663 they were native UNIX users and groups, allowing the NT domain
8664 to be used in much the same manner that NIS+ is used within
8665 UNIX-only environments.</P
8667 >The end result is that whenever any
8668 program on the UNIX machine asks the operating system to lookup
8669 a user or group name, the query will be resolved by asking the
8670 NT domain controller for the specified domain to do the lookup.
8671 Because Winbind hooks into the operating system at a low level
8672 (via the NSS name resolution modules in the C library) this
8673 redirection to the NT domain controller is completely
8676 >Users on the UNIX machine can then use NT user and group
8677 names as they would use "native" UNIX names. They can chown files
8678 so that they are owned by NT domain users or even login to the
8679 UNIX machine and run a UNIX X-Window session as a domain user.</P
8681 >The only obvious indication that Winbind is being used is
8682 that user and group names take the form DOMAIN\user and
8683 DOMAIN\group. This is necessary as it allows Winbind to determine
8684 that redirection to a domain controller is wanted for a particular
8685 lookup and which trusted domain is being referenced.</P
8687 >Additionally, Winbind provides an authentication service
8688 that hooks into the Pluggable Authentication Modules (PAM) system
8689 to provide authentication via a NT domain to any PAM enabled
8690 applications. This capability solves the problem of synchronizing
8691 passwords between systems since all passwords are stored in a single
8692 location (on the domain controller).</P
8699 >10.3.1. Target Uses</A
8702 >Winbind is targeted at organizations that have an
8703 existing NT based domain infrastructure into which they wish
8704 to put UNIX workstations or servers. Winbind will allow these
8705 organizations to deploy UNIX workstations without having to
8706 maintain a separate account infrastructure. This greatly
8707 simplifies the administrative overhead of deploying UNIX
8708 workstations into a NT based organization.</P
8710 >Another interesting way in which we expect Winbind to
8711 be used is as a central part of UNIX based appliances. Appliances
8712 that provide file and print services to Microsoft based networks
8713 will be able to use Winbind to provide seamless integration of
8714 the appliance into the domain.</P
8723 >10.4. How Winbind Works</A
8726 >The winbind system is designed around a client/server
8727 architecture. A long running <B
8731 listens on a UNIX domain socket waiting for requests
8732 to arrive. These requests are generated by the NSS and PAM
8733 clients and processed sequentially.</P
8735 >The technologies used to implement winbind are described
8743 >10.4.1. Microsoft Remote Procedure Calls</A
8746 >Over the last two years, efforts have been underway
8747 by various Samba Team members to decode various aspects of
8748 the Microsoft Remote Procedure Call (MSRPC) system. This
8749 system is used for most network related operations between
8750 Windows NT machines including remote management, user authentication
8751 and print spooling. Although initially this work was done
8752 to aid the implementation of Primary Domain Controller (PDC)
8753 functionality in Samba, it has also yielded a body of code which
8754 can be used for other purposes.</P
8756 >Winbind uses various MSRPC calls to enumerate domain users
8757 and groups and to obtain detailed information about individual
8758 users or groups. Other MSRPC calls can be used to authenticate
8759 NT domain users and to change user passwords. By directly querying
8760 a Windows PDC for user and group information, winbind maps the
8761 NT account information onto UNIX user and group names.</P
8769 >10.4.2. Name Service Switch</A
8772 >The Name Service Switch, or NSS, is a feature that is
8773 present in many UNIX operating systems. It allows system
8774 information such as hostnames, mail aliases and user information
8775 to be resolved from different sources. For example, a standalone
8776 UNIX workstation may resolve system information from a series of
8777 flat files stored on the local filesystem. A networked workstation
8778 may first attempt to resolve system information from local files,
8779 and then consult a NIS database for user information or a DNS server
8780 for hostname information.</P
8782 >The NSS application programming interface allows winbind
8783 to present itself as a source of system information when
8784 resolving UNIX usernames and groups. Winbind uses this interface,
8785 and information obtained from a Windows NT server using MSRPC
8786 calls to provide a new source of account enumeration. Using standard
8787 UNIX library calls, one can enumerate the users and groups on
8788 a UNIX machine running winbind and see all users and groups in
8789 a NT domain plus any trusted domain as though they were local
8790 users and groups.</P
8792 >The primary control file for NSS is
8795 >/etc/nsswitch.conf</TT
8797 When a UNIX application makes a request to do a lookup
8798 the C library looks in <TT
8800 >/etc/nsswitch.conf</TT
8802 for a line which matches the service type being requested, for
8803 example the "passwd" service type is used when user or group names
8804 are looked up. This config line species which implementations
8805 of that service should be tried and in what order. If the passwd
8810 >passwd: files example</B
8813 >then the C library will first load a module called
8816 >/lib/libnss_files.so</TT
8820 >/lib/libnss_example.so</TT
8822 C library will dynamically load each of these modules in turn
8823 and call resolver functions within the modules to try to resolve
8824 the request. Once the request is resolved the C library returns the
8825 result to the application.</P
8827 >This NSS interface provides a very easy way for Winbind
8828 to hook into the operating system. All that needs to be done
8831 >libnss_winbind.so</TT
8836 then add "winbind" into <TT
8838 >/etc/nsswitch.conf</TT
8840 the appropriate place. The C library will then call Winbind to
8841 resolve user and group names.</P
8849 >10.4.3. Pluggable Authentication Modules</A
8852 >Pluggable Authentication Modules, also known as PAM,
8853 is a system for abstracting authentication and authorization
8854 technologies. With a PAM module it is possible to specify different
8855 authentication methods for different system applications without
8856 having to recompile these applications. PAM is also useful
8857 for implementing a particular policy for authorization. For example,
8858 a system administrator may only allow console logins from users
8859 stored in the local password file but only allow users resolved from
8860 a NIS database to log in over the network.</P
8862 >Winbind uses the authentication management and password
8863 management PAM interface to integrate Windows NT users into a
8864 UNIX system. This allows Windows NT users to log in to a UNIX
8865 machine and be authenticated against a suitable Primary Domain
8866 Controller. These users can also change their passwords and have
8867 this change take effect directly on the Primary Domain Controller.
8870 >PAM is configured by providing control files in the directory
8874 > for each of the services that
8875 require authentication. When an authentication request is made
8876 by an application the PAM code in the C library looks up this
8877 control file to determine what modules to load to do the
8878 authentication check and in what order. This interface makes adding
8879 a new authentication service for Winbind very easy, all that needs
8880 to be done is that the <TT
8888 control files for relevant services are updated to allow
8889 authentication via winbind. See the PAM documentation
8890 for more details.</P
8898 >10.4.4. User and Group ID Allocation</A
8901 >When a user or group is created under Windows NT
8902 is it allocated a numerical relative identifier (RID). This is
8903 slightly different to UNIX which has a range of numbers that are
8904 used to identify users, and the same range in which to identify
8905 groups. It is winbind's job to convert RIDs to UNIX id numbers and
8906 vice versa. When winbind is configured it is given part of the UNIX
8907 user id space and a part of the UNIX group id space in which to
8908 store Windows NT users and groups. If a Windows NT user is
8909 resolved for the first time, it is allocated the next UNIX id from
8910 the range. The same process applies for Windows NT groups. Over
8911 time, winbind will have mapped all Windows NT users and groups
8912 to UNIX user ids and group ids.</P
8914 >The results of this mapping are stored persistently in
8915 an ID mapping database held in a tdb database). This ensures that
8916 RIDs are mapped to UNIX IDs in a consistent way.</P
8924 >10.4.5. Result Caching</A
8927 >An active system can generate a lot of user and group
8928 name lookups. To reduce the network cost of these lookups winbind
8929 uses a caching scheme based on the SAM sequence number supplied
8930 by NT domain controllers. User or group information returned
8931 by a PDC is cached by winbind along with a sequence number also
8932 returned by the PDC. This sequence number is incremented by
8933 Windows NT whenever any user or group information is modified. If
8934 a cached entry has expired, the sequence number is requested from
8935 the PDC and compared against the sequence number of the cached entry.
8936 If the sequence numbers do not match, then the cached information
8937 is discarded and up to date information is requested directly
8947 >10.5. Installation and Configuration</A
8950 >Many thanks to John Trostel <A
8951 HREF="mailto:jtrostel@snapserver.com"
8953 >jtrostel@snapserver.com</A
8955 for providing the HOWTO for this section.</P
8957 >This HOWTO describes how to get winbind services up and running
8958 to control access and authenticate users on your Linux box using
8959 the winbind services which come with SAMBA 2.2.2.</P
8966 >10.5.1. Introduction</A
8969 >This HOWTO describes the procedures used to get winbind up and
8970 running on my RedHat 7.1 system. Winbind is capable of providing access
8971 and authentication control for Windows Domain users through an NT
8972 or Win2K PDC for 'regular' services, such as telnet a nd ftp, as
8973 well for SAMBA services.</P
8975 >This HOWTO has been written from a 'RedHat-centric' perspective, so if
8976 you are using another distribution, you may have to modify the instructions
8977 somewhat to fit the way your distribution works.</P
8984 >Why should I to this?</EM
8988 >This allows the SAMBA administrator to rely on the
8989 authentication mechanisms on the NT/Win2K PDC for the authentication
8990 of domain members. NT/Win2K users no longer need to have separate
8991 accounts on the SAMBA server.
8997 >Who should be reading this document?</EM
9001 > This HOWTO is designed for system administrators. If you are
9002 implementing SAMBA on a file server and wish to (fairly easily)
9003 integrate existing NT/Win2K users from your PDC onto the
9004 SAMBA server, this HOWTO is for you. That said, I am no NT or PAM
9005 expert, so you may find a better or easier way to accomplish
9017 >10.5.2. Requirements</A
9020 >If you have a samba configuration file that you are currently
9023 > If your system already uses PAM,
9030 > If you haven't already made a boot disk,
9035 >Messing with the pam configuration files can make it nearly impossible
9036 to log in to yourmachine. That's why you want to be able to boot back
9037 into your machine in single user mode and restore your
9041 > back to the original state they were in if
9042 you get frustrated with the way things are going. ;-)</P
9044 >The latest version of SAMBA (version 2.2.2 as of this writing), now
9045 includes a functioning winbindd daemon. Please refer to the
9047 HREF="http://samba.org/"
9049 >main SAMBA web page</A
9051 better yet, your closest SAMBA mirror site for instructions on
9052 downloading the source code.</P
9054 >To allow Domain users the ability to access SAMBA shares and
9055 files, as well as potentially other services provided by your
9056 SAMBA machine, PAM (pluggable authentication modules) must
9057 be setup properly on your machine. In order to compile the
9058 winbind modules, you should have at least the pam libraries resident
9059 on your system. For recent RedHat systems (7.1, for instance), that
9063 >. For best results, it is helpful to also
9064 install the development packages in <TT
9066 >pam-devel-0.74-22</TT
9075 >10.5.3. Testing Things Out</A
9078 >Before starting, it is probably best to kill off all the SAMBA
9079 related daemons running on your server. Kill off all <B
9089 > processes that may
9090 be running. To use PAM, you will want to make sure that you have the
9091 standard PAM package (for RedHat) which supplies the <TT
9095 directory structure, including the pam modules are used by pam-aware
9096 services, several pam libraries, and the <TT
9103 > entries for pam. Winbind built better
9104 in SAMBA if the pam-devel package was also installed. This package includes
9105 the header files needed to compile pam-aware applications. For instance,
9106 my RedHat system has both <TT
9112 >pam-devel-0.74-22</TT
9113 > RPMs installed.</P
9120 >10.5.3.1. Configure and compile SAMBA</A
9123 >The configuration and compilation of SAMBA is pretty straightforward.
9124 The first three steps may not be necessary depending upon
9125 whether or not you have previously built the Samba binaries.</P
9134 CLASS="PROGRAMLISTING"
9161 >./configure --with-winbind</B
9182 >This will, by default, install SAMBA in <TT
9184 >/usr/local/samba</TT
9186 See the main SAMBA documentation if you want to install SAMBA somewhere else.
9187 It will also build the winbindd executable and libraries. </P
9195 >10.5.3.2. Configure <TT
9199 winbind libraries</A
9202 >The libraries needed to run the <B
9206 through nsswitch need to be copied to their proper locations, so</P
9213 >cp ../samba/source/nsswitch/libnss_winbind.so /lib</B
9216 >I also found it necessary to make the following symbolic link:</P
9223 >ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B
9226 >Now, as root you need to edit <TT
9228 >/etc/nsswitch.conf</TT
9230 allow user and group entries to be visible from the <B
9236 >/etc/nsswitch.conf</TT
9238 this after editing:</P
9247 CLASS="PROGRAMLISTING"
9248 > passwd: files winbind
9250 group: files winbind</PRE
9257 The libraries needed by the winbind daemon will be automatically
9261 > cache the next time
9262 your system reboots, but it
9263 is faster (and you don't need to reboot) if you do it manually:</P
9270 >/sbin/ldconfig -v | grep winbind</B
9276 > available to winbindd
9277 and echos back a check to you.</P
9285 >10.5.3.3. Configure smb.conf</A
9288 >Several parameters are needed in the smb.conf file to control
9296 > These are described in more detail in
9298 HREF="winbindd.8.html"
9305 > file was modified to
9306 include the following entries in the [global] section:</P
9315 CLASS="PROGRAMLISTING"
9318 # separate domain and username with '+', like DOMAIN+username
9320 HREF="winbindd.8.html#WINBINDSEPARATOR"
9322 >winbind separator</A
9324 # use uids from 10000 to 20000 for domain users
9326 HREF="winbindd.8.html#WINBINDUID"
9330 # use gids from 10000 to 20000 for domain groups
9332 HREF="winbindd.8.html#WINBINDGID"
9336 # allow enumeration of winbind users and groups
9338 HREF="winbindd.8.html#WINBINDENUMUSERS"
9340 >winbind enum users</A
9343 HREF="winbindd.8.html#WINBINDENUMGROUP"
9345 >winbind enum groups</A
9347 # give winbind users a real shell (only needed if they have telnet access)
9349 HREF="winbindd.8.html#TEMPLATEHOMEDIR"
9351 >template homedir</A
9352 > = /home/winnt/%D/%U
9354 HREF="winbindd.8.html#TEMPLATESHELL"
9369 >10.5.3.4. Join the SAMBA server to the PDC domain</A
9372 >Enter the following command to make the SAMBA server join the
9373 PDC domain, where <TT
9379 your Windows domain and <TT
9385 a domain user who has administrative privileges in the domain.</P
9392 >/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</B
9395 >The proper response to the command should be: "Joined the domain
9407 is your DOMAIN name.</P
9415 >10.5.3.5. Start up the winbindd daemon and test it!</A
9418 >Eventually, you will want to modify your smb startup script to
9419 automatically invoke the winbindd daemon when the other parts of
9420 SAMBA start, but it is possible to test out just the winbind
9421 portion first. To start up winbind services, enter the following
9429 >/usr/local/samba/bin/winbindd</B
9432 >I'm always paranoid and like to make sure the daemon
9433 is really running...</P
9440 >ps -ae | grep winbindd</B
9443 >This command should produce output like this, if the daemon is running</P
9445 >3025 ? 00:00:00 winbindd</P
9447 >Now... for the real test, try to get some information about the
9448 users on your PDC</P
9455 >/usr/local/samba/bin/wbinfo -u</B
9459 This should echo back a list of users on your Windows users on
9460 your PDC. For example, I get the following response:</P
9469 CLASS="PROGRAMLISTING"
9475 CEO+TsInternetUser</PRE
9481 >Obviously, I have named my domain 'CEO' and my <TT
9489 >You can do the same sort of thing to get group information from
9499 CLASS="PROGRAMLISTING"
9505 >/usr/local/samba/bin/wbinfo -g</B
9510 CEO+Domain Computers
9511 CEO+Domain Controllers
9514 CEO+Enterprise Admins
9515 CEO+Group Policy Creator Owners</PRE
9521 >The function 'getent' can now be used to get unified
9522 lists of both local and PDC users and groups.
9523 Try the following command:</P
9533 >You should get a list that looks like your <TT
9537 list followed by the domain users with their new uids, gids, home
9538 directories and default shells.</P
9540 >The same thing can be done for groups with the command</P
9556 >10.5.3.6. Fix the <TT
9558 >/etc/rc.d/init.d/smb</TT
9565 > daemon needs to start up after the
9572 > daemons are running.
9573 To accomplish this task, you need to modify the <TT
9575 >/etc/init.d/smb</TT
9577 script to add commands to invoke this daemon in the proper sequence. My
9580 >/etc/init.d/smb</TT
9594 >/usr/local/samba/bin</TT
9595 > directory directly. The 'start'
9596 function in the script looks like this:</P
9605 CLASS="PROGRAMLISTING"
9608 echo -n $"Starting $KIND services: "
9609 daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
9613 echo -n $"Starting $KIND services: "
9614 daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
9618 echo -n $"Starting $KIND services: "
9619 daemon /usr/local/samba/bin/winbindd
9622 [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \
9631 >The 'stop' function has a corresponding entry to shut down the
9632 services and look s like this:</P
9641 CLASS="PROGRAMLISTING"
9644 echo -n $"Shutting down $KIND services: "
9649 echo -n $"Shutting down $KIND services: "
9654 echo -n $"Shutting down $KIND services: "
9657 [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb
9666 >If you restart the <B
9676 > daemons at this point, you
9677 should be able to connect to the samba server as a domain member just as
9678 if you were a local user.</P
9686 >10.5.3.7. Configure Winbind and PAM</A
9689 >If you have made it this far, you know that winbindd and samba are working
9690 together. If you want to use winbind to provide authentication for other
9691 services, keep reading. The pam configuration files need to be altered in
9692 this step. (Did you remember to make backups of your original
9696 > files? If not, do it now.)</P
9698 >You will need a pam module to use winbindd with these other services. This
9699 module will be compiled in the <TT
9701 >../source/nsswitch</TT
9703 by invoking the command</P
9710 >make nsswitch/pam_winbind.so</B
9720 > file should be copied to the location of
9721 your other pam security modules. On my RedHat system, this was the
9732 >cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B
9737 >/etc/pam.d/samba</TT
9738 > file does not need to be changed. I
9739 just left this fileas it was:</P
9748 CLASS="PROGRAMLISTING"
9749 >auth required /lib/security/pam_stack.so service=system-auth
9750 account required /lib/security/pam_stack.so service=system-auth</PRE
9756 >The other services that I modified to allow the use of winbind
9757 as an authentication service were the normal login on the console (or a terminal
9758 session), telnet logins, and ftp service. In order to enable these
9759 services, you may first need to change the entries in
9765 >/etc/inetd.conf</TT
9767 RedHat 7.1 uses the new xinetd.d structure, in this case you need
9768 to change the lines in <TT
9770 >/etc/xinetd.d/telnet</TT
9774 >/etc/xinetd.d/wu-ftp</TT
9784 CLASS="PROGRAMLISTING"
9800 CLASS="PROGRAMLISTING"
9808 For ftp services to work properly, you will also need to either
9809 have individual directories for the domain users already present on
9810 the server, or change the home directory template to a general
9811 directory for all domain users. These can be easily set using
9818 >template homedir</B
9824 > file can be changed
9825 to allow winbind ftp access in a manner similar to the
9830 changed to look like this:</P
9839 CLASS="PROGRAMLISTING"
9840 >auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
9841 auth sufficient /lib/security/pam_winbind.so
9842 auth required /lib/security/pam_stack.so service=system-auth
9843 auth required /lib/security/pam_shells.so
9844 account sufficient /lib/security/pam_winbind.so
9845 account required /lib/security/pam_stack.so service=system-auth
9846 session required /lib/security/pam_stack.so service=system-auth</PRE
9854 >/etc/pam.d/login</TT
9855 > file can be changed nearly the
9856 same way. It now looks like this:</P
9865 CLASS="PROGRAMLISTING"
9866 >auth required /lib/security/pam_securetty.so
9867 auth sufficient /lib/security/pam_winbind.so
9868 auth sufficient /lib/security/pam_unix.so use_first_pass
9869 auth required /lib/security/pam_stack.so service=system-auth
9870 auth required /lib/security/pam_nologin.so
9871 account sufficient /lib/security/pam_winbind.so
9872 account required /lib/security/pam_stack.so service=system-auth
9873 password required /lib/security/pam_stack.so service=system-auth
9874 session required /lib/security/pam_stack.so service=system-auth
9875 session optional /lib/security/pam_console.so</PRE
9881 >In this case, I added the <B
9883 >auth sufficient /lib/security/pam_winbind.so</B
9885 lines as before, but also added the <B
9887 >required pam_securetty.so</B
9889 above it, to disallow root logins over the network. I also added a
9892 >sufficient /lib/security/pam_unix.so use_first_pass</B
9897 > line to get rid of annoying
9898 double prompts for passwords.</P
9908 >10.6. Limitations</A
9911 >Winbind has a number of limitations in its current
9912 released version that we hope to overcome in future
9919 >Winbind is currently only available for
9920 the Linux operating system, although ports to other operating
9921 systems are certainly possible. For such ports to be feasible,
9922 we require the C library of the target operating system to
9923 support the Name Service Switch and Pluggable Authentication
9924 Modules systems. This is becoming more common as NSS and
9925 PAM gain support among UNIX vendors.</P
9929 >The mappings of Windows NT RIDs to UNIX ids
9930 is not made algorithmically and depends on the order in which
9931 unmapped users or groups are seen by winbind. It may be difficult
9932 to recover the mappings of rid to UNIX id mapping if the file
9933 containing this information is corrupted or destroyed.</P
9937 >Currently the winbind PAM module does not take
9938 into account possible workstation and logon time restrictions
9939 that may be been set for Windows NT users.</P
9949 >10.7. Conclusion</A
9952 >The winbind system, through the use of the Name Service
9953 Switch, Pluggable Authentication Modules, and appropriate
9954 Microsoft RPC calls have allowed us to provide seamless
9955 integration of Microsoft Windows NT domain users on a
9956 UNIX system. The result is a great reduction in the administrative
9957 cost of running a mixed UNIX and NT network.</P
9965 >Chapter 11. OS2 Client HOWTO</A
9981 >11.1.1. How can I configure OS/2 Warp Connect or
9982 OS/2 Warp 4 as a client for Samba?</A
9985 >A more complete answer to this question can be
9987 HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html"
9989 > http://carol.wins.uva.nl/~leeuw/samba/warp.html</A
9992 >Basically, you need three components:</P
9998 >The File and Print Client ('IBM Peer')
10003 >TCP/IP ('Internet support')
10008 >The "NetBIOS over TCP/IP" driver ('TCPBEUI')
10013 >Installing the first two together with the base operating
10014 system on a blank system is explained in the Warp manual. If Warp
10015 has already been installed, but you now want to install the
10016 networking support, use the "Selective Install for Networking"
10017 object in the "System Setup" folder.</P
10019 >Adding the "NetBIOS over TCP/IP" driver is not described
10020 in the manual and just barely in the online documentation. Start
10021 MPTS.EXE, click on OK, click on "Configure LAPS" and click
10022 on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line
10023 is then moved to 'Current Configuration'. Select that line,
10024 click on "Change number" and increase it from 0 to 1. Save this
10027 >If the Samba server(s) is not on your local subnet, you
10028 can optionally add IP names and addresses of these servers
10029 to the "Names List", or specify a WINS server ('NetBIOS
10030 Nameserver' in IBM and RFC terminology). For Warp Connect you
10031 may need to download an update for 'IBM Peer' to bring it on
10032 the same level as Warp 4. See the webpage mentioned above.</P
10040 >11.1.2. How can I configure OS/2 Warp 3 (not Connect),
10041 OS/2 1.2, 1.3 or 2.x for Samba?</A
10044 >You can use the free Microsoft LAN Manager 2.2c Client
10047 HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"
10049 > ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A
10052 HREF="http://carol.wins.uva.nl/~leeuw/lanman.html"
10054 > http://carol.wins.uva.nl/~leeuw/lanman.html</A
10056 more information on how to install and use this client. In
10057 a nutshell, edit the file \OS2VER in the root directory of
10058 the OS/2 boot partition and add the lines:</P
10067 CLASS="PROGRAMLISTING"
10077 >before you install the client. Also, don't use the
10078 included NE2000 driver because it is buggy. Try the NE2000
10079 or NS2000 driver from
10081 HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/"
10083 > ftp://ftp.cdrom.com/pub/os2/network/ndis/</A
10093 >11.1.3. Are there any other issues when OS/2 (any version)
10094 is used as a client?</A
10097 >When you do a NET VIEW or use the "File and Print
10098 Client Resource Browser", no Samba servers show up. This can
10099 be fixed by a patch from <A
10100 HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html"
10102 > http://carol.wins.uva.nl/~leeuw/samba/fix.html</A
10104 The patch will be included in a later version of Samba. It also
10105 fixes a couple of other problems, such as preserving long
10106 filenames when objects are dragged from the Workplace Shell
10107 to the Samba server. </P
10115 >11.1.4. How do I get printer driver download working
10116 for OS/2 clients?</A
10119 >First, create a share called [PRINTDRV] that is
10120 world-readable. Copy your OS/2 driver files there. Note
10121 that the .EA_ files must still be separate, so you will need
10122 to use the original install files, and not copy an installed
10123 driver from an OS/2 system.</P
10125 >Install the NT driver first for that printer. Then,
10126 add to your smb.conf a parameter, "os2 driver map =
10128 CLASS="REPLACEABLE"
10132 >". Then, in the file
10134 CLASS="REPLACEABLE"
10139 name of the NT driver name to the OS/2 driver name as
10142 ><nt driver name> = <os2 driver
10143 name>.<device name>, e.g.:
10144 HP LaserJet 5L = LASERJET.HP LaserJet 5L</P
10146 >You can have multiple drivers mapped in this file.</P
10148 >If you only specify the OS/2 driver name, and not the
10149 device name, the first attempt to download the driver will
10150 actually download the files, but the OS/2 client will tell
10151 you the driver is not available. On the second attempt, it
10152 will work. This is fixed simply by adding the device name
10153 to the mapping, after which it will work on the first attempt.
10163 >Chapter 12. HOWTO Access Samba source code via CVS</A
10171 >12.1. Introduction</A
10174 >Samba is developed in an open environment. Developers use CVS
10175 (Concurrent Versioning System) to "checkin" (also known as
10176 "commit") new source code. Samba's various CVS branches can
10177 be accessed via anonymous CVS using the instructions
10178 detailed in this chapter.</P
10180 >This document is a modified version of the instructions found at
10182 HREF="http://samba.org/samba/cvs.html"
10184 >http://samba.org/samba/cvs.html</A
10193 >12.2. CVS Access to samba.org</A
10196 >The machine samba.org runs a publicly accessible CVS
10197 repository for access to the source code of several packages,
10198 including samba, rsync and jitterbug. There are two main ways of
10199 accessing the CVS server on this host.</P
10206 >12.2.1. Access via CVSweb</A
10209 >You can access the source code via your
10210 favourite WWW browser. This allows you to access the contents of
10211 individual files in the repository and also to look at the revision
10212 history and commit logs of individual files. You can also ask for a diff
10213 listing between any two versions on the repository.</P
10216 HREF="http://samba.org/cgi-bin/cvsweb"
10218 >http://samba.org/cgi-bin/cvsweb</A
10227 >12.2.2. Access via cvs</A
10230 >You can also access the source code via a
10231 normal cvs client. This gives you much more control over you can
10232 do with the repository and allows you to checkout whole source trees
10233 and keep them up to date via normal cvs commands. This is the
10234 preferred method of access if you are a developer and not
10235 just a casual browser.</P
10237 >To download the latest cvs source code, point your
10238 browser at the URL : <A
10239 HREF="http://www.cyclic.com/"
10241 >http://www.cyclic.com/</A
10243 and click on the 'How to get cvs' link. CVS is free software under
10244 the GNU GPL (as is Samba). Note that there are several graphical CVS clients
10245 which provide a graphical interface to the sometimes mundane CVS commands.
10246 Links to theses clients are also available from http://www.cyclic.com.</P
10248 >To gain access via anonymous cvs use the following steps.
10249 For this example it is assumed that you want a copy of the
10250 samba source code. For the other source code repositories
10251 on this system just substitute the correct package name</P
10258 > Install a recent copy of cvs. All you really need is a
10259 copy of the cvs client binary.
10269 >cvs -d :pserver:cvs@samba.org:/cvsroot login</B
10273 > When it asks you for a password type <TT
10288 >cvs -d :pserver:cvs@samba.org:/cvsroot co samba</B
10292 > This will create a directory called samba containing the
10293 latest samba source code (i.e. the HEAD tagged cvs branch). This
10294 currently corresponds to the 3.0 development tree.
10297 > CVS branches other HEAD can be obtained by using the <TT
10303 and defining a tag name. A list of branch tag names can be found on the
10304 "Development" page of the samba web site. A common request is to obtain the
10305 latest 2.2 release code. This could be done by using the following command.
10310 >cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</B
10316 > Whenever you want to merge in the latest code changes use
10317 the following command from within the samba directory:
10322 >cvs update -d -P</B
10337 >Primary Domain Controller,
git.samba.org / gd / samba-autobuild / .git / blob