This book is a collection of HOWTOs added to Samba documentation over the year. +>This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job -than one person can maintain. You can always find the later version of this -PDF file at http://www.samba.org/

4.2. Configuration

WARNING!!! 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 +>

[print$] vs. [printer$]

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.

These parameters, including printer driver +>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 of this document.

Migration section +of this document.

4.2.1. Creating [print$]

smb.conf(5) man page for more information on -configuring file shares.

smb.conf(5) +man page for more information on configuring file shares.

The requirement for guest ok = yesguest +ok = yes depends upon how your site is configured. If users will be guaranteed to have @@ -2538,26 +2682,26 @@ ALIGN="CENTER" ALIGN="LEFT" >

In order to currently add a new driver to you Samba host, - one of two conditions must hold true:

The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)
The account used to connect to the Samba host - must be a member of the printer - admin list.

Of course, the connected account must still possess access - to add files to the subdirectories beneath [print$].

4.2.2. Setting Drivers for Existing Printers

The initial listing of printers in the Samba host's -Printers folder will have no printer driver assigned to them. -The way assign a driver to a printer is to view the Properties -of the printer and either

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:

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?

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

4.2.3. Support a large number of printers

$ rpcclient pogo -U root%bleaK.er \ +>rpcclient pogo -U root%secret \ >

4.2.4. Adding New Printers via the Windows NT APW

printer admin. +>).

addprinter -commandadd +printer command must have a defined value. The program @@ -2789,7 +2952,7 @@ CLASS="COMMAND" CLASS="PARAMETER" >add printer -program and reparse to the add printer program is executed undet the context +> is executed under the context of the connected user, not necessarily a root account.
There is a complementing deleteprinter -commanddelete +printer command for removing entries from the "Printers..." @@ -2823,7 +2986,7 @@ CLASS="SECT2" >
4.2.5. Samba and Printer Ports
4.3. The Imprints Toolset
4.3.1. What is Imprints?
4.3.2. Creating Printer Driver Packages
4.3.3. The Imprints server
4.3.4. The Installation Client
will reveal that Windows NT always uses the NT driver - name. The is ok as Windows NT always requires that at least + 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 @@ -3049,18 +3212,60 @@ CLASS="SECT1" >
4.4. Migration to from Samba 2.0.x to - 2.2.xMigration to from Samba 2.0.x to 2.2.x
Given that printer driver management has changed - (we hope improved :) ) in 2.2.0 over prior releases, - migration from an existing setup to 2.2.0 can follow - several paths.
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.
The following smb.conf parameters are considered to be - depreciated and will be removed soon. Do not use them - in new installations
The following smb.conf parameters are considered to be depreciated and will +be removed soon. Do not use them in new installations
- printer driver (S) -
- printer driver location (S) -
If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.
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 moved to the "this tool is the old way of doing it" - pile.
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).
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 and rpcclient. See the - Imprints installation client at http://imprints.sourceforge.net/ - for an example. -

Chapter 5. security = domain in Samba 2.x

5.1. Joining an NT Domain with Samba 2.2

5.2. Samba and Windows 2000 Domains

5.3. Why is this better than security = server?

Chapter 6. How to Configure Samba 2.2.x as a Primary Domain ControllerChapter 6. How to Configure Samba 2.2 as a Primary Domain Controller

6.1. Background6.1. Prerequisite Reading

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 Encryption chapter +of this HOWTO Collection.

6.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.
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.

Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). The following -functionality should work in 2.2.0:

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
domain logons for Windows NT 4.0/2000 clients. +
placing a Windows 9x client in user level security
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
retrieving a list of users and groups from a Samba PDC to + Windows 9x/NT/2000 clients +
roving user profiles
roving (roaming) user profiles +
Windows NT 4.0 style system policies
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
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)
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
Adding users via the User Manager for Domains +
Acting as a Windows 2000 Domain Controller (i.e. Kerberos - and Active Directory)
Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) +
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 and Windows 2000 (including SP1) clients. This article -outlines the steps necessary for configuring Samba as a PDC. -Note that 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.
Implementing a Samba PDC can basically be divided into 2 broad steps.
Configuring the Samba Domain Controller +> Configuring the Samba PDC
Creating machine trust accounts - and joining clients to the domain
Creating machine trust accounts and joining clients + to the domain +
6.2. Configuring the Samba Domain Controller6.3. Configuring the Samba Domain Controller
The first step in creating a working Samba PDC is to @@ -3768,7 +4040,7 @@ TARGET="_top" > = \\homeserver\%u ; specify a generic logon script for all users - ; this is a relative path to the [netlogon] share + ; this is a relative **DOS** path to the [netlogon] share
There are a couple of points to emphasize in the above -configuration.
There are a couple of points to emphasize in the above configuration.
encrypted passwords must be enabled. - For more details on how to do this, refer to - Encrypted passwords must be enabled. For more details on how + to do this, refer to ENCRYPTION.html
The server must support domain logons - and a The server must support domain logons and a + [netlogon] share
share +
The server must be the domain master browser - in order for Windows client to locate the server as a DC.
The server must be the domain master browser in order for Windows + client to locate the server as a DC. Please refer to the various + Network Browsing documentation included with this distribution for + details. +
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
6.3. Creating Machine Trust Accounts and Joining Clients +NAME="AEN870" +>6.4. Creating Machine Trust Accounts and Joining Clients to the Domain
First you must understand what a machine trust account is and what -it is used for.
A machine trust account is a user account owned by a computer. +>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. Hence the reason that -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.
On a Windows NT PDC, these machine trust account passwords are stored -in the registry. A Samba PDC stores these accounts in he same location +in the registry. A Samba PDC stores these accounts in the same location as user LanMan and NT password hashes (currently smbpasswd). -However, machine trust accounts only possess the NT password hash.
Because Samba requires machine accounts to possess a UNIX uid from +which an Windows NT SID can be generated, all of these accounts +must have an entry in /etc/passwd and smbpasswd. +Future releases will alleviate the need to create +/etc/passwd entries.
There are two means of creating machine trust accounts.
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.
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. +
Creation of the account at the time of - joining the domain. In this case, the session key of the - administrative account used to join the client to the domain acts - as an encryption key for setting the password to a random value.
Creation of the account at the time of joining the domain. In + this case, the session key of the administrative account used to join + the client to the domain acts as an encryption key for setting the + password to a random value (This is the recommended method). +
6.4.1. Manually creating machine trust accounts
Because Samba requires machine accounts to possess a UNIX uid from -which an Windows NT SID can be generated, all of these accounts -will have an entry in /etc/passwd and smbpasswd. -Future releases will alleviate the need to create -/etc/passwd entries.
The The first step in creating a machine trust account by hand is to +create an entry for the machine in /etc/passwd. This can be done +using vipw or any 'add userr' command which is normally +used to create new UNIX accounts. The following is an example for a Linux +based Samba server:
root# /usr/sbin/useradd -g 100 -d /dev/null -c machine_nickname -m -s /bin/false machine_name$
The /etc/passwd entry will list the machine name @@ -3949,23 +4255,43 @@ WIDTH="100%" >
doppy$:x:505:501:NTMachine:/dev/null:/bin/false
doppy$:x:505:501:machine_nickname:/dev/null:/bin/false If you are manually creating the machine accounts, it is necessary -to add the /etc/passwd (or NIS passwd -map) entry prior to adding the smbpasswd -entry. The following command will create a new machine account -ready for use. Above, machine_nickname can be any descriptive name for the +pc i.e. BasementComputer. The machine_name absolutely must be +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 +the smbpasswd entry for the machine containing the well known initial +trust account password. This can be done using the smbpasswd(8) command +as shown here: machine_name is the machine's netbios -name. If you manually create a machine account, immediately join -the client to the domain. An open account like this -can allow intruders to gain access to user account information -in your domain. The second way of creating machine trust accounts is to add -them on the fly at the time the client is joined to the domain. -You will need to include a value for the - Join the client to the domain immediately Manually creating a machine trust account using this method is the + equivalent of creating a machine account on a Windows NT PDC using + the "Server Manager". From the time at which the account is created + to the time which th client joins the domain and changes the password, + your domain is vulnerable to an intruder joining your domain using a + a machine with the same netbios name. A PDC inherently trusts + members of the domain and will serve out a large degree of user + information to such clients. You have been warned! +
6.4.2. Creating machine trust accounts "on the fly"
The second, and most recommended way of creating machine trust accounts +is to create them as needed at the time the client is joined to +the domain. You will need to include a value for the add user script -parameter. Below is an example I use on a RedHat 6.2 Linux system.
In Samba 2.2.0, In Samba 2.2.1, only the root account can be used to create -machine accounts on the fly like this. Therefore, it is required -to create an entry in smbpasswd for root. -The password . The password +SHOULD be set to s different -password that the associated be set to s different password that the +associated /etc/passwd -entry for security reasons.
entry for security reasons.

`6.4. Common Problems and Errors6.5. Common Problems and Errors`

I cannot include a '$' in a machine name.

I cannot include a '$' in a machine name. +
A 'machine name' in (typically) A 'machine name' in (typically) /etc/passwd -of the machine name with a '$' appended. FreeBSD (and other BSD -systems ?) won't create a user with a '$' in their name.
The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use The problem is only in the program used to make the entry, once + made, it works perfectly. So create a user without the '$' and + use vipw to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique uid !
I get told "You already have a connection to the Domain...." -when creating a machine account.
This happens if you try to create a machine account from the -machine itself and use a user name that does not work (for whatever -reason) and then try another (possibly valid) user name. -Exit out of the network applet to close the initial connection -and try again.
+ Further, if the machine is a already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again. This happens if you try to create a machine account from the + machine itself and already have a connection (e.g. mapped drive) + to a share (or IPC$) on the Samba PDC. The following command + will remove all network drive connections: + I get told "Cannot join domain, the credentials supplied -conflict with an existing set.." C:\WINNT\> net use * /d + This is the same basic problem as mentioned above, "You already -have a connection..." Further, if the machine is a already a 'member of a workgroup' that + is the same name as the domain you are joining (bad idea) you will + get this message. Change the workgroup name to something else, it + does not matter what, reboot, and try again. +
"The system can not log you on (C000019B)...."
The system can not log you on (C000019B).... + I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try a gain or consult your -system administrator" when attempting to logon. This occurs when the domain SID stored in - This occurs when the domain SID stored in + private/WORKGROUP.SID is -changed. For example, you remove the file and smbd automatically -creates a new one. Or you are swapping back and forth between -versions 2.0.7, TNG and the HEAD branch code (not recommended). The -only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin.
"The machine account for this computer either does not -exist or is not accessible."
The machine account for this computer either does not + exist or is not accessible. + When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". Whats -wrong ? When I try to join the domain I get the message "The machine account + for this computer either does not exist or is not accessible". Whats + wrong? + This problem is caused by the PDC not having a suitable machine account. -If you are using the add user script = This problem is caused by the PDC not having a suitable machine account. + If you are using the add user script method to create -accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working. Alternatively if you are creating account entries manually then they -have not been created correctly. Make sure that you have the entry -correct for the machine account in smbpasswd file on the Samba PDC. -If you added the account using an editor rather than using the smbpasswd -utility, make sure that the account name is the machine netbios name -with a '$' appended to it ( ie. computer_name$ ). There must be an entry -in both /etc/passwd and the smbpasswd file. Some people have reported -that inconsistent subnet masks between the Samba server and the NT -client have caused this problem. Make sure that these are consistent -for both client and server. Alternatively if you are creating account entries manually then they + have not been created correctly. Make sure that you have the entry + correct for the machine account in smbpasswd file on the Samba PDC. + If you added the account using an editor rather than using the smbpasswd + utility, make sure that the account name is the machine netbios name + with a '$' appended to it ( ie. computer_name$ ). There must be an entry + in both /etc/passwd and the smbpasswd file. Some people have reported + that inconsistent subnet masks between the Samba server and the NT + client have caused this problem. Make sure that these are consistent + for both client and server. +
When I attempt to login to a Samba Domain from a NT4/W2K workstation, + I get a message about my account being disabled. +
This problem is caused by a PAM related bug in Samba 2.2.0. This bug is + fixed in 2.2.1. Other symptoms could be unaccessible shares on + NT/W2K member servers in the domain or the following error in your smbd.log: + passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% +
At first be ensure to enable the useraccounts with smbpasswd -e + %user%, this is normaly done, when you create an account. +
In order to work around this problem in 2.2.0, configure the + account control flag in + /etc/pam.d/samba file as follows: +
account required pam_permit.so +
If you want to remain backward compatibility to samba 2.0.x use + pam_permit.so, it's also possible to use + pam_pwdb.so. There are some bugs if you try to + use pam_unix.so, if you need this, be ensure to use + the most recent version of this file. +

`6.5. System Policies and Profiles6.6. System Policies and Profiles`

Much of the information necessary to implement System Policies and @@ -4159,92 +4611,107 @@ Profiles and Policies in Windows NT 4.0

Here are some additional details:

What about Windows NT Policy Editor ?

What about Windows NT Policy Editor ? +
To create or edit To create or edit ntconfig.pol you must use -the NT Server Policy Editor, poledit.exe which -is included with NT Server but not NT Workstation. -There is a Policy Editor on a NTws -but it is not suitable for creating Domain Policies. -Further, although the Windows 95 -Policy Editor can be installed on an NT Workstation/Server, it will not -work with NT policies because the registry key that are set by the policy templates. -However, the files from the NT Server will run happily enough on an NTws. -You need poledit.exe, common.adm and winnt.adm. It is convenient -to put the two *.adm files in c:\winnt\inf which is where -the binary will look for them unless told otherwise. Note also that that -directory is 'hidden'.
The Windows NT policy editor is also included with the -Service Pack 3 (and later) for Windows NT 4.0. Extract the files using - The Windows NT policy editor is also included with the Service Pack 3 (and + later) for Windows NT 4.0. Extract the files using servicepackname /x, ie thats , + ie thats Nt4sp6ai.exe -/x for service pack 6a. The policy editor, Nt4sp6ai.exe /x for service pack 6a. The policy editor, + poledit.exe and the -associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft.
and the associated template files (*.adm) should + be extracted as well. It is also possible to downloaded the policy template + files for Office97 and get a copy of the policy editor. Another possible + location is with the Zero Administration Kit available for download from Microsoft. +
Can Win95 do Policies ?
+ Install the group policy handler for Win9x to pick up group -policies. Look on the Win98 CD in Install the group policy handler for Win9x to pick up group + policies. Look on the Win98 CD in \tools\reskit\netadmin\poledit. -Install group policies on a Win9x client by double-clicking -grouppol.inf. Log off and on again a couple of -times and see if Win98 picks up group policies. Unfortunately this needs -to be done on every Win9x machine that uses group policies.... If group policies don't work one reports suggests getting the updated -(read: working) grouppol.dll for Windows 9x. The group list is grabbed -from /etc/group. If group policies don't work one reports suggests getting the updated + (read: working) grouppol.dll for Windows 9x. The group list is grabbed + from /etc/group. +
How do I get 'User Manager' and 'Server Manager'
+ Since I don't need to buy an NT Server CD now, how do I get -the 'User Manager for Domains', the 'Server Manager' ? Since I don't need to buy an NT Server CD now, how do I get + the 'User Manager for Domains', the 'Server Manager' ? + Microsoft distributes a version of -these tools called nexus for installation on Windows 95 systems. The -tools set includes Microsoft distributes a version of these tools called nexus for + installation on Windows 95 systems. The tools set includes + Click here to download the archived file Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE + The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from The Windows NT 4.0 version of the 'User Manager for + Domains' and 'Server Manager' are available from Microsoft via ftp + from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE +

`6.6. What other help can I get ?6.7. What other help can I get ?`

There are many sources of information available in the form @@ -4290,10 +4761,15 @@ of mailing lists, RFC's and documentation. The docs that come with the samba distribution contain very good explanations of general SMB topics such as browsing.

What are some diagnostics tools I can use to debug the domain logon -process and where can I find them?

What are some diagnostics tools I can use to debug the domain logon + process and where can I find them? +
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 @@ -4335,7 +4811,7 @@ CLASS="COMMAND" >

An SMB enabled version of tcpdump is available from - http://www.tcpdup.org/

How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?

+ Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes @@ -4457,14 +4936,11 @@ CLASS="FILENAME" information on how to do this. Copy the files from a working Netmon installation. 6.6.1. URLs and similar

The following is a list if helpful URLs and other links: +

`6.6.2. Mailing Lists`

How do I get help from the mailing lists ?

How do I get help from the mailing lists ? +
There are a number of Samba related mailing lists. Go to There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror -and then click on Support and then click on Samba related mailing lists.
Samba related mailing lists. + For questions relating to Samba TNG go to - For questions relating to Samba TNG go to + http://www.samba-tng.org/ -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists. If you post a message to one of the lists please observe the following guide lines : If you post a message to one of the lists please observe the following guide lines : + In addition to the version, if you obtained Samba via - CVS mention the date when you last checked it out.In addition to the version, if you obtained Samba via + CVS mention the date when you last checked it out. Try and make your question clear and brief, lots of long, + convoluted questions get deleted before they are completely read ! + Don't post html encoded messages (if you can select colour or font + size its html). If you run one of those nifty 'I'm on holidays' things when + you are away, make sure its configured to not answer mailing lists. + 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. + 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 + with on another, will forward it on for you. You might include partial + log files written at a debug level set to as much as 20. + Please don't send the entire log but enough to give the context of the + error messages. (Possibly) If you have a complete netmon trace ( from the opening of + the pipe to the error ) you can send the *.CAP file as well. Please think carefully before attaching a document to an email. + Consider pasting the relevant parts into the body of the message. The samba + mailing lists go to a huge number of people, do they all need a copy of your + smb.conf in their attach directory ?
How do I get off the mailing lists ? +
To have your name removed from a samba mailing list, go to the + same place you went to to get on it. Go to http://lists.samba.org, + click on your nearest mirror and then click on Support and + then click on Samba related mailing lists. Or perhaps see + here +
Please don't post messages to the list asking to be removed, you will just + be referred to the above address (unless that process failed in some way...) +

`6.8. Domain Control for Windows 9x/ME`

Note: The following section contains much of the original +DOMAIN.txt file previously included with Samba. Much of +the material is based on what went into the book Special +Edition, Using Samba. (Richard Sharpe)

A domain and a workgroup are exactly the same thing in terms of network +browsing. The difference is that a distributable authentication +database is associated with a domain, for secure login access to a +network. Also, different access rights can be granted to users if they +successfully authenticate against a domain logon server (NT server and +other systems based on NT server support this, as does at least Samba TNG now).

The SMB client logging on to a domain has an expectation that every other +server in the domain should accept the same authentication information. +Network browsing functionality of domains and workgroups is +identical and is explained in BROWSING.txt. It should be noted, that browsing +is total orthogonal to logon support.

Issues related to the single-logon network model are discussed in this +document. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X clients.

When an SMB client in a domain wishes to logon it broadcast requests for a +logon server. The first one to reply gets the job, and validates its +password using whatever mechanism the Samba administrator has installed. +It is possible (but very stupid) to create a domain where the user +database is not shared between servers, ie they are effectively workgroup +servers advertising themselves as participating in a domain. This +demonstrates how authentication is quite different from but closely +involved with domains.

Another thing commonly associated with single-logon domains is remote +administration over the SMB protocol. Again, there is no reason why this +cannot be implemented with an underlying username database which is +different from the Windows NT SAM. Support for the Remote Administration +Protocol is planned for a future release of Samba.

Network logon support as discussed in this section is aimed at Window for +Workgroups, and Windows 9X clients.

Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51. +It is possible to specify: the profile location; script file to be loaded +on login; the user's home directory; and for NT a kick-off time could also +now easily be supported. However, there are some differences between Win9X +profile support and WinNT profile support. These are discussed below.

With NT Workstations, all this does not require the use or intervention of +an NT 4.0 or NT 3.51 server: Samba can now replace the logon services +provided by an NT server, to a limited and experimental degree (for example, +running "User Manager for Domains" will not provide you with access to +a domain created by a Samba Server).

With Win95, the help of an NT server can be enlisted, both for profile storage +and for user authentication. For details on user authentication, see +security_level.txt. For details on profile storage, see below.

Using these features you can make your clients verify their logon via +the Samba server; make clients run a batch file when they logon to +the network and download their preferences, desktop and start menu.

Before launching into the configuration instructions, it is worthwhile looking +at how a Win9X client performs a logon:

The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS address DOMAIN<00> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + \\SERVER. +
The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). +
The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. +
The client then connects to the NetLogon share and searches for this + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. +
The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. +
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 + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented. +
The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for CONFIG.POL, the policies file. If this is + found, it is read and implemented. +

`6.8.1. Configuration Instructions: Network Logons`

To use domain logons and profiles you need to do the following:

Create a share called [netlogon] in your smb.conf. This share should + be readable by all users, and probably should not be writeable. This + share will hold your network logon scripts, and the CONFIG.POL file + (Note: for details on the CONFIG.POL file, how to use it, what it is, + refer to the Microsoft Windows NT Administration documentation. + The format of these files is not known, so you will need to use + Microsoft tools). +
For example I have used: +
[netlogon] + path = /data/dos/netlogon + writeable = no + guest ok = no
Note that it is important that this share is not writeable by ordinary + users, in a secure environment: ordinary users should not be allowed + to modify or add files that another user's computer would then download + when they log in. +
in the [global] section of smb.conf set the following: +
domain logons = yes +logon script = %U.bat +
The choice of batch file is, of course, up to you. The above would + give each user a separate batch file as the %U will be changed to + their username automatically. The other standard % macros may also be + used. You can make the batch files come from a subdirectory by using + something like: +
logon script = scripts\%U.bat +
create the batch files to be run when the user logs in. If the batch + file doesn't exist then no batch file will be run. +
In the batch files you need to be careful to use DOS style cr/lf line + endings. If you don't then DOS may get confused. I suggest you use a + DOS editor to remotely edit the files if you don't know how to produce + DOS style files under unix. +
Use smbclient with the -U option for some users to make sure that + the \\server\NETLOGON share is available, the batch files are + visible and they are readable by the users. +
you will probabaly 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. +

security mode and master browsers

There are a few comments to make in order to tie up some +loose ends. There has been much debate over the issue of whether +or not it is ok to configure Samba as a Domain Controller in security +modes other than USER. The only security mode +which will not work due to technical reasons is SHARE +mode security. DOMAIN and SERVER +mode security is really just a variation on SMB user level security.

Actually, this issue is also closer tied to the debate on whether +or not Samba must be the domain master browser for its workgroup +when operating as a DC. While it may technically be possible +to configure a server as such (after all, browsing and domain logons +are two distinctly different functions), it is not a good idea to +so. You should remember that the DC must register the DOMAIN#1b netbios +name. This is the name used by Windows clients to locate the DC. +Windows clients do not distinguish between the DC and the DMB. +For this reason, it is very wise to configure the Samba DC as the DMB.

Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use +another SMB server or DC in order to validate user connection +requests, then it is a fact that some other machine on the network +(the "password server") knows more about user than the Samba host. +99% of the time, this other host is a domain controller. Now +in order to operate in domain mode security, the "workgroup" parameter +must be set to the name of the Windows NT domain (which already +has a domain controller, right?)

Therefore configuring a Samba box as a DC for a domain that +already by definition has a PDC is asking for trouble. +Therefore, you should always configure the Samba DC to be the DMB +for its domain.

`6.8.2. Configuration Instructions: Setting up Roaming User Profiles`

Warning

NOTE! Roaming profiles support is different +for Win9X and WinNT.

Before discussing how to configure roaming profiles, it is useful to see how +Win9X and WinNT clients implement these features.

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 are restricted to being in the user's home directory.

WinNT clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles. +This means that support for profiles is different for Win9X and WinNT.

`6.8.2.1. Windows NT Configuration`

To support WinNT clients, inn the [global] section of smb.conf set the +following (for example):

logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath

The default for this option is \\%N\%U\profile, namely +\\sambaserver\username\profile. The \\N%\%U service is created +automatically by the [homes] service. +If you are using a samba server for the profiles, you _must_ make the +share specified in the logon path browseable.

Note: [lkcl 26aug96 - we have discovered a problem where Windows clients can +maintain a connection to the [homes] share in between logins. The +[homes] share must NOT therefore be used in a profile path.]

`6.8.2.2. Windows 9X Configuration`

To support Win9X clients, you must use the "logon home" parameter. Samba has +now been fixed so that "net use/home" now works as well, and it, too, relies +on the "logon home" parameter.

By using the logon home parameter, you are restricted to putting Win9X +profiles in the user's home directory. But wait! There is a trick you +can use. If you set the following in the [global] section of your +smb.conf file:

logon home = \\%L\%U\.profiles

then your Win9X clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden).

Not only that, but 'net use/home' will also work, because of a feature in +Win9X. It removes any directory stuff off the end of the home directory area +and only uses the server and share portion. That is, it looks like you +specified \\%L\%U for "logon home".

`6.8.2.3. Win9X and WinNT Configuration`

You can support profiles for both Win9X and WinNT clients by setting both the +"logon home" and "logon path" parameters. For example:

logon home = \\%L\%U\.profiles +logon path = \\%L\profiles\%U

Note: I have not checked what 'net use /home' does on NT when "logon home" is +set as above.

`6.8.2.4. Windows 9X Profile Setup`

When a user first logs in on Windows 9X, the file user.DAT is created, +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 +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders.

The user.DAT file contains all the user's preferences. If you wish to +enforce a set of preferences, rename their user.DAT file to user.MAN, +and deny them write access to this file.

On the Windows 95 machine, go to Control Panel | Passwords and + select the User Profiles tab. Select the required level of + roaming preferences. Press OK, but do _not_ allow the computer + to reboot. +
On the Windows 95 machine, go to Control Panel | Network | + Client for Microsoft Networks | Preferences. Select 'Log on to + NT Domain'. Then, ensure that the Primary Logon is 'Client for + Microsoft Networks'. Press OK, and this time allow the computer + to reboot. +

Under Windows 95, Profiles are downloaded from the Primary Logon. +If you have the Primary Logon as 'Client for Novell Networks', then +the profiles and logon script will be downloaded from your Novell +Server. If you have the Primary Logon as 'Windows Logon', then the +profiles will be loaded from the local machine - a bit against the +concept of roaming profiles, if you ask me.

You will now find that the Microsoft Networks Login box contains +[user, password, domain] instead of just [user, password]. Type in +the samba server's domain name (or any other domain known to exist, +but bear in mind that the user will be authenticated against this +domain and profiles downloaded from it, if that domain logon server +supports it), user name and user's password.

Once the user has been successfully validated, the Windows 95 machine +will inform you that 'The user has not logged on before' and asks you +if you wish to save the user's preferences? Select 'yes'.

Once the Windows 95 client comes up with the desktop, you should be able +to examine the contents of the directory specified in the "logon path" +on the samba server and verify that the "Desktop", "Start Menu", +"Programs" and "Nethood" folders have been created.

These folders will be cached locally on the client, and updated when +the user logs off (if you haven't made them read-only by then :-). +You will find that if the user creates further folders or short-cuts, +that the client will merge the profile contents downloaded with the +contents of the profile directory already on the local client, taking +the newest folders and short-cuts from each set.

If you have made the folders / files read-only on the samba server, +then you will get errors from the w95 machine on logon and logout, as +it attempts to merge the local and the remote profile. Basically, if +you have any errors reported by the w95 machine, check the unix file +permissions and ownership rights on the profile directory contents, +on the samba server.

If you have problems creating user profiles, you can reset the user's +local desktop cache, as shown below. When this user then next logs in, +they will be told that they are logging in "for the first time".

Try and make your question clear and brief, lots of long, - convoluted questions get deleted before they are completely read ! - Don't post html encoded messages (if you can select colour or font - size its html).
instead of logging in under the [user, password, domain] dialog, + press escape. +
If you run one of those nifty 'I'm on holidays' things when - you are away, make sure its configured to not answer mailing lists. -
run the regedit.exe program, and look in: + HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList + you will find an entry, for each user, of ProfilePath. Note the + contents of this key (likely to be c:\windows\profiles\username), + then delete the key ProfilePath for the required user. + [Exit the registry editor]. +
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. - 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 - with on another, will forward it on for you.
WARNING - before deleting the contents of the + directory listed in + the ProfilePath (this is likely to be c:\windows\profiles\username), + ask them if they have any important files stored on their desktop + or in their start menu. delete the contents of the directory + ProfilePath (making a backup if any of the files are needed). + This will have the effect of removing the local (read-only hidden + system file) user.DAT in their profile directory, as well as the + local "desktop", "nethood", "start menu" and "programs" folders. +
You might include partial - log files written at a debug level set to as much as 20. - Please don't send the entire log but enough to give the context of the - error messages.
search for the user's .PWL password-cacheing file in the c:\windows + directory, and delete it. +
(Possibly) If you have a complete netmon trace ( from the opening of - the pipe to the error ) you can send the *.CAP file as well.
log off the windows 95 client. +
Please think carefully before attaching a document to an email. - Consider pasting the relevant parts into the body of the message. The samba - mailing lists go to a huge number of people, do they all need a copy of your - smb.conf in their attach directory ?
check the contents of the profile path (see "logon path" described + above), and delete the user.DAT or user.MAN file for the user, + making a backup if required. +

How do I get off the mailing lists ?

If all else fails, increase samba's debug log levels to between 3 and 10, +and / or run a packet trace program such as tcpdump or netmon.exe, and +look for any error reports. If you have access to an NT server, then first set up roaming profiles +and / or netlogons on the NT server. Make a packet trace, or examine +the example packet traces provided with NT server, and see what the +differences are with the equivalent samba trace.

`6.8.2.5. Windows NT Workstation 4.0`

When a user first logs in to a Windows NT Workstation, the profile +NTuser.DAT is created. The profile location can be now specified +through the "logon path" parameter.

Note: [lkcl 10aug97 - i tried setting the path to +\\samba-server\homes\profile, and discovered that this fails because +a background process maintains the connection to the [homes] share +which does _not_ close down in between user logins. you have to +have \\samba-server\%L\profile, where user is the username created +from the [homes] share].

There is a parameter that is now available for use with NT Profiles: +"logon drive". This should be set to "h:" or any other drive, and +should be used in conjunction with the new "logon home" parameter.

The entry for the NT 4.0 profile is a _directory_ not a file. The NT +help on profiles mentions that a directory is also created with a .PDS +extension. The user, while logging in, must have write permission to +create the full profile path (and the folder with the .PDS extension) +[lkcl 10aug97 - i found that the creation of the .PDS directory failed, +and had to create these manually for each user, with a shell script. +also, i presume, but have not tested, that the full profile path must +be browseable just as it is for w95, due to the manner in which they +attempt to create the full profile path: test existence of each path +component; create path component].

In the profile directory, NT creates more folders than 95. It creates +"Application Data" and others, as well as "Desktop", "Nethood", +"Start Menu" and "Programs". The profile itself is stored in a file +NTuser.DAT. Nothing appears to be stored in the .PDS directory, and +its purpose is currently unknown.

You can use the System Control Panel to copy a local profile onto +a samba server (see NT Help on profiles: it is also capable of firing +up the correct location in the System Control Panel for you). The +NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN +turns a profile into a mandatory one.

Note: [lkcl 10aug97 - i notice that NT Workstation tells me that it is +downloading a profile from a slow link. whether this is actually the +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 +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 +workstation to access the samba server using LAN manager encrypted +passwords, without the user intervention normally required by NT +workstation for clear-text passwords].
[lkcl 25aug97 - more comments received about NT profiles: the case of +the profile _matters_. the file _must_ be called NTuser.DAT or, for +a mandatory profile, NTuser.MAN].

`6.8.2.6. Windows NT Server`

There is nothing to stop you specifying any path that you like for the +location of users' profiles. Therefore, you could specify that the +profile be stored on a samba server, or any other SMB server, as long as +that SMB server supports encrypted passwords.

`6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0`

To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to http://lists.samba.org, click - on your nearest mirror and then click on Support and - then click on Samba related mailing lists. Or perhaps see - here

Potentially outdated or incorrect material follows

Please don't post messages to the list asking to be removed, you will just - be referred to the above address (unless that process failed in some way...) -

I think this is all bogus, but have not deleted it. (Richard Sharpe)

The default logon path is \\%N\U%. NT Workstation will attempt to create +a directory "\\samba-server\username.PDS" if you specify the logon path +as "\\samba-server\username" with the NT User Manager. Therefore, you +will need to specify (for example) "\\samba-server\username\profile". +NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which +is more likely to succeed.

If you then want to share the same Start Menu / Desktop with W95, you will +need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 +this has its drawbacks: i created a shortcut to telnet.exe, which attempts +to run from the c:\winnt\system32 directory. this directory is obviously +unlikely to exist on a Win95-only host].

If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory.

Note: [lkcl 25aug97 - there are some issues to resolve with downloading of +NT profiles, probably to do with time/date stamps. i have found that +NTuser.DAT is never updated on the workstation after the first time that +it is copied to the local workstation profile directory. this is in +contrast to w95, where it _does_ transfer / update profiles correctly].

`6.7. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba`

Possibly Outdated Material

This appendix was originally authored by John H Terpstra of the Samba Team -and is included here for posterity.

This appendix was originally authored by John H Terpstra of + the Samba Team and is included here for posterity. +

NOTE :

Windows NT Server can be installed as either a plain file and print server (WORKGROUP workstation or server) or as a server that participates in Domain -Control (DOMAIN member, Primary Domain controller or Backup Domain controller).

The same is true for OS/2 Warp Server, Digital Pathworks and other similar -products, all of which can participate in Domain Control along with Windows NT. -However only those servers which have licensed Windows NT code in them can be -a primary Domain Controller (eg Windows NT Server, Advanced Server for Unix.)

To many people these terms can be confusing, so let's try to clear the air.

`Chapter 7. Unifed Logons between Windows NT and UNIX using Winbind`

`7.1. Abstract`

`7.2. Introduction`

`7.3. What Winbind Provides`

`7.3.1. Target Uses`

`7.4. How Winbind Works`

`7.4.1. Microsoft Remote Procedure Calls`

`7.4.2. Name Service Switch`

`7.4.3. Pluggable Authentication Modules`

`7.4.4. User and Group ID Allocation`

`7.4.5. Result Caching`

`7.5. Installation and Configuration`

`7.6. Limitations`

`7.7. Conclusion`

`Chapter 8. UNIX Permission Bits and WIndows NT Access Control Lists`

`8.1. Viewing and changing UNIX permissions using the NT security dialogs`

`8.2. How to view file security on a Samba share`

`8.3. Viewing file ownership`

`8.4. Viewing file or directory permissions`

`8.4.1. File Permissions`

`8.4.2. Directory Permissions`

`8.5. Modifying file or directory permissions`

`8.6. Interaction with the standard Samba create mask parameters`

`8.7. Interaction with the standard Samba file attribute mapping`

`Chapter 9. OS2 Client HOWTO`

`9.1. FAQs`

`9.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?`

`9.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?`

`9.1.3. Are there any other issues when OS/2 (any version) is used as a client?`

`9.1.4. How do I get printer driver download working for OS/2 clients?`

`Chapter 10. HOWTO Access Samba source code via CVS`

`10.1. Introduction`

Samba is developed in an open environnment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymouns CVS using the instructions +detailed in this chapter.

This document is a modified version of the instructions found at +http://samba.org/samba/cvs.html

`10.2. CVS Access to samba.org`

The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host.

`10.2.1. Access via CVSweb`

You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository.

Use the URL : http://samba.org/cgi-bin/cvsweb

`10.2.2. Access via cvs`

You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them uptodate via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser.

To download the latest cvs source code, point your +browser at the URL : http://www.cyclic.com/. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com.

To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name

Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. +
Run the command +
cvs -d :pserver:cvs@samba.org:/cvsroot login +
When it asks you for a password type cvs. +
Run the command +
cvs -d :pserver:cvs@samba.org:/cvsroot co samba +
This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. +
CVS branches other HEAD can be obtained by using the -r + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. +
cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba +
Whenever you want to merge in the latest code changes use + the following command from within the samba directory: +
cvs update -d -P +

How to Configure Samba 2.2.x as a Primary Domain ControllerHow to Configure Samba 2.2 as a Primary Domain ControllerHow to Configure Samba 2.2.x as a Primary Domain ControllerHow to Configure Samba 2.2 as a Primary Domain Controller

Prerequisite ReadingBefore 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 Encryption chapter +of this HOWTO Collection.

`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.
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.

Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). The following -functionality should work in 2.2.0:

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 domain logons for Windows NT 4.0/2000 clients. + placing a Windows 9x client in user level security 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 retrieving a list of users and groups from a Samba PDC to + Windows 9x/NT/2000 clients + roving user profiles roving (roaming) user profiles + Windows NT 4.0 style system policies 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 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) 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 Adding users via the User Manager for Domains + Acting as a Windows 2000 Domain Controller (i.e. Kerberos - and Active Directory) Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) + 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 and Windows 2000 (including SP1) clients. This article -outlines the steps necessary for configuring Samba as a PDC. -Note that 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. Implementing a Samba PDC can basically be divided into 2 broad steps. Configuring the Samba Domain Controller +> Configuring the Samba PDC Creating machine trust accounts - and joining clients to the domain Creating machine trust accounts and joining clients + to the domain + Configuring the Samba Domain Controller = \\homeserver\%u ; specify a generic logon script for all users - ; this is a relative path to the [netlogon] share + ; this is a relative **DOS** path to the [netlogon] share = 0700 There are a couple of points to emphasize in the above -configuration. There are a couple of points to emphasize in the above configuration. encrypted passwords must be enabled. - For more details on how to do this, refer to - Encrypted passwords must be enabled. For more details on how + to do this, refer to ENCRYPTION.html The server must support domain logons - and a The server must support domain logons and a + [netlogon] share share + The server must be the domain master browser - in order for Windows client to locate the server as a DC. The server must be the domain master browser in order for Windows + client to locate the server as a DC. Please refer to the various + Network Browsing documentation included with this distribution for + details. + 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 Creating Machine Trust Accounts and Joining Clients to the Domain First you must understand what a machine trust account is and what -it is used for. A machine trust account is a user account owned by a computer. +>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. Hence the reason that -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. On a Windows NT PDC, these machine trust account passwords are stored -in the registry. A Samba PDC stores these accounts in he same location +in the registry. A Samba PDC stores these accounts in the same location as user LanMan and NT password hashes (currently smbpasswd). -However, machine trust accounts only possess the NT password hash. Because Samba requires machine accounts to possess a UNIX uid from +which an Windows NT SID can be generated, all of these accounts +must have an entry in /etc/passwd and smbpasswd. +Future releases will alleviate the need to create +/etc/passwd entries. There are two means of creating machine trust accounts. 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. 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. + Creation of the account at the time of - joining the domain. In this case, the session key of the - administrative account used to join the client to the domain acts - as an encryption key for setting the password to a random value. Creation of the account at the time of joining the domain. In + this case, the session key of the administrative account used to join + the client to the domain acts as an encryption key for setting the + password to a random value (This is the recommended method). + Manually creating machine trust accounts Because Samba requires machine accounts to possess a UNIX uid from -which an Windows NT SID can be generated, all of these accounts -will have an entry in /etc/passwd and smbpasswd. -Future releases will alleviate the need to create -/etc/passwd entries. The first step in creating a machine trust account by hand is to +create an entry for the machine in /etc/passwd. This can be done +using vipw or any 'add userr' command which is normally +used to create new UNIX accounts. The following is an example for a Linux +based Samba server: root# /usr/sbin/useradd -g 100 -d /dev/null -c machine_nickname -m -s /bin/false machine_name$ The doppy$:x:505:501:NTMachine:/dev/null:/bin/false doppy$:x:505:501:machine_nickname:/dev/null:/bin/false If you are manually creating the machine accounts, it is necessary -to add the /etc/passwd (or NIS passwd -map) entry prior to adding the smbpasswd -entry. The following command will create a new machine account -ready for use. Above, machine_nickname can be any descriptive name for the +pc i.e. BasementComputer. The machine_name absolutely must be +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 +the smbpasswd entry for the machine containing the well known initial +trust account password. This can be done using the smbpasswd(8) command +as shown here: machine_name is the machine's netbios -name. If you manually create a machine account, immediately join -the client to the domain. An open account like this -can allow intruders to gain access to user account information -in your domain. The second way of creating machine trust accounts is to add -them on the fly at the time the client is joined to the domain. -You will need to include a value for the - Join the client to the domain immediately Manually creating a machine trust account using this method is the + equivalent of creating a machine account on a Windows NT PDC using + the "Server Manager". From the time at which the account is created + to the time which th client joins the domain and changes the password, + your domain is vulnerable to an intruder joining your domain using a + a machine with the same netbios name. A PDC inherently trusts + members of the domain and will serve out a large degree of user + information to such clients. You have been warned! + Creating machine trust accounts "on the fly" The second, and most recommended way of creating machine trust accounts +is to create them as needed at the time the client is joined to +the domain. You will need to include a value for the add user script -parameter. Below is an example I use on a RedHat 6.2 Linux system. add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u In Samba 2.2.0, In Samba 2.2.1, only the root account can be used to create -machine accounts on the fly like this. Therefore, it is required -to create an entry in smbpasswd for root. -The password . The password +SHOULD be set to s different -password that the associated be set to s different password that the +associated /etc/passwd -entry for security reasons. entry for security reasons.

`Common Problems and Errors`

I cannot include a '$' in a machine name.
+ A 'machine name' in (typically) A 'machine name' in (typically) /etc/passwd -of the machine name with a '$' appended. FreeBSD (and other BSD -systems ?) won't create a user with a '$' in their name. The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use The problem is only in the program used to make the entry, once + made, it works perfectly. So create a user without the '$' and + use vipw to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique uid !
I get told "You already have a connection to the Domain...." -when creating a machine account.
This happens if you try to create a machine account from the -machine itself and use a user name that does not work (for whatever -reason) and then try another (possibly valid) user name. -Exit out of the network applet to close the initial connection -and try again.
+ Further, if the machine is a already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again. This happens if you try to create a machine account from the + machine itself and already have a connection (e.g. mapped drive) + to a share (or IPC$) on the Samba PDC. The following command + will remove all network drive connections: + I get told "Cannot join domain, the credentials supplied -conflict with an existing set.." C:\WINNT\> net use * /d + This is the same basic problem as mentioned above, "You already -have a connection..." Further, if the machine is a already a 'member of a workgroup' that + is the same name as the domain you are joining (bad idea) you will + get this message. Change the workgroup name to something else, it + does not matter what, reboot, and try again. +
"The system can not log you on (C000019B)...."
The system can not log you on (C000019B).... + I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try a gain or consult your -system administrator" when attempting to logon. This occurs when the domain SID stored in - This occurs when the domain SID stored in + private/WORKGROUP.SID is -changed. For example, you remove the file and smbd automatically -creates a new one. Or you are swapping back and forth between -versions 2.0.7, TNG and the HEAD branch code (not recommended). The -only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin.
The machine account for this computer either does not + exist or is not accessible. +
When I try to join the domain I get the message "The machine account + for this computer either does not exist or is not accessible". Whats + wrong? +
This problem is caused by the PDC not having a suitable machine account. + If you are using the add user script method to create + accounts then this would indicate that it has not worked. Ensure the domain + admin user system is working. +
Alternatively if you are creating account entries manually then they + have not been created correctly. Make sure that you have the entry + correct for the machine account in smbpasswd file on the Samba PDC. + If you added the account using an editor rather than using the smbpasswd + utility, make sure that the account name is the machine netbios name + with a '$' appended to it ( ie. computer_name$ ). There must be an entry + in both /etc/passwd and the smbpasswd file. Some people have reported + that inconsistent subnet masks between the Samba server and the NT + client have caused this problem. Make sure that these are consistent + for both client and server. +
"The machine account for this computer either does not -exist or is not accessible."
When I attempt to login to a Samba Domain from a NT4/W2K workstation, + I get a message about my account being disabled. + When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". Whats -wrong ? This problem is caused by a PAM related bug in Samba 2.2.0. This bug is + fixed in 2.2.1. Other symptoms could be unaccessible shares on + NT/W2K member servers in the domain or the following error in your smbd.log: + passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% + This problem is caused by the PDC not having a suitable machine account. -If you are using the At first be ensure to enable the useraccounts with add user script = method to create -accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working. Alternatively if you are creating account entries manually then they -have not been created correctly. Make sure that you have the entry -correct for the machine account in smbpasswd file on the Samba PDC. -If you added the account using an editor rather than using the smbpasswd -utility, make sure that the account name is the machine netbios name -with a '$' appended to it ( ie. computer_name$ ). There must be an entry -in both /etc/passwd and the smbpasswd file. Some people have reported -that inconsistent subnet masks between the Samba server and the NT -client have caused this problem. Make sure that these are consistent -for both client and server. smbpasswd -e + %user%, this is normaly done, when you create an account. + In order to work around this problem in 2.2.0, configure the + account control flag in + /etc/pam.d/samba file as follows: + account required pam_permit.so + If you want to remain backward compatibility to samba 2.0.x use + pam_permit.so, it's also possible to use + pam_pwdb.so. There are some bugs if you try to + use pam_unix.so, if you need this, be ensure to use + the most recent version of this file. +

`System Policies and Profiles`

Here are some additional details:

What about Windows NT Policy Editor ?
+ To create or edit To create or edit ntconfig.pol you must use -the NT Server Policy Editor, poledit.exe which -is included with NT Server but not NT Workstation. -There is a Policy Editor on a NTws -but it is not suitable for creating Domain Policies. -Further, although the Windows 95 -Policy Editor can be installed on an NT Workstation/Server, it will not -work with NT policies because the registry key that are set by the policy templates. -However, the files from the NT Server will run happily enough on an NTws. -You need poledit.exe, common.adm and winnt.adm. It is convenient -to put the two *.adm files in c:\winnt\inf which is where -the binary will look for them unless told otherwise. Note also that that -directory is 'hidden'. The Windows NT policy editor is also included with the -Service Pack 3 (and later) for Windows NT 4.0. Extract the files using - The Windows NT policy editor is also included with the Service Pack 3 (and + later) for Windows NT 4.0. Extract the files using servicepackname /x, ie thats , + ie thats Nt4sp6ai.exe -/x for service pack 6a. The policy editor, Nt4sp6ai.exe /x for service pack 6a. The policy editor, + poledit.exe and the -associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft. and the associated template files (*.adm) should + be extracted as well. It is also possible to downloaded the policy template + files for Office97 and get a copy of the policy editor. Another possible + location is with the Zero Administration Kit available for download from Microsoft. +
Can Win95 do Policies ?
+ Install the group policy handler for Win9x to pick up group -policies. Look on the Win98 CD in Install the group policy handler for Win9x to pick up group + policies. Look on the Win98 CD in \tools\reskit\netadmin\poledit. -Install group policies on a Win9x client by double-clicking -grouppol.inf. Log off and on again a couple of -times and see if Win98 picks up group policies. Unfortunately this needs -to be done on every Win9x machine that uses group policies.... If group policies don't work one reports suggests getting the updated -(read: working) grouppol.dll for Windows 9x. The group list is grabbed -from /etc/group. If group policies don't work one reports suggests getting the updated + (read: working) grouppol.dll for Windows 9x. The group list is grabbed + from /etc/group. +
How do I get 'User Manager' and 'Server Manager'
+ Since I don't need to buy an NT Server CD now, how do I get -the 'User Manager for Domains', the 'Server Manager' ? Since I don't need to buy an NT Server CD now, how do I get + the 'User Manager for Domains', the 'Server Manager' ? + Microsoft distributes a version of -these tools called nexus for installation on Windows 95 systems. The -tools set includes Microsoft distributes a version of these tools called nexus for + installation on Windows 95 systems. The tools set includes + Click here to download the archived file Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE + The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from The Windows NT 4.0 version of the 'User Manager for + Domains' and 'Server Manager' are available from Microsoft via ftp + from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE +

`What other help can I get ?`

What are some diagnostics tools I can use to debug the domain logon -process and where can I find them?
+ 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 @@ -812,7 +1075,7 @@ CLASS="COMMAND" >

An SMB enabled version of tcpdump is available from - http://www.tcpdup.org/

How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?

+ Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes @@ -935,14 +1201,11 @@ CLASS="FILENAME" information on how to do this. Copy the files from a working Netmon installation. URLs and similar

The following is a list if helpful URLs and other links: +

`Mailing Lists`

How do I get help from the mailing lists ?
+ There are a number of Samba related mailing lists. Go to There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror -and then click on Support and then click on Samba related mailing lists. Samba related mailing lists. + For questions relating to Samba TNG go to - For questions relating to Samba TNG go to + http://www.samba-tng.org/ -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists. If you post a message to one of the lists please observe the following guide lines : If you post a message to one of the lists please observe the following guide lines : +
How do I get off the mailing lists ?
+ To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to http://lists.samba.org, click - on your nearest mirror and then click on , + click on your nearest mirror and then click on Support and - then click on Samba related mailing lists. Or perhaps see - here + Please don't post messages to the list asking to be removed, you will just - be referred to the above address (unless that process failed in some way...) -

`Domain Control for Windows 9x/ME`

Note: The following section contains much of the original +DOMAIN.txt file previously included with Samba. Much of +the material is based on what went into the book Special +Edition, Using Samba. (Richard Sharpe)

Network logon support as discussed in this section is aimed at Window for +Workgroups, and Windows 9X clients.

Before launching into the configuration instructions, it is worthwhile looking +at how a Win9X client performs a logon:

The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS address DOMAIN<00> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + \\SERVER. +
The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). +
The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. +
The client then connects to the NetLogon share and searches for this + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. +
The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. +
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 + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented. +
The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for CONFIG.POL, the policies file. If this is + found, it is read and implemented. +

`Configuration Instructions: Network Logons`

To use domain logons and profiles you need to do the following:

Create a share called [netlogon] in your smb.conf. This share should + be readable by all users, and probably should not be writeable. This + share will hold your network logon scripts, and the CONFIG.POL file + (Note: for details on the CONFIG.POL file, how to use it, what it is, + refer to the Microsoft Windows NT Administration documentation. + The format of these files is not known, so you will need to use + Microsoft tools). +
For example I have used: +
```
[netlogon]
+     path = /data/dos/netlogon
+     writeable = no
+     guest ok = no
```
Note that it is important that this share is not writeable by ordinary + users, in a secure environment: ordinary users should not be allowed + to modify or add files that another user's computer would then download + when they log in. +
in the [global] section of smb.conf set the following: +
```
domain logons = yes
+logon script = %U.bat
+	
```
The choice of batch file is, of course, up to you. The above would + give each user a separate batch file as the %U will be changed to + their username automatically. The other standard % macros may also be + used. You can make the batch files come from a subdirectory by using + something like: +
```
logon script = scripts\%U.bat
+	
```
create the batch files to be run when the user logs in. If the batch + file doesn't exist then no batch file will be run. +
In the batch files you need to be careful to use DOS style cr/lf line + endings. If you don't then DOS may get confused. I suggest you use a + DOS editor to remotely edit the files if you don't know how to produce + DOS style files under unix. +
Use smbclient with the -U option for some users to make sure that + the \\server\NETLOGON share is available, the batch files are + visible and they are readable by the users. +
you will probabaly 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. +

security mode and master browsers

Therefore configuring a Samba box as a DC for a domain that +already by definition has a PDC is asking for trouble. +Therefore, you should always configure the Samba DC to be the DMB +for its domain.

`Configuration Instructions: Setting up Roaming User Profiles`

Warning

NOTE! Roaming profiles support is different +for Win9X and WinNT.

Before discussing how to configure roaming profiles, it is useful to see how +Win9X and WinNT clients implement these features.

`Windows NT Configuration`

To support WinNT clients, inn the [global] section of smb.conf set the +following (for example):

logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath

Note: [lkcl 26aug96 - we have discovered a problem where Windows clients can +maintain a connection to the [homes] share in between logins. The +[homes] share must NOT therefore be used in a profile path.]

`Windows 9X Configuration`

To support Win9X clients, you must use the "logon home" parameter. Samba has +now been fixed so that "net use/home" now works as well, and it, too, relies +on the "logon home" parameter.

logon home = \\%L\%U\.profiles

then your Win9X clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden).

`Win9X and WinNT Configuration`

You can support profiles for both Win9X and WinNT clients by setting both the +"logon home" and "logon path" parameters. For example:

logon home = \\%L\%U\.profiles
+logon path = \\%L\profiles\%U

Note: I have not checked what 'net use /home' does on NT when "logon home" is +set as above.

`Windows 9X Profile Setup`

The user.DAT file contains all the user's preferences. If you wish to +enforce a set of preferences, rename their user.DAT file to user.MAN, +and deny them write access to this file.

On the Windows 95 machine, go to Control Panel | Passwords and + select the User Profiles tab. Select the required level of + roaming preferences. Press OK, but do _not_ allow the computer + to reboot. +
On the Windows 95 machine, go to Control Panel | Network | + Client for Microsoft Networks | Preferences. Select 'Log on to + NT Domain'. Then, ensure that the Primary Logon is 'Client for + Microsoft Networks'. Press OK, and this time allow the computer + to reboot. +

instead of logging in under the [user, password, domain] dialog, + press escape. +
run the regedit.exe program, and look in: +
HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList +
you will find an entry, for each user, of ProfilePath. Note the + contents of this key (likely to be c:\windows\profiles\username), + then delete the key ProfilePath for the required user. +
[Exit the registry editor]. +
WARNING - before deleting the contents of the + directory listed in + the ProfilePath (this is likely to be c:\windows\profiles\username), + ask them if they have any important files stored on their desktop + or in their start menu. delete the contents of the directory + ProfilePath (making a backup if any of the files are needed). +
This will have the effect of removing the local (read-only hidden + system file) user.DAT in their profile directory, as well as the + local "desktop", "nethood", "start menu" and "programs" folders. +
search for the user's .PWL password-cacheing file in the c:\windows + directory, and delete it. +
log off the windows 95 client. +
check the contents of the profile path (see "logon path" described + above), and delete the user.DAT or user.MAN file for the user, + making a backup if required. +

If all else fails, increase samba's debug log levels to between 3 and 10, +and / or run a packet trace program such as tcpdump or netmon.exe, and +look for any error reports.

If you have access to an NT server, then first set up roaming profiles +and / or netlogons on the NT server. Make a packet trace, or examine +the example packet traces provided with NT server, and see what the +differences are with the equivalent samba trace.

`Windows NT Workstation 4.0`

When a user first logs in to a Windows NT Workstation, the profile +NTuser.DAT is created. The profile location can be now specified +through the "logon path" parameter.

Note: [lkcl 10aug97 - i tried setting the path to +\\samba-server\homes\profile, and discovered that this fails because +a background process maintains the connection to the [homes] share +which does _not_ close down in between user logins. you have to +have \\samba-server\%L\profile, where user is the username created +from the [homes] share].

Note: [lkcl 10aug97 - i notice that NT Workstation tells me that it is +downloading a profile from a slow link. whether this is actually the +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 +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 +workstation to access the samba server using LAN manager encrypted +passwords, without the user intervention normally required by NT +workstation for clear-text passwords].
[lkcl 25aug97 - more comments received about NT profiles: the case of +the profile _matters_. the file _must_ be called NTuser.DAT or, for +a mandatory profile, NTuser.MAN].

`Windows NT Server`

`Sharing Profiles between W95 and NT Workstation 4.0`

Potentially outdated or incorrect material follows

I think this is all bogus, but have not deleted it. (Richard Sharpe)

If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory.

Note: [lkcl 25aug97 - there are some issues to resolve with downloading of +NT profiles, probably to do with time/date stamps. i have found that +NTuser.DAT is never updated on the workstation after the first time that +it is copied to the local workstation profile directory. this is in +contrast to w95, where it _does_ transfer / update profiles correctly].

`DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba`

This appendix was originally authored by John H Terpstra of the Samba Team -and is included here for posterity.

Possibly Outdated Material

This appendix was originally authored by John H Terpstra of + the Samba Team and is included here for posterity. +

To many people these terms can be confusing, so let's try to clear the air.

`make_smbcodepage`

inputfileThis is the input file to process. In t - he 'This is the input file to process. In + the c' case this will be a text +> case this will be a text codepage definition file such as the ones found in the Samba source/codepages directory. In - the 'd' case this will be the +> case this will be the binary format codepage definition file normally found in the make_unicodemap make_unicodemap Name make_unicodemap -- construct a unicode map file for Samba Synopsis make_unicodemap {codepage} {inputfile} {outputfile} DESCRIPTION This tool is part of the Samba + suite. + make_unicodemap compiles text unicode map + files into binary unicodef map files for use with the + internationalization features of Samba 2.2. + OPTIONS codepage This is the codepage or UNIX character + set we are processing (a number, e.g. 850). + inputfile This is the input file to process. This is a + text unicode map file such as the ones found in the Samba + source/codepages directory. + outputfile This is the binary output file to produce. + Samba Unicode Map Files A text Samba unicode map file is a description that tells Samba + how to map characters from a specified DOS code page or UNIX character + set to 16 bit unicode. + A binary Samba unicode map file is a binary representation + of the same information, including a value that specifies what + codepage or UNIX character set this file is describing. + Files CP<codepage>.TXT These are the input (text) unicode map files provided + in the Samba source/codepages + directory. + A text unicode map file consists of multiple lines + containing two fields. These fields are : + character - which is + the (hex) character mapped on this line. + unicode - which + is the (hex) 16 bit unicode character that the character + will map to. + unicode_map.<codepage> - These are + the output (binary) unicode map files produced and placed in + the Samba destination lib/codepage + directory. + Installation The location of the server and its support files is a matter + for individual system administrators. The following are thus + suggestions only. + It is recommended that the make_unicodemap + program be installed under the + $prefix/samba hierarchy, + in a directory readable by all, writeable only by root. The + program itself should be executable by all. The program + should NOT be setuid or setgid! + VERSION This man page is correct for version 2.2 of + the Samba suite. SEE ALSO smbd(8), + smb.conf(5) + AUTHOR The original Samba software and related utilities + were created by Andrew Tridgell. Samba is now developed + by the Samba Team as an Open Source project similar + to the way the Linux kernel is developed. The original Samba man pages were written by Karl Auer. + The man page sources were converted to YODL format (another + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter \ No newline at end of file diff --git a/docs/htmldocs/printer_driver2.html b/docs/htmldocs/printer_driver2.html index ac845b8433..c44d9c5bf8 100644 --- a/docs/htmldocs/printer_driver2.html +++ b/docs/htmldocs/printer_driver2.html @@ -83,23 +83,61 @@ TARGET="_top" information There has been some initial confusion about what all this means +and whether or not it is a requirement for printer drivers to be +installed on a Samba host in order to support printing from Windows +clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients +require that the Samba server possess a valid driver for the printer. +This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients +can use the local APW for installing drivers to be used with a Samba +served printer. This is the same behavior exhibited by Windows 9x clients. +As a side note, Samba does not use these drivers in any way to process +spooled files. They are utilized entirely by the clients. The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: How to Add Printers with No User +Interaction in Windows 2000 http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP

`Configuration`

WARNING!!! 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 +>

[print$] vs. [printer$]

Migration section +of this document.

`Creating [print$]`

smb.conf(5) man page for more information on -configuring file shares.

smb.conf(5) +man page for more information on configuring file shares.The requirement for guest ok = yesguest +ok = yes depends upon how your site is configured. If users will be guaranteed to have @@ -257,26 +306,26 @@ ALIGN="CENTER" ALIGN="LEFT" > In order to currently add a new driver to you Samba host, - one of two conditions must hold true: The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account) The account used to connect to the Samba host - must be a member of the printer - admin list. Of course, the connected account must still possess access - to add files to the subdirectories beneath [print$]. Setting Drivers for Existing Printers The initial listing of printers in the Samba host's -Printers folder will have no printer driver assigned to them. -The way assign a driver to a printer is to view the Properties -of the printer and either 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: 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? 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
Support a large number of printers$ rpcclient pogo -U root%bleaK.er \ +>rpcclient pogo -U root%secret \ > Adding New Printers via the Windows NT APWprinter admin. +>).
addprinter -commandadd +printer command must have a defined value. The program @@ -499,7 +569,7 @@ CLASS="COMMAND" CLASS="PARAMETER" >add printer -program and reparse to the add printer program is executed undet the context +> is executed under the context of the connected user, not necessarily a root account.There is a complementing deleteprinter -commanddelete +printer command for removing entries from the "Printers..." @@ -533,7 +603,7 @@ CLASS="SECT2" > Samba and Printer Ports The Imprints Toolset What is Imprints? Creating Printer Driver Packages The Imprints server The Installation Client will reveal that Windows NT always uses the NT driver - name. The is ok as Windows NT always requires that at least + 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 @@ -751,18 +821,61 @@ CLASS="SECT1" > Migration to from Samba 2.0.x to - 2.2.xMigration to from Samba 2.0.x to 2.2.x Given that printer driver management has changed - (we hope improved :) ) in 2.2.0 over prior releases, - migration from an existing setup to 2.2.0 can follow - several paths.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.
The following smb.conf parameters are considered to be - depreciated and will be removed soon. Do not use them - in new installationsThe following smb.conf parameters are considered to be depreciated and will +be removed soon. Do not use them in new installations
printer driver file (G) -
printer driver (S) -
printer driver location (S) -
If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.
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 moved to the "this tool is the old way of doing it" - pile.
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).
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 and rpcclient. See the - Imprints installation client at http://imprints.sourceforge.net/ - for an example. -

-l logbasename
File name for log/debug files. .client will be - appended. The log file is never removed by the client. +>File name for log/debug files. The extension + '.client' will be appended. The log file is never removed + by the client.
Set the SMB domain of the username. This - overrides the default domain which is the domain of the - server specified with the -S option. - If the domain specified is the same as the server's NetBIOS name, + overrides the default domain which is the domain defined in + smb.conf. If the domain specified is the same as the server's NetBIOS name, it causes the client to log on using the server's local SAM (as opposed to the Domain SAM).
COMMANDS
lookupsids
- Resolve a list + of SIDs to usernames. +
lookupnames
- Resolve s list + of usernames to SIDs. +
querygroupmem
queryaliasmem
querydispinfo
querydominfo
enumdomgroups

deldriver - Delete the + specified printer driver for all architectures. This + does not delete the actual driver files from the server, + only the entry from the server's list of drivers. +
enumdata - Enumerate all printer setting data stored on the server. On Windows NT clients, @@ -603,7 +641,7 @@ CLASS="COMMAND" >
BUGS
VERSION
AUTHOR
add user scriptadd printer command
add share command
addprinter commandadd user script
change share command
delete user script
deleteprinter commanddelete printer command
dfree commanddelete share command
dns proxydelete user script
domain admin groupdfree command
domain admin usersdns proxy
domain groupsdomain admin group
domain guest users
obey pam restrictions
pam password change

COMPLETE LIST OF SERVICE PARAMETERSEXPLANATION OF EACH PARAMETERadd user script (G) This is the full pathname to a script that will - be run AS ROOT by smbd(8) - under special circumstances described below. Normally, a Samba server requires that UNIX users are - created for all users accessing files on this server. For sites - that use Windows NT account databases as their primary user database - creating these users and keeping the user list in sync with the - Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users - ON DEMAND when a user accesses the Samba server. In order to use this option, smbd - must be set to security=server or security=domain and add user script - must be set to a full pathname for a script that will create a UNIX - user given one argument of %u, which expands into - the UNIX user name to create. When the Windows user attempts to access the Samba server, - at login (session setup in the SMB protocol) time, smbd contacts the password server and - attempts to authenticate the given user with the given password. If the - authentication succeeds then smbd - attempts to find a UNIX user in the UNIX password database to map the - Windows user into. If this lookup fails, and add user script - is set then smbd will - call the specified script AS ROOT, expanding - any %u argument to be the user name to create. If this script successfully creates the user then smbd - will continue on as though the UNIX user - already existed. In this way, UNIX users are dynamically created to - match existing Windows NT accounts. See also security, password server, - delete user - script. Default: add user script = <empty string> - Example: add user script = /usr/local/samba/bin/add_user - %u addprinter command (G) add printer command (G)With the introduction of MS-RPC based printing @@ -4348,7 +4227,8 @@ NAME="ADDPRINTERCOMMAND" physically added to underlying printing system. The addprinter commandadd + printer command defines a script to be run which will perform the necessary operations for adding the printer @@ -4370,7 +4250,7 @@ CLASS="COMMAND" >The addprinter commandadd printer command is automatically invoked with the following parameter (in @@ -4444,7 +4324,7 @@ CLASS="PARAMETER" >Once the addprinter commandadd printer command has been executed, deleteprinter command delete printer command, admin users (S) add share command (G)This is a list of users who will be granted - administrative privileges on the share. This means that they - will do all file operations as the super-user (root). You should use this option very carefully, as any user in - this list will be able to do anything they like on the share, - irrespective of file permissions. Default: no admin users Example: Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + add share command is used to define an + external program or script which will add a new service definition + to smb.conf. In order to successfully + execute the add share command, admin users = jason smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). + When executed, smbd will automatically invoke the + add share command with four parameters. + configFile - the location + of the global smb.conf file. + shareName - the name of the new + share. + pathName - path to an **existing** + directory on disk. + comment - comment string to associate + with the new share. + This parameter is only used for add file shares. To add printer shares, + see the add printer + command. + See also change share + command, delete share + command. + Default: none Example: add share command = /usr/local/bin/addshare add user script (G) This is the full pathname to a script that will + be run AS ROOT by smbd(8) + under special circumstances described below. Normally, a Samba server requires that UNIX users are + created for all users accessing files on this server. For sites + that use Windows NT account databases as their primary user database + creating these users and keeping the user list in sync with the + Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users + ON DEMAND when a user accesses the Samba server. In order to use this option, smbd + must be set to security=server or security=domain and add user script + must be set to a full pathname for a script that will create a UNIX + user given one argument of %u, which expands into + the UNIX user name to create. When the Windows user attempts to access the Samba server, + at login (session setup in the SMB protocol) time, smbd contacts the password server and + attempts to authenticate the given user with the given password. If the + authentication succeeds then smbd + attempts to find a UNIX user in the UNIX password database to map the + Windows user into. If this lookup fails, and add user script + is set then smbd will + call the specified script AS ROOT, expanding + any %u argument to be the user name to create. If this script successfully creates the user then smbd + will continue on as though the UNIX user + already existed. In this way, UNIX users are dynamically created to + match existing Windows NT accounts. See also security, password server, + delete user + script. Default: add user script = <empty string> + Example: add user script = /usr/local/samba/bin/add_user + %u admin users (S) This is a list of users who will be granted + administrative privileges on the share. This means that they + will do all file operations as the super-user (root). You should use this option very carefully, as any user in + this list will be able to do anything they like on the share, + irrespective of file permissions. Default: no admin users Example: admin users = jason change share command (G) Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + change share command is used to define an + external program or script which will modify an existing service definition + in smb.conf. In order to successfully + execute the change share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). + When executed, smbd will automatically invoke the + change share command with four parameters. + configFile - the location + of the global smb.conf file. + shareName - the name of the new + share. + pathName - path to an **existing** + directory on disk. + comment - comment string to associate + with the new share. + This parameter is only used modify existing file shares definitions. To modify + printer shares, use the "Printers..." folder as seen when browsing the Samba host. + See also add share + command, delete + share command. + Default: none Example: change share command = /usr/local/bin/addshare character set (G) parameter. Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the security mask. Default: create mask = 0744debuglevel (G) The value of the parameter (an integer) allows - the debug level (logging level) to be specified in the - smb.conf file. This is to give greater - flexibility in the configuration of the system. The default will be the debug level specified on - the command line or level zero if none was specified. Example: debug level = 3 Synonym for log level. delete printer command (G) With the introduction of MS-RPC based printer + support for Windows NT/2000 clients in Samba 2.2, it is now + possible to delete printer at run time by issuing the + DeletePrinter() RPC call. For a Samba host this means that the printer must be + physically deleted from underlying printing system. The deleteprinter command defines a script to be run which + will perform the necessary operations for removing the printer + from the print system and from smb.conf. + The delete printer command is + automatically called with only one parameter: "printer name". Once the delete printer command has + been executed, smbd will reparse the smb.conf to associated printer no longer exists. + If the sharename is still valid, then smbd + will return an ACCESS_DENIED error to the client. See also add printer command, printing, + show add + printer wizard Default: none Example: deleteprinter command = /usr/bin/removeprinter + delete readonly (S) delete share command (G) Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + delete share command is used to define an + external program or script which will remove an existing service + definition from smb.conf. In order to successfully + execute the delete share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). + When executed, smbd will automatically invoke the + delete share command with two parameters. + configFile - the location + of the global smb.conf file. + shareName - the name of + the existing service. + This parameter is only used to remove file shares. To delete printer shares, + see the delete printer + command. + See also delete share + command, change + share. + Default: none Example: delete share command = /usr/local/bin/delshare delete user script (G) deleteprinter command (G) With the introduction of MS-RPC based printer - support for Windows NT/2000 clients in Samba 2.2, it is now - possible to delete printer at run time by issuing the - DeletePrinter() RPC call. For a Samba host this means that the printer must be - physically deleted from underlying printing system. The deleteprinter command defines a script to be run which - will perform the necessary operations for removing the printer - from the print system and from smb.conf. - The deleteprinter command is - automatically called with only one parameter: "printer name". Once the deleteprinter command has - been executed, smbd will reparse the smb.conf to associated printer no longer exists. - If the sharename is still valid, then smbd - will return an ACCESS_DENIED error to the client. See also addprinter command, printing, - show add - printer wizard Default: none Example: deleteprinter command = /usr/bin/removeprinter - delete veto files (S) parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added). Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the directory security mask. See the If not set explicitly this parameter is set to the same - value as the directory - mask parameter. To allow a user to - modify all the user/group/world permissions on a directory, set - this parameter to 0777. If not set explicitly this parameter is set to 0777 + meaning a user is allowed to modify all the user/group/world + permissions on a directory. Note that users who can access the 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 set - it to 0777. See also the Default: directory security mask = <same as - directory mask>directory security mask = 0777Example: directory security mask = 0777directory security mask = 0700 domain admin group (G) This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at http://lists.samba.org/. domain admin users (G) This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Admins" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + smb.conf notation. + This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at http://lists.samba.org/. See also domain + guest groupdomain groups (G) , domain + logons + This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at http://lists.samba.org/. Default: no domain administrators Example: domain admin group = root @wheel domain guest group (G) This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at http://lists.samba.org/. This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Guests" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + smb.conf notation. + See also domain + admin groupdomain guest users (G) , domain + logons + This is an EXPERIMENTAL parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list samba-ntdom available by - visiting the web page at http://lists.samba.org/. Default: no domain guests Example: domain guest group = nobody @guest parameter is applied.Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the restrict acl with + mask to true. See also the parameter is applied. Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the restrict acl with + mask to true. See also the parameter If not set explicitly this parameter is set to the same - value as the force - directory mode parameter. To allow - a user to modify all the user/group/world permissions on a - directory without restrictions, set this parameter to 000. If not set explicitly this parameter is 000, which + allows a user to modify all the user/group/world permissions on a + directory without restrictions. Note that users who can access the 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 set - it to 0000. See also the Default: force directory security mode = <same as - force directory mode>force directory security mode = 0 Example: force directory security mode = 0force directory security mode = 700 If not set explicitly this parameter is set to the same - value as the force - create mode parameter. To allow a user to - modify all the user/group/world permissions on a file, with no - restrictions set this parameter to 000. If not set explicitly this parameter is set to 0, + and allows a user to modify all the user/group/world permissions on a file, + with no restrictions. Note that users who can access the 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 set - it to 0000. See also the Default: force security mode = <same as force - create mode>force security mode = 0 Example: force security mode = 0force security mode = 700 log level (G) Synonym for debug level. The value of the parameter (an integer) allows + the debug level (logging level) to be specified in the + smb.conf file. This is to give greater + flexibility in the configuration of the system. The default will be the log level specified on + the command line or level zero if none was specified. Example: log level = 3 obey pam restrictions (G) When Samba 2.2 is configure 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 + and to ignore any account or session management. Note that Samba + always ignores PAM for authentication in the case of encrypt passwords = yes + . The reason is that PAM modules cannot support the challenge/response + authentication mechanism needed in the presence of SMB password encryption. + Default: obey pam restrictions = no only user (S) ole locking compatibility (G) This parameter allows an administrator to turn - off the byte range lock manipulation that is done within Samba to - give compatibility for OLE applications. Windows OLE applications - use byte range locking as a form of inter-process communication, by - locking ranges of bytes around the 2^32 region of a file range. This - can cause certain UNIX lock managers to crash or otherwise cause - problems. Setting this parameter to no means you - trust your UNIX lock manager to handle such cases correctly. Default: ole locking compatibility = yes only guest (S) pam password change (G) 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 chat must be + be changed to work with the pam prompts. + Default: pam password change = no panic action (G) Also, 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. + See also passwd program and , passwd chat debug and pam password change. 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 + 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 + parameters create mask, + force create mode + applied before setting the ACL, and all requests to set an ACL on a directory will + have the parameters directory + mask, force + directory mode applied before setting the ACL. + See also create mask, + force create mode, + directory mask, + force directory mode + Default: restrict acl with mask = no restrict anonymous (G) If not set explicitly this parameter is set to the same - value as the create mask - parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter to - 0777. If not set explicitly this parameter is 0777, allowing + a user to modify all the user/group/world permissions on a file. + Note See also the Default: security mask = <same as create mask> - security mask = 0777 Example: security mask = 0777security mask = 0770 WARNINGS VERSION SEE ALSO AUTHOR smbcontrol smbspool Name nmblookup -- send print file to an SMB printer smbspool -- send print file to an SMB printer smbstatus nmblookupswat [-s <smb config file>] [-a]

4.4. Migration to from Samba 2.0.x to - 2.2.xMigration to from Samba 2.0.x to 2.2.x

Chapter 6. How to Configure Samba 2.2.x as a Primary Domain ControllerChapter 6. How to Configure Samba 2.2 as a Primary Domain Controller

6.1. Background6.1. Prerequisite Reading

6.2. Configuring the Samba Domain Controller6.3. Configuring the Samba Domain Controller

6.4. Common Problems and Errors6.5. Common Problems and Errors

6.5. System Policies and Profiles6.6. System Policies and Profiles

6.6. What other help can I get ?6.7. What other help can I get ?

6.7. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba

Name

Synopsis

DESCRIPTION

OPTIONS

Samba Unicode Map Files

Files

Installation

VERSION

SEE ALSO

AUTHOR

Migration to from Samba 2.0.x to - 2.2.xMigration to from Samba 2.0.x to 2.2.x

COMMANDS

BUGS

VERSION

AUTHOR

COMPLETE LIST OF SERVICE PARAMETERS

EXPLANATION OF EACH PARAMETER

WARNINGS

VERSION

SEE ALSO

AUTHOR

Name

`6.4. Common Problems and Errors6.5. Common Problems and Errors`

`6.5. System Policies and Profiles6.6. System Policies and Profiles`

`6.6. What other help can I get ?6.7. What other help can I get ?`

`6.7. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba`