5.4. Migration to from Samba 2.0.x to 2.2.x6.2. Configuration Given that printer driver management has changed (we hope improved) in -2.2 over prior releases, migration from an existing setup to 2.2 can -follow several paths. Windows clients have a tendency to remember things for quite a while. -For example, if a Windows NT client has attached to a Samba 2.0 server, -it will remember the server as a LanMan printer server. Upgrading -the Samba host to 2.2 makes support for MSRPC printing possible, but -the NT client will still remember the previous setting. In order to give an NT client printing "amesia" (only necessary if you -want to use the newer MSRPC printing functionality in Samba), delete -the registry keys associated with the print server contained in -[HKLM\SYSTEM\CurrentControlSet\Control\Print]. The -spooler service on the client should be stopped prior to doing this: C:\WINNT\ > net stop spooler All the normal disclaimers about editing the registry go -here. Be careful, and know what you are doing. The spooler service should be restarted after you have finished -removing the appropriate registry entries by replacing the -stop command above with start. Windows 9x clients will continue to use LanMan printing calls -with a 2.2 Samba server so there is no need to perform any of these -modifications on non-NT clients. Achtung![print$] vs. [printer$] The following smb.conf parameters are considered to be depreciated and will -be removed soon. Do not use them in new installations Previous versions of Samba recommended using a share named [printer$]. +This name was taken from the printer$ service created by Windows 9x +clients when a printer was shared. Windows 9x printer servers always have +a printer$ service which provides read-only access via no +password in order to support printer driver downloads. However, the initial implementation allowed for a +parameter named printer driver file (G)printer driver location - +to be used on a per share basis to specify the location of +the driver files associated with that printer. Another +parameter named printer driver (S)printer driver - provided +a means of defining the printer driver name to be sent to +the client. These parameters, including printer driver location (S)printer driver +file parameter, are being depreciated and should not +be used in new installations. For more information on this change, +you should refer to the Migration section - 6.2.1. Creating [print$] In order to support the uploading of printer driver +files, you must first configure a file share named [print$]. +The name of this share is hard coded in Samba's internals so +the name is very important (print$ is the service used by +Windows NT print servers to provide support for printer driver +download). Here are the possible scenarios for supporting migration: You should modify the server's smb.conf file to add the global +parameters and to create the +following file share (of course, some of the parameter values, +such as 'path' are arbitrary and should be replaced with +appropriate values for your site): [global] + ; members of the ntadmin group should be able + ; to add drivers and set printer properties + ; root is implicitly a 'printer admin' + printer admin = @ntadmin + +[print$] + path = /usr/local/samba/printers + guest ok = yes + browseable = yes + read only = yes + ; since this share is configured as read only, then we need + ; a 'write list'. Check the file system permissions to make + ; sure this account can copy files to the share. If this + ; is setup to a non-root account, then it should also exist + ; as a 'printer admin' + write list = @ntadmin,root If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same. The write list is used to allow administrative +level user accounts to have write access in order to update files +on the share. See the smb.conf(5) +man page for more information on configuring file shares. If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The The requirement for make_printerdef - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile. guest +ok = yes depends upon how your +site is configured. If users will be guaranteed to have +an account on the Samba host, then this is a non-issue. Author's Note: The non-issue is that if all your Windows NT users are guaranteed to be +authenticated by the Samba server (such as a domain member server and the NT +user has already been validated by the Domain Controller in +order to logon to the Windows NT console), then guest access +is not necessary. Of course, in a workgroup environment where +you just want to be able to print without worrying about +silly accounts and security, then configure the share for +guest access. You'll probably want to add map to guest = Bad User in the [global] section as well. Make sure +you understand what this parameter does before using it +though. --jerry In order for a Windows NT print server to support +the downloading of driver files by multiple client architectures, +it must create subdirectories within the [print$] service +which correspond to each of the supported client architectures. +Samba follows this model as well. Next create the directory tree below the [print$] share +for each architecture you wish to support. [print$]----- + |-W32X86 ; "Windows NT x86" + |-WIN40 ; "Windows 95/98" + |-W32ALPHA ; "Windows NT Alpha_AXP" + |-W32MIPS ; "Windows NT R4000" + |-W32PPC ; "Windows NT PowerPC" ATTENTION! REQUIRED PERMISSIONS In order to currently add a new driver to you Samba host, +one of two conditions must hold true: If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location).The account used to connect to the Samba host + must have a uid of 0 (i.e. a root account) If you want to migrate an existing printers.def - file into the new setup, the current only solution is to use the Windows - NT APW to install the NT drivers and the 9x drivers. This can be scripted - using smbclient and rpcclient. See the - Imprints installation client at The account used to connect to the Samba host + must be a member of the http://imprints.sourceforge.net/ - for an example. - printer + admin list. Of course, the connected account must still possess access +to add files to the subdirectories beneath [print$]. Remember +that all file shares are set to 'read only' by default. Once you have created the required [print$] service and +associated subdirectories, simply log onto the Samba server using +a root (or printer admin) account +from a Windows NT 4.0 client. Navigate to the "Printers" folder +on the Samba server. You should see an initial listing of printers +that matches the printer shares defined on your Samba host. Chapter 6. security = domain in Samba 2.x 6.1. Joining an NT Domain with Samba 2.2 6.2.2. Setting Drivers for Existing PrintersIn order for a Samba-2 server to join an NT domain, - you must first add the NetBIOS name of the Samba server to the - NT domain on the PDC using Server Manager for Domains. This creates - the machine account in the domain (PDC) SAM. Note that you should - add the Samba server as a "Windows NT Workstation or Server", - NOT as a Primary or backup domain controller.The initial listing of printers in the Samba host's +Printers folder will have no real printer driver assigned +to them. By default, in Samba 2.2.0 this driver name was set to +NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER. +Later versions changed this to a NULL string to allow the use +tof the local Add Printer Wizard on NT/2000 clients. +Attempting to view the printer properties for a printer +which has this default driver assigned will result in +the error message: Assume you have a Samba-2 server with a NetBIOS name of - SERV1 and are joining an NT domain called - DOM, which has a PDC with a NetBIOS name - of DOMPDC and two backup domain controllers - with NetBIOS names DOMBDC1 and DOMBDC2 - . Device settings cannot be displayed. The driver +for the specified printer is not installed, only spooler +properties will be displayed. Do you want to install the +driver now? In order to join the domain, first stop all Samba daemons - and run the command:Click "No" in the error dialog and you will be presented with +the printer properties window. The way assign a driver to a +printer is to either root# smbpasswd -j DOM -r DOMPDC - as we are joining the domain DOM and the PDC for that domain - (the only machine that has write access to the domain SAM database) - is DOMPDC. If this is successful you will see the message:Use the "New Driver..." button to install + a new printer driver, or smbpasswd: Joined domain DOM. - in your terminal window. See the smbpasswd(8) man page for more details.Select a driver from the popup list of + installed drivers. Initially this list will be empty. There is existing development code to join a domain - without having to create the machine trust account on the PDC - beforehand. This code will hopefully be available soon - in release branches as well.If you wish to install printer drivers for client +operating systems other than "Windows NT x86", you will need +to use the "Sharing" tab of the printer properties dialog. This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :Assuming you have connected with a root account, you +will also be able modify other printer properties such as +ACLs and device settings using this dialog box. A few closing comments for this section, it is possible +on a Windows NT print server to have printers +listed in the Printers folder which are not shared. Samba does +not make this distinction. By definition, the only printers of +which Samba is aware are those which are specified as shares in +/usr/local/samba/private smb.conf. In Samba 2.0.x, the filename looks like this:Another interesting side note is that Windows NT clients do +not use the SMB printer share, but rather can print directly +to any printer on another Windows NT host using MS-RPC. This +of course assumes that the printing client has the necessary +privileges on the remote host serving the printer. The default +permissions assigned by Windows NT to a printer gives the "Print" +permissions to the "Everyone" well-known group. 6.2.3. Support a large number of printers <NT DOMAIN NAME>.<Samba - Server Name>.macOne issue that has arisen during the development +phase of Samba 2.2 is the need to support driver downloads for +100's of printers. Using the Windows NT APW is somewhat +awkward to say the list. If more than one printer are using the +same driver, the rpcclient's +setdriver command can be used to set the driver +associated with an installed driver. The following is example +of how this could be accomplished: +$ rpcclient pogo -U root%secret -c "enumdrivers" +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] + +[Windows NT x86] +Printer Driver Info 1: + Driver Name: [HP LaserJet 4000 Series PS] + +Printer Driver Info 1: + Driver Name: [HP LaserJet 2100 Series PS] + +Printer Driver Info 1: + Driver Name: [HP LaserJet 4Si/4SiMX PS] + +$ rpcclient pogo -U root%secret -c "enumprinters" +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] + flags:[0x800000] + name:[\\POGO\hp-print] + description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] + comment:[] + +$ rpcclient pogo -U root%secret \ +> -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] +Successfully set hp-print to driver HP LaserJet 4000 Series PS. 6.2.4. Adding New Printers via the Windows NT APW The By default, Samba offers all printer shares defined in .mac suffix stands for machine account - password file. So in our example above, the file would be called: smb.conf +in the "Printers..." folder. Also existing in this folder is the Windows NT +Add Printer Wizard icon. The APW will be show only if DOM.SERV1.mac In Samba 2.2, this file has been replaced with a TDB - (Trivial Database) file named secrets.tdb. +>The connected user is able to successfully + execute an OpenPrinterEx(\\server) with administrative + privileges (i.e. root or printer admin). This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file. Now, before restarting the Samba daemons you must - edit your smb.conf(5) - file to tell Samba it should now use domain security. Change (or add) your security =show + add printer wizard = yes line in the [global] section - of your smb.conf to read: security = domain (the default). + Next change the In order to be able to use the APW to successfully add a printer to a Samba +server, the workgroup =add +printer command line in the [global] section to read: must have a defined value. The program +hook must successfully add the printer to the system (i.e. +/etc/printcap or appropriate files) and +smb.conf if necessary. When using the APW from a client, if the named printer share does +not exist, workgroup = DOM as this is the name of the domain we are joining. You must also have the parameter smbd will execute the encrypt passwordsadd printer +command set to yes - in order for your users to authenticate to the NT PDC. Finally, add (or modify) a and reparse to the smb.conf +to attempt to locate the new printer share. If the share is still not defined, +an error of "Access Denied" is returned to the client. Note that the +password server =add printer program line in the [global] - section to read: password server = DOMPDC DOMBDC1 DOMBDC2 These are the primary and backup domain controllers Samba - will attempt to contact in order to authenticate users. Samba will - try to contact each of these servers in order, so you may want to - rearrange this list in order to spread out the authentication load - among domain controllers. Alternatively, if you want smbd to automatically determine - the list of Domain controllers to use for authentication, you may - set this line to be : password server = * This method, which was introduced in Samba 2.0.6, - allows Samba to use exactly the same mechanism that NT does. This - method either broadcasts or uses a WINS database in order to - find domain controllers to authenticate against. Finally, restart your Samba daemons and get ready for - clients to begin using domain security! 6.2. Samba and Windows 2000 Domains Many people have asked regarding the state of Samba's ability to participate in -a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows -2000 domain operating in mixed or native mode. There is much confusion between the circumstances that require a "mixed" mode -Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode -Win2k domain controller is only needed if Windows NT BDCs must exist in the same -domain. By default, a Win2k DC in "native" mode will still support -NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and -NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server. is executed under the context +of the connected user, not necessarily a root account. The steps for adding a Samba 2.2 host to a Win2k domain are the same as those -for adding a Samba server to a Windows NT 4.0 domain. The only exception is that -the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and -Computers" MMC (Microsoft Management Console) plugin. There is a complementing delete +printer command for removing entries from the "Printers..." +folder. 6.3. Why is this better than security = server? Currently, domain security in Samba doesn't free you from - having to create local Unix users to represent the users attaching - to your server. This means that if domain user DOM\fred - attaches to your domain security Samba server, there needs - to be a local Unix user fred to represent that user in the Unix - filesystem. This is very similar to the older Samba security mode - security = server, - where Samba would pass through the authentication request to a Windows - NT server in the same way as a Windows 95 or Windows 98 server would. - Please refer to the Winbind - paper for information on a system to automatically - assign UNIX uids and gids to Windows NT Domain users and groups. - This code is available in development branches only at the moment, - but will be moved to release branches soon. The advantage to domain-level security is that the - authentication in domain-level security is passed down the authenticated - RPC channel in exactly the same way that an NT server would do it. This - means Samba servers now participate in domain trust relationships in - exactly the same way NT servers do (i.e., you can add Samba servers into - a resource domain and have the authentication passed on from a resource - domain PDC to an account domain PDC. 6.2.5. Samba and Printer PortsIn addition, with security = server every Samba - daemon on a server has to keep a connection open to the - authenticating server for as long as that daemon lasts. This can drain - the connection resources on a Microsoft NT server and cause it to run - out of available connections. With security = domain, - however, the Samba daemons connect to the PDC/BDC only for as long - as is necessary to authenticate the user, and then drop the connection, - thus conserving PDC connection resources.Windows NT/2000 print servers associate a port with each printer. These normally +take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the +concept of ports associated with a printer. By default, only one printer port, +named "Samba Printer Port", exists on a system. Samba does not really a port in +order to print, rather it is a requirement of Windows clients. And finally, acting in the same manner as an NT server - authenticating to a PDC means that as part of the authentication - reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc. All - this information will allow Samba to be extended in the future into - a mode the developers currently call appliance mode. In this mode, - no local Unix users will be necessary, and Samba will generate Unix - uids and gids from the information passed back from the PDC when a - user is authenticated, making a Samba server truly plug and play - in an NT domain environment. Watch for this code soon.Note that Samba does not support the concept of "Printer Pooling" internally +either. This is when a logical printer is assigned to multiple ports as +a form of load balancing or fail over. NOTE: Much of the text of this document - was first published in the Web magazine - LinuxWorld as the article If you require that multiple ports be defined for some reason, +smb.conf possesses a Doing - the NIS/NT Samba. enumports +command which can be used to define an external program +that generates a listing of ports on a system. Chapter 7. How to Configure Samba 2.2 as a Primary Domain Controller 7.1. Prerequisite Reading6.3. The Imprints Toolset Before you continue readingin this chapter, please make sure -that you are comfortable with configuring basic files services -in smb.conf and how to enable and administrate password -encryption in Samba. Theses two topics are covered in the -smb.conf(5) -manpage and the The Imprints tool set provides a UNIX equivalent of the + Windows NT Add Printer Wizard. For complete information, please + refer to the Imprints web site at Encryption chapter -of this HOWTO Collection. http://imprints.sourceforge.net/ as well as the documentation + included with the imprints source distribution. This section will + only provide a brief introduction to the features of Imprints. 7.2. Background Note: Author's Note : This document is a combination -of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. -Both documents are superceeded by this one. 6.3.1. What is Imprints?Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). Beginning with -Samba 2.2.0, we are proud to announce official support for Windows NT 4.0 -style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through -SP1) clients. This article outlines the steps necessary for configuring Samba -as a PDC. It is necessary to have a working Samba server prior to implementing the -PDC functionality. If you have not followed the steps outlined in - UNIX_INSTALL.html, please make sure -that your server is configured correctly before proceeding. Another good -resource in the smb.conf(5) man -page. The following functionality should work in 2.2:Imprints is a collection of tools for supporting the goals + of domain logons for Windows NT 4.0/2000 clients. - Providing a central repository information + regarding Windows NT and 95/98 printer driver packages placing a Windows 9x client in user level security - Providing the tools necessary for creating + the Imprints printer driver packages. retrieving a list of users and groups from a Samba PDC to - Windows 9x/NT/2000 clients - Providing an installation client which + will obtain and install printer drivers on remote Samba + and Windows NT 4 print servers. 6.3.2. Creating Printer Driver Packages roving (roaming) user profiles - The process of creating printer driver packages is beyond + the scope of this document (refer to Imprints.txt also included + with the Samba distribution for more information). In short, + an Imprints driver package is a gzipped tarball containing the + driver files, related INF files, and a control file needed by the + installation client. 6.3.3. The Imprints server The Imprints server is really a database server that + may be queried via standard HTTP mechanisms. Each printer + entry in the database has an associated URL for the actual + downloading of the package. Each package is digitally signed + via GnuPG which can be used to verify that package downloaded + is actually the one referred in the Imprints database. It is + not recommended that this security check + be disabled. 6.3.4. The Installation Client More information regarding the Imprints installation client + is available in the Imprints-Client-HOWTO.ps + file included with the imprints source package. The Imprints installation client comes in two forms. a set of command line Perl scripts Windows NT 4.0 style system policies - a GTK+ based graphical interface to + the command line perl scripts The installation client (in both forms) provides a means + of querying the Imprints database server for a matching + list of known printer model names as well as a means to + download and install the drivers on remote Samba and Windows + NT print servers. The basic installation process is in four steps and + perl code is wrapped around smbclient + and rpcclient. Windows 2000 Service Pack 2 Clients Samba 2.2.1 is required for PDC functionality when using Windows 2000 - SP2 clients. - +foreach (supported architecture for a given driver) +{ + 1. rpcclient: Get the appropriate upload directory + on the remote server + 2. smbclient: Upload the driver files + 3. rpcclient: Issues an AddPrinterDriver() MS-RPC +} + +4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually + create the printer One of the problems encountered when implementing + the Imprints tool set was the name space issues between + various supported client architectures. For example, Windows + NT includes a driver named "Apple LaserWriter II NTX v51.8" + and Windows 95 calls its version of this driver "Apple + LaserWriter II NTX" The problem is how to know what client drivers have + been uploaded for a printer. As astute reader will remember + that the Windows NT Printer Properties dialog only includes + space for one printer driver name. A quick look in the + Windows NT 4.0 system registry at HKLM\System\CurrentControlSet\Control\Print\Environment + will reveal that Windows NT always uses the NT driver + name. This is ok as Windows NT always requires that at least + the Windows NT version of the printer driver is present. + However, Samba does not have the requirement internally. + Therefore, how can you use the NT driver name if is has not + already been installed? The way of sidestepping this limitation is to require + that all Imprints printer driver packages include both the Intel + Windows NT and 95/98 printer drivers and that NT driver is + installed first. 6.4. Migration to from Samba 2.0.x to 2.2.x The following pieces of functionality are not included in the 2.2 release:Given that printer driver management has changed (we hope improved) in +2.2 over prior releases, migration from an existing setup to 2.2 can +follow several paths. Here are the possible scenarios for +migration: Windows NT 4 domain trusts - If you do not desire the new Windows NT + print driver support, nothing needs to be done. + All existing parameters work the same. SAM replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) - If you want to take advantage of NT printer + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + printers.def file. When smbd attempts + to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The make_printerdef + tool will also remain for backwards compatibility but will + be removed in the next major release. Adding users via the User Manager for Domains - If you install a Windows 9x driver for a printer + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location). Acting as a Windows 2000 Domain Controller (i.e. Kerberos and - Active Directory) +>If you want to migrate an existing printers.def + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using smbclient and rpcclient. See the + Imprints installation client at http://imprints.sourceforge.net/ + for an example. Please note that Windows 9x clients are not true members of a domain -for reasons outlined in this article. Therefore the protocol for -support Windows 9x style domain logons is completely different -from NT4 domain logons and has been officially supported for some -time. Achtung! Implementing a Samba PDC can basically be divided into 2 broad -steps. The following smb.conf parameters are considered to +be deprecated and will be removed soon. Do not use them in new +installations Configuring the Samba PDC +>printer driver file (G) Creating machine trust accounts and joining clients - to the domain +>printer driver (S) There are other minor details such as user profiles, system -policies, etc... However, these are not necessarily specific -to a Samba PDC as much as they are related to Windows NT networking -concepts. They will be mentioned only briefly here. 7.3. Configuring the Samba Domain Controllerprinter driver location (S) + The have been two new parameters add in Samba 2.2.2 to for +better support of Samba 2.0.x backwards capability (disable +spoolss) and for using local printers drivers on Windows +NT/2000 clients (use client driver). Both of +these options are described in the smb.coinf(5) man page and are +disabled by default. Chapter 7. security = domain in Samba 2.x 7.1. Joining an NT Domain with Samba 2.2 In order for a Samba-2 server to join an NT domain, + you must first add the NetBIOS name of the Samba server to the + NT domain on the PDC using Server Manager for Domains. This creates + the machine account in the domain (PDC) SAM. Note that you should + add the Samba server as a "Windows NT Workstation or Server", + NOT as a Primary or backup domain controller. Assume you have a Samba-2 server with a NetBIOS name of + SERV1 and are joining an NT domain called + DOM, which has a PDC with a NetBIOS name + of DOMPDC and two backup domain controllers + with NetBIOS names DOMBDC1 and DOMBDC2 + . In order to join the domain, first stop all Samba daemons + and run the command: root# smbpasswd -j DOM -r DOMPDC + as we are joining the domain DOM and the PDC for that domain + (the only machine that has write access to the domain SAM database) + is DOMPDC. If this is successful you will see the message: smbpasswd: Joined domain DOM. + in your terminal window. See the smbpasswd(8) man page for more details. There is existing development code to join a domain + without having to create the machine trust account on the PDC + beforehand. This code will hopefully be available soon + in release branches as well. This command goes through the machine account password + change protocol, then writes the new (random) machine account + password for this Samba server into a file in the same directory + in which an smbpasswd file would be stored - normally : /usr/local/samba/private In Samba 2.0.x, the filename looks like this: <NT DOMAIN NAME>.<Samba + Server Name>.mac The .mac suffix stands for machine account + password file. So in our example above, the file would be called: DOM.SERV1.mac In Samba 2.2, this file has been replaced with a TDB + (Trivial Database) file named secrets.tdb. + This file is created and owned by root and is not + readable by any other user. It is the key to the domain-level + security for your system, and should be treated as carefully + as a shadow password file. Now, before restarting the Samba daemons you must + edit your smb.conf(5) + file to tell Samba it should now use domain security. Change (or add) your security = line in the [global] section + of your smb.conf to read: security = domain Next change the workgroup = line in the [global] section to read: workgroup = DOM as this is the name of the domain we are joining. You must also have the parameter encrypt passwords set to yes + in order for your users to authenticate to the NT PDC. Finally, add (or modify) a password server = line in the [global] + section to read: password server = DOMPDC DOMBDC1 DOMBDC2 These are the primary and backup domain controllers Samba + will attempt to contact in order to authenticate users. Samba will + try to contact each of these servers in order, so you may want to + rearrange this list in order to spread out the authentication load + among domain controllers. Alternatively, if you want smbd to automatically determine + the list of Domain controllers to use for authentication, you may + set this line to be : password server = * This method, which was introduced in Samba 2.0.6, + allows Samba to use exactly the same mechanism that NT does. This + method either broadcasts or uses a WINS database in order to + find domain controllers to authenticate against. Finally, restart your Samba daemons and get ready for + clients to begin using domain security! 7.2. Samba and Windows 2000 Domains Many people have asked regarding the state of Samba's ability to participate in +a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows +2000 domain operating in mixed or native mode. There is much confusion between the circumstances that require a "mixed" mode +Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode +Win2k domain controller is only needed if Windows NT BDCs must exist in the same +domain. By default, a Win2k DC in "native" mode will still support +NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and +NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server. The steps for adding a Samba 2.2 host to a Win2k domain are the same as those +for adding a Samba server to a Windows NT 4.0 domain. The only exception is that +the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and +Computers" MMC (Microsoft Management Console) plugin. 7.3. Why is this better than security = server? Currently, domain security in Samba doesn't free you from + having to create local Unix users to represent the users attaching + to your server. This means that if domain user DOM\fred + attaches to your domain security Samba server, there needs + to be a local Unix user fred to represent that user in the Unix + filesystem. This is very similar to the older Samba security mode + security = server, + where Samba would pass through the authentication request to a Windows + NT server in the same way as a Windows 95 or Windows 98 server would. + Please refer to the Winbind + paper for information on a system to automatically + assign UNIX uids and gids to Windows NT Domain users and groups. + This code is available in development branches only at the moment, + but will be moved to release branches soon. The advantage to domain-level security is that the + authentication in domain-level security is passed down the authenticated + RPC channel in exactly the same way that an NT server would do it. This + means Samba servers now participate in domain trust relationships in + exactly the same way NT servers do (i.e., you can add Samba servers into + a resource domain and have the authentication passed on from a resource + domain PDC to an account domain PDC. In addition, with security = server every Samba + daemon on a server has to keep a connection open to the + authenticating server for as long as that daemon lasts. This can drain + the connection resources on a Microsoft NT server and cause it to run + out of available connections. With security = domain, + however, the Samba daemons connect to the PDC/BDC only for as long + as is necessary to authenticate the user, and then drop the connection, + thus conserving PDC connection resources. And finally, acting in the same manner as an NT server + authenticating to a PDC means that as part of the authentication + reply, the Samba server gets the user identification information such + as the user SID, the list of NT groups the user belongs to, etc. All + this information will allow Samba to be extended in the future into + a mode the developers currently call appliance mode. In this mode, + no local Unix users will be necessary, and Samba will generate Unix + uids and gids from the information passed back from the PDC when a + user is authenticated, making a Samba server truly plug and play + in an NT domain environment. Watch for this code soon. NOTE: Much of the text of this document + was first published in the Web magazine + LinuxWorld as the article Doing + the NIS/NT Samba.

Chapter 8. How to Configure Samba 2.2 as a Primary Domain Controller 8.1. Prerequisite Reading Before you continue reading in this chapter, please make sure +that you are comfortable with configuring basic files services +in smb.conf and how to enable and administer password +encryption in Samba. Theses two topics are covered in the +smb.conf(5) +manpage and the Encryption chapter +of this HOWTO Collection. 8.2. Background Note: Author's Note : This document is a combination +of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. +Both documents are superseded by this one. Version of Samba prior to release 2.2 had marginal capabilities to +act as a Windows NT 4.0 Primary DOmain Controller (PDC). Beginning with +Samba 2.2.0, we are proud to announce official support for Windows NT 4.0 +style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through +SP1) clients. This article outlines the steps necessary for configuring Samba +as a PDC. It is necessary to have a working Samba server prior to implementing the +PDC functionality. If you have not followed the steps outlined in + UNIX_INSTALL.html, please make sure +that your server is configured correctly before proceeding. Another good +resource in the smb.conf(5) man +page. The following functionality should work in 2.2: domain logons for Windows NT 4.0/2000 clients. + placing a Windows 9x client in user level security + retrieving a list of users and groups from a Samba PDC to + Windows 9x/NT/2000 clients + roving (roaming) user profiles + Windows NT 4.0 style system policies + Windows 2000 Service Pack 2 Clients Samba 2.2.1 is required for PDC functionality when using Windows 2000 + SP2 clients. + The following pieces of functionality are not included in the 2.2 release: Windows NT 4 domain trusts + SAM replication with Windows NT 4.0 Domain Controllers + (i.e. a Samba PDC and a Windows NT BDC or vice versa) + Adding users via the User Manager for Domains + Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) + Please note that Windows 9x clients are not true members of a domain +for reasons outlined in this article. Therefore the protocol for +support Windows 9x style domain logons is completely different +from NT4 domain logons and has been officially supported for some +time. Implementing a Samba PDC can basically be divided into 2 broad +steps. Configuring the Samba PDC + Creating machine trust accounts and joining clients + to the domain + There are other minor details such as user profiles, system +policies, etc... However, these are not necessarily specific +to a Samba PDC as much as they are related to Windows NT networking +concepts. They will be mentioned only briefly here. 8.3. Configuring the Samba Domain Controller The first step in creating a working Samba PDC is to @@ -5364,16 +5903,11 @@ CLASS="FILENAME" >As Samba 2.2 does not offer a complete implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space), you should refer to the domain -admin users and domain admin group smb.conf parameters for information of creating a Domain Admins +> smb.conf parameter for information of creating "Domain Admins" style accounts.

7.4. Creating Machine Trust Accounts and Joining Clients +NAME="AEN1180" +>8.4. Creating Machine Trust Accounts and Joining Clients to the Domain A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure communication with the Domain Controller. This is a security feature -to prevent an unauthorized machine with the same netbios name from +to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group accounts. Hence a Windows 9x host is never a true member of a domain because it does not posses a machine trust account, and thus has no shared secret with the DC. Manual creation before joining the client to the domain. In this case, the password is set to a known value -- the lower case of the - machine's netbios name. + machine's NetBIOS name. 7.4.1. Manually creating machine trust accounts8.4.1. Manually creating machine trust accounts The first step in creating a machine trust account by hand is to @@ -5458,9 +5992,20 @@ CLASS="PROMPT" >/usr/sbin/useradd -g 100 -d /dev/null -c machine_nickname"machine +nickname" -s /bin/false machine_name -m -s /bin/false $ root# passwd -l machine_namemachine_name absolutely must be -the netbios name of the pc to be added to the domain. The "$" must append the netbios +the NetBIOS name of the pc to be added to the domain. The "$" must append the NetBIOS name of the pc or samba will not recognize this as a machine account Now that the UNIX account has been created, the next step is to create @@ -5539,7 +6084,7 @@ CLASS="REPLACEABLE" >machine_name is the machine's netbios +> is the machine's NetBIOS name. 7.4.2. Creating machine trust accounts "on the fly"8.4.2. Creating machine trust accounts "on the fly" The second, and most recommended way of creating machine trust accounts @@ -5615,7 +6160,7 @@ an entry in smbpasswd for . The password SHOULD be set to s different password that the +> be set to a different password that the associated /etc/passwd 7.5. Common Problems and Errors8.5. Common Problems and Errors smbpasswd -e %user%, this is normaly done, when you create an account. +>, this is normally done, when you create an account. In order to work around this problem in 2.2.0, configure the @@ -5826,8 +6371,8 @@ CLASS="SECT1" > 7.6. System Policies and Profiles8.6. System Policies and ProfilesMuch of the information necessary to implement System Policies and @@ -5890,7 +6435,7 @@ CLASS="FILENAME" CLASS="COMMAND" >servicepackname /x, - ie thats Nt4sp6ai.exe /x for service pack 6a. The policy editor, @@ -5983,8 +6528,8 @@ CLASS="SECT1" > 7.7. What other help can I get ?8.7. What other help can I get ? There are many sources of information available in the form @@ -6003,7 +6548,7 @@ general SMB topics such as browsing. One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specifiy what + You can use the -d option for both smbd and nmbd to specify what 'debug level' at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords). @@ -6059,7 +6604,7 @@ TARGET="_top" (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of netmon that ships with SMS allows for dumping packets between any two - computers (ie. placing the network interface in promiscuous mode). + computers (i.e. placing the network interface in promiscuous mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon @@ -6311,7 +6856,7 @@ TARGET="_top" > Don't cross post. Work out which is the best list to post to - and see what happens, ie don't post to both samba-ntdom and samba-technical. + and see what happens, i.e. don't post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more than one list and get annoyed to see the same message two or more times. Often someone will see a message and thinking it would be better dealt @@ -6379,8 +6924,8 @@ CLASS="SECT1" > 7.8. Domain Control for Windows 9x/ME8.8. Domain Control for Windows 9x/ME The client then connects to the user's home share and searches for the - user's profile. As it turns out, you can specify the users home share as + user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.profile. If the profiles are found, they are implemented. 7.8.1. Configuration Instructions: Network Logons8.8.1. Configuration Instructions: Network Logons To use domain logons and profiles you need to do the following: you will probabaly find that your clients automatically mount the +> you will probably find that your clients automatically mount the \\SERVER\NETLOGON share as drive z: while logging in. You can put some useful programs there to execute from the batch files. 7.8.2. Configuration Instructions: Setting up Roaming User Profiles8.8.2. Configuration Instructions: Setting up Roaming User Profiles Win9X clients send a NetUserGetInfo request to the server to get the user's profiles location. However, the response does not have room for a separate -profiles location field, only the users home share. This means that Win9X +profiles location field, only the user's home share. This means that Win9X profiles are restricted to being in the user's home directory. WinNT clients send a NetSAMLogon RPC request, which contains many fields, @@ -6751,8 +7296,8 @@ CLASS="SECT3" > 7.8.2.1. Windows NT Configuration8.8.2.1. Windows NT Configuration To support WinNT clients, inn the [global] section of smb.conf set the @@ -6795,8 +7340,8 @@ CLASS="SECT3" > 7.8.2.2. Windows 9X Configuration8.8.2.2. Windows 9X Configuration To support Win9X clients, you must use the "logon home" parameter. Samba has @@ -6835,8 +7380,8 @@ CLASS="SECT3" > 7.8.2.3. Win9X and WinNT Configuration8.8.2.3. Win9X and WinNT Configuration You can support profiles for both Win9X and WinNT clients by setting both the @@ -6873,8 +7418,8 @@ CLASS="SECT3" > 7.8.2.4. Windows 9X Profile Setup8.8.2.4. Windows 9X Profile Setup When a user first logs in on Windows 9X, the file user.DAT is created, @@ -6882,7 +7427,7 @@ as are folders "Start Menu", "Desktop", "Programs" and "Nethood". These directories and their contents will be merged with the local versions stored in c:\windows\profiles\username on subsequent logins, taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short case preserve = yes" and +options "preserve case = yes", "short preserve case = yes" and "case sensitive = no" in order to maintain capital letters in shortcuts in any of the profile folders. search for the user's .PWL password-cacheing file in the c:\windows +> search for the user's .PWL password-caching file in the c:\windows directory, and delete it. 7.8.2.5. Windows NT Workstation 4.08.8.2.5. Windows NT Workstation 4.0 When a user first logs in to a Windows NT Workstation, the profile @@ -7091,11 +7636,11 @@ case, or whether there is some configuration issue, as yet unknown, that makes NT Workstation _think_ that the link is a slow one is a matter to be resolved]. [lkcl 20aug97 - after samba digest correspondance, one user found, and +>[lkcl 20aug97 - after samba digest correspondence, one user found, and another confirmed, that profiles cannot be loaded from a samba server unless "security = user" and "encrypt passwords = yes" (see the file ENCRYPTION.txt) or "security = server" and "password server = ip.address. -of.yourNTserver" are used. either of these options will allow the NT +of.yourNTserver" are used. Either of these options will allow the NT workstation to access the samba server using LAN manager encrypted passwords, without the user intervention normally required by NT workstation for clear-text passwords]. 7.8.2.6. Windows NT Server8.8.2.6. Windows NT Server There is nothing to stop you specifying any path that you like for the @@ -7125,8 +7670,8 @@ CLASS="SECT3" > 7.8.2.7. Sharing Profiles between W95 and NT Workstation 4.08.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0 7.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba The User database is called the SAM (Security Access Manager) database and is used for all user authentication as well as for authentication of inter- -process authentication (ie: to ensure that the service action a user has +process authentication (i.e. to ensure that the service action a user has requested is permitted within the limits of that user's privileges). The Samba team have produced a utility that can dump the Windows NT SAM into @@ -7298,7 +7843,7 @@ to Samba systems. Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers can participate in a Domain security system that is controlled by Windows NT -servers that have been correctly configured. At most every domain will have +servers that have been correctly configured. Almost every domain will have ONE Primary Domain Controller (PDC). It is desirable that each domain will have at least one Backup Domain Controller (BDC). Chapter 8. Unifed Logons between Windows NT and UNIX using WinbindChapter 9. Unified Logons between Windows NT and UNIX using Winbind 8.1. Abstract9.1. Abstract Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous - computing environments for a long time. We present winbind - , a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation + computing environments for a long time. We present + winbind, a component of the Samba suite + of programs as a solution to the unified logon problem. Winbind + uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind @@ -7341,8 +7887,8 @@ CLASS="SECT1" > 8.2. Introduction9.2. Introduction It is well known that UNIX and Microsoft Windows NT have @@ -7356,11 +7902,11 @@ NAME="AEN1542" and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which which + and two sets of passwords are required both of which can lead to synchronization problems between the UNIX and Windows systems and confusion for users. We divide the unifed logon problem for UNIX machines into +>We divide the unified logon problem for UNIX machines into three smaller problems: 8.3. What Winbind Provides9.3. What Winbind Provides Winbind unifies UNIX and Windows NT account management by @@ -7409,7 +7955,7 @@ NAME="AEN1555" >The end result is that whenever any program on the UNIX machine asks the operating system to lookup a user or group name, the query will be resolved by asking the - NT domain controller for the specied domain to do the lookup. + NT domain controller for the specified domain to do the lookup. Because Winbind hooks into the operating system at a low level (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely @@ -7426,28 +7972,28 @@ NAME="AEN1555" that redirection to a domain controller is wanted for a particular lookup and which trusted domain is being referenced. Additionally, Winbind provides a authentication service +>Additionally, Winbind provides an authentication service that hooks into the Pluggable Authentication Modules (PAM) system to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing - passwords between systems as all passwords are stored in a single + passwords between systems since all passwords are stored in a single location (on the domain controller). 8.3.1. Target Uses9.3.1. Target Uses Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these organizations to deploy UNIX workstations without having to - maintain a separate account infrastructure. This greatly simplies - the administrative overhead of deploying UNIX workstations into - a NT based organization. Another interesting way in which we expect Winbind to be used is as a central part of UNIX based appliances. Appliances @@ -7461,8 +8007,8 @@ CLASS="SECT1" > 8.4. How Winbind Works9.4. How Winbind Works The winbind system is designed around a client/server @@ -7481,8 +8027,8 @@ CLASS="SECT2" > 8.4.1. Microsoft Remote Procedure Calls9.4.1. Microsoft Remote Procedure Calls Over the last two years, efforts have been underway @@ -7507,18 +8053,18 @@ CLASS="SECT2" > 8.4.2. Name Service Switch9.4.2. Name Service Switch The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information - to be resolved from dierent sources. For example, a standalone + to be resolved from different sources. For example, a standalone UNIX workstation may resolve system information from a series of - flat files stored on the local lesystem. A networked workstation + flat files stored on the local filesystem. A networked workstation may first attempt to resolve system information from local files, - then consult a NIS database for user information or a DNS server + and then consult a NIS database for user information or a DNS server for hostname information. The NSS application programming interface allows winbind @@ -7531,11 +8077,12 @@ NAME="AEN1575" a NT domain plus any trusted domain as though they were local users and groups. The primary control le for NSS is The primary control file for NSS is + /etc/nsswitch.conf - . When a UNIX application makes a request to do a lookup +>/etc/nsswitch.conf. + When a UNIX application makes a request to do a lookup the C library looks in /etc/nsswitch.conf 8.4.3. Pluggable Authentication Modules9.4.3. Pluggable Authentication Modules Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different - authentication methods for dierent system applications without + authentication methods for different system applications without having to recompile these applications. PAM is also useful for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users @@ -7605,10 +8152,10 @@ NAME="AEN1591" UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable Primary Domain Controller. These users can also change their passwords and have - this change take eect directly on the Primary Domain Controller. + this change take effect directly on the Primary Domain Controller. PAM is congured by providing control files in the directory +>PAM is configured by providing control files in the directory /etc/pam.d//lib/security/ and the pam +> and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation for more details. 8.4.4. User and Group ID Allocation9.4.4. User and Group ID Allocation When a user or group is created under Windows NT - is it allocated a numerical relative identier (RID). This is - slightly dierent to UNIX which has a range of numbers which are + is it allocated a numerical relative identifier (RID). This is + slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is congured it is given part of the UNIX + vice versa. When winbind is configured it is given part of the UNIX user id space and a part of the UNIX group id space in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is allocated the next UNIX id from @@ -7653,7 +8200,7 @@ NAME="AEN1599" to UNIX user ids and group ids. The results of this mapping are stored persistently in - a ID mapping database held in a tdb database). This ensures that + an ID mapping database held in a tdb database). This ensures that RIDs are mapped to UNIX IDs in a consistent way. 8.4.5. Result Caching9.4.5. Result Caching An active system can generate a lot of user and group - name lookups. To reduce the network cost of these lookups winbind - uses a caching scheme based on the SAM sequence number supplied - by NT domain controllers. User or group information returned - by a PDC is cached by winbind along with a sequence number also - returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modied. If - a cached entry has expired, the sequence number is requested from - the PDC and compared against the sequence number of the cached entry. - If the sequence numbers do not match, then the cached information - is discarded and up to date information is requested directly - from the PDC. 8.5. Installation and Configuration The easiest way to install winbind is by using the packages - provided in the pub/samba/appliance/ - directory on your nearest - Samba mirror. These packages provide snapshots of the Samba source - code and binaries already setup to provide the full functionality - of winbind. This setup is a little more complex than a normal Samba - build as winbind needs a small amount of functionality from a - development code branch called SAMBA_TNG. Once you have installed the packages you should read - the winbindd(8) man page which will provide you - with conguration information and give you sample conguration files. - You may also wish to update the main Samba daemons smbd and nmbd) - with a more recent development release, such as the recently - announced Samba 2.2 alpha release. 8.6. Limitations Winbind has a number of limitations in its current - released version which we hope to overcome in future - releases: Winbind is currently only available for - the Linux operating system, although ports to other operating - systems are certainly possible. For such ports to be feasible, - we require the C library of the target operating system to - support the Name Service Switch and Pluggable Authentication - Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors. The mappings of Windows NT RIDs to UNIX ids - is not made algorithmically and depends on the order in which - unmapped users or groups are seen by winbind. It may be difficult - to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed. Currently the winbind PAM module does not take - into account possible workstation and logon time restrictions - that may be been set for Windows NT users. Building winbind from source is currently - quite tedious as it requires combining source code from two Samba - branches. Work is underway to solve this by providing all - the necessary functionality in the main Samba code branch. 8.7. Conclusion The winbind system, through the use of the Name Service - Switch, Pluggable Authentication Modules, and appropriate - Microsoft RPC calls have allowed us to provide seamless - integration of Microsoft Windows NT domain users on a - UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network. Chapter 9. UNIX Permission Bits and WIndows NT Access Control Lists 9.1. Viewing and changing UNIX permissions using the NT - security dialogs New in the Samba 2.0.4 release is the ability for Windows - NT clients to use their native security settings dialog box to - view and modify the underlying UNIX permissions. Note that this ability is careful not to compromise - the security of the UNIX host Samba is running on, and - still obeys all the file permission rules that a Samba - administrator can set. In Samba 2.0.4 and above the default value of the - parameter nt acl support has been changed from - false to true, so - manipulation of permissions is turned on by default. 9.2. How to view file security on a Samba share9.5. Installation and Configuration From an NT 4.0 client, single-click with the right - mouse button on any file or directory in a Samba mounted - drive letter or UNC path. When the menu pops-up, click - on the Properties entry at the bottom of - the menu. This brings up the normal file properties dialog - box, but with Samba 2.0.4 this will have a new tab along the top - marked Security. Click on this tab and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen. Many thanks to John Trostel jtrostel@snapserver.com +for providing the HOWTO for this section. This HOWTO describes how to get winbind services up and running +to control access and authenticate users on your Linux box using +the winbind services which come with SAMBA 2.2.2. 9.3. Viewing file ownership 9.5.1. IntroductionClicking on the "Ownership" button - brings up a dialog box telling you who owns the given file. The - owner name will be of the form :This HOWTO describes the procedures used to get winbind up and +running on my RedHat 7.1 system. Winbind is capable of providing access +and authentication control for Windows Domain users through an NT +or Win2K PDC for 'regular' services, such as telnet a nd ftp, as +well for SAMBA services. This HOWTO has been written from a 'RedHat-centric' perspective, so if +you are using another distribution, you may have to modify the instructions +somewhat to fit the way your distribution works. "SERVER\user (Long name)" Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) Why should I to this? - is the discriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the Close - button to remove this dialog. If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone".This allows the SAMBA administrator to rely on the + authentication mechanisms on the NT/Win2K PDC for the authentication + of domain members. NT/Win2K users no longer need to have separate + accounts on the SAMBA server. + The Take Ownership button will not allow - you to change the ownership of this file to yourself (clicking on - it will display a dialog box complaining that the user you are - currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privilaged - operation in UNIX, available only to the root - user. As clicking on this button causes NT to attempt to change - the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time. Who should be reading this document? + There is an NT chown command that will work with Samba - and allow a user with Administrator privillage connected - to a Samba 2.0.4 server as root to change the ownership of - files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the Seclib - NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site. This HOWTO is designed for system administrators. If you are + implementing SAMBA on a file server and wish to (fairly easily) + integrate existing NT/Win2K users from your PDC onto the + SAMBA server, this HOWTO is for you. That said, I am no NT or PAM + expert, so you may find a better or easier way to accomplish + these tasks. + 9.4. Viewing file or directory permissions The third button is the "Permissions" - button. Clicking on this brings up a dialog box that shows both - the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form : 9.5.2. Requirements"SERVER\user (Long name)"If you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, BACK UP +THE /etc/pam.d directory contents! If you +haven't already made a boot disk, MAKE ON NOW! Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the discriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).Messing with the pam configuration files can make it nearly impossible +to log in to yourmachine. That's why you want to be able to boot back +into your machine in single user mode and restore your +/etc/pam.d back to the original state they were in if +you get frustrated with the way things are going. ;-) If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".The newest version of SAMBA (version 2.2.2), available from +cvs.samba.org, now include a functioning winbindd daemon. Please refer +to the main SAMBA web page or, better yet, your closest SAMBA mirror +site for instructions on downloading the source code. The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.To allow Domain users the ability to access SAMBA shares and +files, as well as potentially other services provided by your +SAMBA machine, PAM (pluggable authentication modules) must +be setup properly on your machine. In order to compile the +winbind modules, you should have at least the pam libraries resident +on your system. For recent RedHat systems (7.1, for instance), that +means 'pam-0.74-22'. For best results, it is helpful to also +install the development packages in 'pam-devel-0.74-22'. 9.4.1. File Permissions9.5.3. Testing Things Out The standard UNIX user/group/world triple and - the correspinding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL - with the 'r', 'w', and 'x' bits mapped into the corresponding - NT permissions. The UNIX world permissions are mapped into - the global NT group Everyone, followed - by the list of permissions allowed for UNIX world. The UNIX - owner and group permissions are displayed as an NT - user icon and an NT local - group icon respectively followed by the list - of permissions allowed for the UNIX user and group. As many UNIX permission sets don't map into common - NT names such as "read", "change" or "full control" then - usually the permissions will be prefixed by the words Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all "Special Access" in the NT display list. But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT smbd, +"Take Ownership" ACL attribute - (which has no meaning in UNIX) and reports a component with - no permissions as having the NT nmbd, and "O" bit set. - This was chosen of course to make it look like a zero, meaning - zero permissions. More details on the decision behind this will - be given below. winbindd processes that may +be running. To use PAM, you will want to make sure that you have the +standard PAM package (for RedHat) which supplies the /etc/pam.d +directory structure, including the pam modules are used by pam-aware +services, several pam libraries, and the /usr/doc +and /usr/man entries for pam. Winbind built better +in SAMBA if the pam-devel package was also installed. This package includes +the header files needed to compile pam-aware applications. For instance, my RedHat +system has both 'pam-0.74-22' and 'pam-devel-0.74-22' RPMs installed. 9.4.2. Directory Permissions 9.5.3.1. Configure and compile SAMBADirectories on an NT NTFS file system have two - different sets of permissions. The first set of permissions - is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" - NT style. This first set of permissions is created by Samba in - exactly the same way as normal file permissions are, described - above, and is displayed in the same way.The configuration and compilation of SAMBA is pretty straightforward. +The first three steps maynot be necessary depending upon +whether or not you have previously built the Samba binaries. The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the "inherited" permissions that any file created within - this directory would inherit. root# autoconf +root# make clean +root# rm config.cache +root# ./configure --with-winbind +root# make +root# make install Samba synthesises these inherited permissions for NT by - returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.This will, by default, install SAMBA in /usr/local/samba. See the +main SAMBA documentation if you want to install SAMBA somewhere else. +It will also build the winbindd executable and libraries. 9.5. Modifying file or directory permissions 9.5.3.2. Configure nsswitch.conf and the winbind librariesModifying file and directory permissions is as simple - as changing the displayed permissions in the dialog box, and - clicking the OK button. However, there are - limitations that a user needs to be aware of, and also interactions - with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.The libraries needed to run the winbind daemon through nsswitch +need to be copied to their proper locations, so If the parameter nt acl support - is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message. root# cp ../samba/source/nsswitch/libnss_winbind.so /lib The first thing to note is that the I also found it necessary to make the following symbolic link: root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 Now, as root you need to edit /etc/nsswitch.conf to +allow user and group entries to be visible from the "Add"winbindd - button will not return a list of users in Samba 2.0.4 (it will give - an error message of "The remote proceedure call failed - and did not execute"). This means that you can only - manipulate the current user/group/world permissions listed in - the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has. /etc/nsswitch.conf file look like this after editing: If a permission triple (either user, group, or world) - is removed from the list of permissions in the NT dialog box, - then when the "OK" button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This - allows you to add permissions back to a file or directory once - you have removed them from a triple component. passwd: files winbind + shadow: files winbind + group: files winbind As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server. +The libraries needed by the winbind daemon will be automatically +entered into the ldconfig cache the next time your system reboots, but it +is faster (and you don't need to reboot) if you do it manually: When setting permissions on a directory the second - set of permissions (in the second set of parentheses) is - by default applied to all files within that directory. If this - is not what you want you must uncheck the "Replace - permissions on existing files" checkbox in the NT - dialog before clicking "OK". root# /sbin/ldconfig -v | grep winbind If you wish to remove all permissions from a - user/group/world component then you may either highlight the - component and click the "Remove" button, - or set the component to only have the special "Take - Ownership" permission (dsplayed as This makes libnss_winbind available to winbindd +and echos back a check to you. 9.5.3.3. Configure smb.conf Several parameters are needed in the smb.conf file to control +the behavior of "O" - ) highlighted. winbindd. Configure +smb.conf These are described in more detail in +the winbindd(8) man page. My +smb.conf file was modified to +include the following entries in the [global] section: [global] + <...> + # separate domain and username with '+', like DOMAIN+username + winbind separator = + + # use uids from 10000 to 20000 for domain users + winbind uid = 10000-20000 + # use gids from 10000 to 20000 for domain groups + winbind gid = 10000-20000 + # allow enumeration of winbind users and groups + winbind enum users = yes + winbind enum groups = yes + # give winbind users a real shell (only needed if they have telnet access) + template shell = /bin/bash 9.6. Interaction with the standard Samba create mask - parameters 9.5.3.4. Join the SAMBA server to the PDC domainNote that with Samba 2.0.5 there are four new parameters - to control this interaction. These are :Enter the following command to make the SAMBA server join the +PDC domain, where DOMAIN is the name of +your Windows domain and Administrator is +a domain user who has administrative privileges in the domain. root# /usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator The proper response to the command should be: "Joined the domain +security maskDOMAIN " where DOMAIN +is your DOMAIN name.

9.5.3.5. Start up the winbindd daemon and test it! Eventually, you will want to modify your smb startup script to +automatically invoke the winbindd daemon when the other parts of +SAMBA start, but it is possible to test out just the winbind +portion first. To start up winbind services, enter the following +command as root: root# /usr/local/samba/bin/winbindd I'm always paranoid and like to make sure the daemon +is really running... root# ps -ae | grep winbindd +3025 ? 00:00:00 winbindd force security mode Now... for the real test, try to get some information about the +users on your PDCdirectory security maskroot# # /usr/local/samba/bin/wbinfo -u +This should echo back a list of users on your Windows users on +your PDC. For example, I get the following response: CEO+Administrator +CEO+burdell +CEO+Guest +CEO+jt-ad +CEO+krbtgt +CEO+TsInternetUser Obviously, I have named my domain 'CEO' and my winbindd separator is '+'. You can do the same sort of thing to get group information from +the PDC: force directory security moderoot# /usr/local/samba/bin/wbinfo -g +CEO+Domain Admins +CEO+Domain Users +CEO+Domain Guests +CEO+Domain Computers +CEO+Domain Controllers +CEO+Cert Publishers +CEO+Schema Admins +CEO+Enterprise Admins +CEO+Group Policy Creator Owners Once a user clicks "OK" to apply the - permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that - were changed that are not set to '1' in this parameter are left alone - in the file permissions. Essentially, zero bits in the security mask - mask may be treated as a set of bits the user is not - allowed to change, and one bits are those the user is allowed to change. - The function 'getent' can now be used to get unified +lists of both local and PDC users and groups. +Try the following command: If not set explicitly this parameter is set to the same value as - the create mask - parameter to provide compatibility with Samba 2.0.4 - where this permission change facility was introduced. To allow a user to - modify all the user/group/world permissions on a file, set this parameter - to 0777. root# getent passwd
Next Samba checks the changed permissions for a file against - the bits set in the force security mode parameter. Any bits - that were changed that correspond to bits set to '1' in this parameter - are forced to be set.
You should get a list that looks like your /etc/passwd +list followed by the domain users with their new uids, gids, home +directories and default shells.
Essentially, bits set in the force security mode - parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.
The same thing can be done for groups with the command
If not set explicitly this parameter is set to the same value - as the force - create mode parameter to provide compatibility - with Samba 2.0.4 where the permission change facility was introduced. - To allow a user to modify all the user/group/world permissions on a file, - with no restrictions set this parameter to 000.
root# getent group

9.5.3.6. Fix the /etc/rc.d/init.d/smb startup files

The security mask and force - security mode parameters are applied to the change - request in that order.

The winbindd daemon needs to start up after the +smbd and nmbd daemons are running. +To accomplish this task, you need to modify the /etc/init.d/smb +script to add commands to invoke this daemon in the proper sequence. My +/etc/init.d/smb file starts up smbd, +nmbd, and winbindd from the +/usr/local/samba/bin directory directly. The 'start' +function in the script looks like this:
For a directory Samba will perform the same operations as - described above for a file except using the parameter directory security mask instead of security - mask, and force directory security mode - parameter instead of force security mode -.
start() { + KIND="SMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/smbd $SMBDOPTIONS + RETVAL=$? + echo + KIND="NMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/winbindd + RETVAL3=$? + echo + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + RETVAL=1 + return $RETVAL +}
The directory security mask parameter - by default is set to the same value as the directory mask - parameter and the force directory security - mode parameter by default is set to the same value as - the force directory mode parameter to provide - compatibility with Samba 2.0.4 where the permission change facility - was introduced.
The 'stop' function has a corresponding entry to shut down the +services and look s like this:
stop() { + KIND="SMB" + echo -n $"Shutting down $KIND services: " + killproc smbd + RETVAL=$? + echo + KIND="NMB" + echo -n $"Shutting down $KIND services: " + killproc nmbd + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Shutting down $KIND services: " + killproc winbindd + RETVAL3=$? + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + echo "" + return $RETVAL +}

9.5.3.7. Configure Winbind and PAM

In this way Samba enforces the permission restrictions that - an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.

If you have made it this far, you know that winbindd is working. +Now it is time to integrate it into the operation of samba and other +services. The pam configuration files need to be altered in +this step. (Did you remember to make backups of your original +/etc/pam.d files? If not, do it now.)
If you want to set up a share that allows users full control - in modifying the permission bits on their files and directories and - doesn't force any particular bits to be set 'on', then set the following - parameters in the To get samba to allow domain users and groups, I modified the +smb.conf(5) - file in that share specific section :
/etc/pam.d/samba file from
security mask = 0777
auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_stack.so service=system-auth
force security mode = 0
to
directory security mask = 0777
auth required /lib/security/pam_winbind.so +auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth
force directory security mode = 0The other services that I modified to allow the use of winbind +as an authentication service were the normal login on the console (or a terminal +session), telnet logins, and ftp service. In order to enable these +services, you may first need to change the entries in +/etc/xinetd.d (or /etc/inetd.conf). +RedHat 7.1 uses the new xinetd.d structure, in this case you need +to change the lines in /etc/xinetd.d/telnet +and /etc/xinetd.d/wu-ftp from
enable = no
As described, in Samba 2.0.4 the parameters :
to
create mask
enable = yes
force create mode
+For ftp services to work properly, you will also need to either +have individual directories for the domain users already present on +the server, or change the home directory template to a general +directory for all domain users. These can be easily set using +the smb.conf global entry +template homedir.
directory maskThe /etc/pam.d/ftp file can be changed +to allow winbind ftp access in a manner similar to the +samba file. My /etc/pam.d/ftp file was +changed to look like this:
auth sufficient /lib/security/pam_winbind.so +auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_shells.so +account required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth
force directory modeThe /etc/pam.d/login file can be changed nearly the +same way. It now looks like this:
auth required /lib/security/pam_securetty.so +auth sufficient /lib/security/pam_winbind.so +auth sufficient /lib/security/pam_unix.so use_first_pass +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_nologin.so +account sufficient /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth +password required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth +session optional /lib/security/pam_console.so
were used instead of the parameters discussed here.
In this case, I added the auth sufficient /lib/security/pam_winbind.so +lines as before, but also added the required pam_securetty.so +above it, to disallow root logins over the network. I also added a +sufficient /lib/security/pam_unix.so use_first_pass +line after the winbind.so line to get rid of annoying +double prompts for passwords.
Finally, don't forget to copy the winbind pam modules from +the source directory in which you originally compiled the new +SAMBA up to the /lib/security directory so that pam can use it:
root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security

9.7. Interaction with the standard Samba file attribute - mapping9.6. Limitations

Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can - be a conflict between the permission bits set via the security - dialog and the permission bits set by the file attribute mapping. -

Winbind has a number of limitations in its current + released version that we hope to overcome in future + releases:
One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard - file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.
What this can mean is that if the owner changes the permissions - to allow themselves read access using the security dialog, clicks - "OK" to get back to the standard attributes tab - dialog, and then clicks "OK" on that dialog, then - NT will set the file permissions back to read-only (as that is what - the attributes still say in the dialog). This means that after setting - permissions and clicking "OK" to get back to the - attributes dialog you should always hit "Cancel" - rather than "OK" to ensure that your changes - are not overridden.
Winbind is currently only available for + the Linux operating system, although ports to other operating + systems are certainly possible. For such ports to be feasible, + we require the C library of the target operating system to + support the Name Service Switch and Pluggable Authentication + Modules systems. This is becoming more common as NSS and + PAM gain support among UNIX vendors.
The mappings of Windows NT RIDs to UNIX ids + is not made algorithmically and depends on the order in which + unmapped users or groups are seen by winbind. It may be difficult + to recover the mappings of rid to UNIX id mapping if the file + containing this information is corrupted or destroyed.
Currently the winbind PAM module does not take + into account possible workstation and logon time restrictions + that may be been set for Windows NT users.

9.7. Conclusion

The winbind system, through the use of the Name Service + Switch, Pluggable Authentication Modules, and appropriate + Microsoft RPC calls have allowed us to provide seamless + integration of Microsoft Windows NT domain users on a + UNIX system. The result is a great reduction in the administrative + cost of running a mixed UNIX and NT network.

VERSION AUTHOR The original rpcclient man page was written by Matthew - Geddes, Luke Kenneth Casson, and rewriten by Gerald Carter. + Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. yes. The client's netbios name and any previously +>The client's NetBIOS name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding user. abort shutdown script add machine script disable spoolss hide unreadable large readwrite shutdown script utmp winbind enum users winbind enum groups COMPLETE LIST OF SERVICE PARAMETERS share modes useruse client driver usernameuser usersusername

utmpusers

EXPLANATION OF EACH PARAMETER

abort shutdown script (G) This parameter only exists in the HEAD cvs branch + This a full path name to a script called by + smbd(8) that + should stop a shutdown procedure issued by the shutdown script. This command will be run as user. Default: None. Example: abort shutdown script = /sbin/shutdown -c add printer command (G) For a Samba host this means that the printer must be - physically added to underlying printing system. The add @@ -4521,6 +4657,37 @@ CLASS="COMMAND" > add machine script (G) This is the full pathname to a script that will + be run by smbd(8) when a machine is added + to it's domain using the administrator username and password method. This option is only required when using sam back-ends tied to the + Unix uid method of RID calculation such as smbpasswd. This option is only + available in Samba 3.0. Default: add machine script = <empty string> + Example: add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u + add user script (G) domain. If it is set to no, then attempts to connect to a resource from - a domain or workgroup other than the one which smbd is running + a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication. annouce version (G)announce version (G) This specifies the major and minor version numbers @@ -4797,7 +4968,7 @@ NAME="ANNOUNCEVERSION" > Default: announce version = 4.2announce version = 4.5 Example: This global parameter allows the Samba admin - to limit what interfaces on a machine will serve smb requests. If + to limit what interfaces on a machine will serve SMB requests. If affects file service If this parameter is set to Falsefalse, then Samba 2.2 will behave as previous versions of Samba would and will fail the lock request immediately if the lock range @@ -5362,7 +5533,11 @@ NAME="CHARACTERSET" >character set (G) This allows a smbd to map incoming filenames +>This allows smbd to map incoming filenames from a DOS Code page (see the client @@ -5749,7 +5924,7 @@ CLASS="COMMAND" >codingsystem (G)coding system (G) This parameter is used to determine how incoming @@ -6137,7 +6312,11 @@ NAME="DEBUGPID" >When using only one log file for more then one - forked smbd-process there may be hard to follow which process + forked smbd-process there may be hard to follow which process outputs which message. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on.delete share +>add share commandchange - share. @@ -6763,13 +6942,16 @@ CLASS="PARAMETER" > - option). If this option is set to False (the default) then if a vetoed + option). If this option is set to false (the default) then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail. This is usually what you want.If this option is set to Truetrue, then Samba will attempt to recursively delete any files and directories within the vetoed directory. This can be useful for integration with file @@ -7080,7 +7262,10 @@ NAME="DIRECTORYSECURITYMASK" Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave - it as the default of 0777. 0777. See also the disable spoolss (G) Enabling this parameter will disables Samba's support + for the SPOOLSS set of MS-RPC's and will yield identical behavior + as Samba 2.0.x. Windows NT/2000 clients will downgrade to using + Lanman style printing commands. Windows 9x/ME will be uneffected by + the parameter. However, this will also disable the ability to upload + printer drivers to a Samba server via the Windows NT Add Printer + Wizard or by using the NT printer properties dialog window. It will + also disable the capability of Windows NT/2000 clients to download + print drivers from the Samba host upon demand. + Be very careful about enabling this parameter. + See also use client driver + Default : disable spoolss = no dns proxy (G) domain logons (G)If set to true, the Samba server will serve +>If set to true, the Samba server will serve Windows 95/98 Domain logons for the The default behavior in Samba is to provide - UNIX-like behavor where only the owner of a file/directory is + UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it. However, this behavior is often confusing to DOS/Windows users. Enabling this parameter allows a user who has write access to the file (by whatever @@ -7516,8 +7736,12 @@ CLASS="COMMAND" > is acting on behalf of is not the file owner. Setting this option to True allows DOS semantics and smbd will change the file +> true allows DOS semantics and smbd will change the file timestamp as DOS requires. Default: This option enables a couple of enhancements to - cross-subnet browse propogation that have been added in Samba + cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations. - These enhancements are currently only available in - the HEAD Samba CVS tree (not Samba 2.2.x). The first enhancement to browse propogation consists of a regular +>The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, - followed by a browse synchronisation with each of the returned + followed by a browse synchronization with each of the returned DMBs. The second enhancement consists of a regular randomised browse - synchronisation with all currently known DMBs. You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists. Due to the restrictions @@ -7609,7 +7830,7 @@ NAME="ENHANCEDBROWSING" to stay around forever which can be annoying. In general you should leave this option enabled as it makes - cross-subnet browse propogation much more reliable.Default: to true. to true.See also the parameter to true. to true.See also the parameter parameter is set to Falsefalse. Default: hide unreadable (S) This parameter prevents clients from seeing the + existance of files that cannot be read. Defaults to off. Default: hide unreadable = no homedir map (G) is Truetrue, and hosts equiv may be useful for NT clients which will - not supply passwords to samba. NOTE : This can be particularly useful on large systems with - many users, perhaps several thousand,to allow a single [homes] + many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user.
See also &+group"&+group means check the NIS netgroup database, followed by the UNIX group database (the @@ -9249,12 +9491,9 @@ CLASS="COMMAND" >This parameter defaults to on on systems - that have the support, and off on systems that - don't. You should never need to touch this parameter.
, but is translated + to a no-op on systems that no not have the necessary kernel support. + You should never need to touch this parameter.
See also the lanman auth (G)
This parameter determines whether or not smbd will - attempt to authentication users using the LANMAN password hash. +>This parameter determines whether or not smbd will + attempt to authenticate users using the LANMAN password hash. If disabled, only clients which support NT password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.
large readwrite (G)
This parameter determines whether or not smbd + supports the new 64k streaming read and write varient SMB requests introduced + with Windows 2000. Note that due to Windows 2000 client redirector bugs + this requires Samba to be running on a 64-bit capable operating system such + as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with + Windows 2000 clients. Defaults to off. Not as tested as some other Samba + code paths. +
Default : large readwrite = no
level2 oplocks (S)
parameter must be set to "true" on this share in order for +> parameter must be set to true on this share in order for this parameter to have any effect.
See also the to try and become a local master browser on a subnet. If set to Falsefalse then nmbd will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By - default this value is set to true. Setting this value to true doesn't + default this value is set to true. Setting this value to true doesn't mean that Samba will become the local master @@ -9562,7 +9839,10 @@ CLASS="COMMAND" > participate in elections for local master browser.
Setting this value to False will cause Setting this value to false will cause nmbd @@ -9653,7 +9933,7 @@ CLASS="COMMAND" filesystems which may not need locking (such as - cdrom drives), although setting this parameter of no @@ -9783,7 +10063,7 @@ CLASS="COMMAND" in a NetUserGetInfo request. Win9X clients truncate the info to \\server\share when a user does net use /home"net use /home but use the whole string when dealing with profiles.
The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT - client. The share must be writeable when the logs in for the first + client. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories.
This parameter specifies the batch file (.bat) or NT command file (.cmd) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS - style cr/lf line endings. Using a DOS-style editor to create the + style CR/LF line endings. Using a DOS-style editor to create the file is recommended.
The script must be a relative path to the [netlogon] @@ -9937,7 +10217,7 @@ CLASS="FILENAME" >/usr/local/samba/netlogon/STARTUP.BAT
The contents of the batch file is entirely your choice. A +>The contents of the batch file are entirely your choice. A suggested command would be to add NET TIME \\SERVER /SET @@ -9994,7 +10274,7 @@ CLASS="PARAMETER" >%p is given then the printername +> is given then the printer name is put in its place. A printing = hpux +>printing=hpux), if the %p is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
%p is given then the printername +> is given then the printer name is put in its place. A %p is given then the printername +> is given then the printer name is put in its place. A machine password timeout (G)
If a Samba server is a member of an Windows +>If a Samba server is a member of a Windows NT Domain (see thesecurity = domain
Scripts executed in this way will be deleted upon - completion assuming that the user has the appripriate level - of priviledge and the ile permissions allow the deletion.
If the script generates output, output will be sent to the file specified by the
This is for those who want to directly map UNIX - file names which can not be represented on Windows/DOS. The mangling + file names which cannot be represented on Windows/DOS. The mangling of names is not always what is needed. In particular you may have documents with file extensions that differ between DOS and UNIX. For example, under UNIX it is common to use ;1 off the ends of filenames on some CDROMS (only visible +> off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).
Default:
The larger this value, the more likely it is that mangled names can be successfully converted to correct long UNIX names. - However, large stack sizes will slow most directory access. Smaller + However, large stack sizes will slow most directory accesses. Smaller stacks save memory in the server (each stack element costs 256 bytes).
It is not possible to absolutely guarantee correct long - file names, so be prepared for some surprises!
Default:
This option controls the maximum number of - outstanding simultaneous SMB operations that samba tells the client + outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.
Default: processes concurrently running on a system and is intended - as a stop gap to prevent degrading service to clients in the event + as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections. Remember that under normal operating - conditions, each user will have an smbd associated with him or her + conditions, each user will have an smbd associated with him or her to handle connections to all shares from a given host.
. That's why I have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover - after 30secs, hopefully).
All messages are delivered as the global guest user. The command takes the standard substitutions, although
Default: name resolve order = lmhosts wins host bcast +>name resolve order = lmhosts host wins bcast
obey pam restrictions (G)
When Samba 2.2 is configure to enable PAM support +>When Samba 2.2 is configured to enable PAM support (i.e. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only @@ -12190,7 +12474,11 @@ TARGET="_top" improve the efficiency of the granting of oplocks under multiple client contention for the same file.
In brief it specifies a number, which causes smbd not to +>In brief it specifies a number, which causes smbd not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit. This causes oplocks (S)
This boolean option tells smbd whether to +>This boolean option tells smbd whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve the speed of access to files on Samba servers. It allows the clients @@ -12338,7 +12629,7 @@ NAME="OS2DRIVERMAP" name>.<device name>
For example, a valid entry using the HP LaserJet 5 - printer driver woudl appear as HP LaserJet 5L = LASERJET.HP LaserJet 5L
With the addition of better PAM support in Samba 2.2, - this parameter, it is possible to use PAM's password change control - flag for Samba. If enabled, then PAM will be used for password - changes when requested by an SMB client, and the passwd program. + It should be possible to enable this without changing your + passwd chat must be - be changed to work with the pam prompts. -
+ parameter for most setups. + Default: smbd and the local password changing - program to change the users password. The string describes a + program to change the user's password. The string describes a sequence of response-receive pairs thatThe string can contain the macros Note that this parameter only is only used if the %ounix + password sync - and parameter is set to yes. This + sequence is then called AS ROOT when the SMB password + in the smbpasswd file is being changed, without access to the old + password cleartext. This means that root must be able to reset the user's password + without knowing the text of the previous password. In the presence of NIS/YP, + this means that the passwd program must be + executed on the NIS master. + The string can contain the macro %n which are substituted for the old - and new passwords respectively. It can also contain the standard +> which is substituted + for the new password. The chat sequence can also contain the standard macros \n \t and %s\s to give line-feed, - carriage-return, tab and space. The string can also contain a '*' which matches - any sequence of characters. Double quotes can be used to collect strings with spaces + carriage-return, tab and space. The chat sequence string can also contain + a '*' which matches any sequence of characters. + Double quotes can be used to collect strings with spaces in them into a single string. If the send string in any part of the chat sequence - is a fullstop ".", then no string is sent. Similarly, - if the expect string is a fullstop then no string is expected. Note that if the unix - password sync parameter is set to true, then this - sequence is called AS ROOT when the SMB password - in the smbpasswd file is being changed, without access to the old - password cleartext. In this case the old password cleartext is set - to "" (the empty string). Also, if the If the pam - password change parameter is set to true, then the - chat sequence should consist of three elements. The first element should - match the pam prompt for the old password, the second element should match - the pam prompt for the first request for the new password, and the final - element should match the pam prompt for the second request for the new password. - These matches are done case insentively. Under most conditions this change - is done as root so the prompt for the old password will never be matched. - parameter is set to true, the chat pairs + may be matched in any order, and sucess is determined by the PAM result, + not any particular output. The \n macro is ignored for PAM conversions. +See also passwd program and should - be turned off after this has been done. This parameter is off by - default.
pam password change + paramter is set. This parameter is off by default.
See also <See also passwd chat - , pam password change + , passwd program - .
Default: parameter is set to True +>true then this program is called AS ROOT is set to Falsefalse.
See also
An interesting example may be do unmount server +>An interesting example may be to unmount server resources:
This parameter forces a printer to interpret - the print files as postscript. This is done by adding a %! is a preferred master browser for its workgroup.
If this is set to true, on startup, If this is set to true, on startup, nmbd @@ -13708,17 +14027,15 @@ NAME="PRINTERDRIVER" >
Note :This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in - PRINTER_DRIVER2.txt in the docs - of the Samba distribution for more information + the Samba 2.2. Printing + HOWTO for more information on the new method of loading printer drivers onto a Samba server.
Note :This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in - PRINTER_DRIVER2.txt in the docs - of the Samba distribution for more information + the Samba 2.2. Printing + HOWTO for more information on the new method of loading printer drivers onto a Samba server.
files found on the Windows 95 client system. For more details on setting up serving of printer drivers to Windows 95 - clients, see the documentation file in the docs/ @@ -13841,17 +14156,15 @@ NAME="PRINTERDRIVERLOCATION" >
Note :This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in - PRINTER_DRIVER2.txt in the docs - of the Samba distribution for more information + the Samba 2.2. Printing + HOWTO for more information on the new method of loading printer drivers onto a Samba server.
Where MACHINE is the NetBIOS name of your Samba server, and PRINTER$ is a share you set up for serving printer driver - files. For more details on setting this up see the documentation + files. For more details on setting this up see the outdated documentation file in the docs/lprm command if specified in the - [global]f> section.
Currently eight printing styles are supported. They are
This parameter specifies the command to be - executed on the server host in order to pause the printerqueue.
This command should be a program or script which takes - a printer name as its only parameter and stops the printerqueue, + a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer.
This command is not supported by Windows for Workgroups, - but can be issued from the Printer's window under Windows 95 + but can be issued from the Printers window under Windows 95 and NT.
If a %p is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
This parameter specifies the command to be - executed on the server host in order to resume the printerqueue. It + executed on the server host in order to resume the printer queue. It is the command to undo the behavior that is caused by the previous parameter ().
This command should be a program or script which takes - a printer name as its only parameter and resumes the printerqueue, + a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer.
This command is not supported by Windows for Workgroups, - but can be issued from the Printer's window under Windows 95 + but can be issued from the Printers window under Windows 95 and NT.
If a %p is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
the above line would cause nmbd to announce itself +>the above line would cause nmbd to announce itself to the two given IP addresses using the given workgroup names. If you leave out the workgroup name then the one given in the nmbd(8) to periodically request - synchronization of browse lists with the master browser of a samba + synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This - is done in a manner that does not work with any non-samba servers.
This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse @@ -14447,7 +14763,7 @@ CLASS="COMMAND" of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it - is in fact the browse master on it's segment.
Default: restrict acl with mask (S)
This is a boolean parameter. If set to false (default), then - Creation of files with access control lists (ACLS) and modification of ACLs +>This is a boolean parameter. If set to false (default), then + creation of files with access control lists (ACLS) and modification of ACLs using the Windows NT/2000 ACL editor will be applied directly to the file or directory.
If set to True, then all requests to set an ACL on a file will have the +>If set to true, then all requests to set an ACL on a file will have the parameters restrict anonymous (G)
This is a boolean parameter. If it is true, then +>This is a boolean parameter. If it is true, then anonymous access to the server will be restricted, namely in the case where the server is expecting the client to send a username, - but it doesn't. Setting it to true will force these anonymous + but it doesn't. Setting it to true will force these anonymous connections to be denied, and the client will be required to always supply a username and password when connecting. Use of this parameter is only recommended for homogeneous NT client environments.
When restrict anonymous is true, all anonymous connections +>When restrict anonymous is true, all anonymous connections are denied no matter what they are for. This can effect the ability - of a machine to access the samba Primary Domain Controller to revalidate - it's machine account after someone else has logged on the client + of a machine to access the Samba Primary Domain Controller to revalidate + its machine account after someone else has logged on the client interactively. The NT client will display a message saying that the machine's account in the domain doesn't exist or the password is bad. The best way to deal with this is to reboot NT client machines @@ -14631,7 +14962,7 @@ NAME="ROOTDIRECTORY" CLASS="COMMAND" >chroot() (i.e. - Change it's root directory) to this directory on startup. This is + Change its root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the server will deny access to files not in one of the service entries. It may also check for, and deny access to, soft links to other @@ -14705,7 +15036,7 @@ CLASS="PARAMETER" > parameter except that the command is run as root. This is useful for unmounting filesystems - (such as cdroms) after a connection is closed.
See also parameter except that the command is run as root. This - is useful for mounting filesystems (such as cdroms) after a - connection is closed.
See also
When clients connect to a share level security server then +>When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with @@ -15066,7 +15397,7 @@ HREF="#AEN235" NAME="SECURITYEQUALSUSER" >SECURIYT = USER +>SECURITY = USER
Note that from the clients point of +> that from the client's point of view security = server
Note that from the clients point +> that from the client's point of view security = domain0777.
See also the
share modes (S)
This enables or disables the honoring of - the share modes during a file open. These - modes are used by clients to gain exclusive read or write access - to a file.
These open modes are not directly supported by UNIX, so - they are simulated using shared memory, or lock files if your - UNIX doesn't support shared memory (almost all do).
The share modes that are enabled by this option are - DENY_DOS, DENY_ALL, - DENY_READ, DENY_WRITE, - DENY_NONE and DENY_FCB. -
This option gives full share compatibility and enabled - by default.
You should NEVER turn this parameter - off as many Windows applications will break if you do so.
Default: share modes = yes
short preserve case (S)
printer admin group), the OpenPrinterEx() - call fails and the clients another open call with a request for + call fails and the client makes another open call with a request for a lower privilege level. This should succeed, however the APW icon will not be displayed.
shutdown script (G)
This parameter only exists in the HEAD cvs branch + This a full path name to a script called by + smbd(8) that + should start a shutdown procedure.
This command will be run as the user connected to the + server.
%m %t %r %f parameters are expanded
%m will be substituted with the + shutdown message sent to the server.
%t will be substituted with the + number of seconds to wait before effectively starting the + shutdown procedure.
%r will be substituted with the + switch -r. It means reboot after shutdown + for NT. +
%f will be substituted with the + switch -f. It means force the shutdown + even if applications do not respond for NT.
Default: None.
Example: abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f
Shutdown script example: +
#!/bin/bash + + $time=0 + let "time/60" + let "time++" + + /sbin/shutdown $3 $4 +$time $1 & +
+ Shutdown does not return so we need to launch it in background. +
See also abort shutdown script.
smb passwd file (G)
By default samba will accept connections on any +>By default Samba will accept connections on any address.
Example: no, the SSL enabled samba behaves - exactly like the non-SSL samba. If set to , the SSL-enabled Samba behaves + exactly like the non-SSL Samba. If set to yes, @@ -15971,7 +16356,7 @@ CLASS="COMMAND" >
This variable defines where to look up the Certification Authorities. The given directory should contain one file for - each CA that samba will trust. The file name must be the hash + each CA that Samba will trust. The file name must be the hash value over the "Distinguished Name" of the CA. How this directory is set up is explained later in this document. All files within the directory that don't fit into this naming scheme are ignored. You @@ -16199,8 +16584,8 @@ CLASS="COMMAND" > enabled by default in any current binary version of Samba.
These two variables define whether samba will go - into SSL mode or not. If none of them is defined, samba will +>These two variables define whether Samba will go + into SSL mode or not. If none of them is defined, Samba will allow only SSL connections. If the ssl hosts resign variable lists hosts, only these - hosts will NOT be forced into SSL mode. The syntax for these two + hosts will NOT be forced into SSL mode. The syntax for these two variables is the same as for the the server does file lock checks only when the client explicitly asks for them.
Well behaved clients always ask for lock checks when it +>Well-behaved clients always ask for lock checks when it is important, so in the vast majority of cases strict @@ -16616,7 +17003,11 @@ NAME="STRICTSYNC" CLASS="CONSTANT" >no (the - default) means that smbd ignores the Windows applications requests for + default) means that smbd ignores the Windows applications requests for a sync call. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting. In addition, this fixes many @@ -16664,10 +17055,16 @@ NAME="SYNCALWAYS" >
This is a boolean parameter that controls whether writes will always be written to stable storage before - the write call returns. If this is false then the server will be + the write call returns. If this is false then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous). - If this is true then every write will be followed by a true then every write will be followed by a fsync() template homedir (G)
NOTE: this parameter is - only available in Samba 3.0.
When filling out the user information for a Windows NT user, the template shell (G)
NOTE: this parameter is - only available in Samba 3.0.
When filling out the user information for a Windows NT user, the This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time. If a print job is submitted - by a client which will exceed this number, then smbd will return an + by a client which will exceed this number, then smbd will return an error indicating that no space is available on the server. The default value of 0 means that no such limit exists. This parameter can be used to prevent a server from exceeding its capacity and is @@ -16920,7 +17311,10 @@ NAME="UNIXPASSWORDSYNC" >This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. - If this is set to true the program specified in the true the program specified in the passwd @@ -16930,7 +17324,7 @@ CLASS="PARAMETER" >AS ROOT - to allow the new UNIX password to be set without access to the - old UNIX password (as the SMB password has change code has no + old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new).
See also
use client driver (S)
This parameter applies only to Windows NT/2000 + clients. It has no affect on Windows 95/98/ME clients. When + serving a printer to Windows NT/2000 clients without first installing + a valid printer driver on the Samba host, the client will be required + to install a local printer driver. From this point on, the client + will treat the print as a local printer and not a network printer + connection. This is much the same behavior that will occur + when disable spoolss = yes.
The differentiating + factor is that under normal circumstances, the NT/2000 client will + attempt to open the network printer using MS-RPC. The problem is that + because the client considers the printer to be local, it will attempt + to issue the OpenPrinterEx() call requesting access rights associated + with the logged on user. If the user possesses local administator rights + but not root privilegde on the Samba host (often the case), the OpenPrinterEx() + call will fail. The result is that the client will now display an "Access + Denied; Unable to connect" message in the printer queue window (even though + jobs may successfully be printed).
If this parameter is enabled for a printer, then any attempt + to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped + to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() + call to succeed. This parameter MUST not be able enabled + on a print share which has valid print driver installed on the Samba + server.
See also disable spoolss +
Default: use client driver = no
use rhosts (G)
If this global parameter is a true, it specifies - that the UNIX users If this global parameter is true, it specifies + that the UNIX user's .rhosts file in their home directory @@ -17145,7 +17592,7 @@ CLASS="PARAMETER" > parameter.
If any of the usernames begin with a '@' then the name - will be looked up first in the yp netgroups list (if Samba + will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name.
If any of the usernames begin with a '&'then the name - will be looked up only in the yp netgroups database (if Samba + will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.
utmp (S)utmp (G)
This boolean parameter is only available if Samba has been configured and compiled with the option --with-utmp. If set to True then Samba will attempt +>. If set to true then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the user connecting to a Samba share.
yes. - - . Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned. - - See also . - - Default: No files or directories are vetoed. - - Examples: -
This parameter allows parameters to be passed - to the vfs layer at initialisation time. The Samba VFS layer + to the vfs layer at initialization time. The Samba VFS layer is new to Samba 2.2 and must be enabled at compile time with --with-vfs. See also winbind cache time
NOTE: this parameter is only - available in Samba 3.0.
This parameter specifies the number of seconds the
winbind gid
winbind enum + usersOn large installations using + winbindd(8) it may be + necessary to suppress the enumeration of users through the + setpwent(), + getpwent() and + endpwent() group of system calls. If + the winbind enum users parameter is + false, calls to the getpwent system call + will not return any data. NOTE: this parameter is only - available in Samba 3.0.Warning: Turning off user + enumeration may cause some programs to behave oddly. For + example, the finger program relies on having access to the + full user list when searching for matching + usernames. Default: winbind enum users = yes winbind enum + groups On large installations using + winbindd(8) it may be + necessary to suppress the enumeration of groups through the + setgrent(), + getgrent() and + endgrent() group of system calls. If + the winbind enum groups parameter is + false, calls to the getgrent() system + call will not return any data. Warning: Turning off group + enumeration may cause some programs to behave oddly. + Default: winbind enum groups = no + winbind gid The winbind gid parameter specifies the range of group ids that are allocated by the winbindd(8) daemon. This range of group ids should have no - existing local or nis groups within it as strange conflicts can + existing local or NIS groups within it as strange conflicts can occur otherwise. Default: winbind separator NOTE: this parameter is only - available in Samba 3.0. This parameter allows an admin to define the character used when listing a username of the form of winbind uid NOTE: this parameter is only - available in Samba 3.0. The winbind gid parameter specifies the range of group ids that are allocated by the winbindd(8) daemon. This range of ids should have no - existing local or nis users within it as strange conflicts can + existing local or NIS users within it as strange conflicts can occur otherwise. Default:

The second argument is the netbios name. If the +>The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores and periods.

The third argument is the netbios name +>The third argument is the NetBIOS name type as a 2 digit hexadecimal number.

nmbd(8) process in Samba will act as a WINS server. You should - not set this to true unless you have a multi-subnetted network and + not set this to true unless you have a multi-subnetted network and you wish a particular nmbd to be your WINS server. Note that you should NEVER set this to true +> set this to true on more than one machine in your network. Default: This cache allows Samba to batch client writes into a more - efficient write size for RAID disks (ie. writes may be tuned to + efficient write size for RAID disks (i.e. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs. This parameter controls whether or not the server - will support raw writes SMB's when transferring data from clients. + will support raw write SMB's when transferring data from clients. You should never need to change this parameter. Default: WARNINGS VERSION SEE ALSO AUTHOR Samba suite. The smbcacls program manipulates NT Access Control Lists +>The smbcacls program manipulates NT Access Control Lists (ACLs) on SMB file shares. OPTIONS The following options are available to the smbcacls program. +>The following options are available to the smbcacls program. The format of ACLs is described in the section ACL FORMAT -D acls Delete any ACLs specfied on the command line. +>Delete any ACLs specified on the command line. An error will be printed for each ACL specified that was not already present in the ACL list.
ACL FORMAT
EXIT STATUS If the operation succeded, smbcacls returns and exit - status of 0. If smbcacls couldn't connect to the specified server, +>If the operation succeeded, smbcacls returns and exit + status of 0. If smbcacls couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned. If there was an error parsing any command line arguments, an exit status of 2 is returned.
VERSION AUTHOR smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-S server] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E <terminal code>] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E <terminal code>] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan]
DESCRIPTION
OPTIONS -R parameter to smbclient or - using the name resolve order parameter in the smb.conf file, +> parameter to smbclient or + using the name resolve order parameter in the smb.conf file, allowing an administrator to change the order and methods by which server names are looked up. This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve - host names to IP addresses. The option takes a space separated + host names to IP addresses. The option takes a space-separated string of different name resolution options.
The options are :"lmhosts", "host", "wins" and "bcast". They @@ -227,7 +233,7 @@ CLASS="FILENAME" >/etc/hosts, NIS, or DNS lookups. This method of name resolution - is operating system depended for instance on IRIX or Solaris this + is operating system dependent, for instance on IRIX or Solaris this may be controlled by the /etc/nsswitch.confname resolve order parameter of the smb.conf file the name resolution +> parameter of the smb.conf file the name resolution methods will be attempted in this order.
This specifies a NetBIOS scope that smbclient will use to communicate with when generating NetBIOS names. For details - on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. + on the use of NetBIOS scopes, see rfc1001.txt + and rfc1002.txt. NetBIOS scopes are very rarely used, only set @@ -383,7 +399,12 @@ CLASS="FILENAME" >-d debuglevel
debuglevel is an integer from 0 to 10, or +>debuglevel is an integer from 0 to 10, or the letter 'A'.
The default value if this parameter is not specified @@ -400,7 +421,12 @@ CLASS="FILENAME" data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely - cryptic. If debuglevel is set to the letter 'A', then debuglevel is set to the letter 'A', then all debug messages will be printed. This setting @@ -410,9 +436,9 @@ CLASS="FILENAME" to know how the code works internally).
Note that specifying this parameter here will override - the log level parameter in the smb.conf (5)smb.conf (5) file.
-l logfilename
If specified, logfilename specifies a base filename +>If specified, logfilename specifies a base filename into which operational data from the running client will be logged.
-I IP-address
IP address is the address of the server to connect to. +>IP address is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation.
Normally the client would attempt to locate a named @@ -492,35 +528,37 @@ CLASS="PARAMETER" >
Sets the SMB username or username and password. If %pass is not specified, The user will be prompted. The client - will first check the USER environment variable, then the + will first check the USER environment variable, then the $LOGNAME variable and if either exist, the +CLASS="ENVAR" +>LOGNAME variable and if either exists, the string is uppercased. Anything in these variables following a '%' - sign will be treated as the password. If these environmental + sign will be treated as the password. If these environment variables are not found, the username GUEST is used.
If the password is not included in these environment - variables (using the %pass syntax), rpcclient will look for +>If the password is not included in these environment + variables (using the %pass syntax), smbclient will look for a $PASSWDPASSWD environment variable from which to read the password.
A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin doesn't - desire to pass the credentials on the command line or via environment + wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the
Be cautious about including passwords in scripts or in the $PASSWDPASSWD environment variable. Also, on many systems the command line of a running process may be seen via the command to be safe always allow rpcclientsmbclient to prompt for a password and type it in directly.
option may be useful if your NetBIOS names don't - match your tcp/ip dns host names or if you are trying to reach a + match your TCP/IP DNS host names or if you are trying to reach a host on another network.
-t terminal code
This option tells smbclient how to interpret +>This option tells smbclient how to interpret filenames coming from the remote server. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (r - Regular expression include - or exclude. Uses regular regular expression matching for + or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. @@ -829,7 +868,10 @@ CLASS="COMMAND" >'s tar option now supports long file names both on backup and restore. However, the full path name of the file must be less than 1024 bytes. Also, when - a tar archive is created, smbclient's tar option places all + a tar archive is created, smbclient's tar option places all files in the archive with relative names, not absolute names.
Examples
Restore from tar file backup.tar into myshare on mypc +>Restore from tar file backup.tar into myshare on mypc (no password on share).
smbclient //mypc/myshare "" -N -Tx backup.tar +>smbclient //mypc/yshare "" -N -Tx backup.tar
-c command string
command string is a semicolon separated list of +>command string is a semicolon-separated list of commands to be executed instead of prompting from stdin.
OPERATIONS ? [command]
If "command" is specified, the ? command will display +>If command is specified, the ? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will be displayed.
! [shell command]
If "shell command" is specified, the ! +>If shell command is specified, the ! command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run.
The client will request that the server attempt - to delete all files matching "mask" from the current working + to delete all files matching mask from the current working directory on the server.
dir <mask>
A list of the files matching "mask" in the current +>A list of the files matching mask in the current working directory on the server will be retrieved from the server and displayed.
get <remote file name> [local file name]Copy the file called "remote file name" from +>Copy the file called remote file name from the server to the machine running the client. If specified, name - the local copy "local file name". Note that all transfers in + the local copy local file name. Note that all transfers in smbclientlcd [directory name] If "directory name" is specified, the current +>If directory name is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. mget <mask>Copy all files matching mask from the server to +>Copy all files matching mask from the server to the machine running the client. Note that mask is interpreted differently during recursive +>Note that mask is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in - smbclient are binary. See also the lowercase command. smbclient are binary. See also the lowercase command. mkdir <directory name> mput <mask>Copy all files matching mask in the current working +>Copy all files matching mask in the current working directory on the local machine to the current working directory on the server. Note that mask is interpreted differently during recursive +>Note that mask is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask - commands for more information. Note that all transfers in smbclient + commands for more information. Note that all transfers in smbclient are binary. put <local file name> [remote file name] Copy the file called "local file name" from the +>Copy the file called local file name from the machine running the client to the server. If specified, - name the remote copy "remote file name". Note that all transfers - in smbclient are binary. See also the lowercase command. + name the remote copy remote file name. Note that all transfers + in smbclient are binary. See also the lowercase command. rm <mask> Remove all files matching mask from the current +>Remove all files matching mask from the current working directory on the server.
Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in - blocksize*TBLOCK (usually 512 byte) blocks. blocksize*TBLOCK (usually 512 byte) blocks.
tarmode <full|inc|reset|noreset>
NOTES
ENVIRONMENT VARIABLES
The variable $USERUSER may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.
The variable $PASSWDPASSWD may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.
The variable LIBSMB_PROG may contain + the path, executed with system(), which the client should connect + to instead of connecting to a server. This functionality is primarily + intended as a development aid, and works best when using a LMHOSTS + file
INSTALLATION
smbd(8) an ordinary user - running that server as a daemon +> as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server.
DIAGNOSTICS
VERSION
AUTHOR
smbd.
The close-share message-type sends a + message to smbd which forces smbd to close the share that was + specified as an argument. This may be useful if you made changes + to the access controls on the share.
parameters
VERSION
SEE ALSO
AUTHOR
smbd killed and restarted.
OPTIONS
smbd for servers that provide more than casual use file and - print services. This switch is assumed is smbd -P
Passive option. Causes smbd not to +>Passive option. Causes smbd not to send any network traffic out. Used for debugging by the developers only.
-d <debug level>
debuglevel is an integer +>debuglevel is an integer from 0 to 10. The default value if this parameter is not specified is zero.
-l <log file>
If specified, log fileIf specified, log file specifies a log filename into which informational and debug messages from the running server will be logged. The log @@ -261,7 +278,12 @@ CLASS="FILENAME" >-p <port number>
port number is a positive integer +>port number is a positive integer value. The default value if this parameter is not specified is 139.
FILES
LIMITATIONS
ENVIRONMENTVARIABLES
PRINTER
PRINTER
If no printer name is specified to printable services, most systems will use the value of - this variable (or lp if this variable is + this variable (or lp if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.
INSTALLATION
smbd setgid to an empty group. This is because some systems may have a security hole where daemon processes that become a user can be attached to with a debugger. - Making the smbd file setgid to an empty group may prevent + Making the smbd file setgid to an empty group may prevent this hole from being exploited. This security hole and the suggested fix has only been confirmed on old versions (pre-kernel 2.0) of Linux at the time this was written. It is possible that this hole only @@ -567,7 +601,7 @@ CLASS="COMMAND" >
RUNNING THE SERVER AS A DAEMON
RUNNING THE SERVER ON REQUEST
inetd , you can arrange to have the smbd server started +>, you can arrange to have the smbd server started whenever a process attempts to connect to it. This requires several changes to the startup files on the host machine. If you are experimenting as an ordinary user rather than as root, you will @@ -755,7 +792,52 @@ CLASS="COMPUTEROUTPUT" >
PAM INTERACTION
Samba uses PAM for authentication (when presented with a plaintext + password), for account checking (is this account disabled?) and for + session management. The degree too which samba supports PAM is restricted + by the limitations of the SMB protocol and the + obey pam restricions + smb.conf paramater. When this is set, the following restrictions apply: +
Account Validation: All acccesses to a + samba server are checked + against PAM to see if the account is vaild, not disabled and is permitted to + login at this time. This also applies to encrypted logins. +
Session Management: When not using share + level secuirty, users must pass PAM's session checks before access + is granted. Note however, that this is bypassed in share level secuirty. + Note also that some older pam configuration files may need a line + added for session support. +
TESTING THE INSTALLATION
will reread their configuration tables if they receive a HUP signal.
If your machine's name is fred and your - name is mary, you should now be able to connect +>If your machine's name is fred and your + name is mary, you should now be able to connect to the service \\fred\mary
VERSION
DIAGNOSTICS
SIGNALS
Sending the smbd a SIGHUP will cause it to - re-load its Sending the smbd a SIGHUP will cause it to + reload its smb.conf configuration file within a short period of time.
To shut down a users smbd process it is recommended +>To shut down a user's smbd process it is recommended that SIGKILL (-9) be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate - an smbd is to send it a SIGTERM (-15) signal and wait for + an smbd is to send it a SIGTERM (-15) signal and wait for it to die on its own.
The debug log level of smbd may be raised by sending - it a SIGUSR1 (The debug log level of kill -USR1 <smbd-pid>) - and lowered by sending it a SIGUSR2 (smbd may be raised + or lowered using kill -USR2 <smbd-pid> +>smbcontrol(1) ). This is to allow transient problems to be diagnosed, +> program (SIGUSR[1|2] signals are no longer used in + Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level.
Note that as the signal handlers send a debug write, - they are not re-entrant in smbd. This you should wait until - smbd is in a state of waiting for an incoming smb before + they are not re-entrant in smbd. This you should wait until + smbd is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance.
SEE ALSOAUTHOR smbmnt is meant to be installed setuid root - so that normal users can mount their smb shares. It checks - whether the user has write permissions on the mount point and - then mounts the directory. can be installed setuid root if you want + normal users to be able to mount their SMB shares. A setuid smbmnt will only allow mounts on directories owned + by the user, and that the user has write permission on. The . It should not be invoked directly by users. smbmount searches the normal PATH for smbmnt. You must ensure + that the smbmnt version in your path matches the smbmount used. OPTIONS list of options that are passed as-is to smbfs, if this - command is run on a 2.4 or higher linux kernel. + command is run on a 2.4 or higher Linux kernel.
AUTHOR smbmount mounts a SMB filesystem. It +> mounts a Linux SMB filesystem. It is usually invoked as mount.smb from +>mount.smbfs by the mount(8) command when using the - "-t smb" option. The kernel must support the smbfs filesystem. Options to smbmount are specified as a comma separated +>Options to smbmount are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that smbfs supports them. If you get mount failures, check your kernel log for errors on unknown options. smbmount is a daemon. After mounting it keeps running until +>smbmount is a daemon. After mounting it keeps running until the mounted smbfs is umounted. It will log things that happen when in daemon mode using the "machine name" smbmount, so - typically this output will end up in log.smbmount. The - smbmount process may also be called mount.smbfs. log.smbmount. The + smbmount process may also be called mount.smbfs.
NOTE:
OPTIONS
will prompt for a passeword, unless the guest option is given.
Note that password which contain the arguement delimiter + character (i.e. a comma ',') will failed to be parsed correctly + on the command line. However, the same password defined + in the PASSWD environment variable or a credentials file (see + below) will be read correctly. +
credentials=<filename>
This is preferred over having passwords in plaintext in a - shared file, such as /etc/fstab. Be sure to protect any + shared file, such as /etc/fstab. Be sure to protect any credentials file properly.
dmask=<arg>
sets the directory mask. This deterines the +>sets the directory mask. This determines the permissions that remote directories have in the local filesystem. The default is based on the current umask.
sets the debug level. This is useful for - tracking down SMB connection problems.
ip=<arg>
iocharset=<arg>
sets the charset used by the linux side for codepage +> sets the charset used by the Linux side for codepage to charset translations (NLS). Argument should be the name of a charset, like iso8859-1. (Note: only kernel 2.4.0 or later) @@ -311,7 +336,7 @@ CLASS="PARAMETER" >
ENVIRONMENT VARIABLES
The variable PASSWD_FILE may contain the pathname of - a file to read the password from. A single line of input is - read and used as password.
may contain the pathname + of a file to read the password from. A single line of input is + read and used as the password.
BUGS
Not many known smbmount bugs. But one smbfs bug is - important enough to mention here anyway:
Passwords and other options containing , can not be handled. + For passwords an alternative way of passing them is in a credentials + file or in the PASSWD environment.
The credentials file does not handle usernames or passwords with + leading space.
One smbfs bug is important enough to mention here, even if it + is a bit misplaced:
Mounts sometimes stop working. This is usually caused by smbmount terminating. Since smbfs needs smbmount to - reconnect when the server disconnects, the mount will go - dead. A re-mount normally fixes this. At least 2 ways to + reconnect when the server disconnects, the mount will eventually go + dead. An umount/mount normally fixes this. At least 2 ways to trigger this bug are known.
Note that the typical response to a bugreport is suggestion +>Note that the typical response to a bug report is suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)
SEE ALSO
Documentation/filesystems/smbfs.txt in the kernel source tree - may contain additional options and information.
Documentation/filesystems/smbfs.txt in the linux kernel + source tree may contain additional options and information.
FreeBSD also has a smbfs, but it is not related to smbmount
For Solaris, HP-UX and others you may want to look at + smbsh(1) or at other + solutions, such as sharity or perhaps replacing the SMB server with + a NFS server.
AUTHOR
Lanman Password Hash
This is the LANMAN hash of the users password, +>This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES - encrypting a well known string with the users password as the + encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the @@ -111,7 +111,7 @@ CLASS="VARIABLELIST" is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to - 32 'X' characters then the users account is marked as + 32 'X' characters then the user's account is marked as disabledNT Password Hash
This is the Windows NT hash of the users +>This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is - created by taking the users password as represented in + created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it.
This password hash is considered more secure than - the Lanman Password Hash as it preserves the case of the + the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is @@ -198,7 +198,7 @@ CLASS="CONSTANT" >N - This means the - account has no password (the passwords in the fields Lanman + account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the
Name
smbpasswd -- change a users SMB password
smbpasswd -- change a user's SMB password
smbpasswd [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-j DOMAIN] [-U username] [-h] [-s] [username] [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-j DOMAIN] [-U username[%password]] [-h] [-s] [username]
By default (when run with no arguments) it will attempt to - change the current users SMB password on the local machine. This is + change the current user's SMB password on the local machine. This is similar to the way the passwd(1) file.
When run by an ordinary user with no options. smbpasswd - will prompt them for their old smb password and then ask them + will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen - whilst being typed. If you have a blank smb password (specified by + whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password.
If the smbpasswd file is in the 'old' format (pre-Samba 2.0 - format) there is no space in the users password entry to write + format) there is no space in the user's password entry to write this information and so the user is disabled by writing 'X' characters into the password space in the smbpasswd file. See
debuglevel
This option causes smbpasswd to be silent (i.e. - not issue prompts) and to read it's old and new passwords from + not issue prompts) and to read its old and new passwords from standard input, rather than from /dev/tty
smbsh
rcp. You must use a - shell that is dynmanically linked in order for smbsh @@ -80,7 +80,7 @@ CLASS="COMMAND" CLASS="COMMAND" > smbshfrom the prompt and enter the username and password - that authenticate you to the machine running the Windows NT + that authenticates you to the machine running the Windows NT operating system. ls /smb will show all the machines in your workgroup. The command +> will show a list of workgroups. The command ls /smb/<machine-name>ls /smb/MYGROUP will show all the machines in + the workgroup MYGROUP. The command + ls /smb/MYGROUP/<machine-name> will show the share names for that machine. You could then, for example, use the VERSIONBUGSSEE ALSO AUTHOR smbspool tries to get the URI from argv[0]. If argv[0] contains the name of the program then it looks in the DEVICE_URI DEVICE_URI environment variable. Programs using the functions can pass the URI in argv[0], while shell scripts must set the DEVICE_URIDEVICE_URI environment variable prior to running smbspool. smbumount has - been written to give normal linux-users more control over their + been written to give normal Linux users more control over their resources. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again. For root it is not necessary to use smbumount. The normal umount diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index be16272bb6..386fe5bc7a 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -68,15 +68,24 @@ CLASS="FILENAME" CLASS="COMMAND" >swat configuration page has help links - to all the configurable options in the smb.conf file allowing an + to all the configurable options in the smb.conf file allowing an administrator to easily look up the effects of any change. swat is run from inetd swat is run from inetd OPTIONSsmbd server. This is the file that swat will modify. +> server. This is the file that swat will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. @@ -110,8 +122,14 @@ CLASS="FILENAME" >This option disables authentication and puts - swat in demo mode. In that mode anyone will be able to modify - the smb.conf file. swat in demo mode. In that mode anyone will be able to modify + the smb.conf file. Do NOT enable this option on a production @@ -124,7 +142,7 @@ CLASS="FILENAME" > INSTALLATION Inetd Installation/etc/services - to enable SWAT to be launched via inetd. inetd. In Launching To launch swat just run your favorite web browser and +>To launch SWAT just run your favorite web browser and point it at "http://localhost:901/". Note that you can attach to swat from any IP connected +>Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. FILES WARNINGS VERSION SEE ALSO AUTHOR -L servername Sets the value of the %L macro to servername. +>Sets the value of the %L macro to servername. This is useful for testing include files specified with the %L macro. If this parameter and the following are - specified, then testparm will examine the testparm will examine the hosts @@ -184,7 +192,7 @@ CLASS="COMMAND" > FILESDIAGNOSTICS The program will issue a message saying whether the - configuration file loaded OK or not. This message may be preceeded by + configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details to stdout. VERSIONSEE ALSO AUTHOR nmblookupwbinfo [-u] [-g] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] winbindd(8) daemon is not working wbinfo will always return +> daemon is not working wbinfo will always return failure. VERSION This man page is correct for version 2.2 of - the Samba suite. winbindd is however not available in - stable release of Samba as of yet.SEE ALSO AUTHORwinbindd - were written by TIm Potter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter Unifed Logons between Windows NT and UNIX using WinbindUnified Logons between Windows NT and UNIX using WinbindUnifed Logons between Windows NT and UNIX using WinbindUnified Logons between Windows NT and UNIX using Winbind Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous - computing environments for a long time. We present winbind - , a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation +>winbind, a component of the Samba suite + of programs as a solution to the unified logon problem. Winbind + uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind @@ -66,11 +67,11 @@ NAME="AEN7" and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which which + and two sets of passwords are required both of which can lead to synchronization problems between the UNIX and Windows systems and confusion for users. We divide the unifed logon problem for UNIX machines into +>We divide the unified logon problem for UNIX machines into three smaller problems: The end result is that whenever any program on the UNIX machine asks the operating system to lookup a user or group name, the query will be resolved by asking the - NT domain controller for the specied domain to do the lookup. + NT domain controller for the specified domain to do the lookup. Because Winbind hooks into the operating system at a low level (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely @@ -136,11 +137,11 @@ NAME="AEN20" that redirection to a domain controller is wanted for a particular lookup and which trusted domain is being referenced. Additionally, Winbind provides a authentication service +>Additionally, Winbind provides an authentication service that hooks into the Pluggable Authentication Modules (PAM) system to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing - passwords between systems as all passwords are stored in a single + passwords between systems since all passwords are stored in a single location (on the domain controller).Another interesting way in which we expect Winbind to be used is as a central part of UNIX based appliances. Appliances @@ -224,11 +225,11 @@ NAME="AEN40" >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information - to be resolved from dierent sources. For example, a standalone + to be resolved from different sources. For example, a standalone UNIX workstation may resolve system information from a series of - flat files stored on the local lesystem. A networked workstation + flat files stored on the local filesystem. A networked workstation may first attempt to resolve system information from local files, - then consult a NIS database for user information or a DNS server + and then consult a NIS database for user information or a DNS server for hostname information. The NSS application programming interface allows winbind @@ -241,11 +242,12 @@ NAME="AEN40" a NT domain plus any trusted domain as though they were local users and groups. The primary control le for NSS is The primary control file for NSS is + /etc/nsswitch.conf - . When a UNIX application makes a request to do a lookup +>/etc/nsswitch.conf. + When a UNIX application makes a request to do a lookup the C library looks in /etc/nsswitch.conf Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different - authentication methods for dierent system applications without + authentication methods for different system applications without having to recompile these applications. PAM is also useful for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users @@ -315,10 +317,10 @@ NAME="AEN56" UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable Primary Domain Controller. These users can also change their passwords and have - this change take eect directly on the Primary Domain Controller. + this change take effect directly on the Primary Domain Controller. PAM is congured by providing control files in the directory +>PAM is configured by providing control files in the directory /etc/pam.d//lib/security/ and the pam +> and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation for more details. When a user or group is created under Windows NT - is it allocated a numerical relative identier (RID). This is - slightly dierent to UNIX which has a range of numbers which are + is it allocated a numerical relative identifier (RID). This is + slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is congured it is given part of the UNIX + vice versa. When winbind is configured it is given part of the UNIX user id space and a part of the UNIX group id space in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is allocated the next UNIX id from @@ -363,7 +365,7 @@ NAME="AEN64" to UNIX user ids and group ids. The results of this mapping are stored persistently in - a ID mapping database held in a tdb database). This ensures that + an ID mapping database held in a tdb database). This ensures that RIDs are mapped to UNIX IDs in a consistent way.Installation and ConfigurationThe easiest way to install winbind is by using the packages - provided in the Many thanks to John Trostel jtrostel@snapserver.com +for providing the HOWTO for this section. This HOWTO describes how to get winbind services up and running +to control access and authenticate users on your Linux box using +the winbind services which come with SAMBA 2.2.2. Introduction This HOWTO describes the procedures used to get winbind up and +running on my RedHat 7.1 system. Winbind is capable of providing access +and authentication control for Windows Domain users through an NT +or Win2K PDC for 'regular' services, such as telnet a nd ftp, as +well for SAMBA services. This HOWTO has been written from a 'RedHat-centric' perspective, so if +you are using another distribution, you may have to modify the instructions +somewhat to fit the way your distribution works. Why should I to this? + This allows the SAMBA administrator to rely on the + authentication mechanisms on the NT/Win2K PDC for the authentication + of domain members. NT/Win2K users no longer need to have separate + accounts on the SAMBA server. + Who should be reading this document? + This HOWTO is designed for system administrators. If you are + implementing SAMBA on a file server and wish to (fairly easily) + integrate existing NT/Win2K users from your PDC onto the + SAMBA server, this HOWTO is for you. That said, I am no NT or PAM + expert, so you may find a better or easier way to accomplish + these tasks. + Requirements If you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, BACK UP +THE /etc/pam.d directory contents! If you +haven't already made a boot disk, MAKE ON NOW! Messing with the pam configuration files can make it nearly impossible +to log in to yourmachine. That's why you want to be able to boot back +into your machine in single user mode and restore your +/etc/pam.d back to the original state they were in if +you get frustrated with the way things are going. ;-) The newest version of SAMBA (version 2.2.2), available from +cvs.samba.org, now include a functioning winbindd daemon. Please refer +to the main SAMBA web page or, better yet, your closest SAMBA mirror +site for instructions on downloading the source code. To allow Domain users the ability to access SAMBA shares and +files, as well as potentially other services provided by your +SAMBA machine, PAM (pluggable authentication modules) must +be setup properly on your machine. In order to compile the +winbind modules, you should have at least the pam libraries resident +on your system. For recent RedHat systems (7.1, for instance), that +means 'pam-0.74-22'. For best results, it is helpful to also +install the development packages in 'pam-devel-0.74-22'. Testing Things Out Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all smbd, +nmbd, and winbindd processes that may +be running. To use PAM, you will want to make sure that you have the +standard PAM package (for RedHat) which supplies the /etc/pam.d +directory structure, including the pam modules are used by pam-aware +services, several pam libraries, and the /usr/doc +and /usr/man entries for pam. Winbind built better +in SAMBA if the pam-devel package was also installed. This package includes +the header files needed to compile pam-aware applications. For instance, my RedHat +system has both 'pam-0.74-22' and 'pam-devel-0.74-22' RPMs installed. Configure and compile SAMBA The configuration and compilation of SAMBA is pretty straightforward. +The first three steps maynot be necessary depending upon +whether or not you have previously built the Samba binaries. root# autoconf +root# make clean +root# rm config.cache +root# ./configure --with-winbind +root# make +root# make install This will, by default, install SAMBA in /usr/local/samba. See the +main SAMBA documentation if you want to install SAMBA somewhere else. +It will also build the winbindd executable and libraries. Configure nsswitch.conf and the winbind libraries The libraries needed to run the winbind daemon through nsswitch +need to be copied to their proper locations, so root# cp ../samba/source/nsswitch/libnss_winbind.so /lib I also found it necessary to make the following symbolic link: root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 Now, as root you need to edit pub/samba/appliance//etc/nsswitch.conf to +allow user and group entries to be visible from the winbindd - directory on your nearest - Samba mirror. These packages provide snapshots of the Samba source - code and binaries already setup to provide the full functionality - of winbind. This setup is a little more complex than a normal Samba - build as winbind needs a small amount of functionality from a - development code branch called SAMBA_TNG. Once you have installed the packages you should read - the /etc/nsswitch.conf file look like this after editing: passwd: files winbind + shadow: files winbind + group: files winbind +The libraries needed by the winbind daemon will be automatically +entered into the ldconfig cache the next time your system reboots, but it +is faster (and you don't need to reboot) if you do it manually: root# /sbin/ldconfig -v | grep winbind This makes libnss_winbind available to winbindd +and echos back a check to you. Configure smb.conf Several parameters are needed in the smb.conf file to control +the behavior of winbindd(8) man page which will provide you - with conguration information and give you sample conguration files. - You may also wish to update the main Samba daemons smbd and nmbd) - with a more recent development release, such as the recently - announced Samba 2.2 alpha release. winbindd. Configure +smb.conf These are described in more detail in +the winbindd(8) man page. My +smb.conf file was modified to +include the following entries in the [global] section: [global] + <...> + # separate domain and username with '+', like DOMAIN+username + winbind separator = + + # use uids from 10000 to 20000 for domain users + winbind uid = 10000-20000 + # use gids from 10000 to 20000 for domain groups + winbind gid = 10000-20000 + # allow enumeration of winbind users and groups + winbind enum users = yes + winbind enum groups = yes + # give winbind users a real shell (only needed if they have telnet access) + template shell = /bin/bash Join the SAMBA server to the PDC domain Enter the following command to make the SAMBA server join the +PDC domain, where DOMAIN is the name of +your Windows domain and Administrator is +a domain user who has administrative privileges in the domain. root# /usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator The proper response to the command should be: "Joined the domain +DOMAIN" where DOMAIN +is your DOMAIN name. Start up the winbindd daemon and test it! Eventually, you will want to modify your smb startup script to +automatically invoke the winbindd daemon when the other parts of +SAMBA start, but it is possible to test out just the winbind +portion first. To start up winbind services, enter the following +command as root: root# /usr/local/samba/bin/winbindd I'm always paranoid and like to make sure the daemon +is really running... root# ps -ae | grep winbindd +3025 ? 00:00:00 winbindd Now... for the real test, try to get some information about the +users on your PDC root# # /usr/local/samba/bin/wbinfo -u +This should echo back a list of users on your Windows users on +your PDC. For example, I get the following response: CEO+Administrator +CEO+burdell +CEO+Guest +CEO+jt-ad +CEO+krbtgt +CEO+TsInternetUser Obviously, I have named my domain 'CEO' and my winbindd separator is '+'. You can do the same sort of thing to get group information from +the PDC: root# /usr/local/samba/bin/wbinfo -g +CEO+Domain Admins +CEO+Domain Users +CEO+Domain Guests +CEO+Domain Computers +CEO+Domain Controllers +CEO+Cert Publishers +CEO+Schema Admins +CEO+Enterprise Admins +CEO+Group Policy Creator Owners The function 'getent' can now be used to get unified +lists of both local and PDC users and groups. +Try the following command: root# getent passwd You should get a list that looks like your /etc/passwd +list followed by the domain users with their new uids, gids, home +directories and default shells. The same thing can be done for groups with the command root# getent group Fix the /etc/rc.d/init.d/smb startup files The winbindd daemon needs to start up after the +smbd and nmbd daemons are running. +To accomplish this task, you need to modify the /etc/init.d/smb +script to add commands to invoke this daemon in the proper sequence. My +/etc/init.d/smb file starts up smbd, +nmbd, and winbindd from the +/usr/local/samba/bin directory directly. The 'start' +function in the script looks like this: start() { + KIND="SMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/smbd $SMBDOPTIONS + RETVAL=$? + echo + KIND="NMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/winbindd + RETVAL3=$? + echo + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + RETVAL=1 + return $RETVAL +} The 'stop' function has a corresponding entry to shut down the +services and look s like this: stop() { + KIND="SMB" + echo -n $"Shutting down $KIND services: " + killproc smbd + RETVAL=$? + echo + KIND="NMB" + echo -n $"Shutting down $KIND services: " + killproc nmbd + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Shutting down $KIND services: " + killproc winbindd + RETVAL3=$? + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + echo "" + return $RETVAL +} Configure Winbind and PAM If you have made it this far, you know that winbindd is working. +Now it is time to integrate it into the operation of samba and other +services. The pam configuration files need to be altered in +this step. (Did you remember to make backups of your original +/etc/pam.d files? If not, do it now.) To get samba to allow domain users and groups, I modified the +/etc/pam.d/samba file from auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_stack.so service=system-auth to auth required /lib/security/pam_winbind.so +auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth The other services that I modified to allow the use of winbind +as an authentication service were the normal login on the console (or a terminal +session), telnet logins, and ftp service. In order to enable these +services, you may first need to change the entries in +/etc/xinetd.d (or /etc/inetd.conf). +RedHat 7.1 uses the new xinetd.d structure, in this case you need +to change the lines in /etc/xinetd.d/telnet +and /etc/xinetd.d/wu-ftp from enable = no to enable = yes +For ftp services to work properly, you will also need to either +have individual directories for the domain users already present on +the server, or change the home directory template to a general +directory for all domain users. These can be easily set using +the smb.conf global entry +template homedir. The /etc/pam.d/ftp file can be changed +to allow winbind ftp access in a manner similar to the +samba file. My /etc/pam.d/ftp file was +changed to look like this: auth sufficient /lib/security/pam_winbind.so +auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_shells.so +account required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth The /etc/pam.d/login file can be changed nearly the +same way. It now looks like this: auth required /lib/security/pam_securetty.so +auth sufficient /lib/security/pam_winbind.so +auth sufficient /lib/security/pam_unix.so use_first_pass +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_nologin.so +account sufficient /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth +password required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth +session optional /lib/security/pam_console.so In this case, I added the auth sufficient /lib/security/pam_winbind.so +lines as before, but also added the required pam_securetty.so +above it, to disallow root logins over the network. I also added a +sufficient /lib/security/pam_unix.so use_first_pass +line after the winbind.so line to get rid of annoying +double prompts for passwords. Finally, don't forget to copy the winbind pam modules from +the source directory in which you originally compiled the new +SAMBA up to the /lib/security directory so that pam can use it: root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security Limitations Winbind has a number of limitations in its current - released version which we hope to overcome in future + released version that we hope to overcome in future releases: Building winbind from source is currently - quite tedious as it requires combining source code from two Samba - branches. Work is underway to solve this by providing all - the necessary functionality in the main Samba code branch. Conclusion nmblookup [-d debuglevel] [-i] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] {name} winbindd [-i] [-d <debug level>] [-s <smb config file>] DESCRIPTION This tool is part of the This program is part of the Samba suite version 3.0 and describes functionality not - yet implemented in the main version of Samba. suite. The service provided by winbindd is called `winbind' and +>The service provided by winbindd is called `winbind' and can be used to resolve user and group information from a Windows NT server. The service can also provide authentication services via an associated PAM module. OPTIONS NAME AND ID RESOLUTION CONFIGURATION The winbind uid parameter specifies the range of user ids that are allocated by the winbindd daemon. - This range of ids should have no existing local or nis users + This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise. Default: The winbind gid parameter specifies the range of group ids that are allocated by the winbindd daemon. - This range of group ids should have no existing local or nis + This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise. Default: Warning: Turning off user enumeration - may cause some programs to behave oddly. For example, the finger + may cause some programs to behave oddly. For example, the finger program relies on having access to the full user list when searching for matching usernames. EXAMPLE SETUPThe next step is to join the domain. To do that use the sameditsmbpasswd program like this: samedit -S '*' -W DOMAIN -UAdministratorsmbpasswd -j DOMAIN -r PDC -U + Administrator The username after the -U can be any Domain - user that has administrator priviliges on the machine. Next from - within samedit, run the command: createuser MACHINE$ -j DOMAIN -L This assumes your domain is called "DOMAIN" and your Samba - workstation is called "MACHINE". can be any + Domain user that has administrator privileges on the machine. + Substitute your domain name for "DOMAIN" and the name of your PDC + for "PDC". Next copy /lib/libnss_winbind.so.1. Finally, setup a smb.conf containing directives like the +>Finally, setup a smb.conf containing directives like the following: Notes NOTESThe following notes are useful when configuring and running winbindd nsswitch module read an environment variable named $WINBINDD_DOMAIN $WINBINDD_DOMAIN. If this variable contains a comma separated list of Windows NT domain names, then winbindd will only resolve users and groups within those Windows NT domains. Signals SIGNALSThe following signals can be used to manipulate the Files FILESStorage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially compiled using the --with-lockdir option. +CLASS="PARAMETER" +>--with-lockdir option. This directory is by default /usr/local/samba/var/locks @@ -848,19 +847,18 @@ CLASS="FILENAME" >VERSION This man page is correct for version 2.2 of - the Samba suite. winbindd is however not available in - stable release of Samba as of yet.This man page is correct for version 2.2 of + the Samba suite. SEE ALSO AUTHOR

UNIX Permission Bits and WIndows NT Access Control ListsUNIX Permission Bits and Windows NT Access Control Lists

2.6. Configuration of Samba as ...2.6. Conclusions

Chapter 3. LanMan and NT Password Encryption in Samba 2.xChapter 3. Configuring PAM for distributed but centrally +managed authentication

3.2. How does it work?3.1. Samba and PAM

3.4. The smbpasswd file

3.5. The smbpasswd Command3.2. Distributed Authentication

3.6. Setting up Samba to support LanManager Encryption3.3. PAM Configuration in smb.conf

Chapter 5. Printing Support in Samba 2.2.xChapter 5. UNIX Permission Bits and Windows NT Access Control Lists

5.1. Introduction5.1. Viewing and changing UNIX permissions using the NT + security dialogs

5.2. Configuration5.2. How to view file security on a Samba share

5.3. The Imprints Toolset5.7. Interaction with the standard Samba file attribute + mapping

5.4. Migration to from Samba 2.0.x to 2.2.x6.2. Configuration

7.1. Prerequisite Reading6.3. The Imprints Toolset

6.4. Migration to from Samba 2.0.x to 2.2.x

7.3. Configuring the Samba Domain Controllerprinter driver location (S) +

7.4.1. Manually creating machine trust accounts8.4.1. Manually creating machine trust accounts

7.4.2. Creating machine trust accounts "on the fly"8.4.2. Creating machine trust accounts "on the fly"

7.5. Common Problems and Errors8.5. Common Problems and Errors

7.6. System Policies and Profiles8.6. System Policies and Profiles

7.7. What other help can I get ?8.7. What other help can I get ?

7.8. Domain Control for Windows 9x/ME8.8. Domain Control for Windows 9x/ME

7.8.1. Configuration Instructions: Network Logons8.8.1. Configuration Instructions: Network Logons

7.8.2. Configuration Instructions: Setting up Roaming User Profiles8.8.2. Configuration Instructions: Setting up Roaming User Profiles

7.8.2.1. Windows NT Configuration8.8.2.1. Windows NT Configuration

7.8.2.2. Windows 9X Configuration8.8.2.2. Windows 9X Configuration

7.8.2.3. Win9X and WinNT Configuration8.8.2.3. Win9X and WinNT Configuration

7.8.2.4. Windows 9X Profile Setup8.8.2.4. Windows 9X Profile Setup

7.8.2.5. Windows NT Workstation 4.08.8.2.5. Windows NT Workstation 4.0

7.8.2.6. Windows NT Server8.8.2.6. Windows NT Server

7.8.2.7. Sharing Profiles between W95 and NT Workstation 4.08.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0

7.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba

`3.5. The smbpasswd Command3.2. Distributed Authentication`

`3.6. Setting up Samba to support LanManager Encryption3.3. PAM Configuration in smb.conf`

`Chapter 5. Printing Support in Samba 2.2.xChapter 5. UNIX Permission Bits and Windows NT Access Control Lists`

`5.1. Introduction5.1. Viewing and changing UNIX permissions using the NT + security dialogs`

`5.2. Configuration5.2. How to view file security on a Samba share`

`5.3. The Imprints Toolset5.7. Interaction with the standard Samba file attribute + mapping`

`5.4. Migration to from Samba 2.0.x to 2.2.x6.2. Configuration`

`7.1. Prerequisite Reading6.3. The Imprints Toolset`

7.3. Configuring the Samba Domain Controller`printer driver location (S)` +

`7.4.1. Manually creating machine trust accounts8.4.1. Manually creating machine trust accounts`

`7.4.2. Creating machine trust accounts "on the fly"8.4.2. Creating machine trust accounts "on the fly"`

`7.5. Common Problems and Errors8.5. Common Problems and Errors`

`7.8. Domain Control for Windows 9x/ME8.8. Domain Control for Windows 9x/ME`

`7.8.1. Configuration Instructions: Network Logons8.8.1. Configuration Instructions: Network Logons`

`7.8.2. Configuration Instructions: Setting up Roaming User Profiles8.8.2. Configuration Instructions: Setting up Roaming User Profiles`

`7.8.2.1. Windows NT Configuration8.8.2.1. Windows NT Configuration`

`7.8.2.2. Windows 9X Configuration8.8.2.2. Windows 9X Configuration`

`7.8.2.3. Win9X and WinNT Configuration8.8.2.3. Win9X and WinNT Configuration`

`7.8.2.4. Windows 9X Profile Setup8.8.2.4. Windows 9X Profile Setup`

`7.8.2.5. Windows NT Workstation 4.08.8.2.5. Windows NT Workstation 4.0`

`7.8.2.6. Windows NT Server8.8.2.6. Windows NT Server`

`7.8.2.7. Sharing Profiles between W95 and NT Workstation 4.08.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0`

`7.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba`