sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-03-10 12:58:35 +03:00
Code

Merge over Alexanders' conversion to docbook XML

Browse Source 
(This used to be commit e75624c382d640747b54ba43f134fa043d23b7fe)
This commit is contained in:
Jelmer Vernooij 2003-05-01 13:58:23 +00:00
parent 866fce117e
commit b39559c4e5
44 changed files with 0 additions and 17628 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

101
docs/docbook/faq/clientapp.sgml
View File

@ -1,101 +0,0 @@
<chapter id="ClientApp">
<title>Specific client application problems</title>
<sect1>
<title>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</title>
<para>
When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the
setup program unable to complete the installation.
</para>
<para>
To get around this problem, do the installation without admin user
permissions The problem is that MS Office Setup checks that a file is
rdonly by trying to open it for writing.
</para>
<para>
Admin users can always open a file for writing, as they run as root.
You just have to install as a non-admin user and then use "chown -R"
to fix the owner.
</para>
</sect1>
<sect1>
<title>How to use a Samba share as an administrative share for MS Office, etc.</title>
<para>
Microsoft Office products can be installed as an administrative installation
from which the application can either be run off the administratively installed
product that resides on a shared resource, or from which that product can be
installed onto workstation clients.
</para>
<para>
The general mechanism for implementing an adminstrative installation involves
running <command>X:\setup /A</command>, where X is the drive letter of either CDROM or floppy.
</para>
<para>
This installation process will NOT install the product for use per se, but
rather results in unpacking of the compressed distribution files into a target
shared folder. For this process you need write privilidge to the share and it
is desirable to enable file locking and share mode operation during this
process.
</para>
<para>
Subsequent installation of MS Office from this share will FAIL unless certain
precautions are taken. This failure will be caused by share mode operation
which will prevent the MS Office installation process from re-opening various
dynamic link library files and will cause sporadic file not found problems.
</para>
<itemizedlist>
<listitem><para>
As soon as the administrative installation (unpacking) has completed
set the following parameters on the share containing it:
</para>
<para><programlisting>
[MSOP95]
path = /where_you_put_it
comment = Your comment
volume = "The_CD_ROM_Label"
read only = yes
available = yes
share modes = no
locking = no
browseable = yes
public = yes
</programlisting></para>
</listitem>
<listitem>
<para>Now you are ready to run the setup program from the Microsoft Windows
workstation as follows: <command>\\"Server_Name"\MSOP95\msoffice\setup</command>
</para>
</listitem>
</itemizedlist>
</sect1>
<sect1>
<title>Microsoft Access database opening errors</title>
<para>
Here are some notes on running MS-Access on a Samba drive from <ulink url="stefank@esi.com.au">Stefan Kjellberg</ulink>
</para>
<para><simplelist>
<member>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</member>
<member>Make sure that you open the database as 'shared' and to 'lock modified records'</member>
<member>Of course locking must be enabled for the particular share (smb.conf)</member>
</simplelist>
</para>
</sect1>
</chapter>

11
docs/docbook/faq/config.sgml
View File

@ -1,11 +0,0 @@
<chapter id="Config">
<title>Configuration problems</title>
<sect1>
<title>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</title>
<para>
When you have a user in 'admin users', samba will always do file operations for
this user as 'root', even if 'force user' has been set.
</para>
</sect1>
</chapter>

178
docs/docbook/faq/errors.sgml
View File

@ -1,178 +0,0 @@
<chapter id="errors">
<title>Common errors</title>
<sect1>
<title>Not listening for calling name</title>
<para>
<programlisting>
Session request failed (131,129) with myname=HOBBES destname=CALVIN
Not listening for calling name
</programlisting>
</para>
<para>
If you get this when talking to a Samba box then it means that your
global "hosts allow" or "hosts deny" settings are causing the Samba
server to refuse the connection.
</para>
<para>
Look carefully at your "hosts allow" and "hosts deny" lines in the
global section of smb.conf.
</para>
<para>
It can also be a problem with reverse DNS lookups not functioning
correctly, leading to the remote host identity not being able to
be confirmed, but that is less likely.
</para>
</sect1>
<sect1>
<title>System Error 1240</title>
<para>
System error 1240 means that the client is refusing to talk
to a non-encrypting server. Microsoft changed WinNT in service
pack 3 to refuse to connect to servers that do not support
SMB password encryption.
</para>
<para>There are two main solutions:
<simplelist>
<member>enable SMB password encryption in Samba. See the encryption part of
the samba HOWTO Collection</member>
<member>disable this new behaviour in NT. See the section about
Windows NT in the chapter "Portability" of the samba HOWTO collection
</member>
</simplelist>
</para>
</sect1>
<sect1>
<title>smbclient ignores -N !</title>
<para>
<quote>When getting the list of shares available on a host using the command
<command>smbclient -N -L</command>
the program always prompts for the password if the server is a Samba server.
It also ignores the "-N" argument when querying some (but not all) of our
NT servers.
</quote>
</para>
<para>
No, it does not ignore -N, it is just that your server rejected the
null password in the connection, so smbclient prompts for a password
to try again.
</para>
<para>
To get the behaviour that you probably want use <command>smbclient -L host -U%</command>
</para>
<para>
This will set both the username and password to null, which is
an anonymous login for SMB. Using -N would only set the password
to null, and this is not accepted as an anonymous login for most
SMB servers.
</para>
</sect1>
<sect1>
<title>The data on the CD-Drive I've shared seems to be corrupted!</title>
<para>
Some OSes (notably Linux) default to auto detection of file type on
cdroms and do cr/lf translation. This is a very bad idea when use with
Samba. It causes all sorts of stuff ups.
</para>
<para>
To overcome this problem use conv=binary when mounting the cdrom
before exporting it with Samba.
</para>
</sect1>
<sect1>
<title>Why can users access home directories of other users?</title>
<para>
<quote>
We are unable to keep individual users from mapping to any other user's
home directory once they have supplied a valid password! They only need
to enter their own password. I have not found *any* method that I can
use to configure samba to enforce that only a user may map their own
home directory.
</quote>
</para>
<para><quote>
User xyzzy can map his home directory. Once mapped user xyzzy can also map
*anyone* elses home directory!
</quote></para>
<para>
This is not a security flaw, it is by design. Samba allows
users to have *exactly* the same access to the UNIX filesystem
as they would if they were logged onto the UNIX box, except
that it only allows such views onto the file system as are
allowed by the defined shares.
</para>
<para>
This means that if your UNIX home directories are set up
such that one user can happily cd into another users
directory and do an ls, the UNIX security solution is to
change the UNIX file permissions on the users home directories
such that the cd and ls would be denied.
</para>
<para>
Samba tries very hard not to second guess the UNIX administrators
security policies, and trusts the UNIX admin to set
the policies and permissions he or she desires.
</para>
<para>
Samba does allow the setup you require when you have set the
"only user = yes" option on the share, is that you have not set the
valid users list for the share.
</para>
<para>
Note that only user works in conjunction with the users= list,
so to get the behavior you require, add the line :
<programlisting>
users = %S
</programlisting>
this is equivalent to:
<programlisting>
valid users = %S
</programlisting>
to the definition of the [homes] share, as recommended in
the smb.conf man page.
</para>
</sect1>
<sect1>
<title>Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</title>
<para>
A domain controller has to announce on the network who it is. This usually takes a while.
</para>
</sect1>
<sect1>
<title>I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</title>
<para>Your loopback device isn't working correctly. Make sure it's running.
</para>
</sect1>
</chapter>

376
docs/docbook/faq/features.sgml
View File

@ -1,376 +0,0 @@
<chapter id="features">
<title>Features</title>
<sect1>
<title>How can I prevent my samba server from being used to distribute the Nimda worm?</title>
<para>Author: HASEGAWA Yosuke (translated by <ulink url="monyo@samba.gr.jp">TAKAHASHI Motonobu</ulink>)</para>
<para>
Nimba Worm is infected through shared disks on a network, as well as through
Microsoft IIS, Internet Explorer and mailer of Outlook series.
</para>
<para>
At this time, the worm copies itself by the name *.nws and *.eml on
the shared disk, moreover, by the name of Riched20.dll in the folder
where *.doc file is included.
</para>
<para>
To prevent infection through the shared disk offered by Samba, set
up as follows:
</para>
<para>
<programlisting>
[global]
...
# This can break Administration installations of Office2k.
# in that case, don't veto the riched20.dll
veto files = /*.eml/*.nws/riched20.dll/
</programlisting>
</para>
<para>
By setting the "veto files" parameter, matched files on the Samba
server are completely hidden from the clients and making it impossible
to access them at all.
</para>
<para>
In addition to it, the following setting is also pointed out by the
samba-jp:09448 thread: when the
"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on
a Samba server, it is visible only as "readme.txt" and dangerous
code may be executed if this file is double-clicked.
</para>
<para>
Setting the following,
<programlisting>
veto files = /*.{*}/
</programlisting>
any files having CLSID in its file extension will be inaccessible from any
clients.
</para>
<para>
This technical article is created based on the discussion of
samba-jp:09448 and samba-jp:10900 threads.
</para>
</sect1>
<sect1>
<title>How can I use samba as a fax server?</title>
<para>Contributor: <ulink url="mailto:zuber@berlin.snafu.de">Gerhard Zuber</ulink></para>
<para>Requirements:
<simplelist>
<member>UNIX box (Linux preferred) with SAMBA and a faxmodem</member>
<member>ghostscript package</member>
<member>mgetty+sendfax package</member>
<member>pbm package (portable bitmap tools)</member>
</simplelist>
</para>
<para>First, install and configure the required packages. Be sure to read the mgetty+sendfax
manual carefully.</para>
<sect2>
<title>Tools for printing faxes</title>
<para>Your incomed faxes are in:
<filename>/var/spool/fax/incoming</filename></para>
<para>print it with:</para>
<para><programlisting>
for i in *
do
g3cat $i | g3tolj | lpr -P hp
done
</programlisting>
</para>
<para>
g3cat is in the tools-section, g3tolj is in the contrib-section
for printing to HP lasers.
</para>
<para>
If you want to produce files for displaying and printing with Windows, use
some tools from the pbm-package like the following command: <command>g3cat $i | g3topbm - | ppmtopcx - >$i.pcx</command>
and view it with your favourite Windows tool (maybe paintbrush)
</para>
</sect2>
<sect2>
<title>Making the fax-server</title>
<para>fetch the file <filename>mgetty+sendfax/frontends/winword/faxfilter</filename> and place it in <filename>/usr/local/etc/mgetty+sendfax/</filename>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</para>
<para>prepare your faxspool file as mentioned in this file
edit fax/faxspool.in and reinstall or change the final
/usr/local/bin/faxspool too.
</para>
<para><programlisting>
if [ "$user" = "root" -o "$user" = "fax" -o \
"$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
</programlisting></para>
<para>find the first line and change it to the second.</para>
<para>
make sure you have pbmtext (from the pbm-package). This is
needed for creating the small header line on each page.
</para>
<para>Prepare your faxheader <filename>/usr/local/etc/mgetty+sendfax/faxheader</filename></para>
<para>
Edit your /etc/printcap file:
<programlisting>
# FAX
lp3|fax:\
:lp=/dev/null:\
:sd=/usr/spool/lp3:\
:if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
:lf=/usr/spool/lp3/fax-log:
</programlisting></para>
<para>Now, edit your <filename>smb.conf</filename> so you have a smb based printer named "fax"</para>
</sect2>
<sect2>
<title>Installing the client drivers</title>
<para>
Now you have a printer called "fax" which can be used via
TCP/IP-printing (lpd-system) or via SAMBA (windows printing).
</para>
<para>
On every system you are able to produce postscript-files you
are ready to fax.
</para>
<para>
On Windows 3.1 95 and NT:
</para>
<para>
Install a printer wich produces postscript output,
e.g. apple laserwriter
</para>
<para>Connect the "fax" to your printer.</para>
<para>
Now write your first fax. Use your favourite wordprocessor,
write, winword, notepad or whatever you want, and start
with the headerpage.
</para>
<para>
Usually each fax has a header page. It carries your name,
your address, your phone/fax-number.
</para>
<para>
It carries also the recipient, his address and his *** fax
number ***. Now here is the trick:
</para>
<para>
Use the text:
<programlisting>
Fax-Nr: 123456789
</programlisting>
as the recipients fax-number. Make sure this text does not
occur in regular text ! Make sure this text is not broken
by formatting information, e.g. format it as a single entity.
(Windows Write and Win95 Wordpad are functional, maybe newer
versions of Winword are breaking formatting information).
</para>
<para>
The trick is that postscript output is human readable and
the faxfilter program scans the text for this pattern and
uses the found number as the fax-destination-number.
</para>
<para>
Now print your fax through the fax-printer and it will be
queued for later transmission. Use faxrunq for sending the
queue out.
</para>
</sect2>
<sect2>
<title>Example smb.conf</title>
<para><programlisting>
[global]
printcap name = /etc/printcap
print command = /usr/bin/lpr -r -P %p %s
lpq command = /usr/bin/lpq -P %p
lprm command = /usr/bin/lprm -P %p %j
[fax]
comment = FAX (mgetty+sendfax)
path = /tmp
printable = yes
public = yes
writable = no
create mode = 0700
browseable = yes
guest ok = no
</programlisting></para>
</sect2>
</sect1>
<sect1>
<title>Samba doesn't work well together with DHCP!</title>
<para>
We wish to help those folks who wish to use the ISC DHCP Server and provide
sample configuration settings. Most operating systems today come ship with
the ISC DHCP Server. ISC DHCP is available from:
<ulink url="ftp://ftp.isc.org/isc/dhcp">ftp://ftp.isc.org/isc/dhcp</ulink>
</para>
<para>
Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows
NT/2000) will lead to problems with browsing and with general network
operation. Windows 9X/ME users often report problems where the TCP/IP and related
network settings will inadvertantly become reset at machine start-up resulting
in loss of configuration settings. This results in increased maintenance
overheads as well as serious user frustration.
</para>
<para>
In recent times users on one mailing list incorrectly attributed the cause of
network operating problems to incorrect configuration of Samba.
</para>
<para>
One user insisted that the only way to provent Windows95 from periodically
performing a full system reset and hardware detection process on start-up was
to install the NetBEUI protocol in addition to TCP/IP. This assertion is not
correct.
</para>
<para>
In the first place, there is NO need for NetBEUI. All Microsoft Windows clients
natively run NetBIOS over TCP/IP, and that is the only protocol that is
recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will
cause problems with browse list operation on most networks. Even Windows NT
networks experience these problems when incorrectly configured Windows95
systems share the same name space. It is important that only those protocols
that are strictly needed for site specific reasons should EVER be installed.
</para>
<para>
Secondly, and totally against common opinion, DHCP is NOT an evil design but is
an extension of the BOOTP protocol that has been in use in Unix environments
for many years without any of the melt-down problems that some sensationalists
would have us believe can be experienced with DHCP. In fact, DHCP in covered by
rfc1541 and is a very safe method of keeping an MS Windows desktop environment
under control and for ensuring stable network operation.
</para>
<para>
Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95
store all network configuration settings a registry. There are a few reports
from MS Windows network administrators that warrant mention here. It would appear
that when one sets certain MS TCP/IP protocol settings (either directly or via
DHCP) that these do get written to the registry. Even though a subsequent
change of setting may occur the old value may persist in the registry. This
has been known to create serious networking problems.
</para>
<para>
An example of this occurs when a manual TCP/IP environment is configured to
include a NetBIOS Scope. In this event, when the administrator then changes the
configuration of the MS TCP/IP protocol stack, without first deleting the
current settings, by simply checking the box to configure the MS TCP/IP stack
via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be
applied to the resulting DHCP offered settings UNLESS the DHCP server also sets
a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS
Scope from your DHCP server. The can be done in the dhcpd.conf file with the
parameter:
<command>option netbios-scope "";</command>
</para>
<para>
While it is true that the Microsoft DHCP server that comes with Windows NT
Server provides only a sub-set of rfc1533 functionality this is hardly an issue
in those sites that already have a large investment and commitment to Unix
systems and technologies. The current state of the art of the DHCP Server
specification in covered in rfc2132.
</para>
</sect1>
<sect1>
<title>How can I assign NetBIOS names to clients with DHCP?</title>
<para>
SMB network clients need to be configured so that all standard TCP/IP name to
address resolution works correctly. Once this has been achieved the SMB
environment provides additional tools and services that act as helper agents in
the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One
such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it
in their Windows NT Server implementation WINS (Windows Internet Name Server).
</para>
<para>
A client needs to be configured so that it has a unique Machine (Computer)
Name.
</para>
<para>
This can be done, but needs a few NT registry hacks and you need to be able to
speak UNICODE, which is of course no problem for a True Wizzard(tm) :)
Instructions on how to do this (including a small util for less capable
Wizzards) can be found at
</para>
<para><ulink url="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html">http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</ulink></para>
</sect1>
<sect1>
<title>How do I convert between unix and dos text formats?</title>
<para>
Jim barry has written an <ulink url="ftp://samba.org/pub/samba/contributed/fixcrlf.zip">
excellent drag-and-drop cr/lf converter for
windows</ulink>. Just drag your file onto the icon and it converts the file.
</para>
<para>
The utilities unix2dos and dos2unix(in the mtools package) should do
the job under unix.
</para>
</sect1>
<sect1>
<title>Does samba have wins replication support?</title>
<para>
At the time of writing there is currently being worked on a wins replication implementation(wrepld).
</para>
</sect1>
</chapter>

170
docs/docbook/faq/general.sgml
View File

@ -1,170 +0,0 @@
<chapter id="general">
<title>General Information</title>
<sect1>
<title>Where can I get it?</title>
<para>
The Samba suite is available at the <ulink url="http://samba.org/">samba website</ulink>.
</para>
</sect1>
<sect1>
<title>What do the version numbers mean?</title>
<para>
It is not recommended that you run a version of Samba with the word
"alpha" in its name unless you know what you are doing and are willing
to do some debugging. Many, many people just get the latest
recommended stable release version and are happy. If you are brave, by
all means take the plunge and help with the testing and development -
but don't install it on your departmental server. Samba is typically
very stable and safe, and this is mostly due to the policy of many
public releases.
</para>
<para>
How the scheme works:
<simplelist>
<member>When major changes are made the version number is increased. For
example, the transition from 1.9.15 to 1.9.16. However, this version
number will not appear immediately and people should continue to use
1.9.15 for production systems (see next point.)</member>
<member>Just after major changes are made the software is considered
unstable, and a series of alpha releases are distributed, for example
1.9.16alpha1. These are for testing by those who know what they are
doing. The "alpha" in the filename will hopefully scare off those who
are just looking for the latest version to install.</member>
<member>When Andrew thinks that the alphas have stabilised to the point
where he would recommend new users install it, he renames it to the
same version number without the alpha, for example 1.9.16.</member>
<member>Inevitably bugs are found in the "stable" releases and minor patch
levels are released which give us the pXX series, for example 1.9.16p2.</member>
</simplelist>
</para>
<para>
So the progression goes:
<programlisting>
1.9.15p7 (production)
1.9.15p8 (production)
1.9.16alpha1 (test sites only)
:
1.9.16alpha20 (test sites only)
1.9.16 (production)
1.9.16p1 (production)
</programlisting>
</para>
<para>
The above system means that whenever someone looks at the samba ftp
site they will be able to grab the highest numbered release without an
alpha in the name and be sure of getting the current recommended
version.
</para>
</sect1>
<sect1>
<title>What platforms are supported?</title>
<para>
Many different platforms have run Samba successfully. The platforms
most widely used and thus best tested are Linux and SunOS.</para>
<para>
At time of writing, there is support (or has been support for in earlier
versions):
</para>
<simplelist>
<member>A/UX 3.0</member>
<member>AIX</member>
<member>Altos Series 386/1000</member>
<member>Amiga</member>
<member>Apollo Domain/OS sr10.3</member>
<member>BSDI </member>
<member>B.O.S. (Bull Operating System)</member>
<member>Cray, Unicos 8.0</member>
<member>Convex</member>
<member>DGUX. </member>
<member>DNIX.</member>
<member>FreeBSD</member>
<member>HP-UX</member>
<member>Intergraph. </member>
<member>Linux with/without shadow passwords and quota</member>
<member>LYNX 2.3.0</member>
<member>MachTen (a unix like system for Macintoshes)</member>
<member>Motorola 88xxx/9xx range of machines</member>
<member>NetBSD</member>
<member>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</member>
<member>OS/2 using EMX 0.9b</member>
<member>OSF1</member>
<member>QNX 4.22</member>
<member>RiscIX. </member>
<member>RISCOs 5.0B</member>
<member>SEQUENT. </member>
<member>SCO (including: 3.2v2, European dist., OpenServer 5)</member>
<member>SGI.</member>
<member>SMP_DC.OSx v1.1-94c079 on Pyramid S series</member>
<member>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</member>
<member>SUNOS 4</member>
<member>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</member>
<member>Sunsoft ISC SVR3V4</member>
<member>SVR4</member>
<member>System V with some berkely extensions (Motorola 88k R32V3.2).</member>
<member>ULTRIX.</member>
<member>UNIXWARE</member>
<member>UXP/DS</member>
</simplelist>
</sect1>
<sect1>
<title>How do I subscribe to the Samba Mailing Lists?</title>
<para>
Look at <ulink url="http://samba.org/samba/archives.html">the samba mailing list page</ulink>
</para>
</sect1>
<sect1>
<title>Pizza supply details</title>
<para>
Those who have registered in the Samba survey as "Pizza Factory" will
already know this, but the rest may need some help. Andrew doesn't ask
for payment, but he does appreciate it when people give him
pizza. This calls for a little organisation when the pizza donor is
twenty thousand kilometres away, but it has been done.
</para>
<para>
Method 1: Ring up your local branch of an international pizza chain
and see if they honour their vouchers internationally. Pizza Hut do,
which is how the entire Canberra Linux Users Group got to eat pizza
one night, courtesy of someone in the US.
</para>
<para>
Method 2: Ring up a local pizza shop in Canberra and quote a credit
card number for a certain amount, and tell them that Andrew will be
collecting it (don't forget to tell him.) One kind soul from Germany
did this.
</para>
<para>
Method 3: Purchase a pizza voucher from your local pizza shop that has
no international affiliations and send it to Andrew. It is completely
useless but he can hang it on the wall next to the one he already has
from Germany :-)
</para>
<para>
Method 4: Air freight him a pizza with your favourite regional
flavours. It will probably get stuck in customs or torn apart by
hungry sniffer dogs but it will have been a noble gesture.
</para>
</sect1>
</chapter>

333
docs/docbook/faq/install.sgml
View File

@ -1,333 +0,0 @@
<chapter id="Install">
<title>Compiling and installing Samba on a Unix host</title>
<sect1>
<title>I can't see the Samba server in any browse lists!</title>
<para>
See Browsing.html in the docs directory of the samba source
for more information on browsing.
</para>
<para>
If your GUI client does not permit you to select non-browsable
servers, you may need to do so on the command line. For example, under
Lan Manager you might connect to the above service as disk drive M:
thusly:
<programlisting>
net use M: \\mary\fred
</programlisting>
The details of how to do this and the specific syntax varies from
client to client - check your client's documentation.
</para>
</sect1>
<sect1>
<title>Some files that I KNOW are on the server doesn't show up when I view the files from my client!</title>
<para>See the next question.</para>
</sect1>
<sect1>
<title>Some files on the server show up with really wierd filenames when I view the files from my client!</title>
<para>
If you check what files are not showing up, you will note that they
are files which contain upper case letters or which are otherwise not
DOS-compatible (ie, they are not legal DOS filenames for some reason).
</para>
<para>
The Samba server can be configured either to ignore such files
completely, or to present them to the client in "mangled" form. If you
are not seeing the files at all, the Samba server has most likely been
configured to ignore them. Consult the man page smb.conf(5) for
details of how to change this - the parameter you need to set is
"mangled names = yes".
</para>
</sect1>
<sect1>
<title>My client reports "cannot locate specified computer" or similar</title>
<para>
This indicates one of three things: You supplied an incorrect server
name, the underlying TCP/IP layer is not working correctly, or the
name you specified cannot be resolved.
</para>
<para>
After carefully checking that the name you typed is the name you
should have typed, try doing things like pinging a host or telnetting
to somewhere on your network to see if TCP/IP is functioning OK. If it
is, the problem is most likely name resolution.
</para>
<para>
If your client has a facility to do so, hardcode a mapping between the
hosts IP and the name you want to use. For example, with Lan Manager
or Windows for Workgroups you would put a suitable entry in the file
LMHOSTS. If this works, the problem is in the communication between
your client and the netbios name server. If it does not work, then
there is something fundamental wrong with your naming and the solution
is beyond the scope of this document.
</para>
<para>
If you do not have any server on your subnet supplying netbios name
resolution, hardcoded mappings are your only option. If you DO have a
netbios name server running (such as the Samba suite's nmbd program),
the problem probably lies in the way it is set up. Refer to Section
Two of this FAQ for more ideas.
</para>
<para>
By the way, remember to REMOVE the hardcoded mapping before further
tests :-)
</para>
</sect1>
<sect1>
<title>My client reports "cannot locate specified share name" or similar</title>
<para>
This message indicates that your client CAN locate the specified
server, which is a good start, but that it cannot find a service of
the name you gave.
</para>
<para>
The first step is to check the exact name of the service you are
trying to connect to (consult your system administrator). Assuming it
exists and you specified it correctly (read your client's docs on how
to specify a service name correctly), read on:
</para>
<simplelist>
<member>Many clients cannot accept or use service names longer than eight characters.</member>
<member>Many clients cannot accept or use service names containing spaces.</member>
<member>Some servers (not Samba though) are case sensitive with service names.</member>
<member>Some clients force service names into upper case.</member>
</simplelist>
</sect1>
<sect1>
<title>Printing doesn't work</title>
<para>
Make sure that the specified print command for the service you are
connecting to is correct and that it has a fully-qualified path (eg.,
use "/usr/bin/lpr" rather than just "lpr").
</para>
<para>
Make sure that the spool directory specified for the service is
writable by the user connected to the service. In particular the user
"nobody" often has problems with printing, even if it worked with an
earlier version of Samba. Try creating another guest user other than
"nobody".
</para>
<para>
Make sure that the user specified in the service is permitted to use
the printer.
</para>
<para>
Check the debug log produced by smbd. Search for the printer name and
see if the log turns up any clues. Note that error messages to do with
a service ipc$ are meaningless - they relate to the way the client
attempts to retrieve status information when using the LANMAN1
protocol.
</para>
<para>
If using WfWg then you need to set the default protocol to TCP/IP, not
Netbeui. This is a WfWg bug.
</para>
<para>
If using the Lanman1 protocol (the default) then try switching to
coreplus. Also not that print status error messages don't mean
printing won't work. The print status is received by a different
mechanism.
</para>
</sect1>
<sect1>
<title>My client reports "This server is not configured to list shared resources"</title>
<para>
Your guest account is probably invalid for some reason. Samba uses the
guest account for browsing in smbd. Check that your guest account is
valid.
</para>
<para>See also 'guest account' in smb.conf man page.</para>
</sect1>
<sect1>
<title>Log message "you appear to have a trapdoor uid system" </title>
<para>
This can have several causes. It might be because you are using a uid
or gid of 65535 or -1. This is a VERY bad idea, and is a big security
hole. Check carefully in your /etc/passwd file and make sure that no
user has uid 65535 or -1. Especially check the "nobody" user, as many
broken systems are shipped with nobody setup with a uid of 65535.
</para>
<para>It might also mean that your OS has a trapdoor uid/gid system :-)</para>
<para>
This means that once a process changes effective uid from root to
another user it can't go back to root. Unfortunately Samba relies on
being able to change effective uid from root to non-root and back
again to implement its security policy. If your OS has a trapdoor uid
system this won't work, and several things in Samba may break. Less
things will break if you use user or server level security instead of
the default share level security, but you may still strike
problems.
</para>
<para>
The problems don't give rise to any security holes, so don't panic,
but it does mean some of Samba's capabilities will be unavailable.
In particular you will not be able to connect to the Samba server as
two different uids at once. This may happen if you try to print as a
"guest" while accessing a share as a normal user. It may also affect
your ability to list the available shares as this is normally done as
the guest user.
</para>
<para>
Complain to your OS vendor and ask them to fix their system.
</para>
<para>
Note: the reason why 65535 is a VERY bad choice of uid and gid is that
it casts to -1 as a uid, and the setreuid() system call ignores (with
no error) uid changes to -1. This means any daemon attempting to run
as uid 65535 will actually run as root. This is not good!
</para>
</sect1>
<sect1>
<title>Why are my file's timestamps off by an hour, or by a few hours?</title>
<para>
This is from Paul Eggert eggert@twinsun.com.
</para>
<para>
Most likely it's a problem with your time zone settings.
</para>
<para>
Internally, Samba maintains time in traditional Unix format,
namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
(or ``GMT''), not counting leap seconds.
</para>
<para>
On the server side, Samba uses the Unix TZ variable to convert
internal timestamps to and from local time. So on the server side, there are
two things to get right.
<simplelist>
<member>The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</member>
<member>The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</member>
</simplelist>
</para>
<para>TZ must have the correct value.</para>
<para>
If possible, use geographical time zone settings
(e.g. TZ='America/Los_Angeles' or perhaps
TZ=':US/Pacific'). These are supported by most
popular Unix OSes, are easier to get right, and are
more accurate for historical timestamps. If your
operating system has out-of-date tables, you should be
able to update them from the public domain time zone
tables at <ulink url="ftp://elsie.nci.nih.gov/pub/">ftp://elsie.nci.nih.gov/pub/</ulink>.
</para>
<para>If your system does not support geographical timezone
settings, you must use a Posix-style TZ strings, e.g.
TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
Posix TZ strings can take the following form (with optional
items in brackets):
<programlisting>
StdOffset[Dst[Offset],Date/Time,Date/Time]
</programlisting>
where:
</para>
<para><simplelist>
<member>`Std' is the standard time designation (e.g. `PST').</member>
<member>`Offset' is the number of hours behind UTC (e.g. `8').
Prepend a `-' if you are ahead of UTC, and
append `:30' if you are at a half-hour offset.
Omit all the remaining items if you do not use
daylight-saving time.</member>
<member>`Dst' is the daylight-saving time designation
(e.g. `PDT').</member>
<member>The optional second `Offset' is the number of
hours that daylight-saving time is behind UTC.
The default is 1 hour ahead of standard time.
</member>
<member>`Date/Time,Date/Time' specify when daylight-saving
time starts and ends. The format for a date is
`Mm.n.d', which specifies the dth day (0 is Sunday)
of the nth week of the mth month, where week 5 means
the last such day in the month. The format for a
time is [h]h[:mm[:ss]], using a 24-hour clock.
</member>
</simplelist>
</para>
<para>
Other Posix string formats are allowed but you don't want
to know about them.</para>
<para>
On the client side, you must make sure that your client's clock and
time zone is also set appropriately. [[I don't know how to do this.]]
Samba traditionally has had many problems dealing with time zones, due
to the bizarre ways that Microsoft network protocols handle time
zones.
</para>
</sect1>
<sect1>
<title>How do I set the printer driver name correctly?</title>
<para>Question:
<quote> On NT, I opened "Printer Manager" and "Connect to Printer".
Enter ["\\ptdi270\ps1"] in the box of printer. I got the
following error message
</quote></para>
<para>
<programlisting>
You do not have sufficient access to your machine
to connect to the selected printer, since a driver
needs to be installed locally.
</programlisting>
</para>
<para>Answer:</para>
<para>In the more recent versions of Samba you can now set the "printer
driver" in smb.conf. This tells the client what driver to use. For
example:</para>
<para><programlisting>
printer driver = HP LaserJet 4L
</programlisting></para>
<para>With this, NT knows to use the right driver. You have to get this string
exactly right.</para>
<para>To find the exact string to use, you need to get to the dialog box in
your client where you select which printer driver to install. The
correct strings for all the different printers are shown in a listbox
in that dialog box.</para>
</sect1>
</chapter>

37
docs/docbook/faq/sambafaq.sgml
View File

@ -1,37 +0,0 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY general SYSTEM "general.sgml">
<!ENTITY install SYSTEM "install.sgml">
<!ENTITY errors SYSTEM "errors.sgml">
<!ENTITY clientapp SYSTEM "clientapp.sgml">
<!ENTITY features SYSTEM "features.sgml">
<!ENTITY config SYSTEM "config.sgml">
]>
<book id="Samba-FAQ">
<title>Samba FAQ</title>
<bookinfo>
<author><surname>Samba Team</surname></author>
<pubdate>October 2002</pubdate>
</bookinfo>
<dedication>
<para>
This is the Frequently Asked Questions (FAQ) document for
Samba, the free and very popular SMB server product. An SMB server
allows file and printer connections from clients such as Windows,
OS/2, Linux and others. Current to version 3.0. Please send any
corrections to the samba documentation mailinglist at
<ulink url="mailto:samba-doc@samba.org">samba-doc@samba.org</ulink>.
This FAQ was based on the old Samba FAQ by Dan Shearer and Paul Blackman,
and the old samba text documents which were mostly written by John Terpstra.
</para>
</dedication>
&general;
&install;
&config;
&clientapp;
&errors;
&features;
</book>

167
docs/docbook/projdoc/ADS-HOWTO.sgml
View File

@ -1,167 +0,0 @@
<chapter id="ADS">
<chapterinfo>
&author.tridge;
&author.jelmer;
<pubdate>2002/2003</pubdate>
</chapterinfo>
<title>Samba as a ADS domain member</title>
<para>
This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
Windows2000 KDC.
</para>
<sect1>
<title>Setup your <filename>smb.conf</filename></title>
<para>You must use at least the following 3 options in smb.conf:</para>
<para><programlisting>
realm = YOUR.KERBEROS.REALM
security = ADS
encrypt passwords = yes
</programlisting></para>
<para>
In case samba can't figure out your ads server using your realm name, use the
<command>ads server</command> option in <filename>smb.conf</filename>:
<programlisting>
ads server = your.kerberos.server
</programlisting>
</para>
<note><para>You do *not* need a smbpasswd file, and older clients will
be authenticated as if <command>security = domain</command>,
although it won't do any harm
and allows you to have local users not in the domain.
I expect that the above required options will change soon when we get better
active directory integration.</para></note>
</sect1>
<sect1>
<title>Setup your <filename>/etc/krb5.conf</filename></title>
<para>Note: you will need the krb5 workstation, devel, and libs installed</para>
<para>The minimal configuration for <filename>krb5.conf</filename> is:</para>
<para><programlisting>
[realms]
YOUR.KERBEROS.REALM = {
kdc = your.kerberos.server
}
</programlisting></para>
<para>Test your config by doing a <userinput>kinit
<replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput> and
making sure that your password is accepted by the Win2000 KDC.
</para>
<note><para>The realm must be uppercase or you will get "Cannot find KDC for requested
realm while getting initial credentials" error </para></note>
<note><para>Time between the two servers must be synchronized. You will get a
"kinit(v5): Clock skew too great while getting initial credentials" if the time
difference is more than five minutes. </para></note>
<para>
You also must ensure that you can do a reverse DNS lookup on the IP
address of your KDC. Also, the name that this reverse lookup maps to
must either be the netbios name of the KDC (ie. the hostname with no
domain attached) or it can alternatively be the netbios name
followed by the realm.
</para>
<para>
The easiest way to ensure you get this right is to add a
<filename>/etc/hosts</filename> entry mapping the IP address of your KDC to
its netbios name. If you don't get this right then you will get a
"local error" when you try to join the realm.
</para>
<para>
If all you want is kerberos support in &smbclient; then you can skip
straight to <link linkend="ads-test-smbclient">Test with &smbclient;</link> now.
<link linkend="ads-create-machine-account">Creating a computer account</link>
and <link linkend="ads-test-server">testing your servers</link>
is only needed if you want kerberos support for &smbd; and &winbindd;.
</para>
</sect1>
<sect1 id="ads-create-machine-account">
<title>Create the computer account</title>
<para>
As a user that has write permission on the Samba private directory
(usually root) run:
<programlisting>
<userinput>net join -U Administrator%password</userinput>
</programlisting>
</para>
<sect2>
<title>Possible errors</title>
<para>
<variablelist>
<varlistentry><term>"ADS support not compiled in"</term>
<listitem><para>Samba must be reconfigured (remove config.cache) and recompiled
(make clean all install) after the kerberos libs and headers are installed.
</para></listitem></varlistentry>
<varlistentry><term>net join prompts for user name</term>
<listitem><para>You need to login to the domain using <userinput>kinit
<replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput>.
<replaceable>USERNAME</replaceable> must be a user who has rights to add a machine
to the domain. </para></listitem></varlistentry>
</variablelist>
</para>
</sect2>
</sect1>
<sect1 id="ads-test-server">
<title>Test your server setup</title>
<para>
If the join was successful, you will see a new computer account with the
NetBIOS name of your Samba server in Active Directory (in the "Computers"
folder under Users and Computers.
</para>
<para>
On a Windows 2000 client try <userinput>net use * \\server\share</userinput>. You should
be logged in with kerberos without needing to know a password. If
this fails then run <userinput>klist tickets</userinput>. Did you get a ticket for the
server? Does it have an encoding type of DES-CBC-MD5 ?
</para>
</sect1>
<sect1 id="ads-test-smbclient">
<title>Testing with &smbclient;</title>
<para>
On your Samba server try to login to a Win2000 server or your Samba
server using &smbclient; and kerberos. Use &smbclient; as usual, but
specify the <parameter>-k</parameter> option to choose kerberos authentication.
</para>
</sect1>
<sect1>
<title>Notes</title>
<para>You must change administrator password at least once after DC
install, to create the right encoding types</para>
<para>w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
their defaults DNS setup. Maybe fixed in service packs?</para>
</sect1>
</chapter>

291
docs/docbook/projdoc/AdvancedNetworkAdmin.sgml
View File

@ -1,291 +0,0 @@
<chapter id="AdvancedNetworkManagement">
<chapterinfo>
&author.jht;
<pubdate>April 3 2003</pubdate>
</chapterinfo>
<title>Advanced Network Manangement</title>
<para>
This section attempts to document peripheral issues that are of great importance to network
administrators who want to improve network resource access control, to automate the user
environment, and to make their lives a little easier.
</para>
<sect1>
<title>Configuring Samba Share Access Controls</title>
<para>
This section deals with how to configure Samba per share access control restrictions.
By default samba sets no restrictions on the share itself. Restrictions on the share itself
can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
connect to a share. In the absence of specific restrictions the default setting is to allow
the global user <emphasis>Everyone</emphasis> Full Control (ie: Full control, Change and Read).
</para>
<para>
At this time Samba does NOT provide a tool for configuring access control setting on the Share
itself. Samba does have the capacity to store and act on access control settings, but the only
way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
Computer Management.
</para>
<para>
Samba stores the per share access control settings in a file called <filename>share_info.tdb</filename>.
The location of this file on your system will depend on how samba was compiled. The default location
for samba's tdb files is under <filename>/usr/local/samba/var</filename>. If the <filename>tdbdump</filename>
utility has been compiled and installed on your system then you can examine the contents of this file
by: <userinput>tdbdump share_info.tdb</userinput>.
</para>
<sect2>
<title>Share Permissions Management</title>
<para>
The best tool for the task is platform dependant. Choose the best tool for your environmemt.
</para>
<sect3>
<title>Windows NT4 Workstation/Server</title>
<para>
The tool you need to use to manage share permissions on a Samba server is the NT Server Manager.
Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation.
You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.
</para>
<procedure>
<title>Instructions</title>
<step><para>
Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
select Computer, then click on the Shared Directories entry.
</para></step>
<step><para>
Now click on the share that you wish to manage, then click on the Properties tab, next click on
the Permissions tab. Now you can Add or change access control settings as you wish.
</para></step>
</procedure>
</sect3>
<sect3>
<title>Windows 200x/XP</title>
<para>
On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
<emphasis>Everyone</emphasis> Full Control on the Share.
</para>
<para>
MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
Microsoft Management Console (MMC). This tool is located by clicking on <filename>Control Panel ->
Administrative Tools -> Computer Management</filename>.
</para>
<procedure>
<title>Instructions</title>
<step><para>
After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
to enter a domain login user identifier and a password. This will authenticate you to the domain.
If you where already logged in with administrative privilidge this step is not offered.
</para></step>
<step><para>
If the Samba server is not shown in the Select Computer box, then type in the name of the target
Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
next to 'Shared Folders' in the left panel.
</para></step>
<step><para>
Now in the right panel, double-click on the share you wish to set access control permissions on.
Then click on the tab 'Share Permissions'. It is now possible to add access control entities
to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
wish to assign for each entry.
</para></step>
</procedure>
<warning>
<para>
Be careful. If you take away all permissions from the Everyone user without removing this user
then effectively no user will be able to access the share. This is a result of what is known as
ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
will have no access even if this user is given explicit full control access.
</para>
</warning>
</sect3>
</sect2>
</sect1>
<sect1>
<title>Remote Server Administration</title>
<para>
<emphasis>How do I get 'User Manager' and 'Server Manager'?</emphasis>
</para>
<para>
Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
the 'Server Manager'?
</para>
<para>
Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
systems. The tools set includes:
</para>
<itemizedlist>
<listitem><para>Server Manager</para></listitem>
<listitem><para>User Manager for Domains</para></listitem>
<listitem><para>Event Viewer</para></listitem>
</itemizedlist>
<para>
Click here to download the archived file <ulink
url="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</ulink>
</para>
<para>
The Windows NT 4.0 version of the 'User Manager for
Domains' and 'Server Manager' are available from Microsoft via ftp
from <ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</ulink>
</para>
</sect1>
<sect1>
<title>Network Logon Script Magic</title>
<para>
This section needs work. Volunteer contributions most welcome. Please send your patches or updates
to <ulink url="mailto:jht@samba.org">John Terpstra</ulink>.
</para>
<para>
There are several opportunities for creating a custom network startup configuration environment.
</para>
<simplelist>
<member>No Logon Script</member>
<member>Simple universal Logon Script that applies to all users</member>
<member>Use of a conditional Logon Script that applies per user or per group attirbutes</member>
<member>Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create
a custom Logon Script and then execute it.</member>
<member>User of a tool such as KixStart</member>
</simplelist>
<para>
The Samba source code tree includes two logon script generation/execution tools. See <filename>examples</filename> directory <filename>genlogon</filename> and <filename>ntlogon</filename> subdirectories.
</para>
<para>
The following listings are from the genlogon directory.
</para>
<para>
This is the genlogon.pl file:
<programlisting>
#!/usr/bin/perl
#
# genlogon.pl
#
# Perl script to generate user logon scripts on the fly, when users
# connect from a Windows client. This script should be called from smb.conf
# with the %U, %G and %L parameters. I.e:
#
# root preexec = genlogon.pl %U %G %L
#
# The script generated will perform
# the following:
#
# 1. Log the user connection to /var/log/samba/netlogon.log
# 2. Set the PC's time to the Linux server time (which is maintained
# daily to the National Institute of Standard's Atomic clock on the
# internet.
# 3. Connect the user's home drive to H: (H for Home).
# 4. Connect common drives that everyone uses.
# 5. Connect group-specific drives for certain user groups.
# 6. Connect user-specific drives for certain users.
# 7. Connect network printers.
# Log client connection
#($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
open LOG, ">>/var/log/samba/netlogon.log";
print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
close LOG;
# Start generating logon script
open LOGON, ">/shared/netlogon/$ARGV[0].bat";
print LOGON "\@ECHO OFF\r\n";
# Connect shares just use by Software Development group
if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
{
print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
}
# Connect shares just use by Technical Support staff
if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
{
print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
}
# Connect shares just used by Administration staff
If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
{
print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
}
# Now connect Printers. We handle just two or three users a little
# differently, because they are the exceptions that have desktop
# printers on LPT1: - all other user's go to the LaserJet on the
# server.
if ($ARGV[0] eq 'jim'
|| $ARGV[0] eq 'yvonne')
{
print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
}
else
{
print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
}
# All done! Close the output file.
close LOGON;
</programlisting>
</para>
<para>
Those wishing to use more elaborate or capable logon processing system should check out the following sites:
</para>
<simplelist>
<member>http://www.craigelachie.org/rhacer/ntlogon</member>
<member>http://www.kixtart.org</member>
<member>http://support.microsoft.com/default.asp?scid=kb;en-us;189105</member>
</simplelist>
<sect2>
<title>Adding printers without user intervention</title>
<para>
Printers may be added automatically during logon script processing through the use of:
<programlisting>
rundll32 printui.dll,PrintUIEntry /?
</programlisting>
See the documentation in the Microsoft knowledgebase article no: 189105 referred to above.
</para>
</sect2>
</sect1>
</chapter>

204
docs/docbook/projdoc/Bugs.sgml
View File

@ -1,204 +0,0 @@
<chapter id="bugreport">
<chapterinfo>
&author.jelmer;
<author>
<affiliation>
<orgname>Samba Team</orgname>
</affiliation>
</author>
<pubdate> 27 June 1997 </pubdate>
</chapterinfo>
<title>Reporting Bugs</title>
<sect1>
<title>Introduction</title>
<para>
The email address for bug reports for stable releases is <ulink url="mailto:samba@samba.org">samba@samba.org</ulink>.
Bug reports for alpha releases should go to <ulink url="mailto:samba-technical@samba.org">samba-technical@samba.org</ulink>.
</para>
<para>
Please take the time to read this file before you submit a bug
report. Also, please see if it has changed between releases, as we
may be changing the bug reporting mechanism at some time.
</para>
<para>
Please also do as much as you can yourself to help track down the
bug. Samba is maintained by a dedicated group of people who volunteer
their time, skills and efforts. We receive far more mail about it than
we can possibly answer, so you have a much higher chance of an answer
and a fix if you send us a "developer friendly" bug report that lets
us fix it fast.
</para>
<para>
Do not assume that if you post the bug to the comp.protocols.smb
newsgroup or the mailing list that we will read it. If you suspect that your
problem is not a bug but a configuration problem then it is better to send
it to the Samba mailing list, as there are (at last count) 5000 other users on
that list that may be able to help you.
</para>
<para>
You may also like to look though the recent mailing list archives,
which are conveniently accessible on the Samba web pages
at <ulink url="http://samba.org/samba/">http://samba.org/samba/</ulink>.
</para>
</sect1>
<sect1>
<title>General info</title>
<para>
Before submitting a bug report check your config for silly
errors. Look in your log files for obvious messages that tell you that
you've misconfigured something and run testparm to test your config
file for correct syntax.
</para>
<para>
Have you run through the <link linkend="diagnosis">diagnosis</link>?
This is very important.
</para>
<para>
If you include part of a log file with your bug report then be sure to
annotate it with exactly what you were doing on the client at the
time, and exactly what the results were.
</para>
</sect1>
<sect1>
<title>Debug levels</title>
<para>
If the bug has anything to do with Samba behaving incorrectly as a
server (like refusing to open a file) then the log files will probably
be very useful. Depending on the problem a log level of between 3 and
10 showing the problem may be appropriate. A higher level givesmore
detail, but may use too much disk space.
</para>
<para>
To set the debug level use <command>log level =</command> in your
&smb.conf;. You may also find it useful to set the log
level higher for just one machine and keep separate logs for each machine.
To do this use:
</para>
<para><programlisting>
log level = 10
log file = /usr/local/samba/lib/log.%m
include = /usr/local/samba/lib/smb.conf.%m
</programlisting></para>
<para>
then create a file
<filename>/usr/local/samba/lib/smb.conf.<replaceable>machine</replaceable></filename> where
<replaceable>machine</replaceable> is the name of the client you wish to debug. In that file
put any &smb.conf; commands you want, for example
<command>log level=</command> may be useful. This also allows you to
experiment with different security systems, protocol levels etc on just
one machine.
</para>
<para>
The &smb.conf; entry <command>log level =</command>
is synonymous with the entry <command>debuglevel =</command> that has been
used in older versions of Samba and is being retained for backwards
compatibility of &smb.conf; files.
</para>
<para>
As the <command>log level =</command> value is increased you will record
a significantly increasing level of debugging information. For most
debugging operations you may not need a setting higher than 3. Nearly
all bugs can be tracked at a setting of 10, but be prepared for a VERY
large volume of log data.
</para>
</sect1>
<sect1>
<title>Internal errors</title>
<para>
If you get a "INTERNAL ERROR" message in your log files it means that
Samba got an unexpected signal while running. It is probably a
segmentation fault and almost certainly means a bug in Samba (unless
you have faulty hardware or system software).
</para>
<para>
If the message came from smbd then it will probably be accompanied by
a message which details the last SMB message received by smbd. This
info is often very useful in tracking down the problem so please
include it in your bug report.
</para>
<para>
You should also detail how to reproduce the problem, if
possible. Please make this reasonably detailed.
</para>
<para>
You may also find that a core file appeared in a <filename>corefiles</filename>
subdirectory of the directory where you keep your samba log
files. This file is the most useful tool for tracking down the bug. To
use it you do this:
</para>
<para><command>gdb smbd core</command></para>
<para>
adding appropriate paths to smbd and core so gdb can find them. If you
don't have gdb then try <userinput>dbx</userinput>. Then within the debugger use the
command <userinput>where</userinput> to give a stack trace of where the problem
occurred. Include this in your mail.
</para>
<para>
If you know any assembly language then do a <userinput>disass</userinput> of the routine
where the problem occurred (if its in a library routine then
disassemble the routine that called it) and try to work out exactly
where the problem is by looking at the surrounding code. Even if you
don't know assembly then incuding this info in the bug report can be
useful.
</para>
</sect1>
<sect1>
<title>Attaching to a running process</title>
<para>
Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
does often). To debug with this sort of system you could try to attach
to the running process using <userinput>gdb smbd <replaceable>PID</replaceable></userinput> where you get <replaceable>PID</replaceable> from
<application>smbstatus</application>. Then use <userinput>c</userinput> to continue and try to cause the core dump
using the client. The debugger should catch the fault and tell you
where it occurred.
</para>
</sect1>
<sect1>
<title>Patches</title>
<para>
The best sort of bug report is one that includes a fix! If you send us
patches please use <userinput>diff -u</userinput> format if your version of
diff supports it, otherwise use <userinput>diff -c4</userinput>. Make sure
you do the diff against a clean version of the source and let me know
exactly what version you used.
</para>
</sect1>
</chapter>

1794
docs/docbook/projdoc/CUPS-printing.sgml
View File

File diff suppressed because it is too large Load Diff

433
docs/docbook/projdoc/Compiling.sgml
View File

@ -1,433 +0,0 @@
<chapter id="compiling">
<chapterinfo>
<author>
<affiliation>
<orgname>Samba Team</orgname>
</affiliation>
</author>
&author.jelmer;
<pubdate> (22 May 2001) </pubdate>
<pubdate> 18 March 2003 </pubdate>
</chapterinfo>
<title>How to compile SAMBA</title>
<para>
You can obtain the samba source from the <ulink url="http://samba.org/">samba website</ulink>. To obtain a development version,
you can download samba from CVS or using rsync.
</para>
<sect1>
<title>Access Samba source code via CVS</title>
<sect2>
<title>Introduction</title>
<para>
Samba is developed in an open environment. Developers use CVS
(Concurrent Versioning System) to "checkin" (also known as
"commit") new source code. Samba's various CVS branches can
be accessed via anonymous CVS using the instructions
detailed in this chapter.
</para>
<para>
This chapter is a modified version of the instructions found at
<ulink url="http://samba.org/samba/cvs.html">http://samba.org/samba/cvs.html</ulink>
</para>
</sect2>
<sect2>
<title>CVS Access to samba.org</title>
<para>
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.
</para>
<sect3>
<title>Access via CVSweb</title>
<para>
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.
</para>
<para>
Use the URL : <ulink
url="http://samba.org/cgi-bin/cvsweb">http://samba.org/cgi-bin/cvsweb</ulink>
</para>
</sect3>
<sect3>
<title>Access via cvs</title>
<para>
You can also access the source code via a
normal cvs client. This gives you much more control over what you can
do with the repository and allows you to checkout whole source trees
and keep them up to date via normal cvs commands. This is the
preferred method of access if you are a developer and not
just a casual browser.
</para>
<para>
To download the latest cvs source code, point your
browser at the URL : <ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>.
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.
</para>
<para>
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
</para>
<orderedlist>
<listitem>
<para>
Install a recent copy of cvs. All you really need is a
copy of the cvs client binary.
</para>
</listitem>
<listitem>
<para>
Run the command
</para>
<para>
<userinput>cvs -d :pserver:cvs@samba.org:/cvsroot login</userinput>
</para>
<para>
When it asks you for a password type <userinput>cvs</userinput>.
</para>
</listitem>
<listitem>
<para>
Run the command
</para>
<para>
<userinput>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</userinput>
</para>
<para>
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.
</para>
<para>
CVS branches other then HEAD can be obtained by using the <parameter>-r</parameter>
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 userinput.
</para>
<para>
<userinput>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</userinput>
</para>
</listitem>
<listitem>
<para>
Whenever you want to merge in the latest code changes use
the following command from within the samba directory:
</para>
<para>
<userinput>cvs update -d -P</userinput>
</para>
</listitem>
</orderedlist>
</sect3>
</sect2>
</sect1>
<sect1>
<title>Accessing the samba sources via rsync and ftp</title>
<para>
pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <ulink url="ftp://pserver.samba.org/pub/unpacked">ftp://pserver.samba.org/pub/unpacked</ulink> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp.
See <ulink url="http://rsync.samba.org/">the rsync homepage</ulink> for more info on rsync.
</para>
<para>
The disadvantage of the unpacked trees
is that they do not support automatic
merging of local changes like CVS does.
rsync access is most convenient for an
initial install.
</para>
</sect1>
<sect1>
<title>Verifying Samba's PGP signature</title>
<para>
In these days of insecurity, it's strongly recommended that you verify the PGP signature for any
source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of
all Samba downloads have had a corresponding PGP signature download (a very low percentage, which
should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP
signatures should be a standard reflex.
</para>
<para>
With that said, go ahead and download the following files:
</para>
<para><programlisting>
$ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
$ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
</programlisting></para>
<para>
The first file is the PGP signature for the Samba source file; the other is the Samba public
PGP key itself. Import the public PGP key with:
</para>
<programlisting>
$ gpg --import samba-pubkey.asc
</programlisting>
<para>
And verify the Samba source code integrity with:
</para>
<programlisting>
$ gzip -d samba-2.2.8a.tar.gz
$ gpg --verify samba-2.2.8a.tar.asc
</programlisting>
<para>
If you receive a message like, "Good signature from Samba Distribution Verification Key..."
then all is well. The warnings about trust relationships can be ignored. An example of what
you would not want to see would be:
</para>
<programlisting>
gpg: BAD signature from "Samba Distribution Verification Key"
</programlisting>
</sect1>
<sect1>
<title>Building the Binaries</title>
<para>To do this, first run the program <userinput>./configure
</userinput> in the source directory. This should automatically
configure Samba for your operating system. If you have unusual
needs then you may wish to run</para>
<para><prompt>root# </prompt><userinput>./configure --help
</userinput></para>
<para>first to see what special options you can enable.
Then executing</para>
<para><prompt>root# </prompt><userinput>make</userinput></para>
<para>will create the binaries. Once it's successfully
compiled you can use </para>
<para><prompt>root# </prompt><userinput>make install</userinput></para>
<para>to install the binaries and manual pages. You can
separately install the binaries and/or man pages using</para>
<para><prompt>root# </prompt><userinput>make installbin
</userinput></para>
<para>and</para>
<para><prompt>root# </prompt><userinput>make installman
</userinput></para>
<para>Note that if you are upgrading for a previous version
of Samba you might like to know that the old versions of
the binaries will be renamed with a ".old" extension. You
can go back to the previous version with</para>
<para><prompt>root# </prompt><userinput>make revert
</userinput></para>
<para>if you find this version a disaster!</para>
<sect2>
<title>Compiling samba with Active Directory support</title>
<para>In order to compile samba with ADS support, you need to have installed
on your system:
<simplelist>
<member>the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.</member>
<member>the OpenLDAP development libraries.</member>
</simplelist></para>
<para>If your kerberos libraries are in a non-standard location then
remember to add the configure option --with-krb5=DIR.</para>
<para>After you run configure make sure that <filename>include/config.h</filename> it generates contains lines like this:</para>
<para><programlisting>
#define HAVE_KRB5 1
#define HAVE_LDAP 1
</programlisting></para>
<para>If it doesn't then configure did not find your krb5 libraries or
your ldap libraries. Look in config.log to figure out why and fix
it.</para>
<sect3>
<title>Installing the required packages for Debian</title>
<para>On Debian you need to install the following packages:</para>
<para>
<simplelist>
<member>libkrb5-dev</member>
<member>krb5-user</member>
</simplelist>
</para>
</sect3>
<sect3>
<title>Installing the required packages for RedHat</title>
<para>On RedHat this means you should have at least: </para>
<para>
<simplelist>
<member>krb5-workstation (for kinit)</member>
<member>krb5-libs (for linking with)</member>
<member>krb5-devel (because you are compiling from source)</member>
</simplelist>
</para>
<para>in addition to the standard development environment.</para>
<para>Note that these are not standard on a RedHat install, and you may need
to get them off CD2.</para>
</sect3>
</sect2>
</sect1>
<sect1>
<title>Starting the smbd and nmbd</title>
<para>You must choose to start smbd and nmbd either
as daemons or from <application>inetd</application>Don't try
to do both! Either you can put them in <filename>
inetd.conf</filename> and have them started on demand
by <application>inetd</application>, or you can start them as
daemons either from the command line or in <filename>
/etc/rc.local</filename>. See the man pages for details
on the command line options. Take particular care to read
the bit about what user you need to be in order to start
Samba. In many cases you must be root.</para>
<para>The main advantage of starting <application>smbd</application>
and <application>nmbd</application> using the recommended daemon method
is that they will respond slightly more quickly to an initial connection
request.</para>
<sect2>
<title>Starting from inetd.conf</title>
<para>NOTE; The following will be different if
you use NIS, NIS+ or LDAP to distribute services maps.</para>
<para>Look at your <filename>/etc/services</filename>.
What is defined at port 139/tcp. If nothing is defined
then add a line like this:</para>
<para><userinput>netbios-ssn 139/tcp</userinput></para>
<para>similarly for 137/udp you should have an entry like:</para>
<para><userinput>netbios-ns 137/udp</userinput></para>
<para>Next edit your <filename>/etc/inetd.conf</filename>
and add two lines something like this:</para>
<para><programlisting>
netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd
</programlisting></para>
<para>The exact syntax of <filename>/etc/inetd.conf</filename>
varies between unixes. Look at the other entries in inetd.conf
for a guide.</para>
<note><para>Some unixes already have entries like netbios_ns
(note the underscore) in <filename>/etc/services</filename>.
You must either edit <filename>/etc/services</filename> or
<filename>/etc/inetd.conf</filename> to make them consistent.</para></note>
<note><para>On many systems you may need to use the
<command>interfaces</command> option in &smb.conf; to specify the IP address
and netmask of your interfaces. Run <application>ifconfig</application>
as root if you don't know what the broadcast is for your
net. &nmbd; tries to determine it at run
time, but fails on some unixes.
</para></note>
<warning><para>Many unixes only accept around 5
parameters on the command line in <filename>inetd.conf</filename>.
This means you shouldn't use spaces between the options and
arguments, or you should use a script, and start the script
from <command>inetd</command>.</para></warning>
<para>Restart <command>inetd</command>, perhaps just send
it a HUP. If you have installed an earlier version of <application>
nmbd</application> then you may need to kill nmbd as well.</para>
</sect2>
<sect2>
<title>Alternative: starting it as a daemon</title>
<para>To start the server as a daemon you should create
a script something like this one, perhaps calling
it <filename>startsmb</filename>.</para>
<para><programlisting>
#!/bin/sh
/usr/local/samba/bin/smbd -D
/usr/local/samba/bin/nmbd -D
</programlisting></para>
<para>then make it executable with <command>chmod
+x startsmb</command></para>
<para>You can then run <command>startsmb</command> by
hand or execute it from <filename>/etc/rc.local</filename>
</para>
<para>To kill it send a kill signal to the processes
<command>nmbd</command> and <command>smbd</command>.</para>
<note><para>If you use the SVR4 style init system then
you may like to look at the <filename>examples/svr4-startup</filename>
script to make Samba fit into that system.</para></note>
</sect2>
</sect1>
</chapter>

161
docs/docbook/projdoc/DOMAIN_MEMBER.sgml
View File

@ -1,161 +0,0 @@
<chapter id="domain-member">
<chapterinfo>
&author.jeremy;
&author.jerry;
<pubdate>16 Apr 2001</pubdate>
</chapterinfo>
<title>Samba as a NT4 or Win2k domain member</title>
<sect1>
<title>Joining an NT Domain with Samba 3.0</title>
<para><emphasis>Assumptions:</emphasis>
<programlisting>
NetBIOS name: SERV1
Win2K/NT domain name: DOM
Domain's PDC NetBIOS name: DOMPDC
Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2
</programlisting>
</para>
<para>First, you must edit your &smb.conf; file to tell Samba it should
now use domain security.</para>
<para>Change (or add) your <ulink url="smb.conf.5.html#SECURITY">
<parameter>security =</parameter></ulink> line in the [global] section
of your &smb.conf; to read:</para>
<para><command>security = domain</command></para>
<para>Next change the <ulink url="smb.conf.5.html#WORKGROUP"><parameter>
workgroup =</parameter></ulink> line in the [global] section to read: </para>
<para><command>workgroup = DOM</command></para>
<para>as this is the name of the domain we are joining. </para>
<para>You must also have the parameter <ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">
<parameter>encrypt passwords</parameter></ulink> set to <constant>yes
</constant> in order for your users to authenticate to the NT PDC.</para>
<para>Finally, add (or modify) a <ulink url="smb.conf.5.html#PASSWORDSERVER">
<parameter>password server =</parameter></ulink> line in the [global]
section to read: </para>
<para><command>password server = DOMPDC DOMBDC1 DOMBDC2</command></para>
<para>These are the primary and backup domain controllers Samba
will attempt to contact in order to authenticate users. Samba will
try to contact each of these servers in order, so you may want to
rearrange this list in order to spread out the authentication load
among domain controllers.</para>
<para>Alternatively, if you want smbd to automatically determine
the list of Domain controllers to use for authentication, you may
set this line to be :</para>
<para><command>password server = *</command></para>
<para>This method, allows Samba to use exactly the same
mechanism that NT does. This
method either broadcasts or uses a WINS database in order to
find domain controllers to authenticate against.</para>
<para>In order to actually join the domain, you must run this
command:</para>
<para><prompt>root# </prompt><userinput>net join -S DOMPDC
-U<replaceable>Administrator%password</replaceable></userinput></para>
<para>
If the <userinput>-S DOMPDC</userinput> argument is not given then
the domain name will be obtained from smb.conf.
</para>
<para>as we are joining the domain DOM and the PDC for that domain
(the only machine that has write access to the domain SAM database)
is DOMPDC. The <replaceable>Administrator%password</replaceable> is
the login name and password for an account which has the necessary
privilege to add machines to the domain. If this is successful
you will see the message:</para>
<para><computeroutput>Joined domain DOM.</computeroutput>
or <computeroutput>Joined 'SERV1' to realm 'MYREALM'</computeroutput>
</para>
<para>in your terminal window. See the <ulink url="net.8.html">
net(8)</ulink> man page for more details.</para>
<para>This process joins the server to the domain
without having to create the machine trust account on the PDC
beforehand.</para>
<para>This command goes through the machine account password
change protocol, then writes the new (random) machine account
password for this Samba server into a file in the same directory
in which an smbpasswd file would be stored - normally :</para>
<para><filename>/usr/local/samba/private/secrets.tdb</filename></para>
<para>This file is created and owned by root and is not
readable by any other user. It is the key to the domain-level
security for your system, and should be treated as carefully
as a shadow password file.</para>
<para>Finally, restart your Samba daemons and get ready for
clients to begin using domain security!</para>
</sect1>
<sect1>
<title>Why is this better than security = server?</title>
<para>Currently, domain security in Samba doesn't free you from
having to create local Unix users to represent the users attaching
to your server. This means that if domain user <constant>DOM\fred
</constant> attaches to your domain security Samba server, there needs
to be a local Unix user fred to represent that user in the Unix
filesystem. This is very similar to the older Samba security mode
<ulink url="smb.conf.5.html#SECURITYEQUALSSERVER">security = server</ulink>,
where Samba would pass through the authentication request to a Windows
NT server in the same way as a Windows 95 or Windows 98 server would.
</para>
<para>Please refer to the <ulink url="winbind.html">Winbind
paper</ulink> for information on a system to automatically
assign UNIX uids and gids to Windows NT Domain users and groups.
</para>
<para>The advantage to domain-level security is that the
authentication in domain-level security is passed down the authenticated
RPC channel in exactly the same way that an NT server would do it. This
means Samba servers now participate in domain trust relationships in
exactly the same way NT servers do (i.e., you can add Samba servers into
a resource domain and have the authentication passed on from a resource
domain PDC to an account domain PDC).</para>
<para>In addition, with <command>security = server</command> every Samba
daemon on a server has to keep a connection open to the
authenticating server for as long as that daemon lasts. This can drain
the connection resources on a Microsoft NT server and cause it to run
out of available connections. With <command>security = domain</command>,
however, the Samba daemons connect to the PDC/BDC only for as long
as is necessary to authenticate the user, and then drop the connection,
thus conserving PDC connection resources.</para>
<para>And finally, acting in the same manner as an NT server
authenticating to a PDC means that as part of the authentication
reply, the Samba server gets the user identification information such
as the user SID, the list of NT groups the user belongs to, etc. </para>
<note><para> Much of the text of this document
was first published in the Web magazine <ulink url="http://www.linuxworld.com">
LinuxWorld</ulink> as the article <ulink
url="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html">Doing
the NIS/NT Samba</ulink>.</para></note>
</sect1>
</chapter>

522
docs/docbook/projdoc/Diagnosis.sgml
View File

@ -1,522 +0,0 @@
<chapter id="diagnosis">
<chapterinfo>
&author.tridge;
&author.jelmer;
<pubdate>Wed Jan 15</pubdate>
</chapterinfo>
<title>The samba checklist</title>
<sect1>
<title>Introduction</title>
<para>
This file contains a list of tests you can perform to validate your
Samba server. It also tells you what the likely cause of the problem
is if it fails any one of these steps. If it passes all these tests
then it is probably working fine.
</para>
<para>
You should do ALL the tests, in the order shown. We have tried to
carefully choose them so later tests only use capabilities verified in
the earlier tests. However, do not stop at the first error as there
have been some instances when continuing with the tests has helped
to solve a problem.
</para>
<para>
If you send one of the samba mailing lists an email saying "it doesn't work"
and you have not followed this test procedure then you should not be surprised
if your email is ignored.
</para>
</sect1>
<sect1>
<title>Assumptions</title>
<para>
In all of the tests it is assumed you have a Samba server called
BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.
</para>
<para>
The procedure is similar for other types of clients.
</para>
<para>
It is also assumed you know the name of an available share in your
&smb.conf;. I will assume this share is called <replaceable>tmp</replaceable>.
You can add a <replaceable>tmp</replaceable> share like this by adding the
following to &smb.conf;:
</para>
<para><programlisting>
[tmp]
comment = temporary files
path = /tmp
read only = yes
</programlisting>
</para>
<note><para>
These tests assume version 3.0 or later of the samba suite.
Some commands shown did not exist in earlier versions.
</para></note>
<para>
Please pay attention to the error messages you receive. If any error message
reports that your server is being unfriendly you should first check that your
IP name resolution is correctly set up. eg: Make sure your <filename>/etc/resolv.conf</filename>
file points to name servers that really do exist.
</para>
<para>
Also, if you do not have DNS server access for name resolution please check
that the settings for your &smb.conf; file results in <command>dns proxy = no</command>. The
best way to check this is with <userinput>testparm smb.conf</userinput>.
</para>
<para>
It is helpful to monitor the log files during testing by using the
<command>tail -F <replaceable>log_file_name</replaceable></command> in a separate
terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X).
Relevant log files can be found (for default installations) in
<filename>/usr/local/samba/var</filename>. Also, connection logs from
machines can be found here or possibly in <filename>/var/log/samba</filename>
depending on how or if you specified logging in your &smb.conf; file.
</para>
<para>
If you make changes to your &smb.conf; file while going through these test,
don't forget to restart &smbd; and &nmbd;.
</para>
</sect1>
<sect1>
<title>The tests</title>
<procedure>
<title>Diagnosing your samba server</title>
<step performance="required">
<para>
In the directory in which you store your &smb.conf; file, run the command
<userinput>testparm smb.conf</userinput>. If it reports any errors then your &smb.conf;
configuration file is faulty.
</para>
<note><para>
Your &smb.conf; file may be located in: <filename>/etc/samba</filename>
Or in: <filename>/usr/local/samba/lib</filename>
</para></note>
</step>
<step performance="required">
<para>
Run the command <userinput>ping BIGSERVER</userinput> from the PC and
<userinput>ping ACLIENT</userinput> from
the unix box. If you don't get a valid response then your TCP/IP
software is not correctly installed.
</para>
<para>
Note that you will need to start a "dos prompt" window on the PC to
run ping.
</para>
<para>
If you get a message saying "host not found" or similar then your DNS
software or <filename>/etc/hosts</filename> file is not correctly setup.
It is possible to
run samba without DNS entries for the server and client, but I assume
you do have correct entries for the remainder of these tests.
</para>
<para>
Another reason why ping might fail is if your host is running firewall
software. You will need to relax the rules to let in the workstation
in question, perhaps by allowing access from another subnet (on Linux
this is done via the <application>ipfwadm</application> program.)
</para>
<para>
Note: Modern Linux distributions install ipchains/iptables by default.
This is a common problem that is often overlooked.
</para>
</step>
<step performance="required">
<para>
Run the command <userinput>smbclient -L BIGSERVER</userinput> on the unix box. You
should get a list of available shares back.
</para>
<para>
If you get a error message containing the string "Bad password" then
you probably have either an incorrect <command>hosts allow</command>,
<command>hosts deny</command> or <command>valid users</command> line in your
&smb.conf;, or your guest account is not
valid. Check what your guest account is using &testparm; and
temporarily remove any <command>hosts allow</command>, <command>hosts deny</command>, <command>valid users</command> or <command>invalid users</command> lines.
</para>
<para>
If you get a "connection refused" response then the smbd server may
not be running. If you installed it in inetd.conf then you probably edited
that file incorrectly. If you installed it as a daemon then check that
it is running, and check that the netbios-ssn port is in a LISTEN
state using <userinput>netstat -a</userinput>.
</para>
<note><para>
Some Unix / Linux systems use <command>xinetd</command> in place of
<command>inetd</command>. Check your system documentation for the location
of the control file/s for your particular system implementation of
this network super daemon.
</para></note>
<para>
If you get a "session request failed" then the server refused the
connection. If it says "Your server software is being unfriendly" then
its probably because you have invalid command line parameters to &smbd;,
or a similar fatal problem with the initial startup of &smbd;. Also
check your config file (&smb.conf;) for syntax errors with &testparm;
and that the various directories where samba keeps its log and lock
files exist.
</para>
<para>
There are a number of reasons for which smbd may refuse or decline
a session request. The most common of these involve one or more of
the following &smb.conf; file entries:
</para>
<para><programlisting>
hosts deny = ALL
hosts allow = xxx.xxx.xxx.xxx/yy
bind interfaces only = Yes
</programlisting></para>
<para>
In the above, no allowance has been made for any session requests that
will automatically translate to the loopback adaptor address 127.0.0.1.
To solve this problem change these lines to:
</para>
<para><programlisting>
hosts deny = ALL
hosts allow = xxx.xxx.xxx.xxx/yy 127.
</programlisting></para>
<para>
Do NOT use the <command>bind interfaces only</command> parameter where you
may wish to
use the samba password change facility, or where &smbclient; may need to
access a local service for name resolution or for local resource
connections. (Note: the <command>bind interfaces only</command> parameter deficiency
where it will not allow connections to the loopback address will be
fixed soon).
</para>
<para>
Another common cause of these two errors is having something already running
on port 139, such as Samba (ie: smbd is running from <application>inetd</application> already) or
something like Digital's Pathworks. Check your <filename>inetd.conf</filename> file before trying
to start &smbd; as a daemon, it can avoid a lot of frustration!
</para>
<para>
And yet another possible cause for failure of this test is when the subnet mask
and / or broadcast address settings are incorrect. Please check that the
network interface IP Address / Broadcast Address / Subnet Mask settings are
correct and that Samba has correctly noted these in the <filename>log.nmb</filename> file.
</para>
</step>
<step performance="required">
<para>
Run the command <userinput>nmblookup -B BIGSERVER __SAMBA__</userinput>. You should get the
IP address of your Samba server back.
</para>
<para>
If you don't then nmbd is incorrectly installed. Check your <filename>inetd.conf</filename>
if you run it from there, or that the daemon is running and listening
to udp port 137.
</para>
<para>
One common problem is that many inetd implementations can't take many
parameters on the command line. If this is the case then create a
one-line script that contains the right parameters and run that from
inetd.
</para>
</step>
<step performance="required">
<para>run the command <userinput>nmblookup -B ACLIENT '*'</userinput></para>
<para>
You should get the PCs IP address back. If you don't then the client
software on the PC isn't installed correctly, or isn't started, or you
got the name of the PC wrong.
</para>
<para>
If ACLIENT doesn't resolve via DNS then use the IP address of the
client in the above test.
</para>
</step>
<step performance="required">
<para>
Run the command <userinput>nmblookup -d 2 '*'</userinput>
</para>
<para>
This time we are trying the same as the previous test but are trying
it via a broadcast to the default broadcast address. A number of
Netbios/TCPIP hosts on the network should respond, although Samba may
not catch all of the responses in the short time it listens. You
should see "got a positive name query response" messages from several
hosts.
</para>
<para>
If this doesn't give a similar result to the previous test then
nmblookup isn't correctly getting your broadcast address through its
automatic mechanism. In this case you should experiment with the
<command>interfaces</command> option in &smb.conf; to manually configure your IP
address, broadcast and netmask.
</para>
<para>
If your PC and server aren't on the same subnet then you will need to
use the <parameter>-B</parameter> option to set the broadcast address to that of the PCs
subnet.
</para>
<para>
This test will probably fail if your subnet mask and broadcast address are
not correct. (Refer to TEST 3 notes above).
</para>
</step>
<step performance="required">
<para>
Run the command <userinput>smbclient //BIGSERVER/TMP</userinput>. You should
then be prompted for a password. You should use the password of the account
you are logged into the unix box with. If you want to test with
another account then add the <parameter>-U <replaceable>accountname</replaceable></parameter> option to the end of
the command line. eg:
<userinput>smbclient //bigserver/tmp -Ujohndoe</userinput>
</para>
<note><para>
It is possible to specify the password along with the username
as follows:
<userinput>smbclient //bigserver/tmp -Ujohndoe%secret</userinput>
</para></note>
<para>
Once you enter the password you should get the <prompt>smb></prompt> prompt. If you
don't then look at the error message. If it says "invalid network
name" then the service "tmp" is not correctly setup in your &smb.conf;.
</para>
<para>
If it says "bad password" then the likely causes are:
</para>
<orderedlist>
<listitem>
<para>
you have shadow passords (or some other password system) but didn't
compile in support for them in &smbd;
</para>
</listitem>
<listitem>
<para>
your <command>valid users</command> configuration is incorrect
</para>
</listitem>
<listitem>
<para>
you have a mixed case password and you haven't enabled the <command>password
level</command> option at a high enough level
</para>
</listitem>
<listitem>
<para>
the <command>path =</command> line in &smb.conf; is incorrect. Check it with &testparm;
</para>
</listitem>
<listitem>
<para>
you enabled password encryption but didn't create the SMB encrypted
password file
</para>
</listitem>
</orderedlist>
<para>
Once connected you should be able to use the commands
<command>dir</command> <command>get</command> <command>put</command> etc.
Type <command>help <replaceable>command</replaceable></command> for instructions. You should
especially check that the amount of free disk space shown is correct
when you type <command>dir</command>.
</para>
</step>
<step performance="required">
<para>
On the PC, type the command <userinput>net view \\BIGSERVER</userinput>. You will
need to do this from within a "dos prompt" window. You should get back a
list of available shares on the server.
</para>
<para>
If you get a "network name not found" or similar error then netbios
name resolution is not working. This is usually caused by a problem in
nmbd. To overcome it you could do one of the following (you only need
to choose one of them):
</para>
<orderedlist>
<listitem><para>
fixup the &nmbd; installation
</para></listitem>
<listitem><para>
add the IP address of BIGSERVER to the <command>wins server</command> box in the
advanced tcp/ip setup on the PC.
</para></listitem>
<listitem><para>
enable windows name resolution via DNS in the advanced section of
the tcp/ip setup
</para></listitem>
<listitem><para>
add BIGSERVER to your lmhosts file on the PC.
</para></listitem>
</orderedlist>
<para>
If you get a "invalid network name" or "bad password error" then the
same fixes apply as they did for the <userinput>smbclient -L</userinput> test above. In
particular, make sure your <command>hosts allow</command> line is correct (see the man
pages)
</para>
<para>
Also, do not overlook that fact that when the workstation requests the
connection to the samba server it will attempt to connect using the
name with which you logged onto your Windows machine. You need to make
sure that an account exists on your Samba server with that exact same
name and password.
</para>
<para>
If you get "specified computer is not receiving requests" or similar
it probably means that the host is not contactable via tcp services.
Check to see if the host is running tcp wrappers, and if so add an entry in
the <filename>hosts.allow</filename> file for your client (or subnet, etc.)
</para>
</step>
<step performance="required">
<para>
Run the command <userinput>net use x: \\BIGSERVER\TMP</userinput>. You should
be prompted for a password then you should get a "command completed
successfully" message. If not then your PC software is incorrectly
installed or your smb.conf is incorrect. make sure your <command>hosts allow</command>
and other config lines in &smb.conf; are correct.
</para>
<para>
It's also possible that the server can't work out what user name to
connect you as. To see if this is the problem add the line <command>user =
<replaceable>username</replaceable></command> to the <command>[tmp]</command> section of
&smb.conf; where <replaceable>username</replaceable> is the
username corresponding to the password you typed. If you find this
fixes things you may need the username mapping option.
</para>
<para>
It might also be the case that your client only sends encrypted passwords
and you have <command>encrypt passwords = no</command> in &smb.conf;
Turn it back on to fix.
</para>
</step>
<step performance="required">
<para>
Run the command <userinput>nmblookup -M <replaceable>testgroup</replaceable></userinput> where
<replaceable>testgroup</replaceable> is the name of the workgroup that your Samba server and
Windows PCs belong to. You should get back the IP address of the
master browser for that workgroup.
</para>
<para>
If you don't then the election process has failed. Wait a minute to
see if it is just being slow then try again. If it still fails after
that then look at the browsing options you have set in &smb.conf;. Make
sure you have <command>preferred master = yes</command> to ensure that
an election is held at startup.
</para>
</step>
<step performance="required">
<para>
>From file manager try to browse the server. Your samba server should
appear in the browse list of your local workgroup (or the one you
specified in smb.conf). You should be able to double click on the name
of the server and get a list of shares. If you get a "invalid
password" error when you do then you are probably running WinNT and it
is refusing to browse a server that has no encrypted password
capability and is in user level security mode. In this case either set
<command>security = server</command> AND
<command>password server = Windows_NT_Machine</command> in your
&smb.conf; file, or make sure <command>encrypted passwords</command> is
set to "yes".
</para>
</step>
</procedure>
</sect1>
<sect1>
<title>Still having troubles?</title>
<para>Read the chapter on
<link linkend="problems">Analysing and Solving Problems</link>.
</para>
</sect1>
</chapter>

104
docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml
View File

@ -1,104 +0,0 @@
<?xml version="1.0" encoding="iso8859-1"?>
<chapter id="groupmapping">
<chapterinfo>
<author>
<firstname>Jean François</firstname><surname>Micouleau</surname>
</author>
&author.jerry;
</chapterinfo>
<title>Configuring Group Mapping</title>
<para>
Starting with Samba 3.0 alpha 2, new group mapping functionality
is available to create associations between Windows SIDs and UNIX
groups. The <parameter>groupmap</parameter> subcommand included with
the <command>net</command> tool can be used to manage these associations.
</para>
<para>
The first immediate reason to use the group mapping on a Samba PDC, is that
the <parameter>domain admin group</parameter> &smb.conf; has been removed.
This parameter was used to give the listed users membership in the "Domain Admins"
Windows group which gave local admin rights on their workstations (in
default configurations).
</para>
<para>
When installing NT/W2K on a computer, the installer program creates some users
and groups. Notably the 'Administrators' group, and gives to that group some
privileges like the ability to change the date and time or to kill any process
(or close too) running on the local machine. The 'Administrator' user is a
member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
group privileges. If a 'joe' user is created and become a member of the
'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.
</para>
<para>
When a NT/W2K machine is joined to a domain, the "Domain Adminis" group of the
PDC is added to the local 'Administrators' group of the workstation. Every
member of the 'Domain Administrators' group 'inherit' the
rights of the local 'Administrators' group when logging on the workstation.
</para>
<para>
The following steps describe how to make samba PDC users members of the
'Domain Admins' group?
</para>
<orderedlist>
<listitem><para>create a unix group (usually in <filename>/etc/group</filename>),
let's call it domadm</para></listitem>
<listitem><para>add to this group the users that must be Administrators. For example
if you want joe,john and mary, your entry in <filename>/etc/group</filename> will
look like:</para>
<para><programlisting>
domadm:x:502:joe,john,mary
</programlisting></para>
</listitem>
<listitem><para>Map this domadm group to the "Domain Admins" group
by running the command:</para>
<para><prompt>root# </prompt><userinput>net groupmap add ntgroup="Domain Admins" unixgroup=domadm</userinput></para>
<para>The quotes around "Domain Admins" are necessary due to the space in the group name. Also make
sure to leave no whitespace surrounding the equal character (=).</para>
</listitem>
</orderedlist>
<para>Now joe, john and mary are domain administrators!</para>
<para>
It is possible to map any arbitrary UNIX group to any Windows NT
group as well as making any UNIX group a Windows domain group.
For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a
local file or printer on a domain member machine, you would flag
that group as a domain group by running the following on the Samba PDC:
</para>
<para><prompt>root# </prompt><userinput>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</userinput></para>
<para>Be aware that the rid parmeter is a unsigned 32 bit integer that should
normally start at 1000. However, this rid must not overlap with any RID assigned
to a user. Verifying this is done differently depending on on the passdb backend
you are using. Future versions of the tools may perform the verification automatically,
but for now the burden in on you.</para>
<para>You can list the various groups in the mapping database by executing
<command>net groupmap list</command>. Here is an example:</para>
<para><programlisting><prompt>root# </prompt>net groupmap list
System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
</programlisting></para>
<para>For complete details on <command>net groupmap</command>, refer to the
net(8) man page.</para>
</chapter>

545
docs/docbook/projdoc/Integrating-with-Windows.sgml
View File

@ -1,545 +0,0 @@
<chapter id="integrate-ms-networks">
<chapterinfo>
&author.jht;
<pubdate> (Jan 01 2001) </pubdate>
</chapterinfo>
<title>Integrating MS Windows networks with Samba</title>
<para>
This section deals with NetBIOS over TCP/IP name to IP address resolution. If
your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
section does not apply to your installation. If your installation involves use of
NetBIOS over TCP/IP then this section may help you to resolve networking problems.
</para>
<note>
<para>
NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
over Logical Link Control (LLC). On modern networks it is highly advised
to NOT run NetBEUI at all. Note also that there is NO such thing as
NetBEUI over TCP/IP - the existence of such a protocol is a complete
and utter mis-apprehension.
</para>
</note>
<para>
Since the introduction of MS Windows 2000 it is possible to run MS Windows networking
without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be
used and UDP port 137 and TCP port 139 will not.
</para>
<note>
<para>
When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then
the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).
</para>
</note>
<para>
When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that
disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires
Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR).
Use of DHCP with ADS is recommended as a further means of maintaining central control
over client workstation network configuration.
</para>
<sect1>
<title>Name Resolution in a pure Unix/Linux world</title>
<para>
The key configuration files covered in this section are:
</para>
<itemizedlist>
<listitem><para><filename>/etc/hosts</filename></para></listitem>
<listitem><para><filename>/etc/resolv.conf</filename></para></listitem>
<listitem><para><filename>/etc/host.conf</filename></para></listitem>
<listitem><para><filename>/etc/nsswitch.conf</filename></para></listitem>
</itemizedlist>
<sect2>
<title><filename>/etc/hosts</filename></title>
<para>
Contains a static list of IP Addresses and names.
eg:
</para>
<para><programlisting>
127.0.0.1 localhost localhost.localdomain
192.168.1.1 bigbox.caldera.com bigbox alias4box
</programlisting></para>
<para>
The purpose of <filename>/etc/hosts</filename> is to provide a
name resolution mechanism so that uses do not need to remember
IP addresses.
</para>
<para>
Network packets that are sent over the physical network transport
layer communicate not via IP addresses but rather using the Media
Access Control address, or MAC address. IP Addresses are currently
32 bits in length and are typically presented as four (4) decimal
numbers that are separated by a dot (or period). eg: 168.192.1.1
</para>
<para>
MAC Addresses use 48 bits (or 6 bytes) and are typically represented
as two digit hexadecimal numbers separated by colons. eg:
40:8e:0a:12:34:56
</para>
<para>
Every network interfrace must have an MAC address. Associated with
a MAC address there may be one or more IP addresses. There is NO
relationship between an IP address and a MAC address, all such assignments
are arbitary or discretionary in nature. At the most basic level all
network communications takes place using MAC addressing. Since MAC
addresses must be globally unique, and generally remains fixed for
any particular interface, the assignment of an IP address makes sense
from a network management perspective. More than one IP address can
be assigned per MAC address. One address must be the primary IP address,
this is the address that will be returned in the ARP reply.
</para>
<para>
When a user or a process wants to communicate with another machine
the protocol implementation ensures that the "machine name" or "host
name" is resolved to an IP address in a manner that is controlled
by the TCP/IP configuration control files. The file
<filename>/etc/hosts</filename> is one such file.
</para>
<para>
When the IP address of the destination interface has been
determined a protocol called ARP/RARP is used to identify
the MAC address of the target interface. ARP stands for Address
Resolution Protocol, and is a broadcast oriented method that
uses UDP (User Datagram Protocol) to send a request to all
interfaces on the local network segment using the all 1's MAC
address. Network interfaces are programmed to respond to two
MAC addresses only; their own unique address and the address
ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will
contain the MAC address and the primary IP address for each
interface.
</para>
<para>
The <filename>/etc/hosts</filename> file is foundational to all
Unix/Linux TCP/IP installations and as a minumum will contain
the localhost and local network interface IP addresses and the
primary names by which they are known within the local machine.
This file helps to prime the pump so that a basic level of name
resolution can exist before any other method of name resolution
becomes available.
</para>
</sect2>
<sect2>
<title><filename>/etc/resolv.conf</filename></title>
<para>
This file tells the name resolution libraries:
</para>
<itemizedlist>
<listitem><para>The name of the domain to which the machine
belongs
</para></listitem>
<listitem><para>The name(s) of any domains that should be
automatically searched when trying to resolve unqualified
host names to their IP address
</para></listitem>
<listitem><para>The name or IP address of available Domain
Name Servers that may be asked to perform name to address
translation lookups
</para></listitem>
</itemizedlist>
</sect2>
<sect2>
<title><filename>/etc/host.conf</filename></title>
<para>
<filename>/etc/host.conf</filename> is the primary means by
which the setting in /etc/resolv.conf may be affected. It is a
critical configuration file. This file controls the order by
which name resolution may procede. The typical structure is:
</para>
<para><programlisting>
order hosts,bind
multi on
</programlisting></para>
<para>
then both addresses should be returned. Please refer to the
man page for host.conf for further details.
</para>
</sect2>
<sect2>
<title><filename>/etc/nsswitch.conf</filename></title>
<para>
This file controls the actual name resolution targets. The
file typically has resolver object specifications as follows:
</para>
<para><programlisting>
# /etc/nsswitch.conf
#
# Name Service Switch configuration file.
#
passwd: compat
# Alternative entries for password authentication are:
# passwd: compat files nis ldap winbind
shadow: compat
group: compat
hosts: files nis dns
# Alternative entries for host name resolution are:
# hosts: files dns nis nis+ hesoid db compat ldap wins
networks: nis files dns
ethers: nis files
protocols: nis files
rpc: nis files
services: nis files
</programlisting></para>
<para>
Of course, each of these mechanisms requires that the appropriate
facilities and/or services are correctly configured.
</para>
<para>
It should be noted that unless a network request/message must be
sent, TCP/IP networks are silent. All TCP/IP communications assumes a
principal of speaking only when necessary.
</para>
<para>
Starting with version 2.2.0 samba has Linux support for extensions to
the name service switch infrastructure so that linux clients will
be able to obtain resolution of MS Windows NetBIOS names to IP
Addresses. To gain this functionality Samba needs to be compiled
with appropriate arguments to the make command (ie: <command>make
nsswitch/libnss_wins.so</command>). The resulting library should
then be installed in the <filename>/lib</filename> directory and
the "wins" parameter needs to be added to the "hosts:" line in
the <filename>/etc/nsswitch.conf</filename> file. At this point it
will be possible to ping any MS Windows machine by it's NetBIOS
machine name, so long as that machine is within the workgroup to
which both the samba machine and the MS Windows machine belong.
</para>
</sect2>
</sect1>
<sect1>
<title>Name resolution as used within MS Windows networking</title>
<para>
MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
the "computer name", "machine name", "networking name", "netbios name",
"SMB name". All terms mean the same thing with the exception of
"netbios name" which can apply also to the name of the workgroup or the
domain name. The terms "workgroup" and "domain" are really just a
simply name with which the machine is associated. All NetBIOS names
are exactly 16 characters in length. The 16th character is reserved.
It is used to store a one byte value that indicates service level
information for the NetBIOS name that is registered. A NetBIOS machine
name is therefore registered for each service type that is provided by
the client/server.
</para>
<para>
The following are typical NetBIOS name/service type registrations:
</para>
<para><programlisting>
Unique NetBIOS Names:
MACHINENAME&lt;00&gt; = Server Service is running on MACHINENAME
MACHINENAME&lt;03&gt; = Generic Machine Name (NetBIOS name)
MACHINENAME&lt;20&gt; = LanMan Server service is running on MACHINENAME
WORKGROUP&lt;1b&gt; = Domain Master Browser
Group Names:
WORKGROUP&lt;03&gt; = Generic Name registered by all members of WORKGROUP
WORKGROUP&lt;1c&gt; = Domain Controllers / Netlogon Servers
WORKGROUP&lt;1d&gt; = Local Master Browsers
WORKGROUP&lt;1e&gt; = Internet Name Resolvers
</programlisting></para>
<para>
It should be noted that all NetBIOS machines register their own
names as per the above. This is in vast contrast to TCP/IP
installations where traditionally the system administrator will
determine in the /etc/hosts or in the DNS database what names
are associated with each IP address.
</para>
<para>
One further point of clarification should be noted, the <filename>/etc/hosts</filename>
file and the DNS records do not provide the NetBIOS name type information
that MS Windows clients depend on to locate the type of service that may
be needed. An example of this is what happens when an MS Windows client
wants to locate a domain logon server. It finds this service and the IP
address of a server that provides it by performing a lookup (via a
NetBIOS broadcast) for enumeration of all machines that have
registered the name type *&lt;1c&gt;. A logon request is then sent to each
IP address that is returned in the enumerated list of IP addresses. Which
ever machine first replies then ends up providing the logon services.
</para>
<para>
The name "workgroup" or "domain" really can be confusing since these
have the added significance of indicating what is the security
architecture of the MS Windows network. The term "workgroup" indicates
that the primary nature of the network environment is that of a
peer-to-peer design. In a WORKGROUP all machines are responsible for
their own security, and generally such security is limited to use of
just a password (known as SHARE MODE security). In most situations
with peer-to-peer networking the users who control their own machines
will simply opt to have no security at all. It is possible to have
USER MODE security in a WORKGROUP environment, thus requiring use
of a user name and a matching password.
</para>
<para>
MS Windows networking is thus predetermined to use machine names
for all local and remote machine message passing. The protocol used is
called Server Message Block (SMB) and this is implemented using
the NetBIOS protocol (Network Basic Input Output System). NetBIOS can
be encapsulated using LLC (Logical Link Control) protocol - in which case
the resulting protocol is called NetBEUI (Network Basic Extended User
Interface). NetBIOS can also be run over IPX (Internetworking Packet
Exchange) protocol as used by Novell NetWare, and it can be run
over TCP/IP protocols - in which case the resulting protocol is called
NBT or NetBT, the NetBIOS over TCP/IP.
</para>
<para>
MS Windows machines use a complex array of name resolution mechanisms.
Since we are primarily concerned with TCP/IP this demonstration is
limited to this area.
</para>
<sect2>
<title>The NetBIOS Name Cache</title>
<para>
All MS Windows machines employ an in memory buffer in which is
stored the NetBIOS names and IP addresses for all external
machines that that machine has communicated with over the
past 10-15 minutes. It is more efficient to obtain an IP address
for a machine from the local cache than it is to go through all the
configured name resolution mechanisms.
</para>
<para>
If a machine whose name is in the local name cache has been shut
down before the name had been expired and flushed from the cache, then
an attempt to exchange a message with that machine will be subject
to time-out delays. i.e.: Its name is in the cache, so a name resolution
lookup will succeed, but the machine can not respond. This can be
frustrating for users - but it is a characteristic of the protocol.
</para>
<para>
The MS Windows utility that allows examination of the NetBIOS
name cache is called "nbtstat". The Samba equivalent of this
is called "nmblookup".
</para>
</sect2>
<sect2>
<title>The LMHOSTS file</title>
<para>
This file is usually located in MS Windows NT 4.0 or
2000 in <filename>C:\WINNT\SYSTEM32\DRIVERS\ETC</filename> and contains
the IP Address and the machine name in matched pairs. The
<filename>LMHOSTS</filename> file performs NetBIOS name
to IP address mapping.
</para>
<para>
It typically looks like:
</para>
<para><programlisting>
# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
# over TCP/IP) stack for Windows98
#
# This file contains the mappings of IP addresses to NT computernames
# (NetBIOS) names. Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the comptername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
# #PRE
# #DOM:&lt;domain&gt;
# #INCLUDE &lt;filename&gt;
# #BEGIN_ALTERNATE
# #END_ALTERNATE
# \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:&lt;domain&gt;" tag will associate the
# entry with the domain specified by &lt;domain&gt;. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The &lt;domain&gt; is always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE &lt;filename&gt;" will force the RFC NetBIOS (NBT)
# software to seek the specified &lt;filename&gt; and parse it as if it were
# local. &lt;filename&gt; is generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
# in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
# 102.54.94.102 "appname \0x14" #special app server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the include
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.
</programlisting></para>
</sect2>
<sect2>
<title>HOSTS file</title>
<para>
This file is usually located in MS Windows NT 4.0 or 2000 in
<filename>C:\WINNT\SYSTEM32\DRIVERS\ETC</filename> and contains
the IP Address and the IP hostname in matched pairs. It can be
used by the name resolution infrastructure in MS Windows, depending
on how the TCP/IP environment is configured. This file is in
every way the equivalent of the Unix/Linux <filename>/etc/hosts</filename> file.
</para>
</sect2>
<sect2>
<title>DNS Lookup</title>
<para>
This capability is configured in the TCP/IP setup area in the network
configuration facility. If enabled an elaborate name resolution sequence
is followed the precise nature of which is dependant on what the NetBIOS
Node Type parameter is configured to. A Node Type of 0 means use
NetBIOS broadcast (over UDP broadcast) is first used if the name
that is the subject of a name lookup is not found in the NetBIOS name
cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to
Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
lookup is used.
</para>
</sect2>
<sect2>
<title>WINS Lookup</title>
<para>
A WINS (Windows Internet Name Server) service is the equivaent of the
rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
the names and IP addresses that are registered by a Windows client
if the TCP/IP setup has been given at least one WINS Server IP Address.
</para>
<para>
To configure Samba to be a WINS server the following parameter needs
to be added to the &smb.conf; file:
</para>
<para><programlisting>
wins support = Yes
</programlisting></para>
<para>
To configure Samba to use a WINS server the following parameters are
needed in the &smb.conf; file:
</para>
<para><programlisting>
wins support = No
wins server = xxx.xxx.xxx.xxx
</programlisting></para>
<para>
where <replaceable>xxx.xxx.xxx.xxx</replaceable> is the IP address
of the WINS server.
</para>
</sect2>
</sect1>
</chapter>

222
docs/docbook/projdoc/InterdomainTrusts.sgml
View File

@ -1,222 +0,0 @@
<chapter id="InterdomainTrusts">
<chapterinfo>
&author.jht;
&author.mimir;
<pubdate>April 3, 2003</pubdate>
</chapterinfo>
<title>Interdomain Trust Relationships</title>
<para>
Samba-3 supports NT4 style domain trust relationships. This is feature that many sites
will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to
adopt Active Directory or an LDAP based authentication back end. This section explains
some background information regarding trust relationships and how to create them. It is now
possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.
</para>
<sect1>
<title>Trust Relationship Background</title>
<para>
MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure.
The limitations of this architecture as it affects the scalability of MS Windows networking
in large organisations is well known. Additionally, the flat-name space that results from
this design significantly impacts the delegation of administrative responsibilities in
large and diverse organisations.
</para>
<para>
Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
of circumventing the limitations of the older technologies. Not every organisation is ready
or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
is quite adequate, there thus remains an entrenched user base for whom there is no direct
desire to go through a disruptive change to adopt ADS.
</para>
<para>
Microsoft introduced with MS Windows NT the ability to allow differing security domains
to affect a mechanism so that users from one domain may be given access rights and privileges
in another domain. The language that describes this capability is couched in terms of
<emphasis>Trusts</emphasis>. Specifically, one domain will <emphasis>trust</emphasis> the users
from another domain. The domain from which users are available to another security domain is
said to be a trusted domain. The domain in which those users have assigned rights and privileges
is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
thus if users in both domains are to have privileges and rights in each others' domain, then it is
necessary to establish two (2) relationships, one in each direction.
</para>
<para>
In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
transitive.
</para>
<para>
New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
an inherent feature of ADS domains. Samba-3 implements MS Windows NT4
style Interdomain trusts and interoperates with MS Windows 200x ADS
security domains in similar manner to MS Windows NT4 style domains.
</para>
</sect1>
<sect1>
<title>Native MS Windows NT4 Trusts Configuration</title>
<para>
There are two steps to creating an interdomain trust relationship.
</para>
<sect2>
<title>NT4 as the Trusting Domain (ie. creating the trusted account)</title>
<para>
For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager.
To affect a two way trust relationship it is necessary for each domain administrator to make
available (for use by an external domain) it's security resources. This is done from the Domain
User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then
next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and
"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that
will be able to assign user rights to your domain. In addition it is necessary to enter a password
that is specific to this trust relationship. The password needs to be
typed twice (for standard confirmation).
</para>
</sect2>
<sect2>
<title>NT4 as the Trusted Domain (ie. creating trusted account's password)</title>
<para>
A trust relationship will work only when the other (trusting) domain makes the appropriate connections
with the trusted domain. To consumate the trust relationship the administrator will launch the
Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in
which must be entered the name of the remote domain as well as the password assigned to that trust.
</para>
</sect2>
</sect1>
<sect1>
<title>Configuring Samba NT-style Domain Trusts</title>
<para>
This description is meant to be a fairly short introduction about how to set up a Samba server so
that it could participate in interdomain trust relationships. Trust relationship support in Samba
is in its early stage, so lot of things don't work yet.
</para>
<para>
Each of the procedures described below is treated as they were performed with Windows NT4 Server on
one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after
reading this document, that combining Samba-specific parts of what's written below leads to trust
between domains in purely Samba environment.
</para>
<sect2>
<title>Samba-3 as the Trusting Domain</title>
<para>
In order to set the Samba PDC to be the trusted party of the relationship first you need
to create special account for the domain that will be the trusting party. To do that,
you can use the 'smbpasswd' utility. Creating the trusted domain account is very
similiar to creating a trusted machine account. Suppose, your domain is
called SAMBA, and the remote domain is called RUMBA. The first step
will be to issue this command from your favourite shell:
</para>
<para>
<screen>
<prompt>deity#</prompt> <userinput>smbpasswd -a -i rumba</userinput>
New SMB password: XXXXXXXX
Retype SMB password: XXXXXXXX
Added user rumba$
</screen>
where <parameter>-a</parameter> means to add a new account into the
passdb database and <parameter>-i</parameter> means: ''create this
account with the InterDomain trust flag''
</para>
<para>
The account name will be 'rumba$' (the name of the remote domain)
</para>
<para>
After issuing this command you'll be asked to enter the password for
the account. You can use any password you want, but be aware that Windows NT will
not change this password until 7 days following account creation.
After the command returns successfully, you can look at the entry for the new account
(in the stardard way depending on your configuration) and see that account's name is
really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm
the trust by establishing it from Windows NT Server.
</para>
<para>
Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'.
Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for
the trusted domain name and the relationship password. Type in SAMBA, as this is
your domain name, and the password used at the time of account creation.
Press OK and, if everything went without incident, you will see 'Trusted domain relationship
successfully established' message.
</para>
</sect2>
<sect2>
<title>Samba-3 as the Trusted Domain</title>
<para>
This time activities are somewhat reversed. Again, we'll assume that your domain
controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.
</para>
<para>
The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.
</para>
<para>
Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'.
Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted
domain (SAMBA) and password securing the relationship.
</para>
<para>
The password can be arbitrarily chosen. It is easy to change the password
from the Samba server whenever you want. After confirming the password your account is
ready for use. Now it's Samba's turn.
</para>
<para>
Using your favourite shell while being logged in as root, issue this command:
</para>
<para>
<prompt>deity# </prompt><userinput>net rpc trustdom establish rumba</userinput>
</para>
<para>
You will be prompted for the password you just typed on your Windows NT4 Server box.
Do not worry if you see an error message that mentions a returned code of
<errorname>NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT</errorname>. It means the
password you gave is correct and the NT4 Server says the account is
ready for interdomain connection and not for ordinary
connection. After that, be patient it can take a while (especially
in large networks), you should see the 'Success' message. Congratulations! Your trust
relationship has just been established.
</para>
<note><para>
Note that you have to run this command as root because you must have write access to
the <filename>secrets.tdb</filename> file.
</para></note>
</sect2>
</sect1>
</chapter>

361
docs/docbook/projdoc/IntroSMB.sgml
View File

@ -1,361 +0,0 @@
<chapter id="IntroSMB">
<chapterinfo>
&author.dlechnyr;
<pubdate>April 14, 2003</pubdate>
</chapterinfo>
<title>Introduction to Samba</title>
<para><emphasis>
"If you understand what you're doing, you're not learning anything."
-- Anonymous
</emphasis></para>
<para>
Samba is a file and print server for Windows-based clients using TCP/IP as the underlying
transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big
strengths is that you can use it to blend your mix of Windows and Linux machines together
without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed
by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.
</para>
<sect1>
<title>Background</title>
<para>
Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed
Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was
originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only
ran over UDP. When there was a need to run it over TCP so that it would be compatible
with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became
known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to
license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the
concept continued in the form of SMB (Server Message Block, or the "what") using the
NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can
run SMB (i.e., transport) over several different protocols; many different implementations
arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT
(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form
of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing
term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445
only. As of yet, direct-hosted TCP has yet to catch on.
</para>
<para>
Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS:
Common Insecurities Fail Scrutiny:
</para>
<para><emphasis>
Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba
stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have
been dutifully waded through during the information-gathering stages of this project, and there
are *still* many missing pieces... While often tedious, at least the way has been generously
littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they
thinking?
</emphasis></para>
</sect1>
<sect1>
<title>Terminology</title>
<itemizedlist>
<listitem><para>
SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.
</para></listitem>
<listitem><para>
CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently
decided that SMB needed the word "Internet" in it, so they changed it to CIFS.
</para></listitem>
<listitem><para>
Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp
only using DNS for name resolution instead of WINS.
</para></listitem>
<listitem><para>
IPC: Acronym for "Inter-Process Communication". A method to communicate specific
information between programs.
</para></listitem>
<listitem><para>
Marshalling: - A method of serializing (i.e., sequential ordering of) variable data
suitable for transmission via a network connection or storing in a file. The source
data can be re-created using a similar process called unmarshalling.
</para></listitem>
<listitem><para>
NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol;
it is a method of communication across an existing protocol. This is a standard which
was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit,
it can help to think of this in comparison your computer's BIOS -- it controls the
essential functions of your input/output hardware -- whereas NetBIOS controls the
essential functions of your input/output traffic via the network. Again, this is a bit
of an exaggeration but it should help that paradigm shift. What is important to realize
is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically
brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second
thought; this will cause no end (and no doubt) of confusion.
</para></listitem>
<listitem><para>
NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI
is a protocol, not a standard. It is also not routable, so traffic on one side of a
router will be unable to communicate with the other side. Understanding NetBEUI is
not essential to deciphering SMB; however it helps to point out that it is not the
same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally
referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver".
It is not often heard from these days.
</para></listitem>
<listitem><para>
NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use
of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made
to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports.
This is how file and printer sharing are accomplished in Windows 95/98/ME. They
traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137,
NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service
(nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts,
and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002
(Detailed specifications).
</para></listitem>
<listitem><para>
W2K: Acronym for Windows 2000 Professional or Server
</para></listitem>
<listitem><para>
W3K: Acronym for Windows 2003 Server
</para></listitem>
</itemizedlist>
<para>If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at
http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com
</para>
</sect1>
<sect1>
<title>Related Projects</title>
<para>
There are currently two network filesystem client projects for Linux that are directly
related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself.
</para>
<itemizedlist>
<listitem><para>
SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol
that Microsoft Windows and OS/2 Lan Manager use to share files and printers
over local networks) and access them just like any other Unix directory. This is useful
if you just want to mount such filesystems without being a SMBFS server.
</para></listitem>
<listitem><para>
CIFS VFS (Common Internet File System Virtual File System) is the successor to SMBFS, and
is being actively developed for the upcoming version of the Linux kernel. The intent of this module
is to provide advanced network file system functionality including support for dfs (heirarchical
name space), secure per-user session establishment, safe distributed caching (oplock),
optional packet signing, Unicode and other internationalization improvements, and optional
Winbind (nsswitch) integration.
</para></listitem>
</itemizedlist>
<para>
Again, it's important to note that these are implementations for client filesystems, and have
nothing to do with acting as a file and print server for SMB/CIFS clients.
</para>
<para>
There are other Open Source CIFS client implementations, such as the jCIFS project
(jcifs.samba.org) which provides an SMB client toolkit written in Java.
</para>
</sect1>
<sect1>
<title>SMB Methodology</title>
<para>
Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns),
UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS
session service, or netbios-ssn). Anyone looking at their network with a good
packet sniffer will be amazed at the amount of traffic generated by just opening
up a single file. In general, SMB sessions are established in the following order:
</para>
<itemizedlist>
<listitem><para>
"TCP Connection" - establish 3-way handshake (connection) to port 139/tcp
or 445/tcp.
</para></listitem>
<listitem><para>
"NetBIOS Session Request" - using the following "Calling Names": The local
machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS
name plus the 16th character 0x20
</para></listitem>
<listitem><para>
"SMB Negotiate Protocol" - determine the protocol dialect to use, which will
be one of the following: PC Network Program 1.0 (Core) - share level security
mode only; Microsoft Networks 1.03 (Core Plus) - share level security
mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response
Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response
Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response
Authentication
</para></listitem>
<listitem><para>
SMB Session Startup. Passwords are encrypted (or not) according to one of
the following methods: Null (no encryption); Cleartext (no encryption); LM
and NTLM; NTLM; NTLMv2
</para></listitem>
<listitem><para>
SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect
to a service type (e.g., IPC$ named pipe)
</para></listitem>
</itemizedlist>
<para>
A good way to examine this process in depth is to try out SecurityFriday's SWB program
at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to
walk through the establishment of a SMB/CIFS session step by step.
</para>
</sect1>
<sect1>
<title>Additional Resources</title>
<itemizedlist>
<listitem><para>
<emphasis>CIFS: Common Insecurities Fail Scrutiny</emphasis> by "Hobbit",
http://hr.uoregon.edu/davidrl/cifs.txt
</para></listitem>
<listitem><para>
<emphasis>Doing the Samba on Windows</emphasis> by Financial Review,
http://afr.com/it/2002/10/01/FFXDF43AP6D.html
</para></listitem>
<listitem><para>
<emphasis>Implementing CIFS</emphasis> by Christopher R. Hertel,
http://ubiqx.org/cifs/
</para></listitem>
<listitem><para>
<emphasis>Just What Is SMB?</emphasis> by Richard Sharpe,
http://samba.anu.edu.au/cifs/docs/what-is-smb.html
</para></listitem>
<listitem><para>
<emphasis>Opening Windows Everywhere</emphasis> by Mike Warfield,
http://www.linux-mag.com/1999-05/samba_01.html
</para></listitem>
<listitem><para>
<emphasis>SMB HOWTO</emphasis> by David Wood,
http://www.tldp.org/HOWTO/SMB-HOWTO.html
</para></listitem>
<listitem><para>
<emphasis>SMB/CIFS by The Root</emphasis> by "ledin",
http://www.phrack.org/phrack/60/p60-0x0b.txt
</para></listitem>
<listitem><para>
<emphasis>The Story of Samba</emphasis> by Christopher R. Hertel,
http://www.linux-mag.com/1999-09/samba_01.html
</para></listitem>
<listitem><para>
<emphasis>The Unofficial Samba HOWTO</emphasis> by David Lechnyr,
http://hr.uoregon.edu/davidrl/samba/
</para></listitem>
<listitem><para>
<emphasis>Understanding the Network Neighborhood</emphasis> by Christopher R. Hertel,
http://www.linux-mag.com/2001-05/smb_01.html
</para></listitem>
<listitem><para>
<emphasis>Using Samba as a PDC</emphasis> by Andrew Bartlett,
http://www.linux-mag.com/2002-02/samba_01.html
</para></listitem>
</itemizedlist>
</sect1>
<sect1>
<title>Epilogue</title>
<para><emphasis>
"What's fundamentally wrong is that nobody ever had any taste when they
did it. Microsoft has been very much into making the user interface look good,
but internally it's just a complete mess. And even people who program for Microsoft
and who have had years of experience, just don't know how it works internally.
Worse, nobody dares change it. Nobody dares to fix bugs because it's such a
mess that fixing one bug might just break a hundred programs that depend on
that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested
in making money. They don't have anybody who takes pride in Windows 95 as an
operating system.
</emphasis></para>
<para><emphasis>
People inside Microsoft know it's a bad operating system and they still
continue obviously working on it because they want to get the next version out
because they want to have all these new features to sell more copies of the
system.
</emphasis></para>
<para><emphasis>
The problem with that is that over time, when you have this kind of approach,
and because nobody understands it, because nobody REALLY fixes bugs (other than
when they're really obvious), the end result is really messy. You can't trust
it because under certain circumstances it just spontaneously reboots or just
halts in the middle of something that shouldn't be strange. Normally it works
fine and then once in a blue moon for some completely unknown reason, it's dead,
and nobody knows why. Not Microsoft, not the experienced user and certainly
not the completely clueless user who probably sits there shivering thinking
"What did I do wrong?" when they didn't do anything wrong at all.
</emphasis></para>
<para><emphasis>
That's what's really irritating to me."
</emphasis></para>
<para>
-- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998
(http://hr.uoregon.edu/davidrl/boot.txt)
</para>
</sect1>
<sect1>
<title>Miscellaneous</title>
<para>
This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0,
in case anyone asks.
</para>
<para>
This chapter is Copyright &copy; 2003 David Lechnyr (david at lechnyr dot com).
Permission is granted to copy, distribute and/or modify this document under the terms
of the GNU Free Documentation License, Version 1.2 or any later version published by the Free
Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.
</para>
</sect1>
</chapter>

507
docs/docbook/projdoc/NT4Migration.sgml
View File

@ -1,507 +0,0 @@
<chapter id="NT4Migration">
<chapterinfo>
&author.jht;
<pubdate>April 3, 2003</pubdate>
</chapterinfo>
<title>Migration from NT4 PDC to Samba-3 PDC</title>
<para>
This is a rough guide to assist those wishing to migrate from NT4 domain control to
Samba-3 based domain control.
</para>
<sect1>
<title>Planning and Getting Started</title>
<para>
In the IT world there is often a saying that all problems are encountered because of
poor planning. The corrollary to this saying is that not all problems can be anticpated
and planned for. Then again, good planning will anticpate most show stopper type situations.
</para>
<para>
Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
environment would do well to develop a detailed migration plan. So here are a few pointers to
help migration get under way.
</para>
<sect2>
<title>Objectives</title>
<para>
The key objective for most organisations will be to make the migration from MS Windows NT4
to Samba-3 domain control as painless as possible. One of the challenges you may experience
in your migration process may well be one of convincing management that the new environment
should remain in place. Many who have introduced open source technologies have experienced
pressure to return to a Microsoft based platform solution at the first sign of trouble.
</para>
<para>
It is strongly advised that before attempting a migration to a Samba-3 controlled network
that every possible effort be made to gain all-round commitment to the change. Firstly, you
should know precisely <emphasis>why</emphasis> the change is important for the organisation.
Possible motivations to make a change include:
</para>
<itemizedlist>
<listitem>
<para>Improve network manageability</para>
</listitem>
<listitem>
<para>Obtain better user level functionality</para>
</listitem>
<listitem>
<para>Reduce network operating costs</para>
</listitem>
<listitem>
<para>Reduce exposure caused by Microsoft withdrawal of NT4 support</para>
</listitem>
<listitem>
<para>Avoid MS License 6 implications</para>
</listitem>
<listitem>
<para>Reduce organisation's dependency on Microsoft</para>
</listitem>
</itemizedlist>
<para>
It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
an alternative solution that is both different from MS Windows NT4 and that offers some
advantages compared with it. It should also be recognised that Samba-3 lacks many of the
features that Microsoft has promoted as core values in migration from MS Windows NT4 to
MS Windows 2000 and beyond (with or without Active Directory services).
</para>
<para>
What are the features that Samba-3 can NOT provide?
</para>
<itemizedlist>
<listitem>
<para>Active Directory Server</para>
</listitem>
<listitem>
<para>Group Policy Objects (in Active Direcrtory)</para>
</listitem>
<listitem>
<para>Machine Policy objects</para>
</listitem>
<listitem>
<para>Logon Scripts in Active Directorty</para>
</listitem>
<listitem>
<para>Software Application and Access Controls in Active Directory</para>
</listitem>
</itemizedlist>
<para>
The features that Samba-3 DOES provide and that may be of compelling interest to your site
includes:
</para>
<itemizedlist>
<listitem>
<para>Lower Cost of Ownership</para>
</listitem>
<listitem>
<para>Global availability of support with no strings attached</para>
</listitem>
<listitem>
<para>Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)</para>
</listitem>
<listitem>
<para>Creation of on-the-fly logon scripts</para>
</listitem>
<listitem>
<para>Creation of on-the-fly Policy Files</para>
</listitem>
<listitem>
<para>Greater Stability, Reliability, Performance and Availability</para>
</listitem>
<listitem>
<para>Manageability via an ssh connection</para>
</listitem>
<listitem>
<para>Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)</para>
</listitem>
<listitem>
<para>Ability to implement a full single-signon architecture</para>
</listitem>
<listitem>
<para>Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand</para>
</listitem>
</itemizedlist>
<para>
Before migrating a network from MS Windows NT4 to Samba-3 it is vital that all necessary factors are
considered. Users should be educated about changes they may experience so that the change will be a
welcome one and not become an obstacle to the work they need to do. The following are some of the
factors that will go into a successful migration:
</para>
<sect3>
<title>Domain Layout</title>
<para>
Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called
a secondary controller), a domain member, or as a stand-alone server. The Windows network security
domain context should be sized and scoped before implementation. Particular attention needs to be
paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs).
It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one
chooses to use an LDAP authentication backend then the same database can be used by several different
domains. This means that in a complex organisation there can be a single LDAP database, that itself
can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed).
</para>
<para>
It is recommended that from a design perspective, the number of users per server, as well as the number
of servers, per domain should be scaled according to needs and should also consider server capacity
and network bandwidth.
</para>
<para>
A physical network segment may house several domains, each of which may span multiple network segments.
Where domains span routed network segments it is most advisable to consider and test the performance
implications of the design and layout of a network. A Centrally located domain controller that is being
designed to serve mulitple routed network segments may result in severe performance problems if the
response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations
where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as
the local authentication and access control server.
</para>
</sect3>
<sect3>
<title>Server Share and Directory Layout</title>
<para>
There are few cardinal rules to effective network design that can be broken with impunity.
The most important rule of effective network management is that simplicity is king in every
well controlled network. Every part of the infrastructure must be managed, the more complex
it is, the greater will be the demand of keeping systems secure and functional.
</para>
<para>
The nature of the data that must be stored needs to be born in mind when deciding how many
shares must be created. The physical disk space layout should also be taken into account
when designing where share points will be created. Keep in mind that all data needs to be
backed up, thus the simpler the disk layout the easier it will be to keep track of what must
be backed up to tape or other off-line storage medium. Always plan and implement for minimum
maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance:
Backup and test, validate every backup, create a disaster recovery plan and prove that it works.
</para>
<para>
Users should be grouped according to data access control needs. File and directory access
is best controlled via group permissions and the use of the "sticky bit" on group controlled
directories may substantially avoid file access complaints from samba share users.
</para>
<para>
Many network administrators who are new to the game will attempt to use elaborate techniques
to set access controls, on files, directories, shares, as well as in share definitions.
There is the ever present danger that that administrator's successor will not understand the
complex mess that has been inherited. Remember, apparent job security through complex design
and implementation may ultimately cause loss of operations and downtime to users as the new
administrator learns to untangle your web. Keep access controls simple and effective and
make sure that users will never be interrupted by the stupidity of complexity.
</para>
</sect3>
<sect3>
<title>Logon Scripts</title>
<para>
Please refer to the section of this document on Advanced Network Adminsitration for information
regarding the network logon script options for Samba-3. Logon scripts can help to ensure that
all users gain share and printer connections they need.
</para>
<para>
Logon scripts can be created on-the-fly so that all commands executed are specific to the
rights and privilidges granted to the user. The preferred controls should be affected through
group membership so that group information can be used to custom create a logong script using
the <filename>root preexec</filename> parameters to the <filename>NETLOGON</filename> share.
</para>
<para>
Some sites prefer to use a tool such as <filename>kixstart</filename> to establish a controlled
user environment. In any case you may wish to do a google search for logon script process controls.
In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that
deals with how to add printers without user intervention via the logon script process.
</para>
</sect3>
<sect3>
<title>Profile Migration/Creation</title>
<para>
User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile
Management.
</para>
<para>
Profiles may also be managed using the Samba-3 tool <filename>profiles</filename>. This tool allows
the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file
to be changed to the SID of the Samba-3 domain.
</para>
</sect3>
<sect3>
<title>User and Group Accounts</title>
<para>
It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
groups that are present on the MS Windows NT4 domain <emphasis>AND</emphasis> to connect these to
suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes
should migrate painlessly.
</para>
</sect3>
</sect2>
<sect2>
<title>Steps In Migration Process</title>
<para>
The approximate migration process is described below.
</para>
<itemizedlist>
<listitem><para>
You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
</para></listitem>
<listitem><para>
Samba-3 set up as a DC with netlogon share, profile share, etc.
</para></listitem>
</itemizedlist>
<procedure><title>The Account Migration Process</title>
<step><para>Create a BDC account for the samba server using NT Server Manager</para>
<substeps><step><para>Samba must NOT be running</para></step></substeps></step>
<step>
<para>rpcclient NT4PDC -U Administrator%passwd</para>
<substeps><step><para>lsaquery</para></step>
<step><para>Note the SID returned</para></step>
</substeps>
</step>
<step><para>net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd</para>
<substeps><step><para>Note the SID</para></step></substeps>
</step>
<step><para>net getlocalsid</para>
<substeps>
<step><para>Note the SID, now check that all three SIDS reported are the same!</para></step>
</substeps>
</step>
<step><para>net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd</para></step>
<step><para>net rpc vampire -S NT4PDC -U administrator%passwd</para></step>
<step><para>pdbedit -l</para>
<substeps><step><para>Note - did the users migrate?</para></step></substeps>
</step>
<step><para>initGrps.sh DOMNAME</para></step>
<step><para>net groupmap list</para>
<substeps><step><para>Now check that all groups are recognised</para></step></substeps>
</step>
<step><para>net rpc campire -S NT4PDC -U administrator%passwd</para></step>
<step><para>pdbedit -lv</para>
<substeps><step>
<para>Note - check that all group membership has been migrated</para>
</step></substeps>
</step>
</procedure>
<para>
Now it is time to migrate all the profiles, then migrate all policy files.
More later.
</para>
</sect2>
</sect1>
<sect1>
<title>Migration Options</title>
<para>
Based on feedback from many sites as well as from actual installation and maintenance
experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba
based solution fit into three basic categories.
</para>
<table frame="all"><title>The 3 Major Site Types</title>
<tgroup cols="2" align="center">
<thead>
<row><entry align="center">Number of Users</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry align="center">&lt 50</entry><entry><para>Want simple conversion with NO pain</para></entry></row>
<row><entry align="center">50 - 250</entry><entry><para>Want new features, can manage some in-house complexity</para></entry></row>
<row><entry align="center">&gt 250</entry><entry><para>Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas</para></entry></row>
</tbody>
</tgroup>
</table>
<sect2>
<title>Planning for Success</title>
<para>
There are three basic choices for sites that intend to migrate from MS Windwows NT4
to Samba-3.
</para>
<itemizedlist>
<listitem><para>
Simple Conversion (total replacement)
</para></listitem>
<listitem><para>
Upgraded Conversion (could be one of integration)
</para></listitem>
<listitem><para>
Complete Redesign (completely new solution)
</para></listitem>
</itemizedlist>
<para>
No matter what choice you make, the following rules will minimise down-stream problems:
</para>
<itemizedlist>
<listitem><para>
Take sufficient time
</para></listitem>
<listitem><para>
Avoid Panic
</para></listitem>
<listitem><para>
Test ALL assumptions
</para></listitem>
<listitem><para>
Test full roll-out program, including workstation deployment
</para></listitem>
</itemizedlist>
<table frame="top"><title>Nature of the Conversion Choices</title>
<tgroup cols="3" align="center">
<thead>
<row><entry>Simple</entry><entry>Upgraded</entry><entry>Redesign</entry></row>
</thead>
<tbody>
<row>
<entry><para>Make use of minimal OS specific features</para></entry>
<entry><para>Translate NT4 features to new host OS features</para></entry>
<entry><para>Decide:</para></entry>
</row>
<row>
<entry><para>Suck all accounts from NT4 into Samba-3</para></entry>
<entry><para>Copy and improve:</para></entry>
<entry><para>Authentication Regime (database location and access)</para></entry>
</row>
<row>
<entry><para>Make least number of operational changes</para></entry>
<entry><para>Make progressive improvements</para></entry>
<entry><para>Desktop Management Methods</para></entry>
</row>
<row>
<entry><para>Take least amount of time to migrate</para></entry>
<entry><para>Minimise user impact</para></entry>
<entry><para>Better Control of Desktops / Users</para></entry>
</row>
<row>
<entry><para>Live versus Isolated Conversion</para></entry>
<entry><para>Maximise functionality</para></entry>
<entry><para>Identify Needs for: Manageability, Scalability, Security, Availability</para></entry>
</row>
<row>
<entry><para>Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)</para></entry>
<entry><para>Take advantage of lower maintenance opportunity</para></entry>
<entry><para></para></entry>
</row>
</tbody>
</tgroup>
</table>
</sect2>
<sect2>
<title>Samba Implementation Choices</title>
<para><programlisting>
Authentication database back end
Winbind (external Samba or NT4/200x server)
Can use pam_mkhomedir.so to auto-create home dirs
External server could use Active Directory or NT4 Domain
Database type
smbpasswd, tdbsam, ldapsam, MySQLsam
Access Control Points
On the Share itself (Use NT4 Server Manager)
On the file system
Unix permissions on files and directories
Posix ACLs enablement in file system?
Through Samba share parameters
Not recommended - except as only resort
Policies (migrate or create new ones)
Group Policy Editor (NT4)
Watch out for Tattoo effect
User and Group Profiles
Platform specific so use platform tool to change from a Local
to a Roaming profile Can use new profiles tool to change SIDs
(NTUser.DAT)
Logon Scripts (Know how they work)
User and Group mapping to Unix/Linux
username map facility may be needed
Use 'net groupmap' to connect NT4 groups to Unix groups
Use pdbedit to set/change user configuration
NOTE:
If migrating to LDAP back end it may be easier to dump initial LDAP database
to LDIF, then edit, then reload into LDAP
OS specific scripts / programs may be needed
Add / delete Users
Note OS limits on size of name (Linux 8 chars)
NT4 up to 254 chars
Add / delete machines
Applied only to domain members (note up to 16 chars)
Add / delete Groups
Note OS limits on size and nature
Linux limit is 16 char,
no spaces and no upper case chars (groupadd)
Migration Tools
Domain Control (NT4 Style)
Profiles, Policies, Access Controls, Security
Migration Tools
Samba: net, rpcclient, smbpasswd, pdbedit, profiles
Windows: NT4 Domain User Manager, Server Manager (NEXUS)
Authentication
New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
</programlisting>
</para>
</sect2>
</sect1>
</chapter>

335
docs/docbook/projdoc/NT_Security.sgml
View File

@ -1,335 +0,0 @@
<chapter id="unix-permissions">
<chapterinfo>
&author.jeremy;
<pubdate>12 Apr 1999</pubdate>
</chapterinfo>
<title>UNIX Permission Bits and Windows NT Access Control Lists</title>
<sect1>
<title>Viewing and changing UNIX permissions using the NT
security dialogs</title>
<para>Windows NT clients can use their native security settings
dialog box to view and modify the underlying UNIX permissions.</para>
<para>Note that this ability is careful not to compromise
the security of the UNIX host Samba is running on, and
still obeys all the file permission rules that a Samba
administrator can set.</para>
<note>
<para>
All access to Unix/Linux system file via Samba is controlled at
the operating system file access control level. When trying to
figure out file access problems it is vitally important to identify
the identity of the Windows user as it is presented by Samba at
the point of file access. This can best be determined from the
Samba log files.
</para>
</note>
</sect1>
<sect1>
<title>How to view file security on a Samba share</title>
<para>From an NT4/2000/XP client, single-click with the right
mouse button on any file or directory in a Samba mounted
drive letter or UNC path. When the menu pops-up, click
on the <emphasis>Properties</emphasis> entry at the bottom of
the menu. This brings up the file properties dialog
box. Click on the tab <emphasis>Security</emphasis> and you
will see three buttons, <emphasis>Permissions</emphasis>,
<emphasis>Auditing</emphasis>, and <emphasis>Ownership</emphasis>.
The <emphasis>Auditing</emphasis> button will cause either
an error message <errorname>A requested privilege is not held
by the client</errorname> to appear if the user is not the
NT Administrator, or a dialog which is intended to allow an
Administrator to add auditing requirements to a file if the
user is logged on as the NT Administrator. This dialog is
non-functional with a Samba share at this time, as the only
useful button, the <command>Add</command> button will not currently
allow a list of users to be seen.</para>
</sect1>
<sect1>
<title>Viewing file ownership</title>
<para>Clicking on the <command>"Ownership"</command> button
brings up a dialog box telling you who owns the given file. The
owner name will be of the form :</para>
<para><command>"SERVER\user (Long name)"</command></para>
<para>Where <replaceable>SERVER</replaceable> is the NetBIOS name of
the Samba server, <replaceable>user</replaceable> is the user name of
the UNIX user who owns the file, and <replaceable>(Long name)</replaceable>
is the descriptive string identifying the user (normally found in the
GECOS field of the UNIX password database). Click on the <command>Close
</command> button to remove this dialog.</para>
<para>If the parameter <parameter>nt acl support</parameter>
is set to <constant>false</constant> then the file owner will
be shown as the NT user <command>"Everyone"</command>.</para>
<para>The <command>Take Ownership</command> button will not allow
you to change the ownership of this file to yourself (clicking on
it will display a dialog box complaining that the user you are
currently logged onto the NT client cannot be found). The reason
for this is that changing the ownership of a file is a privileged
operation in UNIX, available only to the <emphasis>root</emphasis>
user. As clicking on this button causes NT to attempt to change
the ownership of a file to the current user logged into the NT
client this will not work with Samba at this time.</para>
<para>There is an NT chown command that will work with Samba
and allow a user with Administrator privilege connected
to a Samba server as root to change the ownership of
files on both a local NTFS filesystem or remote mounted NTFS
or Samba drive. This is available as part of the <emphasis>Seclib
</emphasis> NT security library written by Jeremy Allison of
the Samba Team, available from the main Samba ftp site.</para>
</sect1>
<sect1>
<title>Viewing file or directory permissions</title>
<para>The third button is the <command>"Permissions"</command>
button. Clicking on this brings up a dialog box that shows both
the permissions and the UNIX owner of the file or directory.
The owner is displayed in the form :</para>
<para><command>"SERVER\user (Long name)"</command></para>
<para>Where <replaceable>SERVER</replaceable> is the NetBIOS name of
the Samba server, <replaceable>user</replaceable> is the user name of
the UNIX user who owns the file, and <replaceable>(Long name)</replaceable>
is the descriptive string identifying the user (normally found in the
GECOS field of the UNIX password database).</para>
<para>If the parameter <parameter>nt acl support</parameter>
is set to <constant>false</constant> then the file owner will
be shown as the NT user <command>"Everyone"</command> and the
permissions will be shown as NT "Full Control".</para>
<para>The permissions field is displayed differently for files
and directories, so I'll describe the way file permissions
are displayed first.</para>
<sect2>
<title>File Permissions</title>
<para>The standard UNIX user/group/world triple and
the corresponding "read", "write", "execute" permissions
triples are mapped by Samba into a three element NT ACL
with the 'r', 'w', and 'x' bits mapped into the corresponding
NT permissions. The UNIX world permissions are mapped into
the global NT group <command>Everyone</command>, followed
by the list of permissions allowed for UNIX world. The UNIX
owner and group permissions are displayed as an NT
<command>user</command> icon and an NT <command>local
group</command> icon respectively followed by the list
of permissions allowed for the UNIX user and group.</para>
<para>As many UNIX permission sets don't map into common
NT names such as <command>"read"</command>, <command>
"change"</command> or <command>"full control"</command> then
usually the permissions will be prefixed by the words <command>
"Special Access"</command> in the NT display list.</para>
<para>But what happens if the file has no permissions allowed
for a particular UNIX user group or world component ? In order
to allow "no permissions" to be seen and modified then Samba
overloads the NT <command>"Take Ownership"</command> ACL attribute
(which has no meaning in UNIX) and reports a component with
no permissions as having the NT <command>"O"</command> bit set.
This was chosen of course to make it look like a zero, meaning
zero permissions. More details on the decision behind this will
be given below.</para>
</sect2>
<sect2>
<title>Directory Permissions</title>
<para>Directories on an NT NTFS file system have two
different sets of permissions. The first set of permissions
is the ACL set on the directory itself, this is usually displayed
in the first set of parentheses in the normal <command>"RW"</command>
NT style. This first set of permissions is created by Samba in
exactly the same way as normal file permissions are, described
above, and is displayed in the same way.</para>
<para>The second set of directory permissions has no real meaning
in the UNIX permissions world and represents the <command>
"inherited"</command> permissions that any file created within
this directory would inherit.</para>
<para>Samba synthesises these inherited permissions for NT by
returning as an NT ACL the UNIX permission mode that a new file
created by Samba on this share would receive.</para>
</sect2>
</sect1>
<sect1>
<title>Modifying file or directory permissions</title>
<para>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
clicking the <command>OK</command> button. However, there are
limitations that a user needs to be aware of, and also interactions
with the standard Samba permission masks and mapping of DOS
attributes that need to also be taken into account.</para>
<para>If the parameter <parameter>nt acl support</parameter>
is set to <constant>false</constant> then any attempt to set
security permissions will fail with an <command>"Access Denied"
</command> message.</para>
<para>The first thing to note is that the <command>"Add"</command>
button will not return a list of users in Samba (it will give
an error message of <command>"The remote procedure call failed
and did not execute"</command>). This means that you can only
manipulate the current user/group/world permissions listed in
the dialog box. This actually works quite well as these are the
only permissions that UNIX actually has.</para>
<para>If a permission triple (either user, group, or world)
is removed from the list of permissions in the NT dialog box,
then when the <command>"OK"</command> button is pressed it will
be applied as "no permissions" on the UNIX side. If you then
view the permissions again the "no permissions" entry will appear
as the NT <command>"O"</command> flag, as described above. This
allows you to add permissions back to a file or directory once
you have removed them from a triple component.</para>
<para>As UNIX supports only the "r", "w" and "x" bits of
an NT ACL then if other NT security attributes such as "Delete
access" are selected then they will be ignored when applied on
the Samba server.</para>
<para>When setting permissions on a directory the second
set of permissions (in the second set of parentheses) is
by default applied to all files within that directory. If this
is not what you want you must uncheck the <command>"Replace
permissions on existing files"</command> checkbox in the NT
dialog before clicking <command>"OK"</command>.</para>
<para>If you wish to remove all permissions from a
user/group/world component then you may either highlight the
component and click the <command>"Remove"</command> button,
or set the component to only have the special <command>"Take
Ownership"</command> permission (displayed as <command>"O"
</command>) highlighted.</para>
</sect1>
<sect1>
<title>Interaction with the standard Samba create mask
parameters</title>
<para>There are four parameters
to control interaction with the standard Samba create mask parameters.
These are :</para>
<para><parameter>security mask</parameter></para>
<para><parameter>force security mode</parameter></para>
<para><parameter>directory security mask</parameter></para>
<para><parameter>force directory security mode</parameter></para>
<para>Once a user clicks <command>"OK"</command> to apply the
permissions Samba maps the given permissions into a user/group/world
r/w/x triple set, and then will check the changed permissions for a
file against the bits set in the <ulink url="smb.conf.5.html#SECURITYMASK">
<parameter>security mask</parameter></ulink> parameter. Any bits that
were changed that are not set to '1' in this parameter are left alone
in the file permissions.</para>
<para>Essentially, zero bits in the <parameter>security mask</parameter>
mask may be treated as a set of bits the user is <emphasis>not</emphasis>
allowed to change, and one bits are those the user is allowed to change.
</para>
<para>If not set explicitly this parameter is set to the same value as
the <ulink url="smb.conf.5.html#CREATEMASK"><parameter>create mask
</parameter></ulink> parameter. To allow a user to modify all the
user/group/world permissions on a file, set this parameter
to 0777.</para>
<para>Next Samba checks the changed permissions for a file against
the bits set in the <ulink url="smb.conf.5.html#FORCESECURITYMODE">
<parameter>force security mode</parameter></ulink> parameter. Any bits
that were changed that correspond to bits set to '1' in this parameter
are forced to be set.</para>
<para>Essentially, bits set in the <parameter>force security mode
</parameter> parameter may be treated as a set of bits that, when
modifying security on a file, the user has always set to be 'on'.</para>
<para>If not set explicitly this parameter is set to the same value
as the <ulink url="smb.conf.5.html#FORCECREATEMODE"><parameter>force
create mode</parameter></ulink> parameter.
To allow a user to modify all the user/group/world permissions on a file
with no restrictions set this parameter to 000.</para>
<para>The <parameter>security mask</parameter> and <parameter>force
security mode</parameter> parameters are applied to the change
request in that order.</para>
<para>For a directory Samba will perform the same operations as
described above for a file except using the parameter <parameter>
directory security mask</parameter> instead of <parameter>security
mask</parameter>, and <parameter>force directory security mode
</parameter> parameter instead of <parameter>force security mode
</parameter>.</para>
<para>The <parameter>directory security mask</parameter> parameter
by default is set to the same value as the <parameter>directory mask
</parameter> parameter and the <parameter>force directory security
mode</parameter> parameter by default is set to the same value as
the <parameter>force directory mode</parameter> parameter. </para>
<para>In this way Samba enforces the permission restrictions that
an administrator can set on a Samba share, whilst still allowing users
to modify the permission bits within that restriction.</para>
<para>If you want to set up a share that allows users full control
in modifying the permission bits on their files and directories and
doesn't force any particular bits to be set 'on', then set the following
parameters in the &smb.conf; file in that share specific section :</para>
<para><parameter>security mask = 0777</parameter></para>
<para><parameter>force security mode = 0</parameter></para>
<para><parameter>directory security mask = 0777</parameter></para>
<para><parameter>force directory security mode = 0</parameter></para>
</sect1>
<sect1>
<title>Interaction with the standard Samba file attribute
mapping</title>
<para>Samba maps some of the DOS attribute bits (such as "read
only") into the UNIX permissions of a file. This means there can
be a conflict between the permission bits set via the security
dialog and the permission bits set by the file attribute mapping.
</para>
<para>One way this can show up is if a file has no UNIX read access
for the owner it will show up as "read only" in the standard
file attributes tabbed dialog. Unfortunately this dialog is
the same one that contains the security info in another tab.</para>
<para>What this can mean is that if the owner changes the permissions
to allow themselves read access using the security dialog, clicks
<command>"OK"</command> to get back to the standard attributes tab
dialog, and then clicks <command>"OK"</command> on that dialog, then
NT will set the file permissions back to read-only (as that is what
the attributes still say in the dialog). This means that after setting
permissions and clicking <command>"OK"</command> to get back to the
attributes dialog you should always hit <command>"Cancel"</command>
rather than <command>"OK"</command> to ensure that your changes
are not overridden.</para>
</sect1>
</chapter>

1288
docs/docbook/projdoc/NetworkBrowsing.sgml
View File

File diff suppressed because it is too large Load Diff

373
docs/docbook/projdoc/Other-Clients.sgml
View File

@ -1,373 +0,0 @@
<chapter id="Other-Clients">
<chapterinfo>
&author.jmcd;
&author.jelmer;
<pubdate>5 Mar 2001</pubdate>
</chapterinfo>
<title>Samba and other CIFS clients</title>
<para>This chapter contains client-specific information.</para>
<sect1>
<title>Macintosh clients?</title>
<para>
Yes. <ulink url="http://www.thursby.com/">Thursby</ulink> now have a CIFS Client / Server called <ulink url="http://www.thursby.com/products/dave.html">DAVE</ulink>
</para>
<para>
They test it against Windows 95, Windows NT and samba for
compatibility issues. At the time of writing, DAVE was at version
1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
the Thursby web site (the speed of finder copies has been greatly
enhanced, and there are bug-fixes included).
</para>
<para>
Alternatives - There are two free implementations of AppleTalk for
several kinds of UNIX machnes, and several more commercial ones.
These products allow you to run file services and print services
natively to Macintosh users, with no additional support required on
the Macintosh. The two free omplementations are
<ulink url="http://www.umich.edu/~rsug/netatalk/">Netatalk</ulink>, and
<ulink url="http://www.cs.mu.oz.au/appletalk/atalk.html">CAP</ulink>.
What Samba offers MS
Windows users, these packages offer to Macs. For more info on these
packages, Samba, and Linux (and other UNIX-based systems) see
<ulink url="http://www.eats.com/linux_mac_win.html">http://www.eats.com/linux_mac_win.html</ulink>
</para>
</sect1>
<sect1>
<title>OS2 Client</title>
<sect2>
<title>How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</title>
<para>A more complete answer to this question can be
found on <ulink url="http://carol.wins.uva.nl/~leeuw/samba/warp.html">
http://carol.wins.uva.nl/~leeuw/samba/warp.html</ulink>.</para>
<para>Basically, you need three components:</para>
<itemizedlist>
<listitem><para>The File and Print Client ('IBM Peer')
</para></listitem>
<listitem><para>TCP/IP ('Internet support')
</para></listitem>
<listitem><para>The "NetBIOS over TCP/IP" driver ('TCPBEUI')
</para></listitem>
</itemizedlist>
<para>Installing the first two together with the base operating
system on a blank system is explained in the Warp manual. If Warp
has already been installed, but you now want to install the
networking support, use the "Selective Install for Networking"
object in the "System Setup" folder.</para>
<para>Adding the "NetBIOS over TCP/IP" driver is not described
in the manual and just barely in the online documentation. Start
MPTS.EXE, click on OK, click on "Configure LAPS" and click
on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line
is then moved to 'Current Configuration'. Select that line,
click on "Change number" and increase it from 0 to 1. Save this
configuration.</para>
<para>If the Samba server(s) is not on your local subnet, you
can optionally add IP names and addresses of these servers
to the "Names List", or specify a WINS server ('NetBIOS
Nameserver' in IBM and RFC terminology). For Warp Connect you
may need to download an update for 'IBM Peer' to bring it on
the same level as Warp 4. See the webpage mentioned above.</para>
</sect2>
<sect2>
<title>How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</title>
<para>You can use the free Microsoft LAN Manager 2.2c Client
for OS/2 from
<ulink url="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/">
ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</ulink>.
See <ulink url="http://carol.wins.uva.nl/~leeuw/lanman.html">
http://carol.wins.uva.nl/~leeuw/lanman.html</ulink> for
more information on how to install and use this client. In
a nutshell, edit the file \OS2VER in the root directory of
the OS/2 boot partition and add the lines:</para>
<para><programlisting>
20=setup.exe
20=netwksta.sys
20=netvdd.sys
</programlisting></para>
<para>before you install the client. Also, don't use the
included NE2000 driver because it is buggy. Try the NE2000
or NS2000 driver from
<ulink url="ftp://ftp.cdrom.com/pub/os2/network/ndis/">
ftp://ftp.cdrom.com/pub/os2/network/ndis/</ulink> instead.
</para>
</sect2>
<sect2>
<title>Are there any other issues when OS/2 (any version)
is used as a client?</title>
<para>When you do a NET VIEW or use the "File and Print
Client Resource Browser", no Samba servers show up. This can
be fixed by a patch from <ulink
url="http://carol.wins.uva.nl/~leeuw/samba/fix.html">
http://carol.wins.uva.nl/~leeuw/samba/fix.html</ulink>.
The patch will be included in a later version of Samba. It also
fixes a couple of other problems, such as preserving long
filenames when objects are dragged from the Workplace Shell
to the Samba server. </para>
</sect2>
<sect2>
<title>How do I get printer driver download working
for OS/2 clients?</title>
<para>First, create a share called [PRINTDRV] that is
world-readable. Copy your OS/2 driver files there. Note
that the .EA_ files must still be separate, so you will need
to use the original install files, and not copy an installed
driver from an OS/2 system.</para>
<para>Install the NT driver first for that printer. Then,
add to your smb.conf a parameter, os2 driver map =
<replaceable>filename</replaceable>". Then, in the file
specified by <replaceable>filename</replaceable>, map the
name of the NT driver name to the OS/2 driver name as
follows:</para>
<para><command>nt driver name = os2 "driver
name"."device name"</command>, e.g.:
HP LaserJet 5L = LASERJET.HP LaserJet 5L</para>
<para>You can have multiple drivers mapped in this file.</para>
<para>If you only specify the OS/2 driver name, and not the
device name, the first attempt to download the driver will
actually download the files, but the OS/2 client will tell
you the driver is not available. On the second attempt, it
will work. This is fixed simply by adding the device name
to the mapping, after which it will work on the first attempt.
</para>
</sect2>
</sect1>
<sect1>
<title>Windows for Workgroups</title>
<sect2>
<title>Use latest TCP/IP stack from Microsoft</title>
<para>Use the latest TCP/IP stack from microsoft if you use Windows
for workgroups.
</para>
<para>The early TCP/IP stacks had lots of bugs.</para>
<para>
Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
VxD drivers. The latest release can be found on their ftp site at
ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
There is an update.txt file there that describes the problems that were
fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386,
WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.
</para>
</sect2>
<sect2>
<title>Delete .pwl files after password change</title>
<para>
WfWg does a lousy job with passwords. I find that if I change my
password on either the unix box or the PC the safest thing to do is to
delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.
</para>
<para>
If you don't do this you may find that WfWg remembers and uses the old
password, even if you told it a new one.
</para>
<para>
Often WfWg will totally ignore a password you give it in a dialog box.
</para>
</sect2>
<sect2>
<title>Configure WfW password handling</title>
<para>
There is a program call admincfg.exe
on the last disk (disk 8) of the WFW 3.11 disk set. To install it
type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon
for it via the "Progam Manager" "New" Menu. This program allows you
to control how WFW handles passwords. ie disable Password Caching etc
for use with <command>security = user</command>
</para>
</sect2>
<sect2>
<title>Case handling of passwords</title>
<para>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <ulink url="smb.conf.5.html">smb.conf(5)</ulink> information on <command>password level</command> to specify what characters samba should try to uppercase when checking.</para>
</sect2>
<sect2>
<title>Use TCP/IP as default protocol</title>
<para>To support print queue reporting you may find
that you have to use TCP/IP as the default protocol under
WfWg. For some reason if you leave Netbeui as the default
it may break the print queue reporting on some systems.
It is presumably a WfWg bug.</para>
</sect2>
<sect2>
<title>Speed improvement</title>
<para>
Note that some people have found that setting DefaultRcvWindow in
the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
big improvement. I don't know why.
</para>
<para>
My own experience wth DefaultRcvWindow is that I get much better
performance with a large value (16384 or larger). Other people have
reported that anything over 3072 slows things down enourmously. One
person even reported a speed drop of a factor of 30 when he went from
3072 to 8192. I don't know why.
</para>
</sect2>
</sect1>
<sect1>
<title>Windows '95/'98</title>
<para>
When using Windows 95 OEM SR2 the following updates are recommended where Samba
is being used. Please NOTE that the above change will affect you once these
updates have been installed.
</para>
<para>
There are more updates than the ones mentioned here. You are referred to the
Microsoft Web site for all currently available updates to your specific version
of Windows 95.
</para>
<orderedlist>
<listitem><para>Kernel Update: KRNLUPD.EXE</para></listitem>
<listitem><para>Ping Fix: PINGUPD.EXE</para></listitem>
<listitem><para>RPC Update: RPCRTUPD.EXE</para></listitem>
<listitem><para>TCP/IP Update: VIPUPD.EXE</para></listitem>
<listitem><para>Redirector Update: VRDRUPD.EXE</para></listitem>
</orderedlist>
<para>
Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This
fix may stop your machine from hanging for an extended period when exiting
OutLook and you may also notice a significant speedup when accessing network
neighborhood services.
</para>
<sect2>
<title>Speed improvement</title>
<para>
Configure the win95 TCPIP registry settings to give better
performance. I use a program called MTUSPEED.exe which I got off the
net. There are various other utilities of this type freely available.
</para>
</sect2>
</sect1>
<sect1>
<title>Windows 2000 Service Pack 2</title>
<para>
There are several annoyances with Windows 2000 SP2. One of which
only appears when using a Samba server to host user profiles
to Windows 2000 SP2 clients in a Windows domain. This assumes
that Samba is a member of the domain, but the problem will
likely occur if it is not.
</para>
<para>
In order to server profiles successfully to Windows 2000 SP2
clients (when not operating as a PDC), Samba must have
<command>nt acl support = no</command>
added to the file share which houses the roaming profiles.
If this is not done, then the Windows 2000 SP2 client will
complain about not being able to access the profile (Access
Denied) and create multiple copies of it on disk (DOMAIN.user.001,
DOMAIN.user.002, etc...). See the
<ulink url="smb.conf.5.html">smb.conf(5)</ulink> man page
for more details on this option. Also note that the
<command>nt acl support</command> parameter was formally a global parameter in
releases prior to Samba 2.2.2.
</para>
<para>
The following is a minimal profile share:
</para>
<para><programlisting>
[profile]
path = /export/profile
create mask = 0600
directory mask = 0700
nt acl support = no
read only = no
</programlisting></para>
<para>
The reason for this bug is that the Win2k SP2 client copies
the security descriptor for the profile which contains
the Samba server's SID, and not the domain SID. The client
compares the SID for SAMBA\user and realizes it is
different that the one assigned to DOMAIN\user. Hence the reason
for the "access denied" message.
</para>
<para>
By disabling the <command>nt acl support</command> parameter, Samba will send
the Win2k client a response to the QuerySecurityDescriptor
trans2 call which causes the client to set a default ACL
for the profile. This default ACL includes
</para>
<para><command>DOMAIN\user "Full Control"</command></para>
<note><para>This bug does not occur when using winbind to
create accounts on the Samba host for Domain users.</para></note>
</sect1>
<sect1>
<title>Windows NT 3.1</title>
<para>If you have problems communicating across routers with Windows
NT 3.1 workstations, read <ulink url="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765">this Microsoft Knowledge Base article</ulink>.
</para>
</sect1>
</chapter>

389
docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml
View File

@ -1,389 +0,0 @@
<chapter id="pam">
<chapterinfo>
&author.jht;
<pubdate> (Jun 21 2001) </pubdate>
</chapterinfo>
<title>PAM Configuration for Centrally Managed Authentication</title>
<sect1>
<title>Samba and PAM</title>
<para>
A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
Modules (PAM) facility to provide all authentication,
authorization and resource control services. Prior to the
introduction of PAM, a decision to use an alternative to
the system password database (<filename>/etc/passwd</filename>)
would require the provision of alternatives for all programs that provide
security services. Such a choice would involve provision of
alternatives to such programs as: <command>login</command>,
<command>passwd</command>, <command>chown</command>, etc.
</para>
<para>
PAM provides a mechanism that disconnects these security programs
from the underlying authentication/authorization infrastructure.
PAM is configured either through one file <filename>/etc/pam.conf</filename> (Solaris),
or by editing individual files that are located in <filename>/etc/pam.d</filename>.
</para>
<note>
<para>
If the PAM authentication module (loadable link library file) is located in the
default location then it is not necessary to specify the path. In the case of
Linux, the default location is <filename>/lib/security</filename>. If the module
is located outside the default then the path must be specified as:
<programlisting>
auth required /other_path/pam_strange_module.so
</programlisting>
</para>
</note>
<para>
The following is an example <filename>/etc/pam.d/login</filename> configuration file.
This example had all options been uncommented is probably not usable
as it stacks many conditions before allowing successful completion
of the login process. Essentially all conditions can be disabled
by commenting them out except the calls to <filename>pam_pwdb.so</filename>.
</para>
<para><programlisting>
#%PAM-1.0
# The PAM configuration file for the `login' service
#
auth required pam_securetty.so
auth required pam_nologin.so
# auth required pam_dialup.so
# auth optional pam_mail.so
auth required pam_pwdb.so shadow md5
# account requisite pam_time.so
account required pam_pwdb.so
session required pam_pwdb.so
# session optional pam_lastlog.so
# password required pam_cracklib.so retry=3
password required pam_pwdb.so shadow md5
</programlisting></para>
<para>
PAM allows use of replacable modules. Those available on a
sample system include:
</para>
<para><prompt>$</prompt><userinput>/bin/ls /lib/security</userinput>
<programlisting>
pam_access.so pam_ftp.so pam_limits.so
pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
pam_cracklib.so pam_group.so pam_listfile.so
pam_nologin.so pam_rootok.so pam_tally.so
pam_deny.so pam_issue.so pam_mail.so
pam_permit.so pam_securetty.so pam_time.so
pam_dialup.so pam_lastlog.so pam_mkhomedir.so
pam_pwdb.so pam_shells.so pam_unix.so
pam_env.so pam_ldap.so pam_motd.so
pam_radius.so pam_smbpass.so pam_unix_acct.so
pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
pam_userdb.so pam_warn.so pam_unix_session.so
</programlisting></para>
<para>
The following example for the login program replaces the use of
the <filename>pam_pwdb.so</filename> module which uses the system
password database (<filename>/etc/passwd</filename>,
<filename>/etc/shadow</filename>, <filename>/etc/group</filename>) with
the module <filename>pam_smbpass.so</filename> which uses the Samba
database which contains the Microsoft MD4 encrypted password
hashes. This database is stored in either
<filename>/usr/local/samba/private/smbpasswd</filename>,
<filename>/etc/samba/smbpasswd</filename>, or in
<filename>/etc/samba.d/smbpasswd</filename>, depending on the
Samba implementation for your Unix/Linux system. The
<filename>pam_smbpass.so</filename> module is provided by
Samba version 2.2.1 or later. It can be compiled by specifying the
<command>--with-pam_smbpass</command> options when running Samba's
<filename>configure</filename> script. For more information
on the <filename>pam_smbpass</filename> module, see the documentation
in the <filename>source/pam_smbpass</filename> directory of the Samba
source distribution.
</para>
<para><programlisting>
#%PAM-1.0
# The PAM configuration file for the `login' service
#
auth required pam_smbpass.so nodelay
account required pam_smbpass.so nodelay
session required pam_smbpass.so nodelay
password required pam_smbpass.so nodelay
</programlisting></para>
<para>
The following is the PAM configuration file for a particular
Linux system. The default condition uses <filename>pam_pwdb.so</filename>.
</para>
<para><programlisting>
#%PAM-1.0
# The PAM configuration file for the `samba' service
#
auth required pam_pwdb.so nullok nodelay shadow audit
account required pam_pwdb.so audit nodelay
session required pam_pwdb.so nodelay
password required pam_pwdb.so shadow md5
</programlisting></para>
<para>
In the following example the decision has been made to use the
smbpasswd database even for basic samba authentication. Such a
decision could also be made for the passwd program and would
thus allow the smbpasswd passwords to be changed using the passwd
program.
</para>
<para><programlisting>
#%PAM-1.0
# The PAM configuration file for the `samba' service
#
auth required pam_smbpass.so nodelay
account required pam_pwdb.so audit nodelay
session required pam_pwdb.so nodelay
password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
</programlisting></para>
<note><para>PAM allows stacking of authentication mechanisms. It is
also possible to pass information obtained within one PAM module through
to the next module in the PAM stack. Please refer to the documentation for
your particular system implementation for details regarding the specific
capabilities of PAM in this environment. Some Linux implmentations also
provide the <filename>pam_stack.so</filename> module that allows all
authentication to be configured in a single central file. The
<filename>pam_stack.so</filename> method has some very devoted followers
on the basis that it allows for easier administration. As with all issues in
life though, every decision makes trade-offs, so you may want examine the
PAM documentation for further helpful information.
</para></note>
<sect2>
<title>PAM Configuration in smb.conf</title>
<para>
There is an option in smb.conf called <ulink
url="smb.conf.5.html#OBEYPAMRESTRICTIONS">obey pam restrictions</ulink>.
The following is from the on-line help for this option in SWAT;
</para>
<para>
When Samba is configured to enable PAM support (i.e.
<constant>--with-pam</constant>), 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
<ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords = yes</ulink>.
The reason is that PAM modules cannot support the challenge/response
authentication mechanism needed in the presence of SMB
password encryption.
</para>
<para>Default: <command>obey pam restrictions = no</command></para>
</sect2>
<sect2>
<title>Password Synchronisation using pam_smbpass.so</title>
<para>
pam_smbpass is a PAM module which can be used on conforming systems to
keep the smbpasswd (Samba password) database in sync with the unix
password file. PAM (Pluggable Authentication Modules) is an API supported
under some Unices, such as Solaris, HPUX and Linux, that provides a
generic interface to authentication mechanisms.
</para>
<para>
For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/
</para>
<para>
This module authenticates a local smbpasswd user database. If you require
support for authenticating against a remote SMB server, or if you're
concerned about the presence of suid root binaries on your system, it is
recommended that you use pam_winbind instead.
</para>
<para><programlisting>
Options recognized by this module are as follows:
debug - log more debugging info
audit - like debug, but also logs unknown usernames
use_first_pass - don't prompt the user for passwords;
take them from PAM_ items instead
try_first_pass - try to get the password from a previous
PAM module, fall back to prompting the user
use_authtok - like try_first_pass, but *fail* if the new
PAM_AUTHTOK has not been previously set.
(intended for stacking password modules only)
not_set_pass - don't make passwords used by this module
available to other modules.
nodelay - don't insert ~1 second delays on authentication
failure.
nullok - null passwords are allowed.
nonull - null passwords are not allowed. Used to
override the Samba configuration.
migrate - only meaningful in an "auth" context;
used to update smbpasswd file with a
password used for successful authentication.
smbconf=&lt file &gt - specify an alternate path to the smb.conf
file.
</programlisting></para>
<para><programlisting>
Thanks go to the following people:
* Andrew Morgan &lt morgan@transmeta.com &gt, for providing the Linux-PAM
framework, without which none of this would have happened
* Christian Gafton &lt gafton@redhat.com &gt and Andrew Morgan again, for the
pam_pwdb module upon which pam_smbpass was originally based
* Luke Leighton &lt lkcl@switchboard.net &gt for being receptive to the idea,
and for the occasional good-natured complaint about the project's status
that keep me working on it :)
* and of course, all the other members of the Samba team
&lt http://www.samba.org/samba/team.html &gt, for creating a great product
and for giving this project a purpose
---------------------
Stephen Langasek &lt vorlon@netexpress.net &gt
</programlisting></para>
<para>
The following are examples of the use of pam_smbpass.so in the format of Linux
<filename>/etc/pam.d/</filename> files structure. Those wishing to implement this
tool on other platforms will need to adapt this appropriately.
</para>
<sect3>
<title>Password Synchonisation Configuration</title>
<para>
A sample PAM configuration that shows the use of pam_smbpass to make
sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow)
is changed. Useful when an expired password might be changed by an
application (such as ssh).
</para>
<para><programlisting>
#%PAM-1.0
# password-sync
#
auth requisite pam_nologin.so
auth required pam_unix.so
account required pam_unix.so
password requisite pam_cracklib.so retry=3
password requisite pam_unix.so shadow md5 use_authtok try_first_pass
password required pam_smbpass.so nullok use_authtok try_first_pass
session required pam_unix.so
</programlisting></para>
</sect3>
<sect3>
<title>Password Migration Configuration</title>
<para>
A sample PAM configuration that shows the use of pam_smbpass to migrate
from plaintext to encrypted passwords for Samba. Unlike other methods,
this can be used for users who have never connected to Samba shares:
password migration takes place when users ftp in, login using ssh, pop
their mail, etc.
</para>
<para><programlisting>
#%PAM-1.0
# password-migration
#
auth requisite pam_nologin.so
# pam_smbpass is called IFF pam_unix succeeds.
auth requisite pam_unix.so
auth optional pam_smbpass.so migrate
account required pam_unix.so
password requisite pam_cracklib.so retry=3
password requisite pam_unix.so shadow md5 use_authtok try_first_pass
password optional pam_smbpass.so nullok use_authtok try_first_pass
session required pam_unix.so
</programlisting></para>
</sect3>
<sect3>
<title>Mature Password Configuration</title>
<para>
A sample PAM configuration for a 'mature' smbpasswd installation.
private/smbpasswd is fully populated, and we consider it an error if
the smbpasswd doesn't exist or doesn't match the Unix password.
</para>
<para><programlisting>
#%PAM-1.0
# password-mature
#
auth requisite pam_nologin.so
auth required pam_unix.so
account required pam_unix.so
password requisite pam_cracklib.so retry=3
password requisite pam_unix.so shadow md5 use_authtok try_first_pass
password required pam_smbpass.so use_authtok use_first_pass
session required pam_unix.so
</programlisting></para>
</sect3>
<sect3>
<title>Kerberos Password Integration Configuration</title>
<para>
A sample PAM configuration that shows pam_smbpass used together with
pam_krb5. This could be useful on a Samba PDC that is also a member of
a Kerberos realm.
</para>
<para><programlisting>
#%PAM-1.0
# kdc-pdc
#
auth requisite pam_nologin.so
auth requisite pam_krb5.so
auth optional pam_smbpass.so migrate
account required pam_krb5.so
password requisite pam_cracklib.so retry=3
password optional pam_smbpass.so nullok use_authtok try_first_pass
password required pam_krb5.so use_authtok try_first_pass
session required pam_krb5.so
</programlisting></para>
</sect3>
</sect2>
</sect1>
<sect1>
<title>Distributed Authentication</title>
<para>
The astute administrator will realize from this that the
combination of <filename>pam_smbpass.so</filename>,
<command>winbindd</command>, and a distributed
passdb backend, such as ldap, will allow the establishment of a
centrally managed, distributed
user/password database that can also be used by all
PAM (eg: Linux) aware programs and applications. This arrangement
can have particularly potent advantages compared with the
use of Microsoft Active Directory Service (ADS) in so far as
reduction of wide area network authentication traffic.
</para>
</sect1>
</chapter>

385
docs/docbook/projdoc/PolicyMgmt.sgml
View File

@ -1,385 +0,0 @@
<chapter id="PolicyMgmt">
<chapterinfo>
&author.jht;
<pubdate>April 3 2003</pubdate>
</chapterinfo>
<title>System and Account Policies</title>
<sect1>
<title>Creating and Managing System Policies</title>
<para>
Under MS Windows platforms, particularly those following the release of MS Windows
NT4 and MS Windows 95) it is possible to create a type of file that would be placed
in the NETLOGON share of a domain controller. As the client logs onto the network
this file is read and the contents initiate changes to the registry of the client
machine. This file allows changes to be made to those parts of the registry that
affect users, groups of users, or machines.
</para>
<para>
For MS Windows 9x/Me this file must be called <filename>Config.POL</filename> and may
be generated using a tool called <filename>poledit.exe</filename>, better known as the
Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
dissappeared again with the introduction of MS Windows Me (Millenium Edition). From
comments from MS Windows network administrators it would appear that this tool became
a part of the MS Windows Me Resource Kit.
</para>
<para>
MS Windows NT4 Server products include the <emphasis>System Policy Editor</emphasis>
under the <filename>Start -> Programs -> Administrative Tools</filename> menu item.
For MS Windows NT4 and later clients this file must be called <filename>NTConfig.POL</filename>.
</para>
<para>
New with the introduction of MS Windows 2000 was the Microsoft Management Console
or MMC. This tool is the new wave in the ever changing landscape of Microsoft
methods for management of network access and security. Every new Microsoft product
or technology seems to obsolete the old rules and to introduce newer and more
complex tools and methods. To Microsoft's credit though, the MMC does appear to
be a step forward, but improved functionality comes at a great price.
</para>
<para>
Before embarking on the configuration of network and system policies it is highly
advisable to read the documentation available from Microsoft's web site regarding
<ulink url="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp">
Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</ulink> available from Microsoft.
There are a large number of documents in addition to this old one that should also
be read and understood. Try searching on the Microsoft web site for "Group Policies".
</para>
<para>
What follows is a very brief discussion with some helpful notes. The information provided
here is incomplete - you are warned.
</para>
<sect2>
<title>Windows 9x/Me Policies</title>
<para>
You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me.
It can be found on the Original full product Win98 installation CD under
<filename>tools/reskit/netadmin/poledit</filename>. Install this using the
Add/Remove Programs facility and then click on the 'Have Disk' tab.
</para>
<para>
Use the Group Policy Editor to create a policy file that specifies the location of
user profiles and/or the <filename>My Documents</filename> etc. stuff. Then
save these settings in a file called <filename>Config.POL</filename> that needs to
be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto
the Samba Domain, it will automatically read this file and update the Win9x/Me registry
of the machine as it logs on.
</para>
<para>
Further details are covered in the Win98 Resource Kit documentation.
</para>
<para>
If you do not take the right steps, then every so often Win9x/Me will check the
integrity of the registry and will restore it's settings from the back-up
copy of the registry it stores on each Win9x/Me machine. Hence, you will
occasionally notice things changing back to the original settings.
</para>
<para>
Install the group policy handler for Win9x to pick up group policies. Look on the
Win98 CD in <filename>\tools\reskit\netadmin\poledit</filename>.
Install group policies on a Win9x client by double-clicking
<filename>grouppol.inf</filename>. 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/Me machine that uses group policies.
</para>
</sect2>
<sect2>
<title>Windows NT4 Style Policy Files</title>
<para>
To create or edit <filename>ntconfig.pol</filename> you must use the NT Server
Policy Editor, <command>poledit.exe</command> which is included with NT4 Server
but <emphasis>not NT Workstation</emphasis>. There is a Policy Editor on a NT4
Workstation but it is not suitable for creating <emphasis>Domain Policies</emphasis>.
Further, although the Windows 95 Policy Editor can be installed on an NT4
Workstation/Server, it will not work with NT clients. However, the files from
the NT Server will run happily enough on an NT4 Workstation.
</para>
<para>
You need <filename>poledit.exe, common.adm</filename> and <filename>winnt.adm</filename>.
It is convenient to put the two *.adm files in the <filename>c:\winnt\inf</filename>
directory which is where the binary will look for them unless told otherwise. Note also that that
directory is normally 'hidden'.
</para>
<para>
The Windows NT policy editor is also included with the Service Pack 3 (and
later) for Windows NT 4.0. Extract the files using <command>servicepackname /x</command>,
i.e. that's <command>Nt4sp6ai.exe /x</command> for service pack 6a. The policy editor,
<command>poledit.exe</command> 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.
</para>
<sect3>
<title>Registry Tattoos</title>
<para>
With NT4 style registry based policy changes, a large number of settings are not
automatically reversed as the user logs off. Since the settings that were in the
NTConfig.POL file were applied to the client machine registry and that apply to the
hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
as tattooing. It can have serious consequences down-stream and the administrator must
be extremely careful not to lock out the ability to manage the machine at a later date.
</para>
</sect3>
</sect2>
<sect2>
<title>MS Windows 200x / XP Professional Policies</title>
<para>
Windows NT4 System policies allows setting of registry parameters specific to
users, groups and computers (client workstations) that are members of the NT4
style domain. Such policy file will work with MS Windows 2000 / XP clients also.
</para>
<para>
New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
a superset of capabilities compared with NT4 style policies. Obviously, the tool used
to create them is different, and the mechanism for implementing them is much changed.
</para>
<para>
The older NT4 style registry based policies are known as <emphasis>Administrative Templates</emphasis>
in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
users' desktop (including: the location of <emphasis>My Documents</emphasis> files (directory), as
well as intrinsics of where menu items will appear in the Start menu). An additional new
feature is the ability to make available particular software Windows applications to particular
users and/or groups.
</para>
<para>
Remember: NT4 policy files are named <filename>NTConfig.POL</filename> and are stored in the root
of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
and selects the domain name to which the logon will attempt to take place. During the logon
process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
server, modifies the local registry values according to the settings in this file.
</para>
<para>
Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
Directory domain controllers. The part that is stored in the Active Directory itself is called the
group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
known as the group policy template (GPT).
</para>
<para>
With NT4 clients the policy file is read and executed upon only as each user logs onto the network.
MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
startup (machine specific part) and when the user logs onto the network the user specific part
is applied. In MS Windows 200x style policy management each machine and/or user may be subject
to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows
the administrator to also set filters over the policy settings. No such equivalent capability
exists with NT4 style policy files.
</para>
<sect3>
<title>Administration of Win2K / XP Policies</title>
<procedure>
<title>Instructions</title>
<para>
Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the
executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console
(MMC) snap-in as follows:</para>
<step>
<para>
Go to the Windows 200x / XP menu <filename>Start->Programs->Administrative Tools</filename>
and select the MMC snap-in called "Active Directory Users and Computers"
</para>
</step>
<step><para>
Select the domain or organizational unit (OU) that you wish to manage, then right click
to open the context menu for that object, select the properties item.
</para></step>
<step><para>
Now left click on the Group Policy tab, then left click on the New tab. Type a name
for the new policy you will create.
</para></step>
<step><para>
Now left click on the Edit tab to commence the steps needed to create the GPO.
</para></step>
</procedure>
<para>
All policy configuration options are controlled through the use of policy administrative
templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x.
The later introduces many new features as well as extended definition capabilities. It is
well beyond the scope of this documentation to explain how to program .adm files, for that
the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular
version of MS Windows.
</para>
<note>
<para>
The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
use this powerful tool. Please refer to the resource kit manuals for specific usage information.
</para>
</note>
</sect3>
</sect2>
</sect1>
<sect1>
<title>Managing Account/User Policies</title>
<para>
Policies can define a specific user's settings or the settings for a group of users. The resulting
policy file contains the registry settings for all users, groups, and computers that will be using
the policy file. Separate policy files for each user, group, or computer are not not necessary.
</para>
<para>
If you create a policy that will be automatically downloaded from validating domain controllers,
you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
policy file and, by modifying the Windows NT-based workstation, directing the computer to update
the policy from a manual path. You can do this by either manually changing the registry or by using
the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
but if a change is necessary to all machines, this change must be made individually to each workstation.
</para>
<para>
When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain
controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
applied to the user's part of the registry.
</para>
<para>
MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
itself. The key benefit of using AS GPOs is that they impose no registry <emphasis>tatooing</emphasis> effect.
This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.
</para>
<para>
In addition to user access controls that may be imposed or applied via system and/or group policies
in a manner that works in conjunction with user profiles, the user management environment under
MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
Common restrictions that are frequently used includes:
</para>
<para>
<simplelist>
<member>Logon Hours</member>
<member>Password Aging</member>
<member>Permitted Logon from certain machines only</member>
<member>Account type (Local or Global)</member>
<member>User Rights</member>
</simplelist>
</para>
<sect2>
<title>With Windows NT4/200x</title>
<para>
The tools that may be used to configure these types of controls from the MS Windows environment are:
The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe).
Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate
"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.
</para>
</sect2>
<sect2>
<title>With a Samba PDC</title>
<para>
With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
<filename>smbpasswd, pdbedit, net, rpcclient.</filename>. The administrator should read the
man pages for these tools and become familiar with their use.
</para>
</sect2>
</sect1>
<sect1>
<title>System Startup and Logon Processing Overview</title>
<para>
The following attempts to document the order of processing of system and user policies following a system
reboot and as part of the user logon:
</para>
<orderedlist>
<listitem><para>
Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming
Convention Provider (MUP) start
</para></listitem>
<listitem><para>
Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded
and applied. The list may include GPOs that:
<simplelist>
<member>Apply to the location of machines in a Directory</member>
<member>Apply only when settings have changed</member>
<member>Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.</member>
</simplelist>
No desktop user interface is presented until the above have been processed.
</para></listitem>
<listitem><para>
Execution of start-up scripts (hidden and synchronous by defaut).
</para></listitem>
<listitem><para>
A keyboard action to affect start of logon (Ctrl-Alt-Del).
</para></listitem>
<listitem><para>
User credentials are validated, User profile is loaded (depends on policy settings).
</para></listitem>
<listitem><para>
An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of:
<simplelist>
<member>Is user a domain member, thus subject to particular policies</member>
<member>Loopback enablement, and the state of the loopback policy (Merge or Replace)</member>
<member>Location of the Active Directory itself</member>
<member>Has the list of GPOs changed. No processing is needed if not changed.</member>
</simplelist>
</para></listitem>
<listitem><para>
User Policies are applied from Active Directory. Note: There are several types.
</para></listitem>
<listitem><para>
Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group
Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal
window.
</para></listitem>
<listitem><para>
The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4
Domain) machine (system) policies are applied at start-up, User policies are applied at logon.
</para></listitem>
</orderedlist>
</sect1>
</chapter>

235
docs/docbook/projdoc/Portability.sgml
View File

@ -1,235 +0,0 @@
<chapter id="Portability">
<chapterinfo>
&author.jelmer;
</chapterinfo>
<title>Portability</title>
<para>Samba works on a wide range of platforms but the interface all the
platforms provide is not always compatible. This chapter contains
platform-specific information about compiling and using samba.</para>
<sect1>
<title>HPUX</title>
<para>
HP's implementation of supplementary groups is, er, non-standard (for
hysterical reasons). There are two group files, /etc/group and
/etc/logingroup; the system maps UIDs to numbers using the former, but
initgroups() reads the latter. Most system admins who know the ropes
symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons
too stupid to go into here). initgroups() will complain if one of the
groups you're in in /etc/logingroup has what it considers to be an invalid
ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think)
60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody'
GIDs.
</para>
<para>
If you encounter this problem, make sure that the programs that are failing
to initgroups() be run as users not in any groups with GIDs outside the
allowed range.
</para>
<para>This is documented in the HP manual pages under setgroups(2) and passwd(4).
</para>
<para>
On HPUX you must use gcc or the HP Ansi compiler. The free compiler
that comes with HP-UX is not Ansi compliant and cannot compile
Samba.
</para>
</sect1>
<sect1>
<title>SCO Unix</title>
<para>
If you run an old version of SCO Unix then you may need to get important
TCP/IP patches for Samba to work correctly. Without the patch, you may
encounter corrupt data transfers using samba.
</para>
<para>
The patch you need is UOD385 Connection Drivers SLS. It is available from
SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z).
</para>
</sect1>
<sect1>
<title>DNIX</title>
<para>
DNIX has a problem with seteuid() and setegid(). These routines are
needed for Samba to work correctly, but they were left out of the DNIX
C library for some reason.
</para>
<para>
For this reason Samba by default defines the macro NO_EID in the DNIX
section of includes.h. This works around the problem in a limited way,
but it is far from ideal, some things still won't work right.
</para>
<para>
To fix the problem properly you need to assemble the following two
functions and then either add them to your C library or link them into
Samba.
</para>
<para>
put this in the file <filename>setegid.s</filename>:
</para>
<para><programlisting>
.globl _setegid
_setegid:
moveq #47,d0
movl #100,a0
moveq #1,d1
movl 4(sp),a1
trap #9
bccs 1$
jmp cerror
1$:
clrl d0
rts
</programlisting></para>
<para>
put this in the file <filename>seteuid.s</filename>:
</para>
<para><programlisting>
.globl _seteuid
_seteuid:
moveq #47,d0
movl #100,a0
moveq #0,d1
movl 4(sp),a1
trap #9
bccs 1$
jmp cerror
1$:
clrl d0
rts
</programlisting></para>
<para>
after creating the above files you then assemble them using
</para>
<para><command>as seteuid.s</command></para>
<para><command>as setegid.s</command></para>
<para>
that should produce the files <filename>seteuid.o</filename> and
<filename>setegid.o</filename>
</para>
<para>
then you need to add these to the LIBSM line in the DNIX section of
the Samba Makefile. Your LIBSM line will then look something like this:
</para>
<para><programlisting>
LIBSM = setegid.o seteuid.o -ln
</programlisting></para>
<para>
You should then remove the line:
</para>
<para><programlisting>
#define NO_EID
</programlisting></para>
<para>from the DNIX section of <filename>includes.h</filename></para>
</sect1>
<sect1>
<title>RedHat Linux Rembrandt-II</title>
<para>
By default RedHat Rembrandt-II during installation adds an
entry to /etc/hosts as follows:
<programlisting>
127.0.0.1 loopback "hostname"."domainname"
</programlisting>
</para>
<para>
This causes Samba to loop back onto the loopback interface.
The result is that Samba fails to communicate correctly with
the world and therefor may fail to correctly negotiate who
is the master browse list holder and who is the master browser.
</para>
<para>
Corrective Action: Delete the entry after the word loopback
in the line starting 127.0.0.1
</para>
</sect1>
<sect1>
<title>AIX</title>
<sect2>
<title>Sequential Read Ahead</title>
<!-- From an email by William Jojo <jojowil@hvcc.edu> -->
<para>
Disabling Sequential Read Ahead using <userinput>vmtune -r 0</userinput> improves
samba performance significally.
</para>
</sect2>
</sect1>
<sect1>
<title>Solaris</title>
<sect2>
<title>Locking improvements</title>
<para>Some people have been experiencing problems with F_SETLKW64/fcntl
when running samba on solaris. The built in file locking mechanism was
not scalable. Performance would degrade to the point where processes would
get into loops of trying to lock a file. It woul try a lock, then fail,
then try again. The lock attempt was failing before the grant was
occurring. So the visible manifestation of this would be a handful of
processes stealing all of the CPU, and when they were trussed they would
be stuck if F_SETLKW64 loops.
</para>
<para>
Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7
has not been released yet.
</para>
<para>
The patch revision for 2.6 is 105181-34
for 8 is 108528-19
and for 9 is 112233-04
</para>
<para>
After the install of these patches it is recommended to reconfigure
and rebuild samba.
</para>
<para>Thanks to Joe Meslovich for reporting</para>
</sect2>
<sect2 id="winbind-solaris9">
<title>Winbind on Solaris 9</title>
<para>
Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior
is fixed by Sun in patch 113476-05 which as of March 2003 is not in any
roll-up packages.
</para>
</sect2>
</sect1>
</chapter>

276
docs/docbook/projdoc/Problems.sgml
View File

@ -1,276 +0,0 @@
<chapter id="problems">
<chapterinfo>
&author.jerry;
&author.jelmer;
<author>
<firstname>David</firstname><surname>Bannon</surname>
<affiliation>
<orgname>Samba Team</orgname>
<address><email>dbannon@samba.org</email></address>
</affiliation>
</author>
<pubdate>8 Apr 2003</pubdate>
</chapterinfo>
<title>Analysing and solving samba problems</title>
<para>
There are many sources of information available in the form
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.</para>
<sect1>
<title>Diagnostics tools</title>
<para>
One of the best diagnostic tools for debugging problems is Samba itself.
You can use the -d option for both smbd and nmbd to specify what
'debug level' at which to run. See the man pages on smbd, nmbd and
smb.conf for more information on debugging options. The debug
level can range from 1 (the default) to 10 (100 for debugging passwords).
</para>
<para>
Another helpful method of debugging is to compile samba using the
<command>gcc -g </command> flag. This will include debug
information in the binaries and allow you to attach gdb to the
running smbd / nmbd process. In order to attach gdb to an smbd
process for an NT workstation, first get the workstation to make the
connection. Pressing ctrl-alt-delete and going down to the domain box
is sufficient (at least, on the first time you join the domain) to
generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
maintains an open connection, and therefore there will be an smbd
process running (assuming that you haven't set a really short smbd
idle timeout) So, in between pressing ctrl alt delete, and actually
typing in your password, you can attach gdb and continue.
</para>
<para>
Some useful samba commands worth investigating:
</para>
<itemizedlist>
<listitem><para>testparam | more</para></listitem>
<listitem><para>smbclient -L //{netbios name of server}</para></listitem>
</itemizedlist>
<para>
An SMB enabled version of tcpdump is available from
<ulink url="http://www.tcpdump.org/">http://www.tcpdup.org/</ulink>.
Ethereal, another good packet sniffer for Unix and Win32
hosts, can be downloaded from <ulink
url="http://www.ethereal.com/">http://www.ethereal.com</ulink>.
</para>
<para>
For tracing things on the Microsoft Windows NT, Network Monitor
(aka. netmon) is available on the Microsoft Developer Network CD's,
the Windows NT Server install CD and the SMS CD's. The version of
netmon that ships with SMS allows for dumping packets between any two
computers (i.e. placing the network interface in promiscuous mode).
The version on the NT Server install CD will only allow monitoring
of network traffic directed to the local NT box and broadcasts on the
local subnet. Be aware that Ethereal can read and write netmon
formatted files.
</para>
</sect1>
<sect1>
<title>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</title>
<para>
Installing netmon on an NT workstation requires a couple
of steps. The following are for installing Netmon V4.00.349, which comes
with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
Workstation 4.0. The process should be similar for other versions of
Windows NT / Netmon. You will need both the Microsoft Windows
NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
</para>
<para>
Initially you will need to install 'Network Monitor Tools and Agent'
on the NT Server. To do this
</para>
<itemizedlist>
<listitem><para>Goto Start - Settings - Control Panel -
Network - Services - Add </para></listitem>
<listitem><para>Select the 'Network Monitor Tools and Agent' and
click on 'OK'.</para></listitem>
<listitem><para>Click 'OK' on the Network Control Panel.
</para></listitem>
<listitem><para>Insert the Windows NT Server 4.0 install CD
when prompted.</para></listitem>
</itemizedlist>
<para>
At this point the Netmon files should exist in
<filename>%SYSTEMROOT%\System32\netmon\*.*</filename>.
Two subdirectories exist as well, <filename>parsers\</filename>
which contains the necessary DLL's for parsing the netmon packet
dump, and <filename>captures\</filename>.
</para>
<para>
In order to install the Netmon tools on an NT Workstation, you will
first need to install the 'Network Monitor Agent' from the Workstation
install CD.
</para>
<itemizedlist>
<listitem><para>Goto Start - Settings - Control Panel -
Network - Services - Add</para></listitem>
<listitem><para>Select the 'Network Monitor Agent' and click
on 'OK'.</para></listitem>
<listitem><para>Click 'OK' on the Network Control Panel.
</para></listitem>
<listitem><para>Insert the Windows NT Workstation 4.0 install
CD when prompted.</para></listitem>
</itemizedlist>
<para>
Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
permissions as you deem appropriate for your site. You will need
administrative rights on the NT box to run netmon.
</para>
<para>
To install Netmon on a Windows 9x box install the network monitor agent
from the Windows 9x CD (\admin\nettools\netmon). There is a readme
file located with the netmon driver files on the CD if you need
information on how to do this. Copy the files from a working
Netmon installation.
</para>
</sect1>
<sect1>
<title>Useful URL's</title>
<itemizedlist>
<listitem><para>Home of Samba site <ulink url="http://samba.org">
http://samba.org</ulink>. We have a mirror near you !</para></listitem>
<listitem><para> The <emphasis>Development</emphasis> document
on the Samba mirrors might mention your problem. If so,
it might mean that the developers are working on it.</para></listitem>
<listitem><para>See how Scott Merrill simulates a BDC behavior at
<ulink url="http://www.skippy.net/linux/smb-howto.html">
http://www.skippy.net/linux/smb-howto.html</ulink>. </para></listitem>
<listitem><para>Although 2.0.7 has almost had its day as a PDC, David Bannon will
keep the 2.0.7 PDC pages at <ulink url="http://bioserve.latrobe.edu.au/samba">
http://bioserve.latrobe.edu.au/samba</ulink> going for a while yet.</para></listitem>
<listitem><para>Misc links to CIFS information
<ulink url="http://samba.org/cifs/">http://samba.org/cifs/</ulink></para></listitem>
<listitem><para>NT Domains for Unix <ulink url="http://mailhost.cb1.com/~lkcl/ntdom/">
http://mailhost.cb1.com/~lkcl/ntdom/</ulink></para></listitem>
<listitem><para>FTP site for older SMB specs:
<ulink url="ftp://ftp.microsoft.com/developr/drg/CIFS/">
ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></para></listitem>
</itemizedlist>
</sect1>
<sect1>
<title>Getting help from the mailing lists</title>
<para>
There are a number of Samba related mailing lists. Go to <ulink
url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror
and then click on <command>Support</command> and then click on <command>
Samba related mailing lists</command>.
</para>
<para>
For questions relating to Samba TNG go to
<ulink url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink>
It has been requested that you don't post questions about Samba-TNG to the
main stream Samba lists.</para>
<para>
If you post a message to one of the lists please observe the following guide lines :
</para>
<itemizedlist>
<listitem><para> Always remember that the developers are volunteers, they are
not paid and they never guarantee to produce a particular feature at
a particular time. Any time lines are 'best guess' and nothing more.
</para></listitem>
<listitem><para> Always mention what version of samba you are using and what
operating system its running under. You should probably list the
relevant sections of your &smb.conf; file, at least the options
in [global] that affect PDC support.</para></listitem>
<listitem><para>In addition to the version, if you obtained Samba via
CVS mention the date when you last checked it out.</para></listitem>
<listitem><para> 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).</para></listitem>
<listitem><para> 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.
</para></listitem>
<listitem><para> Don't cross post. Work out which is the best list to post to
and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
Many people active on the lists subscribe to more
than one list and get annoyed to see the same message two or more times.
Often someone will see a message and thinking it would be better dealt
with on another, will forward it on for you.</para></listitem>
<listitem><para>You might include <emphasis>partial</emphasis>
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.</para></listitem>
<listitem><para>(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.</para></listitem>
<listitem><para>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?</para></listitem>
</itemizedlist>
</sect1>
<sect1>
<title>How to get off the mailinglists</title>
<para>To have your name removed from a samba mailing list, go to the
same place you went to to get on it. Go to <ulink
url="http://lists.samba.org/">http://lists.samba.org</ulink>,
click on your nearest mirror and then click on <command>Support</command> and
then click on <command> Samba related mailing lists</command>. Or perhaps see
<ulink url="http://lists.samba.org/mailman/roster/samba-ntdom">here</ulink>
</para>
<para>
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...)
</para>
</sect1>
</chapter>

1126
docs/docbook/projdoc/ProfileMgmt.sgml
View File

File diff suppressed because it is too large Load Diff

351
docs/docbook/projdoc/SWAT.sgml
View File

@ -1,351 +0,0 @@
<chapter id="SWAT">
<chapterinfo>
&author.jht;
<pubdate>April 21, 2003</pubdate>
</chapterinfo>
<title>SWAT - The Samba Web Admininistration Tool</title>
<para>
There are many and varied opinions regarding the usefulness or otherwise of SWAT.
No matter how hard one tries to produce the perfect configuration tool it remains
an object of personal taste. SWAT is a tool that will allow web based configuration
of samba. It has a wizard that may help to get samba configured quickly, it has context
sensitive help on each smb.conf parameter, it provides for monitoring of current state
of connection information, and it allows network wide MS Windows network password
management.
</para>
<sect1>
<title>SWAT Features and Benefits</title>
<para>
There are network administrators who believe that it is a good idea to write systems
documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT
does not store the configuration file in any intermediate form, rather, it stores only the
parameter settings, so when SWAT writes the smb.conf file to disk it will write only
those parameters that are at other than the default settings. The result is that all comments
will be lost from the smb.conf file. Additionally, the parameters will be written back in
internal ordering.
</para>
<note><para>
So before using SWAT please be warned - SWAT will completely replace your smb.conf with
a fully optimised file that has been stripped of all comments you might have placed there
and only non-default settings will be written to the file.
</para></note>
<sect2>
<title>Enabling SWAT for use</title>
<para>
SWAT should be installed to run via the network super daemon. Depending on which system
your Unix/Linux system has you will have either an <filename>inetd</filename> or
<filename>xinetd</filename> based system.
</para>
<para>
The nature and location of the network super-daemon varies with the operating system
implementation. The control file (or files) can be located in the file
<filename>/etc/inetd.conf</filename> or in the directory <filename>/etc/[x]inet.d</filename>
or similar.
</para>
<para>
The control entry for the older style file might be:
</para>
<para><programlisting>
# swat is the Samba Web Administration Tool
swat stream tcp nowait.400 root /usr/sbin/swat swat
</programlisting></para>
<para>
A control file for the newer style xinetd could be:
</para>
<para>
<programlisting>
# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901 with your favorite web browser.
service swat
{
port = 901
socket_type = stream
wait = no
only_from = localhost
user = root
server = /usr/sbin/swat
log_on_failure += USERID
disable = yes
}
</programlisting>
</para>
<para>
Both the above examples assume that the <filename>swat</filename> binary has been
located in the <filename>/usr/sbin</filename> directory. In addition to the above
SWAT will use a directory access point from which it will load it's help files
as well as other control information. The default location for this on most Linux
systems is in the directory <filename>/usr/share/samba/swat</filename>. The default
location using samba defaults will be <filename>/usr/local/samba/swat</filename>.
</para>
<para>
Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user
the only permission allowed is to view certain aspects of configuration as well as
access to the password change facility. The buttons that will be exposed to the non-root
user are: <emphasis>HOME, STATUS, VIEW, PASSWORD</emphasis>. The only page that allows
change capability in this case is <emphasis>PASSWORD</emphasis>.
</para>
<para>
So long as you log onto SWAT as the user <command>root</command> you should obtain
full change and commit ability. The buttons that will be exposed includes:
<emphasis>HOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD</emphasis>.
</para>
</sect2>
<sect2>
<title>Securing SWAT through SSL</title>
<para>
Lots of people have asked about how to setup SWAT with SSL to allow for secure remote
administration of Samba. Here is a method that works, courtesy of Markus Krieger
</para>
<para>
Modifications to the swat setup are as following:
</para>
<itemizedlist>
<listitem><para>
install OpenSSL
</para></listitem>
<listitem><para>
generate certificate and private key
<programlisting>
root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
/usr/share/doc/packages/stunnel/stunnel.cnf \
-out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem
</programlisting></para></listitem>
<listitem><para>
remove swat-entry from [x]inetd
</para></listitem>
<listitem><para>
start stunnel
<programlisting>
root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \
-l /usr/local/samba/bin/swat swat
</programlisting></para></listitem>
</itemizedlist>
<para>
afterwards simply contact to swat by using the URL "https://myhost:901", accept the certificate
and the SSL connection is up.
</para>
</sect2>
<sect2>
<title>The SWAT Home Page</title>
<para>
The SWAT title page provides access to the latest Samba documentation. The manual page for
each samba component is accessible from this page as are the Samba-HOWTO-Collection (this
document) as well as the O'Reilly book "Using Samba".
</para>
<para>
Administrators who wish to validate their samba configuration may obtain useful information
from the man pages for the diganostic utilities. These are available from the SWAT home page
also. One diagnostic tool that is NOT mentioned on this page, but that is particularly
useful is <command>ethereal</command>, available from <ulink url="http://www.ethereal.com">
http://www.ethereal.com</ulink>.
</para>
<note><para>
SWAT can be configured to run in <emphasis>demo</emphasis> mode. This is NOT recommended
as it runs SWAT without authentication and with full administrative ability. ie: Allows
changes to smb.conf as well as general operation with root privilidges. The option that
creates this ability is the <command>-a</command> flag to swat. DO NOT USE THIS IN ANY
PRODUCTION ENVIRONMENT - you have been warned!
</para></note>
</sect2>
<sect2>
<title>Global Settings</title>
<para>
The Globals button will expose a page that allows configuration of the global parameters
in smb.conf. There are three levels of exposure of the parameters:
</para>
<itemizedlist>
<listitem><para>
<command>Basic</command> - exposes common configuration options.
</para></listitem>
<listitem><para>
<command>Advanced</command> - exposes configuration options needed in more
complex environments.
</para></listitem>
<listitem><para>
<command>Developer</command> - exposes configuration options that only the brave
will want to tamper with.
</para></listitem>
</itemizedlist>
<para>
To switch to other than <emphasis>Basic</emphasis> editing ability click on either the
<emphasis>Advanced</emphasis> or the <emphasis>Developer</emphasis> dial, then click the
<emphasis>Commit Changes</emphasis> button.
</para>
<para>
After making any changes to configuration parameters make sure that you click on the
<emphasis>Commit Changes</emphasis> button before moving to another area otherwise
your changes will be immediately lost.
</para>
<note><para>
SWAT has context sensitive help. To find out what each parameter is for simply click the
<command>Help</command> link to the left of the configurartion parameter.
</para></note>
</sect2>
<sect2>
<title>Share Settings</title>
<para>
To affect a currenly configured share, simply click on the pull down button between the
<emphasis>Choose Share</emphasis> and the <emphasis>Delete Share</emphasis> buttons,
select the share you wish to operate on, then to edit the settings click on the
<emphasis>Choose Share</emphasis> button, to delete the share simply press the
<emphasis>Delete Share</emphasis> button.
</para>
<para>
To create a new share, next to the button labelled <emphasis>Create Share</emphasis> enter
into the text field the name of the share to be created, then click on the
<emphasis>Create Share</emphasis> button.
</para>
</sect2>
<sect2>
<title>Printers Settings</title>
<para>
To affect a currenly configured printer, simply click on the pull down button between the
<emphasis>Choose Printer</emphasis> and the <emphasis>Delete Printer</emphasis> buttons,
select the printer you wish to operate on, then to edit the settings click on the
<emphasis>Choose Printer</emphasis> button, to delete the share simply press the
<emphasis>Delete Printer</emphasis> button.
</para>
<para>
To create a new printer, next to the button labelled <emphasis>Create Printer</emphasis> enter
into the text field the name of the share to be created, then click on the
<emphasis>Create Printer</emphasis> button.
</para>
</sect2>
<sect2>
<title>The SWAT Wizard</title>
<para>
The purpose if the SWAT Wizard is to help the Microsoft knowledgable network administrator
to configure Samba with a minimum of effort.
</para>
<para>
The Wizard page provides a tool for rewiting the smb.conf file in fully optimised format.
This will also happen if you press the commit button. The two differ in the the rewrite button
ignores any changes that may have been made, while the Commit button causes all changes to be
affected.
</para>
<para>
The <emphasis>Edit</emphasis> button permits the editing (setting) of the minimal set of
options that may be necessary to create a working samba server.
</para>
<para>
Finally, there are a limited set of options that will determine what type of server samba
will be configured for, whether it will be a WINS server, participate as a WINS client, or
operate with no WINS support. By clicking on one button you can elect to epose (or not) user
home directories.
</para>
</sect2>
<sect2>
<title>The Status Page</title>
<para>
The status page serves a limited purpose. Firstly, it allows control of the samba daemons.
The key daemons that create the samba server environment are: <command> smbd, nmbd, winbindd</command>.
</para>
<para>
The daemons may be controlled individually or as a total group. Additionally, you may set
an automatic screen refresh timing. As MS Windows clients interact with Samba new smbd processes
will be continually spawned. The auto-refresh facility will allow you to track the changing
conditions with minimal effort.
</para>
<para>
Lastly, the Status page may be used to terminate specific smbd client connections in order to
free files that may be locked.
</para>
</sect2>
<sect2>
<title>The View Page</title>
<para>
This page allows the administrator to view the optimised smb.conf file and if you are
particularly massochistic will permit you also to see all possible global configuration
parameters and their settings.
</para>
</sect2>
<sect2>
<title>The Password Change Page</title>
<para>
The Password Change page is a popular tool. This tool allows the creation, deletion, deactivation
and reactivation of MS Windows networking users on the local machine. Alternatively, you can use
this tool to change a local password for a user account.
</para>
<para>
When logged in as a non-root account the user will have to provide the old password as well as
the new password (twice). When logged in as <command>root</command> only the new password is
required.
</para>
<para>
One popular use for this tool is to change user passwords across a range of remote MS Windows
servers.
</para>
</sect2>
</sect1>
</chapter>

250
docs/docbook/projdoc/Samba-BDC-HOWTO.sgml
View File

@ -1,250 +0,0 @@
<chapter id="samba-bdc">
<chapterinfo>
&author.vl;
<pubdate> (26 Apr 2001) </pubdate>
</chapterinfo>
<title>
Samba Backup Domain Controller to Samba Domain Control
</title>
<sect1>
<title>Prerequisite Reading</title>
<para>
Before you continue reading in this chapter, please make sure
that you are comfortable with configuring a Samba PDC
as described in the <ulink url="Samba-PDC-HOWTO.html">Samba-PDC-HOWTO</ulink>.
</para>
</sect1>
<sect1>
<title>Background</title>
<para>
What is a Domain Controller? It is a machine that is able to answer
logon requests from workstations in a Windows NT Domain. Whenever a
user logs into a Windows NT Workstation, the workstation connects to a
Domain Controller and asks him whether the username and password the
user typed in is correct. The Domain Controller replies with a lot of
information about the user, for example the place where the users
profile is stored, the users full name of the user. All this
information is stored in the NT user database, the so-called SAM.
</para>
<para>
There are two kinds of Domain Controller in a NT 4 compatible Domain:
A Primary Domain Controller (PDC) and one or more Backup Domain
Controllers (BDC). The PDC contains the master copy of the
SAM. Whenever the SAM has to change, for example when a user changes
his password, this change has to be done on the PDC. A Backup Domain
Controller is a machine that maintains a read-only copy of the
SAM. This way it is able to reply to logon requests and authenticate
users in case the PDC is not available. During this time no changes to
the SAM are possible. Whenever changes to the SAM are done on the PDC,
all BDC receive the changes from the PDC.
</para>
<para>
Since version 2.2 Samba officially supports domain logons for all
current Windows Clients, including Windows 2000 and XP. This text
assumes the domain to be named SAMBA. To be able to act as a PDC, some
parameters in the [global]-section of the smb.conf have to be set:
</para>
<para><programlisting>
workgroup = SAMBA
domain master = yes
domain logons = yes
</programlisting></para>
<para>
Several other things like a [homes] and a [netlogon] share also may be
set along with settings for the profile path, the users home drive and
others. This will not be covered in this document.
</para>
</sect1>
<sect1>
<title>What qualifies a Domain Controller on the network?</title>
<para>
Every machine that is a Domain Controller for the domain SAMBA has to
register the NetBIOS group name SAMBA#1c with the WINS server and/or
by broadcast on the local network. The PDC also registers the unique
NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
normally reserved for the domain master browser, a role that has
nothing to do with anything related to authentication, but the
Microsoft Domain implementation requires the domain master browser to
be on the same machine as the PDC.
</para>
<sect2>
<title>How does a Workstation find its domain controller?</title>
<para>
A NT workstation in the domain SAMBA that wants a local user to be
authenticated has to find the domain controller for SAMBA. It does
this by doing a NetBIOS name query for the group name SAMBA#1c. It
assumes that each of the machines it gets back from the queries is a
domain controller and can answer logon requests. To not open security
holes both the workstation and the selected (TODO: How is the DC
chosen) domain controller authenticate each other. After that the
workstation sends the user's credentials (his name and password) to
the domain controller, asking for approval.
</para>
</sect2>
<sect2>
<title>When is the PDC needed?</title>
<para>
Whenever a user wants to change his password, this has to be done on
the PDC. To find the PDC, the workstation does a NetBIOS name query
for SAMBA#1b, assuming this machine maintains the master copy of the
SAM. The workstation contacts the PDC, both mutually authenticate and
the password change is done.
</para>
</sect2>
</sect1>
<sect1>
<title>Can Samba be a Backup Domain Controller to an NT PDC?</title>
<para>
With version 2.2, no. The native NT SAM replication protocols have
not yet been fully implemented. The Samba Team is working on
understanding and implementing the protocols, but this work has not
been finished for version 2.2.
</para>
<para>
With version 3.0, the work on both the replication protocols and a
suitable storage mechanism has progressed, and some form of NT4 BDC
support is expected soon.
</para>
<para>
Can I get the benefits of a BDC with Samba? Yes. The main reason for
implementing a BDC is availability. If the PDC is a Samba machine,
a second Samba machine can be set up to
service logon requests whenever the PDC is down.
</para>
</sect1>
<sect1>
<title>How do I set up a Samba BDC?</title>
<para>
Several things have to be done:
</para>
<itemizedlist>
<listitem><para>
The domain SID has to be the same on the PDC and the BDC. This used to
be stored in the file private/MACHINE.SID. This file is not created
anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
stored in the file private/secrets.tdb. Simply copying the secrets.tdb
from the PDC to the BDC does not work, as the BDC would
generate a new SID for itself and override the domain SID with this
new BDC SID.</para>
<para>
To retrieve the domain SID from the PDC or an existing BDC and store it in the
secrets.tdb, execute 'net rpc getsid' on the BDC.
</para></listitem>
<listitem><para>
The Unix user database has to be synchronized from the PDC to the
BDC. This means that both the /etc/passwd and /etc/group have to be
replicated from the PDC to the BDC. This can be done manually
whenever changes are made, or the PDC is set up as a NIS master
server and the BDC as a NIS slave server. To set up the BDC as a
mere NIS client would not be enough, as the BDC would not be able to
access its user database in case of a PDC failure.
</para>
</listitem>
<listitem><para>
The Samba password database in the file private/smbpasswd has to be
replicated from the PDC to the BDC. This is a bit tricky, see the
next section.
</para></listitem>
<listitem><para>
Any netlogon share has to be replicated from the PDC to the
BDC. This can be done manually whenever login scripts are changed,
or it can be done automatically together with the smbpasswd
synchronization.
</para></listitem>
</itemizedlist>
<para>
Finally, the BDC has to be found by the workstations. This can be done
by setting
</para>
<para><programlisting>
workgroup = samba
domain master = no
domain logons = yes
</programlisting></para>
<para>
in the [global]-section of the smb.conf of the BDC. This makes the BDC
only register the name SAMBA#1c with the WINS server. This is no
problem as the name SAMBA#1c is a NetBIOS group name that is meant to
be registered by more than one machine. The parameter 'domain master =
no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
name is reserved for the Primary Domain Controller.
</para>
<sect2>
<title>How do I replicate the smbpasswd file?</title>
<para>
Replication of the smbpasswd file is sensitive. It has to be done
whenever changes to the SAM are made. Every user's password change is
done in the smbpasswd file and has to be replicated to the BDC. So
replicating the smbpasswd file very often is necessary.
</para>
<para>
As the smbpasswd file contains plain text password equivalents, it
must not be sent unencrypted over the wire. The best way to set up
smbpasswd replication from the PDC to the BDC is to use the utility
rsync. rsync can use ssh as a transport. ssh itself can be set up to
accept *only* rsync transfer without requiring the user to type a
password.
</para>
</sect2>
<sect2>
<title>Can I do this all with LDAP?</title>
<para>The simple answer is YES. Samba's pdb_ldap code supports
binding to a replica LDAP server, and will also follow referrals and
rebind to the master if it ever needs to make a modification to the
database. (Normally BDCs are read only, so this will not occur
often).
</para>
</sect2>
</sect1>
</chapter>

842
docs/docbook/projdoc/Samba-PDC-HOWTO.sgml
View File

@ -1,842 +0,0 @@
<chapter id="samba-pdc">
<chapterinfo>
&author.jerry;
&author.jht;
<author>
<firstname>David</firstname><surname>Bannon</surname>
<affiliation>
<orgname>Samba Team</orgname>
<address><email>dbannon@samba.org</email></address>
</affiliation>
</author>
<pubdate> (26 Apr 2001) </pubdate>
</chapterinfo>
<title>
Samba as an NT4 or Win2k Primary Domain Controller
</title>
<sect1>
<title>Prerequisite Reading</title>
<para>
Before you continue reading in this chapter, please make sure
that you are comfortable with configuring basic files services
in smb.conf and how to enable and administer password
encryption in Samba. Theses two topics are covered in the
&smb.conf; manpage.
</para>
</sect1>
<sect1>
<title>
Background
</title>
<para>
This article outlines the steps necessary for configuring Samba as a PDC.
It is necessary to have a working Samba server prior to implementing the
PDC functionality.
</para>
<itemizedlist>
<listitem><para>
Domain logons for Windows NT 4.0 / 200x / XP Professional clients.
</para></listitem>
<listitem><para>
Placing Windows 9x / Me clients in user level security
</para></listitem>
<listitem><para>
Retrieving a list of users and groups from a Samba PDC to
Windows 9x / Me / NT / 200x / XP Professional clients
</para></listitem>
<listitem><para>
Roaming Profiles
</para></listitem>
<listitem><para>
Network/System Policies
</para></listitem>
</itemizedlist>
<note>
<para>
Roaming Profiles and System/Network policies are advanced network administration topics
that are covered separately in this document.
</para>
</note>
<para>
The following functionalities are new to the Samba 3.0 release:
</para>
<itemizedlist>
<listitem><para>
Windows NT 4 domain trusts
</para></listitem>
<listitem><para>
Adding users via the User Manager for Domains
</para></listitem>
</itemizedlist>
<para>
The following functionalities are NOT provided by Samba 3.0:
</para>
<itemizedlist>
<listitem><para>
SAM replication with Windows NT 4.0 Domain Controllers
(i.e. a Samba PDC and a Windows NT BDC or vice versa)
</para></listitem>
<listitem><para>
Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
Active Directory)
</para></listitem>
</itemizedlist>
<para>
Please note that Windows 9x / Me / XP Home clients are not true members of a domain
for reasons outlined in this article. Therefore the protocol for
support of Windows 9x-style domain logons is completely different
from NT4 / Win2k type domain logons and has been officially supported for some
time.
</para>
<para><emphasis>
MS Windows XP Home edition is NOT able to join a domain and does not permit
the use of domain logons.</emphasis>
</para>
<para>
Implementing a Samba PDC can basically be divided into 3 broad
steps.
</para>
<orderedlist numeration="arabic">
<listitem><para>
Configuring the Samba PDC
</para></listitem>
<listitem><para>
Creating machine trust accounts and joining clients to the domain
</para></listitem>
<listitem><para>
Adding and managing domain user accounts
</para></listitem>
</orderedlist>
<para>
There are other minor details such as user profiles, system
policies, etc... However, these are not necessarily specific
to a Samba PDC as much as they are related to Windows NT networking
concepts.
</para>
</sect1>
<sect1>
<title>Configuring the Samba Domain Controller</title>
<para>
The first step in creating a working Samba PDC is to
understand the parameters necessary in smb.conf. Here we
attempt to explain the parameters that are covered in
the &smb.conf; man page.
</para>
<para>
Here is an example &smb.conf; for acting as a PDC:
</para>
<para><programlisting>
[global]
; Basic server settings
<ulink url="smb.conf.5.html#NETBIOSNAME">netbios name</ulink> = <replaceable>POGO</replaceable>
<ulink url="smb.conf.5.html#WORKGROUP">workgroup</ulink> = <replaceable>NARNIA</replaceable>
; User and Machine Account Backends
; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ...
; mysqlsam, xmlsam, guest
<ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend</ulink> = ldapsam, guest
; we should act as the domain and local master browser
<ulink url="smb.conf.5.html#OSLEVEL">os level</ulink> = 64
<ulink url="smb.conf.5.html#PERFERREDMASTER">preferred master</ulink> = yes
<ulink url="smb.conf.5.html#DOMAINMASTER">domain master</ulink> = yes
<ulink url="smb.conf.5.html#LOCALMASTER">local master</ulink> = yes
; security settings (must user security = user)
<ulink url="smb.conf.5.html#SECURITYEQUALSUSER">security</ulink> = user
; encrypted passwords are a requirement for a PDC
<ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords</ulink> = yes
; support domain logons
<ulink url="smb.conf.5.html#DOMAINLOGONS">domain logons</ulink> = yes
; where to store user profiles?
<ulink url="smb.conf.5.html#LOGONPATH">logon path</ulink> = \\%N\profiles\%u
; where is a user's home directory and where should it be mounted at?
<ulink url="smb.conf.5.html#LOGONDRIVE">logon drive</ulink> = H:
<ulink url="smb.conf.5.html#LOGONHOME">logon home</ulink> = \\homeserver\%u
; specify a generic logon script for all users
; this is a relative **DOS** path to the [netlogon] share
<ulink url="smb.conf.5.html#LOGONSCRIPT">logon script</ulink> = logon.cmd
; necessary share for domain controller
[netlogon]
<ulink url="smb.conf.5.html#PATH">path</ulink> = /usr/local/samba/lib/netlogon
<ulink url="smb.conf.5.html#READONLY">read only</ulink> = yes
<ulink url="smb.conf.5.html#WRITELIST">write list</ulink> = <replaceable>ntadmin</replaceable>
; share for storing user profiles
[profiles]
<ulink url="smb.conf.5.html#PATH">path</ulink> = /export/smb/ntprofile
<ulink url="smb.conf.5.html#READONLY">read only</ulink> = no
<ulink url="smb.conf.5.html#CREATEMASK">create mask</ulink> = 0600
<ulink url="smb.conf.5.html#DIRECTORYMASK">directory mask</ulink> = 0700
</programlisting></para>
<note><para>
The above parameters make for a full set of parameters that may define the server's mode
of operation. The following parameters are the essentials alone:
<programlisting>
workgroup = NARNIA
domain logons = Yes
security = User
</programlisting>
The additional parameters shown in the longer listing above just makes for a
more complete environment.
</para></note>
<para>
There are a couple of points to emphasize in the above configuration.
</para>
<itemizedlist>
<listitem><para>
Encrypted passwords must be enabled. For more details on how
to do this, refer to <link linkend="passdb">the User Database chapter</link>.
</para></listitem>
<listitem><para>
The server must support domain logons and a
<filename>[netlogon]</filename> share
</para></listitem>
<listitem><para>
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.
</para></listitem>
</itemizedlist>
<para>
Samba 3.0 offers a complete implementation of group mapping
between Windows NT groups and Unix groups (this is really quite
complicated to explain in a short space).
</para>
</sect1>
<sect1>
<title>Creating Machine Trust Accounts and Joining Clients to the Domain</title>
<para>
A machine trust account is a Samba account that is used to
authenticate a client machine (rather than a user) to the Samba
server. In Windows terminology, this is known as a "Computer
Account."</para>
<para>
The password of a machine trust account acts as the shared secret for
secure communication with the Domain Controller. This is a security
feature to prevent an unauthorized machine with the same NetBIOS name
from joining the domain and gaining access to domain user/group
accounts. Windows NT, 200x, XP Professional clients use machine trust
accounts, but Windows 9x / Me / XP Home clients do not. Hence, a
Windows 9x / Me / XP Home client is never a true member of a domain
because it does not possess a machine trust account, and thus has no
shared secret with the domain controller.
</para>
<para>A Windows PDC stores each machine trust account in the Windows
Registry. A Samba-3 PDC also has to store machine trust account information
in a suitable backend data store. With Samba-3 there can be multiple back-ends
for this including:
</para>
<itemizedlist>
<listitem><para>
<emphasis>smbpasswd</emphasis> - the plain ascii file stored used by
earlier versions of Samba. This file configuration option requires
a Unix/Linux system account for EVERY entry (ie: both for user and for
machine accounts). This file will be located in the <emphasis>private</emphasis>
directory (default is /usr/local/samba/lib/private or on linux /etc/samba).
</para></listitem>
<listitem><para>
<emphasis>smbpasswd_nua</emphasis> - This file is independant of the
system wide user accounts. The use of this back-end option requires
specification of the "non unix account range" option also. It is called
smbpasswd and will be located in the <filename>private</filename> directory.
</para></listitem>
<listitem><para>
<emphasis>tdbsam</emphasis> - a binary database backend that will be
stored in the <emphasis>private</emphasis> directory in a file called
<emphasis>passwd.tdb</emphasis>. The key benefit of this binary format
file is that it can store binary objects that can not be accomodated
in the traditional plain text smbpasswd file.
</para></listitem>
<listitem><para>
<emphasis>tdbsam_nua</emphasis> like the smbpasswd_nua option above, this
file allows the creation of arbitrary user and machine accounts without
requiring that account to be added to the system (/etc/passwd) file. It
too requires the specification of the "non unix account range" option
in the [globals] section of the &smb.conf; file.
</para></listitem>
<listitem><para>
<emphasis>ldapsam</emphasis> - An LDAP based back-end. Permits the
LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com
</para></listitem>
<listitem><para>
<emphasis>ldapsam_nua</emphasis> - LDAP based back-end with no unix
account requirement, like smbpasswd_nua and tdbsam_nua above.
</para></listitem>
</itemizedlist>
<para>Read the chapter about the <link linkend="passdb">User Database</link>
for details.</para>
<note><para>
The new tdbsam and ldapsam account backends store vastly more information than
smbpasswd is capable of. The new backend database includes capacity to specify
per user settings for many parameters, over-riding global settings given in the
<filename>smb.conf</filename> file. eg: logon drive, logon home, logon path, etc.
</para></note>
<para>
A Samba PDC, however, stores each machine trust account in two parts,
as follows:
<itemizedlist>
<listitem><para>A Samba account, stored in the same location as user
LanMan and NT password hashes (currently
<filename>smbpasswd</filename>). The Samba account
possesses and uses only the NT password hash.</para></listitem>
<listitem><para>A corresponding Unix account, typically stored in
<filename>/etc/passwd</filename>. (Future releases will alleviate the need to
create <filename>/etc/passwd</filename> entries.) </para></listitem>
</itemizedlist>
</para>
<para>
There are two ways to create machine trust accounts:
</para>
<itemizedlist>
<listitem><para> Manual creation. Both the Samba and corresponding
Unix account are created by hand.</para></listitem>
<listitem><para> "On-the-fly" creation. The Samba machine trust
account is automatically created by Samba at the time the client
is joined to the domain. (For security, this is the
recommended method.) The corresponding Unix account may be
created automatically or manually. </para>
</listitem>
</itemizedlist>
<sect2>
<title>Manual Creation of Machine Trust Accounts</title>
<para>
The first step in manually creating a machine trust account is to
manually create the corresponding Unix account in
<filename>/etc/passwd</filename>. This can be done using
<command>vipw</command> or other 'add user' command that is normally
used to create new Unix accounts. The following is an example for a
Linux based Samba server:
</para>
<para>
<prompt>root# </prompt><command>/usr/sbin/useradd -g 100 -d /dev/null -c <replaceable>"machine
nickname"</replaceable> -s /bin/false <replaceable>machine_name</replaceable>$ </command>
</para>
<para>
<prompt>root# </prompt><command>passwd -l <replaceable>machine_name</replaceable>$</command>
</para>
<para>On *BSD systems, this can be done using the 'chpass' utility:</para>
<para>
<prompt>root# </prompt><command>chpass -a "<replaceable>machine_name</replaceable>$:*:101:100::0:0:Workstation <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin"</command>
</para>
<para>
The <filename>/etc/passwd</filename> entry will list the machine name
with a "$" appended, won't have a password, will have a null shell and no
home directory. For example a machine named 'doppy' would have an
<filename>/etc/passwd</filename> entry like this:
</para>
<para><programlisting>
doppy$:x:505:501:<replaceable>machine_nickname</replaceable>:/dev/null:/bin/false
</programlisting></para>
<para>
Above, <replaceable>machine_nickname</replaceable> can be any
descriptive name for the client, i.e., BasementComputer.
<replaceable>machine_name</replaceable> absolutely must be the NetBIOS
name of the client to be joined to the domain. The "$" must be
appended to the NetBIOS name of the client or Samba will not recognize
this as a machine trust account.
</para>
<para>
Now that the corresponding Unix account has been created, the next step is to create
the Samba account for the client containing the well-known initial
machine trust account password. This can be done using the <ulink
url="smbpasswd.8.html"><command>smbpasswd(8)</command></ulink> command
as shown here:
</para>
<para>
<prompt>root# </prompt><userinput>smbpasswd -a -m <replaceable>machine_name</replaceable></userinput>
</para>
<para>
where <replaceable>machine_name</replaceable> is the machine's NetBIOS
name. The RID of the new machine account is generated from the UID of
the corresponding Unix account.
</para>
<warning>
<title>Join the client to the domain immediately</title>
<para>
Manually creating a machine trust account using this method is the
equivalent of creating a machine trust account on a Windows NT PDC using
the "Server Manager". From the time at which the account is created
to the time which the client joins the domain and changes the password,
your domain is vulnerable to an intruder joining your domain using
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!
</para>
</warning>
</sect2>
<sect2>
<title>"On-the-Fly" Creation of Machine Trust Accounts</title>
<para>
The second (and recommended) way of creating machine trust accounts is
simply to allow the Samba server to create them as needed when the client
is joined to the domain. </para>
<para>Since each Samba machine trust account requires a corresponding
Unix account, a method for automatically creating the
Unix account is usually supplied; this requires configuration of the
<ulink url="smb.conf.5.html#ADDUSERSCRIPT">add user script</ulink>
option in <filename>smb.conf</filename>. This
method is not required, however; corresponding Unix accounts may also
be created manually.
</para>
<para>Below is an example for a RedHat 6.2 Linux system.
</para>
<para><programlisting>
[global]
# &lt;...remainder of parameters...&gt;
add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
</programlisting></para>
</sect2>
<sect2><title>Joining the Client to the Domain</title>
<para>
The procedure for joining a client to the domain varies with the
version of Windows.
</para>
<itemizedlist>
<listitem><para><emphasis>Windows 2000</emphasis></para>
<para>
When the user elects to join the client to a domain, Windows prompts for
an account and password that is privileged to join the domain. A Samba administrative
account (i.e., a Samba account that has root privileges on the Samba server) must be
entered here; the operation will fail if an ordinary user account is given.
The password for this account should be set to a different password than the associated
<filename>/etc/passwd</filename> entry, for security reasons.
</para>
<para>
The session key of the Samba administrative account acts as an
encryption key for setting the password of the machine trust
account. The machine trust account will be created on-the-fly, or
updated if it already exists.
</para>
</listitem>
<listitem><para><emphasis>Windows NT</emphasis></para>
<para> If the machine trust account was created manually, on the
Identification Changes menu enter the domain name, but do not
check the box "Create a Computer Account in the Domain." In this case,
the existing machine trust account is used to join the machine to
the domain.</para>
<para> If the machine trust account is to be created
on-the-fly, on the Identification Changes menu enter the domain
name, and check the box "Create a Computer Account in the Domain." In
this case, joining the domain proceeds as above for Windows 2000
(i.e., you must supply a Samba administrative account when
prompted).</para>
</listitem>
<listitem><para><emphasis>Samba</emphasis></para>
<para>Joining a samba client to a domain is documented in
the <link linkend="domain-member">Domain Member</link> chapter.
</para></listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1>
<title>Common Problems and Errors</title>
<sect2>
<title>I cannot include a '$' in a machine name</title>
<para>
A 'machine name' in (typically) <filename>/etc/passwd</filename>
of the machine name with a '$' appended. FreeBSD (and other BSD
systems?) won't create a user with a '$' in their name.
</para>
<para>
The problem is only in the program used to make the entry. Once made, it works perfectly.
Create a user without the '$' using <command>vipw</command> to edit the entry, adding
the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID!
</para>
</sect2>
<sect2>
<title>I get told "You already have a connection to the Domain...."
or "Cannot join domain, the credentials supplied conflict with an
existing set.." when creating a machine trust account.</title>
<para>
This happens if you try to create a machine trust 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:
</para>
<para>
<prompt>C:\WINNT\></prompt> <command>net use * /d</command>
</para>
<para>
Further, if the machine is 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.
</para>
</sect2>
<sect2>
<title>The system can not log you on (C000019B)....</title>
<para>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 again or consult your
system administrator" when attempting to logon.
</para>
<para>
This occurs when the domain SID stored in the secrets.tdb database
is changed. The most common cause of a change in domain SID is when
the domain name and/or the server name (netbios name) is changed.
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 domain
SID may be reset using either the net or rpcclient utilities.
</para>
<para>
The reset or change the domain SID you can use the net command as follows:
<programlisting>
net getlocalsid 'OLDNAME'
net setlocalsid 'SID'
</programlisting>
</para>
</sect2>
<sect2>
<title>The machine trust account for this computer either does not
exist or is not accessible.</title>
<para>
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". What's
wrong?
</para>
<para>
This problem is caused by the PDC not having a suitable machine trust account.
If you are using the <parameter>add user script</parameter> method to create
accounts then this would indicate that it has not worked. Ensure the domain
admin user system is working.
</para>
<para>
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 trust 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 ( i.e. 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.
</para>
</sect2>
<sect2>
<title>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
I get a message about my account being disabled.</title>
<para>
At first be ensure to enable the useraccounts with <command>smbpasswd -e
%user%</command>, this is normally done, when you create an account.
</para>
</sect2>
</sect1>
<sect1>
<title>Domain Control for Windows 9x/ME</title>
<para>
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. Samba-3 does this
now in the same way that MS Windows NT/2K.
</para>
<para>
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 this documentation under the browsing discussions.
It should be noted, that browsing is totally orthogonal to logon support.
</para>
<para>
Issues related to the single-logon network model are discussed in this
section. Samba supports domain logons, network logon scripts, and user
profiles for MS Windows for workgroups and MS Windows 9X/ME clients
which are the focus of this section.
</para>
<para>
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, i.e. 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.
</para>
<para>
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.
</para>
<para>
Before launching into the configuration instructions, it is
worthwhile to look at how a Windows 9x/ME client performs a logon:
</para>
<orderedlist>
<listitem>
<para>
The client broadcasts (to the IP broadcast address of the subnet it is in)
a NetLogon request. This is sent to the NetBIOS name DOMAIN&lt;1c&gt; 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.
</para>
</listitem>
<listitem>
<para>
The client then connects to that server, logs on (does an SMBsessetupX) and
then connects to the IPC$ share (using an SMBtconX).
</para>
</listitem>
<listitem>
<para>
The client then does a NetWkstaUserLogon request, which retrieves the name
of the user's logon script.
</para>
</listitem>
<listitem>
<para>
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.
</para>
</listitem>
<listitem>
<para>
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 then
the user's home share, profiles for Win9X clients MUST reside in the user
home directory.
</para>
</listitem>
<listitem>
<para>
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 user's home share as
a sharename and path. For example, \\server\fred\.profile.
If the profiles are found, they are implemented.
</para>
</listitem>
<listitem>
<para>
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.
</para>
</listitem>
</orderedlist>
<sect2>
<title>Configuration Instructions: Network Logons</title>
<para>
The main difference between a PDC and a Windows 9x logon
server configuration is that
</para>
<itemizedlist>
<listitem><para>
Password encryption is not required for a Windows 9x logon server.
</para></listitem>
<listitem><para>
Windows 9x/ME clients do not possess machine trust accounts.
</para></listitem>
</itemizedlist>
<para>
Therefore, a Samba PDC will also act as a Windows 9x logon
server.
</para>
<warning>
<title>security mode and master browsers</title>
<para>
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 <constant>USER</constant>. The only security mode
which will not work due to technical reasons is <constant>SHARE</constant>
mode security. <constant>DOMAIN</constant> and <constant>SERVER</constant>
mode security is really just a variation on SMB user level security.
</para>
<para>
Actually, this issue is also closely 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 do
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.
</para>
<para>
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 the 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?)
</para>
<para>
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.
</para>
</warning>
</sect2>
</sect1>
</chapter>

143
docs/docbook/projdoc/ServerType.sgml
View File

@ -1,143 +0,0 @@
<chapter id="ServerType">
<chapterinfo>
&author.jht;
</chapterinfo>
<title>Nomenclature of Server Types</title>
<para>Adminstrators of Microsoft networks often refer to there being three
different type of servers:</para>
<itemizedlist>
<listitem><para>Stand Alone Server</para></listitem>
<listitem><para>Domain Member Server</para></listitem>
<listitem><para>Domain Controller</para>
<itemizedlist>
<listitem><para>Primary Domain Controller</para></listitem>
<listitem><para>Backup Domain Controller</para></listitem>
<listitem><para>ADS Domain Controller</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>A network administrator who is familiar with these terms and who
wishes to migrate to or use Samba will want to know what these terms mean
within a Samba context.</para>
<sect1>
<title>Stand Alone Server</title>
<para>
The term <emphasis>stand alone server</emphasis> means that the server
will provide local authentication and access control for all resources
that are available from it. In general this means that there will be a
local user database. In more technical terms, it means that resources
on the machine will either be made available in either SHARE mode or in
USER mode. SHARE mode and USER mode security are documented under
discussions regarding "security mode". The smb.conf configuration parameters
that control security mode are: "security = user" and "security = share".
</para>
<para>
No special action is needed other than to create user accounts. Stand-alone
servers do NOT provide network logon services, meaning that machines that
use this server do NOT perform a domain logon but instead make use only of
the MS Windows logon which is local to the MS Windows workstation/server.
</para>
<para>
Samba tends to blur the distinction a little in respect of what is
a stand alone server. This is because the authentication database may be
local or on a remote server, even if from the samba protocol perspective
the samba server is NOT a member of a domain security context.
</para>
<para>
Through the use of PAM (Pluggable Authentication Modules) and nsswitch
(the name service switcher) the source of authentication may reside on
another server. We would be inclined to call this the authentication server.
This means that the samba server may use the local Unix/Linux system
password database (/etc/passwd or /etc/shadow), may use a local smbpasswd
file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or
may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB
server for authentication.
</para>
</sect1>
<sect1>
<title>Domain Member Server</title>
<para>
This mode of server operation involves the samba machine being made a member
of a domain security context. This means by definition that all user authentication
will be done from a centrally defined authentication regime. The authentication
regime may come from an NT3/4 style (old domain technology) server, or it may be
provided from an Active Directory server (ADS) running on MS Windows 2000 or later.
</para>
<para><emphasis>
Of course it should be clear that the authentication back end itself could be from any
distributed directory architecture server that is supported by Samba. This can be
LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.
</emphasis></para>
<para>
Please refer to the section on Howto configure Samba as a Primary Domain Controller
and for more information regarding how to create a domain machine account for a
domain member server as well as for information regarding how to enable the samba
domain member machine to join the domain and to be fully trusted by it.
</para>
</sect1>
<sect1>
<title>Domain Controller</title>
<para>
Over the years public perceptions of what Domain Control really is has taken on an
almost mystical nature. Before we branch into a brief overview of what Domain Control
is the following types of controller are known:
</para>
<sect2>
<title>Domain Controller Types</title>
<simplelist>
<member>Primary Domain Controller</member>
<member>Backup Domain Controller</member>
<member>ADS Domain Controller</member>
</simplelist>
<para>
The <emphasis>Primary Domain Controller</emphasis> or PDC plays an important role in the MS
Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many
expect. The PDC seeds the Domain Control database (a part of the Windows registry) and
it plays a key part in synchronisation of the domain authentication database.
</para>
<para>
New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as
the NT4 style SAM (Security Account Manager) database (one of the registry files).
The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and
valid options include <emphasis> smbpasswd tdbsam ldapsam nisplussam plugin unixsam</emphasis>.
The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix
Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux
system accounts, provided a uid range is defined from which SAM accounts can be created.
</para>
<para>
The <emphasis>Backup Domain Controller</emphasis> or BDC plays a key role in servicing network
authentication requests. The BDC is biased to answer logon requests so that on a network segment
that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will
answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to
a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is
automatically demoted to a BDC.
</para>
<para>
At this time Samba is NOT capable of acting as an <emphasis>ADS Domain Controller</emphasis>.
</para>
</sect2>
</sect1>
</chapter>

211
docs/docbook/projdoc/Speed.sgml
View File

@ -1,211 +0,0 @@
<chapter id="speed">
<chapterinfo>
<author>
<firstname>Paul</firstname><surname>Cochrane</surname>
<affiliation>
<orgname>Dundee Limb Fitting Centre</orgname>
<address><email>paulc@dth.scot.nhs.uk</email></address>
</affiliation>
</author>
&author.jelmer;
</chapterinfo>
<title>Samba performance issues</title>
<sect1>
<title>Comparisons</title>
<para>
The Samba server uses TCP to talk to the client. Thus if you are
trying to see if it performs well you should really compare it to
programs that use the same protocol. The most readily available
programs for file transfer that use TCP are ftp or another TCP based
SMB server.
</para>
<para>
If you want to test against something like a NT or WfWg server then
you will have to disable all but TCP on either the client or
server. Otherwise you may well be using a totally different protocol
(such as Netbeui) and comparisons may not be valid.
</para>
<para>
Generally you should find that Samba performs similarly to ftp at raw
transfer speed. It should perform quite a bit faster than NFS,
although this very much depends on your system.
</para>
<para>
Several people have done comparisons between Samba and Novell, NFS or
WinNT. In some cases Samba performed the best, in others the worst. I
suspect the biggest factor is not Samba vs some other system but the
hardware and drivers used on the various systems. Given similar
hardware Samba should certainly be competitive in speed with other
systems.
</para>
</sect1>
<sect1>
<title>Socket options</title>
<para>
There are a number of socket options that can greatly affect the
performance of a TCP based server like Samba.
</para>
<para>
The socket options that Samba uses are settable both on the command
line with the -O option, or in the smb.conf file.
</para>
<para>
The <command>socket options</command> section of the &smb.conf; manual page describes how
to set these and gives recommendations.
</para>
<para>
Getting the socket options right can make a big difference to your
performance, but getting them wrong can degrade it by just as
much. The correct settings are very dependent on your local network.
</para>
<para>
The socket option TCP_NODELAY is the one that seems to make the
biggest single difference for most networks. Many people report that
adding <command>socket options = TCP_NODELAY</command> doubles the read
performance of a Samba drive. The best explanation I have seen for this is
that the Microsoft TCP/IP stack is slow in sending tcp ACKs.
</para>
</sect1>
<sect1>
<title>Read size</title>
<para>
The option <command>read size</command> affects the overlap of disk
reads/writes with network reads/writes. If the amount of data being
transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and
SMBreadbraw) is larger than this value then the server begins writing
the data before it has received the whole packet from the network, or
in the case of SMBreadbraw, it begins writing to the network before
all the data has been read from disk.
</para>
<para>
This overlapping works best when the speeds of disk and network access
are similar, having very little effect when the speed of one is much
greater than the other.
</para>
<para>
The default value is 16384, but very little experimentation has been
done yet to determine the optimal value, and it is likely that the best
value will vary greatly between systems anyway. A value over 65536 is
pointless and will cause you to allocate memory unnecessarily.
</para>
</sect1>
<sect1>
<title>Max xmit</title>
<para>
At startup the client and server negotiate a <command>maximum transmit</command> size,
which limits the size of nearly all SMB commands. You can set the
maximum size that Samba will negotiate using the <command>max xmit = </command> option
in &smb.conf;. Note that this is the maximum size of SMB requests that
Samba will accept, but not the maximum size that the *client* will accept.
The client maximum receive size is sent to Samba by the client and Samba
honours this limit.
</para>
<para>
It defaults to 65536 bytes (the maximum), but it is possible that some
clients may perform better with a smaller transmit unit. Trying values
of less than 2048 is likely to cause severe problems.
</para>
<para>
In most cases the default is the best option.
</para>
</sect1>
<sect1>
<title>Log level</title>
<para>
If you set the log level (also known as <command>debug level</command>) higher than 2
then you may suffer a large drop in performance. This is because the
server flushes the log file after each operation, which can be very
expensive.
</para>
</sect1>
<sect1>
<title>Read raw</title>
<para>
The <command>read raw</command> operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
however. and Samba makes support for <command>read raw</command> optional, with it
being enabled by default.
</para>
<para>
In some cases clients don't handle <command>read raw</command> very well and actually
get lower performance using it than they get using the conventional
read operations.
</para>
<para>
So you might like to try <command>read raw = no</command> and see what happens on your
network. It might lower, raise or not affect your performance. Only
testing can really tell.
</para>
</sect1>
<sect1>
<title>Write raw</title>
<para>
The <command>write raw</command> operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
however. and Samba makes support for <command>write raw</command> optional, with it
being enabled by default.
</para>
<para>
Some machines may find <command>write raw</command> slower than normal write, in which
case you may wish to change this option.
</para>
</sect1>
<sect1>
<title>Slow Logins</title>
<para>
Slow logins are almost always due to the password checking time. Using
the lowest practical <command>password level</command> will improve things.
</para>
</sect1>
<sect1>
<title>Client tuning</title>
<para>
Often a speed problem can be traced to the client. The client (for
example Windows for Workgroups) can often be tuned for better TCP
performance. Check the sections on the various clients in
<link linkend="Other-Clients">Samba and Other Clients</link>.
</para>
</sect1>
</chapter>

176
docs/docbook/projdoc/UNIX_INSTALL.sgml
View File

@ -1,176 +0,0 @@
<chapter id="install">
<chapterinfo>
&author.tridge;
&author.jelmer;
<author><firstname>Karl</firstname><surname>Auer</surname></author>
<!-- Isn't some of this written by others as well? -->
</chapterinfo>
<title>How to Install and Test SAMBA</title>
<sect1>
<title>Obtaining and installing samba</title>
<para>Binary packages of samba are included in almost any Linux or
Unix distribution. There are also some packages available at
<ulink url="http://samba.org/">the samba homepage</ulink>.
</para>
<para>If you need to compile samba from source, check the
<link linkend="compiling">appropriate appendix chapter</link>.</para>
</sect1>
<sect1>
<title>Configuring samba</title>
<para>Samba's configuration is stored in the smb.conf file,
that usually resides in <filename>/etc/samba/smb.conf</filename>
or <filename>/usr/local/samba/lib/smb.conf</filename>. You can either
edit this file yourself or do it using one of the many graphical
tools that are available, such as the web-based interface swat, that
is included with samba.</para>
<sect2>
<title>Editing the <filename>smb.conf</filename> file</title>
<para>There are sample configuration files in the examples
subdirectory in the distribution. I suggest you read them
carefully so you can see how the options go together in
practice. See the man page for all the options.</para>
<para>The simplest useful configuration file would be
something like this:</para>
<para><programlisting>
[global]
workgroup = MYGROUP
[homes]
guest ok = no
read only = no
</programlisting></para>
<para>which would allow connections by anyone with an
account on the server, using either their login name or
"<command>homes</command>" as the service name. (Note that I also set the
workgroup that Samba is part of. See BROWSING.txt for details)</para>
<para>Make sure you put the <filename>smb.conf</filename> file in the same place
you specified in the<filename>Makefile</filename> (the default is to
look for it in <filename>/usr/local/samba/lib/</filename>).</para>
<para>For more information about security settings for the
<command>[homes]</command> share please refer to the chapter
<link linkend="securing-samba">Securing Samba</link>.</para>
<sect3>
<title>Test your config file with
<command>testparm</command></title>
<para>It's important that you test the validity of your
<filename>smb.conf</filename> file using the <application>testparm</application> program.
If testparm runs OK then it will list the loaded services. If
not it will give an error message.</para>
<para>Make sure it runs OK and that the services look
reasonable before proceeding. </para>
<para>Always run testparm again when you change
<filename>smb.conf</filename>!</para>
</sect3>
</sect2>
<sect2>
<title>SWAT</title>
<para>
SWAT is a web-based interface that helps you configure samba.
SWAT might not be available in the samba package on your platform,
but in a separate package. Please read the swat manpage
on compiling, installing and configuring swat from source.
</para>
<para>To launch SWAT just run your favorite web browser and
point it at "http://localhost:901/". Replace <replaceable>localhost</replaceable> with the name of the computer you are running samba on if you
are running samba on a different computer than your browser.</para>
<para>Note that you can attach to SWAT from any IP connected
machine but connecting from a remote machine leaves your
connection open to password sniffing as passwords will be sent
in the clear over the wire. </para>
</sect2>
</sect1>
<sect1>
<title>Try listing the shares available on your
server</title>
<para><prompt>$ </prompt><userinput>smbclient -L
<replaceable>yourhostname</replaceable></userinput></para>
<para>You should get back a list of shares available on
your server. If you don't then something is incorrectly setup.
Note that this method can also be used to see what shares
are available on other LanManager clients (such as WfWg).</para>
<para>If you choose user level security then you may find
that Samba requests a password before it will list the shares.
See the <command>smbclient</command> man page for details. (you
can force it to list the shares without a password by
adding the option -U% to the command line. This will not work
with non-Samba servers)</para>
</sect1>
<sect1>
<title>Try connecting with the unix client</title>
<para><prompt>$ </prompt><userinput>smbclient <replaceable>
//yourhostname/aservice</replaceable></userinput></para>
<para>Typically the <replaceable>yourhostname</replaceable>
would be the name of the host where you installed &smbd;.
The <replaceable>aservice</replaceable> is
any service you have defined in the &smb.conf;
file. Try your user name if you just have a <command>[homes]</command>
section
in &smb.conf;.</para>
<para>For example if your unix host is <replaceable>bambi</replaceable>
and your login name is <replaceable>fred</replaceable> you would type:</para>
<para><prompt>$ </prompt><userinput>smbclient //<replaceable>bambi</replaceable>/<replaceable>fred</replaceable>
</userinput></para>
</sect1>
<sect1>
<title>Try connecting from a DOS, WfWg, Win9x, WinNT,
Win2k, OS/2, etc... client</title>
<para>Try mounting disks. eg:</para>
<para><prompt>C:\WINDOWS\> </prompt><userinput>net use d: \\servername\service
</userinput></para>
<para>Try printing. eg:</para>
<para><prompt>C:\WINDOWS\> </prompt><userinput>net use lpt1:
\\servername\spoolservice</userinput></para>
<para><prompt>C:\WINDOWS\> </prompt><userinput>print filename
</userinput></para>
</sect1>
<sect1>
<title>What If Things Don't Work?</title>
<para>Then you might read the file chapter
<link linkend="diagnosis">Diagnosis</link> and the
FAQ. If you are still stuck then try to follow
the <link linkend="problems">Analysing and Solving Problems chapter</link>
Samba has been successfully installed at thousands of sites worldwide,
so maybe someone else has hit your problem and has overcome it. </para>
</sect1>
</chapter>

230
docs/docbook/projdoc/VFS.sgml
View File

@ -1,230 +0,0 @@
<chapter id="VFS">
<chapterinfo>
&author.jelmer;
&author.jht;
<author><firstname>Alexander</firstname><surname>Bokovoy</surname></author>
<author><firstname>Tim</firstname><surname>Potter</surname></author>
<author><firstname>Simo</firstname><surname>Sorce</surname></author>
</chapterinfo>
<title>Stackable VFS modules</title>
<sect1>
<title>Introduction and configuration</title>
<para>
Since samba 3.0, samba supports stackable VFS(Virtual File System) modules.
Samba passes each request to access the unix file system thru the loaded VFS modules.
This chapter covers all the modules that come with the samba source and references to
some external modules.
</para>
<para>
You may have problems to compile these modules, as shared libraries are
compiled and linked in different ways on different systems.
They currently have been tested against GNU/linux and IRIX.
</para>
<para>
To use the VFS modules, create a share similar to the one below. The
important parameter is the <command>vfs object</command> parameter which must point to
the exact pathname of the shared library objects. For example, to log all access
to files and use a recycle bin:
<programlisting>
[audit]
comment = Audited /data directory
path = /data
vfs object = /path/to/audit.so /path/to/recycle.so
writeable = yes
browseable = yes
</programlisting>
</para>
<para>
The modules are used in the order they are specified.
</para>
<para>
Further documentation on writing VFS modules for Samba can be found in
the Samba Developers Guide.
</para>
</sect1>
<sect1>
<title>Included modules</title>
<sect2>
<title>audit</title>
<para>A simple module to audit file access to the syslog
facility. The following operations are logged:
<simplelist>
<member>share</member>
<member>connect/disconnect</member>
<member>directory opens/create/remove</member>
<member>file open/close/rename/unlink/chmod</member>
</simplelist>
</para>
</sect2>
<sect2>
<title>extd_audit</title>
<para>
This module is identical with the <emphasis>audit</emphasis> module above except
that it sends audit logs to both syslog as well as the smbd log file/s. The
loglevel for this module is set in the smb.conf file.
</para>
<para>
The logging information that will be written to the smbd log file is controlled by
the <emphasis>log level</emphasis> parameter in <filename>smb.conf</filename>. The
following information will be recorded:
</para>
<table frame="all"><title>Extended Auditing Log Information</title>
<tgroup cols="2" align="center">
<thead>
<row><entry align="center">Log Level</entry><entry>Log Details - File and Directory Operations</entry></row>
</thead>
<tbody>
<row><entry align="center">0</entry><entry align="left">Creation / Deletion</entry></row>
<row><entry align="center">1</entry><entry align="left">Create / Delete / Rename / Permission Changes</entry></row>
<row><entry align="center">2</entry><entry align="left">Create / Delete / Rename / Perm Change / Open / Close</entry></row>
</tbody>
</tgroup>
</table>
</sect2>
<sect2>
<title>recycle</title>
<para>
A recycle-bin like module. When used any unlink call
will be intercepted and files moved to the recycle
directory instead of being deleted.
</para>
<para>Supported options:
<variablelist>
<varlistentry>
<term>vfs_recycle_bin:repository</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:keeptree</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:versions</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:touch</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:maxsize</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:exclude</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:exclude_dir</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
<varlistentry>
<term>vfs_recycle_bin:noversions</term>
<listitem><para>FIXME</para></listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
<sect2>
<title>netatalk</title>
<para>
A netatalk module, that will ease co-existence of samba and
netatalk file sharing services.
</para>
<para>Advantages compared to the old netatalk module:
<simplelist>
<member>it doesn't care about creating of .AppleDouble forks, just keeps them in sync</member>
<member>if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically</member>
</simplelist>
</para>
</sect2>
</sect1>
<sect1>
<title>VFS modules available elsewhere</title>
<para>
This section contains a listing of various other VFS modules that
have been posted but don't currently reside in the Samba CVS
tree for one reason or another (e.g. it is easy for the maintainer
to have his or her own CVS tree).
</para>
<para>
No statemets about the stability or functionality of any module
should be implied due to its presence here.
</para>
<sect2>
<title>DatabaseFS</title>
<para>
URL: <ulink url="http://www.css.tayloru.edu/~elorimer/databasefs/index.php">http://www.css.tayloru.edu/~elorimer/databasefs/index.php</ulink>
</para>
<para>By <ulink url="mailto:elorimer@css.tayloru.edu">Eric Lorimer</ulink>.</para>
<para>
I have created a VFS module which implements a fairly complete read-only
filesystem. It presents information from a database as a filesystem in
a modular and generic way to allow different databases to be used
(originally designed for organizing MP3s under directories such as
"Artists," "Song Keywords," etc... I have since applied it to a student
roster database very easily). The directory structure is stored in the
database itself and the module makes no assumptions about the database
structure beyond the table it requires to run.
</para>
<para>
Any feedback would be appreciated: comments, suggestions, patches,
etc... If nothing else, hopefully it might prove useful for someone
else who wishes to create a virtual filesystem.
</para>
</sect2>
<sect2>
<title>vscan</title>
<para>URL: <ulink url="http://www.openantivirus.org/">http://www.openantivirus.org/</ulink></para>
<para>
samba-vscan is a proof-of-concept module for Samba, which
uses the VFS (virtual file system) features of Samba 2.2.x/3.0
alphaX. Of couse, Samba has to be compiled with VFS support.
samba-vscan supports various virus scanners and is maintained
by Rainer Link.
</para>
</sect2>
</sect1>
</chapter>

396
docs/docbook/projdoc/locking.sgml
View File

@ -1,396 +0,0 @@
<chapter id="locking">
<chapterinfo>
&author.jeremy;
&author.jelmer;
&author.jht;
</chapterinfo>
<title>File and Record Locking</title>
<sect1>
<title>Discussion</title>
<para>
One area which sometimes causes trouble is locking.
</para>
<para>
There are two types of locking which need to be performed by a SMB server.
The first is <emphasis>record locking</emphasis> which allows a client to lock
a range of bytes in a open file. The second is the <emphasis>deny modes</emphasis>
that are specified when a file is open.
</para>
<para>
Record locking semantics under Unix is very different from record locking under
Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix
system call to implement proper record locking between different Samba clients.
This can not be fully correct due to several reasons. The simplest is the fact
that a Windows client is allowed to lock a byte range up to 2^32 or 2^64,
depending on the client OS. The unix locking only supports byte ranges up to 2^31.
So it is not possible to correctly satisfy a lock request above 2^31. There are
many more differences, too many to be listed here.
</para>
<para>
Samba 2.2 and above implements record locking completely independent of the
underlying unix system. If a byte range lock that the client requests happens
to fall into the range 0-2^31, Samba hands this request down to the Unix system.
All other locks can not be seen by unix anyway.
</para>
<para>
Strictly a SMB server should check for locks before every read and write call on
a file. Unfortunately with the way fcntl() works this can be slow and may overstress
the rpc.lockd. It is also almost always unnecessary as clients are supposed to
independently make locking calls before reads and writes anyway if locking is
important to them. By default Samba only makes locking calls when explicitly asked
to by a client, but if you set <emphasis>strict locking = yes</emphasis> then it
will make lock checking calls on every read and write.
</para>
<para>
You can also disable by range locking completely using <emphasis>locking = no</emphasis>.
This is useful for those shares that don't support locking or don't need it
(such as cdroms). In this case Samba fakes the return codes of locking calls to
tell clients that everything is OK.
</para>
<para>
The second class of locking is the <emphasis>deny modes</emphasis>. These
are set by an application when it opens a file to determine what types of
access should be allowed simultaneously with its open. A client may ask for
DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special compatibility
modes called DENY_FCB and DENY_DOS.
</para>
</sect1>
<sect1>
<title>Samba Opportunistic Locking Control</title>
<para>
Opportunistic locking essentially means that the client is allowed to download and cache
a file on their hard drive while making changes; if a second client wants to access the
file, the first client receives a break and must synchronise the file back to the server.
This can give significant performance gains in some cases; some programs insist on
synchronising the contents of the entire file back to the server for a single change.
</para>
<para>
Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking.
</para>
<para>
Level2 Oplocks provids opportunistic locking for a file that will be treated as
<emphasis>read only</emphasis>. Typically this is used on files that are read-only or
on files that the client has no initial intention to write to at time of opening the file.
</para>
<para>
Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with
Samba's oplocked files, although this has provided better integration of MS Windows network
file locking with the under lying OS, SGI IRIX and Linux are the only two OS's that are
oplock aware at this time.
</para>
<para>
Unless your system supports kernel oplocks, you should disable oplocks if you are
accessing the same files from both Unix/Linux and SMB clients. Regardless, oplocks should
always be disabled if you are sharing a database file (e.g., Microsoft Access) between
multiple clients, as any break the first client receives will affect synchronisation of
the entire file (not just the single record), which will result in a noticable performance
impairment and, more likely, problems accessing the database in the first place. Notably,
Microsoft Outlook's personal folders (*.pst) react very badly to oplocks. If in doubt,
disable oplocks and tune your system from that point.
</para>
<para>
If client-side caching is desirable and reliable on your network, you will benefit from
turning on oplocks. If your network is slow and/or unreliable, or you are sharing your
files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people
will be accessing the same files frequently, you probably will not benefit from the overhead
of your client sending oplock breaks and will instead want to disable oplocks for the share.
</para>
<para>
Another factor to consider is the perceived performance of file access. If oplocks provide no
measurable speed benefit on your network, it might not be worth the hassle of dealing with them.
</para>
<para>
You can disable oplocks on a per-share basis with the following:
<programlisting>
oplocks = False
level2 oplocks = False
</programlisting>
Alternately, you could disable oplocks on a per-file basis within the share:
<programlisting>
veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/
</programlisting>
</para>
<para>
If you are experiencing problems with oplocks as apparent from Samba's log entries,
you may want to play it safe and disable oplocks and level2 oplocks.
</para>
</sect1>
<sect1>
<title>MS Windows Opportunistic Locking and Caching Controls</title>
<para>
There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP
workstation computer that can affect any application attempting to access shared database files
across a network. This is a result of a default setting configured in the Windows 2000/XP
operating system known as <emphasis>Opportunistic Locking</emphasis>. When a workstation
attempts to access shared data files located on another Windows 2000/XP computer,
the Windows 2000/XP operating system will attempt to increase performance by locking the
files and caching information locally. When this occurs, the application is unable to
properly function, which results in an <emphasis>Access Denied</emphasis>
error message being displayed during network operations.
</para>
<para>
All Windows operating systems in the NT family that act as database servers for data files
(meaning that data files are stored there and accessed by other Windows PCs) may need to
have opportunistic locking disabled in order to minimize the risk of data file corruption.
This includes Windows 9x/Me, Windows NT, Windows 200x and Windows XP.
</para>
<para>
If you are using a Windows NT family workstation in place of a server, you must also
disable opportunistic locking (oplocks) on that workstation. For example, if you use a
PC with the Windows NT Workstation operating system instead of Windows NT Server, and you
have data files located on it that are accessed from other Windows PCs, you may need to
disable oplocks on that system.
</para>
<para>
The major difference is the location in the Windows registry where the values for disabling
oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location
may be used.
</para>
<para>
You can verify (or change or add, if necessary) this Registry value using the Windows
Registry Editor. When you change this registry value, you will have to reboot the PC
to ensure that the new setting goes into effect.
</para>
<para>
The location of the client registry entry for opportunistic locking has changed in
Windows 2000 from the earlier location in Microsoft Windows NT.
</para>
<note><para>
Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks
in earlier versions of Windows.
</para></note>
<para>
You can also deny the granting of opportunistic locks by changing the following registry entries:
</para>
<para>
<programlisting>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
OplocksDisabled REG_DWORD 0 or 1
Default: 0 (not disabled)
</programlisting>
</para>
<note><para>
The OplocksDisabled registry value configures Windows clients to either request or not
request opportunistic locks on a remote file. To disable oplocks, the value of
OplocksDisabled must be set to 1.
</para></note>
<para>
<programlisting>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
EnableOplocks REG_DWORD 0 or 1
Default: 1 (Enabled by Default)
EnableOpLockForceClose REG_DWORD 0 or 1
Default: 0 (Disabled by Default)
</programlisting>
</para>
<note><para>
The EnableOplocks value configures Windows-based servers (including Workstations sharing
files) to allow or deny opportunistic locks on local files.
</para></note>
<para>
To force closure of open oplocks on close or program exit EnableOpLockForceClose must be set to 1.
</para>
<para>
An illustration of how level II oplocks work:
</para>
<itemizedlist>
<listitem><para>
Station 1 opens the file, requesting oplock.
</para></listitem>
<listitem><para>
Since no other station has the file open, the server grants station 1 exclusive oplock.
</para></listitem>
<listitem><para>
Station 2 opens the file, requesting oplock.
</para></listitem>
<listitem><para>
Since station 1 has not yet written to the file, the server asks station 1 to Break
to Level II Oplock.
</para></listitem>
<listitem><para>
Station 1 complies by flushing locally buffered lock information to the server.
</para></listitem>
<listitem><para>
Station 1 informs the server that it has Broken to Level II Oplock (alternatively,
station 1 could have closed the file).
</para></listitem>
<listitem><para>
The server responds to station 2's open request, granting it level II oplock.
Other stations can likewise open the file and obtain level II oplock.
</para></listitem>
<listitem><para>
Station 2 (or any station that has the file open) sends a write request SMB.
The server returns the write response.
</para></listitem>
<listitem><para>
The server asks all stations that have the file open to Break to None, meaning no
station holds any oplock on the file. Because the workstations can have no cached
writes or locks at this point, they need not respond to the break-to-none advisory;
all they need do is invalidate locally cashed read-ahead data.
</para></listitem>
</itemizedlist>
<sect2>
<title>Workstation Service Entries</title>
<para><programlisting>
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
UseOpportunisticLocking REG_DWORD 0 or 1
Default: 1 (true)
</programlisting></para>
<para>
Indicates whether the redirector should use opportunistic-locking (oplock) performance
enhancement. This parameter should be disabled only to isolate problems.
</para>
</sect2>
<sect2>
<title>Server Service Entries</title>
<para><programlisting>
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
EnableOplocks REG_DWORD 0 or 1
Default: 1 (true)
</programlisting></para>
<para>
Specifies whether the server allows clients to use oplocks on files. Oplocks are a
significant performance enhancement, but have the potential to cause lost cached
data on some networks, particularly wide-area networks.
</para>
<para><programlisting>
MinLinkThroughput REG_DWORD 0 to infinite bytes per second
Default: 0
</programlisting></para>
<para>
Specifies the minimum link throughput allowed by the server before it disables
raw and opportunistic locks for this connection.
</para>
<para><programlisting>
MaxLinkDelay REG_DWORD 0 to 100,000 seconds
Default: 60
</programlisting></para>
<para>
Specifies the maximum time allowed for a link delay. If delays exceed this number,
the server disables raw I/O and opportunistic locking for this connection.
</para>
<para><programlisting>
OplockBreakWait REG_DWORD 10 to 180 seconds
Default: 35
</programlisting></para>
<para>
Specifies the time that the server waits for a client to respond to an oplock break
request. Smaller values can allow detection of crashed clients more quickly but can
potentially cause loss of cached data.
</para>
</sect2>
</sect1>
<sect1>
<title>Persistent Data Corruption</title>
<para>
If you have applied all of the settings discussed in this paper but data corruption problems
and other symptoms persist, here are some additional things to check out:
</para>
<para>
We have credible reports from developers that faulty network hardware, such as a single
faulty network card, can cause symptoms similar to read caching and data corruption.
If you see persistent data corruption even after repeated reindexing, you may have to
rebuild the data files in question. This involves creating a new data file with the
same definition as the file to be rebuilt and transferring the data from the old file
to the new one. There are several known methods for doing this that can be found in
our Knowledge Base.
</para>
</sect1>
<sect1>
<title>Additional Reading</title>
<para>
You may want to check for an updated version of this white paper on our Web site from
time to time. Many of our white papers are updated as information changes. For those papers,
the Last Edited date is always at the top of the paper.
</para>
<para>
Section of the Microsoft MSDN Library on opportunistic locking:
</para>
<para>
Opportunistic Locks, Microsoft Developer Network (MSDN), Windows Development &gt
Windows Base Services &gt Files and I/O &gt SDK Documentation &gt File Storage &gt File Systems
&gt About File Systems &gt Opportunistic Locks, Microsoft Corporation.
<ulink url="http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp">http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp</ulink>
</para>
<para>
Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS",
Microsoft Corporation, April 1999, <ulink url="=http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992</ulink>.
</para>
<para>
Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000",
Microsoft Corporation, April 2001, <ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264</ulink>.
</para>
<para>
Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT",
Microsoft Corporation, April 1995, <ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202</ulink>.
</para>
</sect1>
</chapter>

116
docs/docbook/projdoc/msdfs_setup.sgml
View File

@ -1,116 +0,0 @@
<chapter id="msdfs">
<chapterinfo>
<author>
<firstname>Shirish</firstname><surname>Kalele</surname>
<affiliation>
<orgname>Samba Team &amp; Veritas Software</orgname>
<address>
<email>samba@samba.org</email>
</address>
</affiliation>
</author>
<pubdate>12 Jul 2000</pubdate>
</chapterinfo>
<title>Hosting a Microsoft Distributed File System tree on Samba</title>
<sect1>
<title>Instructions</title>
<para>The Distributed File System (or Dfs) provides a means of
separating the logical view of files and directories that users
see from the actual physical locations of these resources on the
network. It allows for higher availability, smoother storage expansion,
load balancing etc. For more information about Dfs, refer to <ulink
url="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp">
Microsoft documentation</ulink>. </para>
<para>This document explains how to host a Dfs tree on a Unix
machine (for Dfs-aware clients to browse) using Samba.</para>
<para>To enable SMB-based DFS for Samba, configure it with the
<parameter>--with-msdfs</parameter> option. Once built, a
Samba server can be made a Dfs server by setting the global
boolean <ulink url="smb.conf.5.html#HOSTMSDFS"><parameter>
host msdfs</parameter></ulink> parameter in the <filename>smb.conf
</filename> file. You designate a share as a Dfs root using the share
level boolean <ulink url="smb.conf.5.html#MSDFSROOT"><parameter>
msdfs root</parameter></ulink> parameter. A Dfs root directory on
Samba hosts Dfs links in the form of symbolic links that point
to other servers. For example, a symbolic link
<filename>junction-&gt;msdfs:storage1\share1</filename> in
the share directory acts as the Dfs junction. When Dfs-aware
clients attempt to access the junction link, they are redirected
to the storage location (in this case, \\storage1\share1).</para>
<para>Dfs trees on Samba work with all Dfs-aware clients ranging
from Windows 95 to 2000.</para>
<para>Here's an example of setting up a Dfs tree on a Samba
server.</para>
<para><programlisting>
# The smb.conf file:
[global]
netbios name = SAMBA
host msdfs = yes
[dfs]
path = /export/dfsroot
msdfs root = yes
</programlisting></para>
<para>In the /export/dfsroot directory we set up our dfs links to
other servers on the network.</para>
<para><prompt>root# </prompt><userinput>cd /export/dfsroot</userinput></para>
<para><prompt>root# </prompt><userinput>chown root /export/dfsroot</userinput></para>
<para><prompt>root# </prompt><userinput>chmod 755 /export/dfsroot</userinput></para>
<para><prompt>root# </prompt><userinput>ln -s msdfs:storageA\\shareA linka</userinput></para>
<para><prompt>root# </prompt><userinput>ln -s msdfs:serverB\\share,serverC\\share linkb</userinput></para>
<para>You should set up the permissions and ownership of
the directory acting as the Dfs root such that only designated
users can create, delete or modify the msdfs links. Also note
that symlink names should be all lowercase. This limitation exists
to have Samba avoid trying all the case combinations to get at
the link name. Finally set up the symbolic links to point to the
network shares you want, and start Samba.</para>
<para>Users on Dfs-aware clients can now browse the Dfs tree
on the Samba server at \\samba\dfs. Accessing
links linka or linkb (which appear as directories to the client)
takes users directly to the appropriate shares on the network.</para>
<sect2>
<title>Notes</title>
<itemizedlist>
<listitem><para>Windows clients need to be rebooted
if a previously mounted non-dfs share is made a dfs
root or vice versa. A better way is to introduce a
new share and make it the dfs root.</para>
</listitem>
<listitem><para>Currently there's a restriction that msdfs
symlink names should all be lowercase.</para>
</listitem>
<listitem><para>For security purposes, the directory
acting as the root of the Dfs tree should have ownership
and permissions set so that only designated users can
modify the symbolic links in the directory.</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
</chapter>

972
docs/docbook/projdoc/passdb.sgml
View File

@ -1,972 +0,0 @@
<chapter id="passdb">
<chapterinfo>
&author.jelmer;
&author.jerry;
&author.jeremy;
&author.jht;
<author>
<firstname>Olivier (lem)</firstname><surname>Lemaire</surname>
<affiliation>
<orgname>IDEALX</orgname>
<address><email>olem@IDEALX.org</email></address>
</affiliation>
</author>
<pubdate>February 2003</pubdate>
</chapterinfo>
<title>User information database</title>
<sect1>
<title>Introduction</title>
<para>Old windows clients send plain text passwords over the wire.
Samba can check these passwords by crypting them and comparing them
to the hash stored in the unix user database.
</para>
<para>
Newer windows clients send encrypted passwords (so-called
Lanman and NT hashes) over
the wire, instead of plain text passwords. The newest clients
will only send encrypted passwords and refuse to send plain text
passwords, unless their registry is tweaked.
</para>
<para>These passwords can't be converted to unix style encrypted
passwords. Because of that you can't use the standard unix
user database, and you have to store the Lanman and NT hashes
somewhere else. </para>
<para>Next to a differently encrypted passwords,
windows also stores certain data for each user
that is not stored in a unix user database, e.g.
workstations the user may logon from, the location where his/her
profile is stored, etc.
Samba retrieves and stores this information using a "passdb backend".
Commonly
available backends are LDAP, plain text file, MySQL and nisplus.
For more information, see the documentation about the
<command>passdb backend = </command> parameter.
</para>
</sect1>
<sect1>
<title>Important Notes About Security</title>
<para>The unix and SMB password encryption techniques seem similar
on the surface. This similarity is, however, only skin deep. The unix
scheme typically sends clear text passwords over the network when
logging in. This is bad. The SMB encryption scheme never sends the
cleartext password over the network but it does store the 16 byte
hashed values on disk. This is also bad. Why? Because the 16 byte hashed
values are a "password equivalent". You cannot derive the user's
password from them, but they could potentially be used in a modified
client to gain access to a server. This would require considerable
technical knowledge on behalf of the attacker but is perfectly possible.
You should thus treat the data stored in whatever
passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the
cleartext passwords of all your users. Its contents must be kept
secret, and the file should be protected accordingly.</para>
<para>Ideally we would like a password scheme which neither requires
plain text passwords on the net or on disk. Unfortunately this
is not available as Samba is stuck with being compatible with
other SMB systems (WinNT, WfWg, Win95 etc). </para>
<warning>
<para>Note that Windows NT 4.0 Service pack 3 changed the
default for permissible authentication so that plaintext
passwords are <emphasis>never</emphasis> sent over the wire.
The solution to this is either to switch to encrypted passwords
with Samba or edit the Windows NT registry to re-enable plaintext
passwords. See the document WinNT.txt for details on how to do
this.</para>
<para>Other Microsoft operating systems which also exhibit
this behavior includes</para>
<para> These versions of MS Windows do not support full domain
security protocols, although they may log onto a domain environment.
Of these Only MS Windows XP Home does NOT support domain logons.</para>
<simplelist>
<member>MS DOS Network client 3.0 with
the basic network redirector installed</member>
<member>Windows 95 with the network redirector
update installed</member>
<member>Windows 98 [se]</member>
<member>Windows Me</member>
<member>Windows XP Home</member>
</simplelist>
<para> The following versions of MS Windows fully support domain
security protocols.</para>
<simplelist>
<member>Windows NT 3.5x</member>
<member>Windows NT 4.0</member>
<member>Windows 2000 Professional</member>
<member>Windows 200x Server/Advanced Server</member>
<member>Windows XP Professional</member>
</simplelist>
</warning>
<note><para>All current release of
Microsoft SMB/CIFS clients support authentication via the
SMB Challenge/Response mechanism described here. Enabling
clear text authentication does not disable the ability
of the client to participate in encrypted authentication.</para></note>
<para>MS Windows clients will cache the encrypted password alone.
Even when plain text passwords are re-enabled, through the appropriate
registry change, the plain text password is NEVER cached. This means that
in the event that a network connections should become disconnected (broken)
only the cached (encrypted) password will be sent to the resource server
to affect a auto-reconnect. If the resource server does not support encrypted
passwords the auto-reconnect will fail. <emphasis>USE OF ENCRYPTED PASSWORDS
IS STRONGLY ADVISED.</emphasis></para>
<sect2>
<title>Advantages of SMB Encryption</title>
<simplelist>
<member>Plain text passwords are not passed across
the network. Someone using a network sniffer cannot just
record passwords going to the SMB server.</member>
<member>WinNT doesn't like talking to a server
that does not support encrypted passwords. It will refuse
to browse the server if the server is also in user level
security mode. It will insist on prompting the user for the
password on each connection, which is very annoying. The
only things you can do to stop this is to use SMB encryption.
</member>
<member>Encrypted password support allows automatic share
(resource) reconnects.</member>
</simplelist>
</sect2>
<sect2>
<title>Advantages of non-encrypted passwords</title>
<simplelist>
<member>Plain text passwords are not kept
on disk, and are NOT cached in memory. </member>
<member>Uses same password file as other unix
services such as login and ftp</member>
<member>Use of other services (such as telnet and ftp) which
send plain text passwords over the net, so sending them for SMB
isn't such a big deal.</member>
</simplelist>
</sect2>
</sect1>
<sect1>
<title>The smbpasswd Command</title>
<para>The smbpasswd utility is a utility similar to the
<command>passwd</command> or <command>yppasswd</command> programs.
It maintains the two 32 byte password fields in the passdb backend. </para>
<para><command>smbpasswd</command> works in a client-server mode
where it contacts the local smbd to change the user's password on its
behalf. This has enormous benefits - as follows.</para>
<para><command>smbpasswd</command> has the capability
to change passwords on Windows NT servers (this only works when
the request is sent to the NT Primary Domain Controller if you
are changing an NT Domain user's password).</para>
<para>To run smbpasswd as a normal user just type :</para>
<para><prompt>$ </prompt><userinput>smbpasswd</userinput></para>
<para><prompt>Old SMB password: </prompt><userinput>&lt;type old value here -
or hit return if there was no old password&gt;</userinput></para>
<para><prompt>New SMB Password: </prompt><userinput>&lt;type new value&gt;
</userinput></para>
<para><prompt>Repeat New SMB Password: </prompt><userinput>&lt;re-type new value
</userinput></para>
<para>If the old value does not match the current value stored for
that user, or the two new values do not match each other, then the
password will not be changed.</para>
<para>If invoked by an ordinary user it will only allow the user
to change his or her own Samba password.</para>
<para>If run by the root user smbpasswd may take an optional
argument, specifying the user name whose SMB password you wish to
change. Note that when run as root smbpasswd does not prompt for
or check the old password value, thus allowing root to set passwords
for users who have forgotten their passwords.</para>
<para><command>smbpasswd</command> is designed to work in the same way
and be familiar to UNIX users who use the <command>passwd</command> or
<command>yppasswd</command> commands.</para>
<para>For more details on using <command>smbpasswd</command> refer
to the man page which will always be the definitive reference.</para>
</sect1>
<!--
<sect1>
<title>The <command>pdbedit</command> command</title>
FIXME
</sect1>
-->
<sect1>
<title>Plain text</title>
<para>
Older versions of samba retrieved user information from the unix user database
and eventually some other fields from the file <filename>/etc/samba/smbpasswd</filename>
or <filename>/etc/smbpasswd</filename>. When password encryption is disabled, no
data is stored at all.
</para>
</sect1>
<sect1>
<title>TDB</title>
<para>Samba can also store the user data in a "TDB" (Trivial Database). Using this backend
doesn't require any additional configuration. This backend is recommended for new installations that
don not require LDAP.
</para>
</sect1>
<sect1>
<title>LDAP</title>
<sect2>
<title>Introduction</title>
<para>
This document describes how to use an LDAP directory for storing Samba user
account information traditionally stored in the smbpasswd(5) file. It is
assumed that the reader already has a basic understanding of LDAP concepts
and has a working directory server already installed. For more information
on LDAP architectures and Directories, please refer to the following sites.
</para>
<itemizedlist>
<listitem><para>OpenLDAP - <ulink url="http://www.openldap.org/">http://www.openldap.org/</ulink></para></listitem>
<listitem><para>iPlanet Directory Server - <ulink url="http://iplanet.netscape.com/directory">http://iplanet.netscape.com/directory</ulink></para></listitem>
</itemizedlist>
<para>
Note that <ulink url="http://www.ora.com/">O'Reilly Publishing</ulink> is working on
a guide to LDAP for System Administrators which has a planned release date of
early summer, 2002.
</para>
<para>
Two additional Samba resources which may prove to be helpful are
</para>
<itemizedlist>
<listitem><para>The <ulink url="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html">Samba-PDC-LDAP-HOWTO</ulink>
maintained by Ignacio Coupeau.</para></listitem>
<listitem><para>The NT migration scripts from <ulink url="http://samba.idealx.org/">IDEALX</ulink> that are
geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
</para></listitem>
</itemizedlist>
</sect2>
<sect2>
<title>Encrypted Password Database</title>
<para>
Traditionally, when configuring <ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">"encrypt
passwords = yes"</ulink> in Samba's <filename>smb.conf</filename> file, user account
information such as username, LM/NT password hashes, password change times, and account
flags have been stored in the <filename>smbpasswd(5)</filename> file. There are several
disadvantages to this approach for sites with very large numbers of users (counted
in the thousands).
</para>
<itemizedlist>
<listitem><para>
The first is that all lookups must be performed sequentially. Given that
there are approximately two lookups per domain logon (one for a normal
session connection such as when mapping a network drive or printer), this
is a performance bottleneck for large sites. What is needed is an indexed approach
such as is used in databases.
</para></listitem>
<listitem><para>
The second problem is that administrators who desired to replicate a
smbpasswd file to more than one Samba server were left to use external
tools such as <command>rsync(1)</command> and <command>ssh(1)</command>
and wrote custom, in-house scripts.
</para></listitem>
<listitem><para>
And finally, the amount of information which is stored in an
smbpasswd entry leaves no room for additional attributes such as
a home directory, password expiration time, or even a Relative
Identified (RID).
</para></listitem>
</itemizedlist>
<para>
As a result of these defeciencies, a more robust means of storing user attributes
used by smbd was developed. The API which defines access to user accounts
is commonly referred to as the samdb interface (previously this was called the passdb
API, and is still so named in the CVS trees).
</para>
<para>
There are a few points to stress about that the ldapsam
does not provide. The LDAP support referred to in the this documentation does not
include:
</para>
<itemizedlist>
<listitem><para>A means of retrieving user account information from
an Windows 2000 Active Directory server.</para></listitem>
<listitem><para>A means of replacing /etc/passwd.</para></listitem>
</itemizedlist>
<para>
The second item can be accomplished by using LDAP NSS and PAM modules. LGPL
versions of these libraries can be obtained from PADL Software
(<ulink url="http://www.padl.com/">http://www.padl.com/</ulink>). More
information about the configuration of these packages may be found at "LDAP,
System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS".
</para>
</sect2>
<sect2>
<title>Supported LDAP Servers</title>
<!-- FIXME: This is outdated for 3.0 -->
<para>
The LDAP samdb code in 2.2.3 (and later) has been developed and tested
using the OpenLDAP 2.0 server and client libraries.
The same code should be able to work with Netscape's Directory Server
and client SDK. However, due to lack of testing so far, there are bound
to be compile errors and bugs. These should not be hard to fix.
If you are so inclined, please be sure to forward all patches to
<ulink url="mailto:samba-patches@samba.org">samba-patches@samba.org</ulink> and
<ulink url="mailto:jerry@samba.org">jerry@samba.org</ulink>.
</para>
</sect2>
<sect2>
<title>Schema and Relationship to the RFC 2307 posixAccount</title>
<para>
Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
<filename>examples/LDAP/samba.schema</filename>. The sambaAccount objectclass is given here:
</para>
<para><programlisting>
objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top AUXILIARY
DESC 'Samba Account'
MUST ( uid $ rid )
MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
description $ userWorkstations $ primaryGroupID $ domain ))
</programlisting></para>
<para>
The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are
owned by the Samba Team and as such is legal to be openly published.
If you translate the schema to be used with Netscape DS, please
submit the modified schema file as a patch to <ulink
url="mailto:jerry@samba.org">jerry@samba.org</ulink>
</para>
<para>
Just as the smbpasswd file is meant to store information which supplements a
user's <filename>/etc/passwd</filename> entry, so is the sambaAccount object
meant to supplement the UNIX user account information. A sambaAccount is a
<constant>STRUCTURAL</constant> objectclass so it can be stored individually
in the directory. However, there are several fields (e.g. uid) which overlap
with the posixAccount objectclass outlined in RFC2307. This is by design.
</para>
<!--olem: we should perhaps have a note about shadowAccounts too as many
systems use them, isn'it ? -->
<para>
In order to store all user account information (UNIX and Samba) in the directory,
it is necessary to use the sambaAccount and posixAccount objectclasses in
combination. However, smbd will still obtain the user's UNIX account
information via the standard C library calls (e.g. getpwnam(), et. al.).
This means that the Samba server must also have the LDAP NSS library installed
and functioning correctly. This division of information makes it possible to
store all Samba account information in LDAP, but still maintain UNIX account
information in NIS while the network is transitioning to a full LDAP infrastructure.
</para>
</sect2>
<sect2>
<title>Configuring Samba with LDAP</title>
<sect3>
<title>OpenLDAP configuration</title>
<para>
To include support for the sambaAccount object in an OpenLDAP directory
server, first copy the samba.schema file to slapd's configuration directory.
</para>
<para>
<prompt>root# </prompt><userinput>cp samba.schema /etc/openldap/schema/</userinput>
</para>
<para>
Next, include the <filename>samba.schema</filename> file in <filename>slapd.conf</filename>.
The sambaAccount object contains two attributes which depend upon other schema
files. The 'uid' attribute is defined in <filename>cosine.schema</filename> and
the 'displayName' attribute is defined in the <filename>inetorgperson.schema</filename>
file. Both of these must be included before the <filename>samba.schema</filename> file.
</para>
<para><programlisting>
## /etc/openldap/slapd.conf
## schema files (core.schema is required by default)
include /etc/openldap/schema/core.schema
## needed for sambaAccount
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/samba.schema
include /etc/openldap/schema/nis.schema
....
</programlisting></para>
<para>
It is recommended that you maintain some indices on some of the most usefull attributes,
like in the following example, to speed up searches made on sambaAccount objectclasses
(and possibly posixAccount and posixGroup as well).
</para>
<para><programlisting>
# Indices to maintain
## required by OpenLDAP 2.0
index objectclass eq
## support pb_getsampwnam()
index uid pres,eq
## support pdb_getsambapwrid()
index rid eq
## uncomment these if you are storing posixAccount and
## posixGroup entries in the directory as well
##index uidNumber eq
##index gidNumber eq
##index cn eq
##index memberUid eq
# (both fetched via ldapsearch):
index primaryGroupID eq
index displayName pres,eq
</programlisting></para>
</sect3>
<sect3>
<title>Configuring Samba</title>
<para>
The following parameters are available in smb.conf only with <parameter>--with-ldapsam</parameter>
was included when compiling Samba.
</para>
<itemizedlist>
<listitem><para><ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend [ldapsam|ldapsam_nua]:url</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPSSL">ldap ssl</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPADMINDN">ldap admin dn</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPSUFFIX">ldap suffix</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPFILTER">ldap filter</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPPORT">ldap port</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPMACHINSUFFIX">ldap machine suffix</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPUSERSUFFIX">ldap user suffix</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPDELETEDN">ldap delete dn</ulink></para></listitem>
</itemizedlist>
<para>
These are described in the <ulink url="smb.conf.5.html">smb.conf(5)</ulink> man
page and so will not be repeated here. However, a sample smb.conf file for
use with an LDAP directory could appear as
</para>
<para><programlisting>
## /usr/local/samba/lib/smb.conf
[global]
security = user
encrypt passwords = yes
netbios name = TASHTEGO
workgroup = NARNIA
# ldap related parameters
# define the DN to use when binding to the directory servers
# The password for this DN is not stored in smb.conf. Rather it
# must be set by using 'smbpasswd -w <replaceable>secretpw</replaceable>' to store the
# passphrase in the secrets.tdb file. If the "ldap admin dn" values
# change, this password will need to be reset.
ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
# Define the SSL option when connecting to the directory
# ('off', 'start tls', or 'on' (default))
ldap ssl = start tls
passdb backend ldapsam:ldap://ahab.samba.org
# smbpasswd -x delete the entire dn-entry
ldap delete dn = no
# the machine and user suffix added to the base suffix
# wrote WITHOUT quotes. NULL siffixes by default
ldap user suffix = ou=People
ldap machine suffix = ou=Systems
# define the port to use in the LDAP session (defaults to 636 when
# "ldap ssl = on")
ldap port = 389
# specify the base DN to use when searching the directory
ldap suffix = "ou=people,dc=samba,dc=org"
# generally the default ldap search filter is ok
# ldap filter = "(&amp;(uid=%u)(objectclass=sambaAccount))"
</programlisting></para>
</sect3>
</sect2>
<sect2>
<title>Accounts and Groups management</title>
<para>
As users accounts are managed thru the sambaAccount objectclass, you should
modify your existing administration tools to deal with sambaAccount attributes.
</para>
<para>
Machines accounts are managed with the sambaAccount objectclass, just
like users accounts. However, it's up to you to store thoses accounts
in a different tree of you LDAP namespace: you should use
"ou=Groups,dc=plainjoe,dc=org" to store groups and
"ou=People,dc=plainjoe,dc=org" to store users. Just configure your
NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration
file).
</para>
<para>
In Samba release 3.0, the group management system is based on posix
groups. This means that Samba makes usage of the posixGroup objectclass.
For now, there is no NT-like group system management (global and local
groups).
</para>
</sect2>
<sect2>
<title>Security and sambaAccount</title>
<para>
There are two important points to remember when discussing the security
of sambaAccount entries in the directory.
</para>
<itemizedlist>
<listitem><para><emphasis>Never</emphasis> retrieve the lmPassword or
ntPassword attribute values over an unencrypted LDAP session.</para></listitem>
<listitem><para><emphasis>Never</emphasis> allow non-admin users to
view the lmPassword or ntPassword attribute values.</para></listitem>
</itemizedlist>
<para>
These password hashes are clear text equivalents and can be used to impersonate
the user without deriving the original clear text strings. For more information
on the details of LM/NT password hashes, refer to the <link
linkend="passdb">User Database</link> of the Samba-HOWTO-Collection.
</para>
<para>
To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
to require an encrypted session (<command>ldap ssl = on</command>) using
the default port of 636
when contacting the directory server. When using an OpenLDAP 2.0 server, it
is possible to use the use the StartTLS LDAP extended operation in the place of
LDAPS. In either case, you are strongly discouraged to disable this security
(<command>ldap ssl = off</command>).
</para>
<para>
Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
extended operation. However, the OpenLDAP library still provides support for
the older method of securing communication between clients and servers.
</para>
<para>
The second security precaution is to prevent non-administrative users from
harvesting password hashes from the directory. This can be done using the
following ACL in <filename>slapd.conf</filename>:
</para>
<para><programlisting>
## allow the "ldap admin dn" access, but deny everyone else
access to attrs=lmPassword,ntPassword
by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
by * none
</programlisting></para>
</sect2>
<sect2>
<title>LDAP specials attributes for sambaAccounts</title>
<para>
The sambaAccount objectclass is composed of the following attributes:
</para>
<itemizedlist>
<listitem><para><constant>lmPassword</constant>: the LANMAN password 16-byte hash stored as a character
representation of a hexidecimal string.</para></listitem>
<listitem><para><constant>ntPassword</constant>: the NT password hash 16-byte stored as a character
representation of a hexidecimal string.</para></listitem>
<listitem><para><constant>pwdLastSet</constant>: The integer time in seconds since 1970 when the
<constant>lmPassword</constant> and <constant>ntPassword</constant> attributes were last set.
</para></listitem>
<listitem><para><constant>acctFlags</constant>: string of 11 characters surrounded by square brackets []
representing account flags such as U (user), W(workstation), X(no password expiration), and
D(disabled).</para></listitem>
<listitem><para><constant>logonTime</constant>: Integer value currently unused</para></listitem>
<listitem><para><constant>logoffTime</constant>: Integer value currently unused</para></listitem>
<listitem><para><constant>kickoffTime</constant>: Integer value currently unused</para></listitem>
<listitem><para><constant>pwdCanChange</constant>: Integer value currently unused</para></listitem>
<listitem><para><constant>pwdMustChange</constant>: Integer value currently unused</para></listitem>
<listitem><para><constant>homeDrive</constant>: specifies the drive letter to which to map the
UNC path specified by homeDirectory. The drive letter must be specified in the form "X:"
where X is the letter of the drive to map. Refer to the "logon drive" parameter in the
smb.conf(5) man page for more information.</para></listitem>
<listitem><para><constant>scriptPath</constant>: The scriptPath property specifies the path of
the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
is relative to the netlogon share. Refer to the "logon script" parameter in the
smb.conf(5) man page for more information.</para></listitem>
<listitem><para><constant>profilePath</constant>: specifies a path to the user's profile.
This value can be a null string, a local absolute path, or a UNC path. Refer to the
"logon path" parameter in the smb.conf(5) man page for more information.</para></listitem>
<listitem><para><constant>smbHome</constant>: The homeDirectory property specifies the path of
the home directory for the user. The string can be null. If homeDrive is set and specifies
a drive letter, homeDirectory should be a UNC path. The path must be a network
UNC path of the form \\server\share\directory. This value can be a null string.
Refer to the "logon home" parameter in the smb.conf(5) man page for more information.
</para></listitem>
<listitem><para><constant>userWorkstation</constant>: character string value currently unused.
</para></listitem>
<listitem><para><constant>rid</constant>: the integer representation of the user's relative identifier
(RID).</para></listitem>
<listitem><para><constant>primaryGroupID</constant>: the relative identifier (RID) of the primary group
of the user.</para></listitem>
</itemizedlist>
<para>
The majority of these parameters are only used when Samba is acting as a PDC of
a domain (refer to the <ulink url="Samba-PDC-HOWTO.html">Samba-PDC-HOWTO</ulink> for details on
how to configure Samba as a Primary Domain Controller). The following four attributes
are only stored with the sambaAccount entry if the values are non-default values:
</para>
<itemizedlist>
<listitem><para>smbHome</para></listitem>
<listitem><para>scriptPath</para></listitem>
<listitem><para>logonPath</para></listitem>
<listitem><para>homeDrive</para></listitem>
</itemizedlist>
<para>
These attributes are only stored with the sambaAccount entry if
the values are non-default values. For example, assume TASHTEGO has now been
configured as a PDC and that <command>logon home = \\%L\%u</command> was defined in
its <filename>smb.conf</filename> file. When a user named "becky" logons to the domain,
the <parameter>logon home</parameter> string is expanded to \\TASHTEGO\becky.
If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org",
this value is used. However, if this attribute does not exist, then the value
of the <parameter>logon home</parameter> parameter is used in its place. Samba
will only write the attribute value to the directory entry if the value is
something other than the default (e.g. \\MOBY\becky).
</para>
</sect2>
<sect2>
<title>Example LDIF Entries for a sambaAccount</title>
<para>
The following is a working LDIF with the inclusion of the posixAccount objectclass:
</para>
<para><programlisting>
dn: uid=guest2, ou=people,dc=plainjoe,dc=org
ntPassword: 878D8014606CDA29677A44EFA1353FC7
pwdMustChange: 2147483647
primaryGroupID: 1201
lmPassword: 552902031BEDE9EFAAD3B435B51404EE
pwdLastSet: 1010179124
logonTime: 0
objectClass: sambaAccount
uid: guest2
kickoffTime: 2147483647
acctFlags: [UX ]
logoffTime: 2147483647
rid: 19006
pwdCanChange: 0
</programlisting></para>
<para>
The following is an LDIF entry for using both the sambaAccount and
posixAccount objectclasses:
</para>
<para><programlisting>
dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
logonTime: 0
displayName: Gerald Carter
lmPassword: 552902031BEDE9EFAAD3B435B51404EE
primaryGroupID: 1201
objectClass: posixAccount
objectClass: sambaAccount
acctFlags: [UX ]
userPassword: {crypt}BpM2ej8Rkzogo
uid: gcarter
uidNumber: 9000
cn: Gerald Carter
loginShell: /bin/bash
logoffTime: 2147483647
gidNumber: 100
kickoffTime: 2147483647
pwdLastSet: 1010179230
rid: 19000
homeDirectory: /home/tashtego/gcarter
pwdCanChange: 0
pwdMustChange: 2147483647
ntPassword: 878D8014606CDA29677A44EFA1353FC7
</programlisting></para>
</sect2>
</sect1>
<sect1>
<title>MySQL</title>
<sect2>
<title>Creating the database</title>
<para>
You either can set up your own table and specify the field names to pdb_mysql (see below
for the column names) or use the default table. The file <filename>examples/pdb/mysql/mysql.dump</filename>
contains the correct queries to create the required tables. Use the command :
<command>mysql -u<replaceable>username</replaceable> -h<replaceable>hostname</replaceable> -p<replaceable>password</replaceable> <replaceable>databasename</replaceable> < <filename>/path/to/samba/examples/pdb/mysql/mysql.dump</filename></command>
</para>
</sect2>
<sect2>
<title>Configuring</title>
<para>This plugin lacks some good documentation, but here is some short info:</para>
<para>Add a the following to the <command>passdb backend</command> variable in your <filename>smb.conf</filename>:
<programlisting>
passdb backend = [other-plugins] mysql:identifier [other-plugins]
</programlisting>
</para>
<para>The identifier can be any string you like, as long as it doesn't collide with
the identifiers of other plugins or other instances of pdb_mysql. If you
specify multiple pdb_mysql.so entries in 'passdb backend', you also need to
use different identifiers!
</para>
<para>
Additional options can be given thru the smb.conf file in the [global] section.
</para>
<para><programlisting>
identifier:mysql host - host name, defaults to 'localhost'
identifier:mysql password
identifier:mysql user - defaults to 'samba'
identifier:mysql database - defaults to 'samba'
identifier:mysql port - defaults to 3306
identifier:table - Name of the table containing users
</programlisting></para>
<warning>
<para>
Since the password for the mysql user is stored in the
smb.conf file, you should make the the smb.conf file
readable only to the user that runs samba. This is considered a security
bug and will be fixed soon.
</para>
</warning>
<para>Names of the columns in this table(I've added column types those columns should have first):</para>
<para><programlisting>
identifier:logon time column - int(9)
identifier:logoff time column - int(9)
identifier:kickoff time column - int(9)
identifier:pass last set time column - int(9)
identifier:pass can change time column - int(9)
identifier:pass must change time column - int(9)
identifier:username column - varchar(255) - unix username
identifier:domain column - varchar(255) - NT domain user is part of
identifier:nt username column - varchar(255) - NT username
identifier:fullname column - varchar(255) - Full name of user
identifier:home dir column - varchar(255) - Unix homedir path
identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:')
identifier:logon script column - varchar(255)
- Batch file to run on client side when logging on
identifier:profile path column - varchar(255) - Path of profile
identifier:acct desc column - varchar(255) - Some ASCII NT user data
identifier:workstations column - varchar(255)
- Workstations user can logon to (or NULL for all)
identifier:unknown string column - varchar(255) - unknown string
identifier:munged dial column - varchar(255) - ?
identifier:uid column - int(9) - Unix user ID (uid)
identifier:gid column - int(9) - Unix user group (gid)
identifier:user sid column - varchar(255) - NT user SID
identifier:group sid column - varchar(255) - NT group ID
identifier:lanman pass column - varchar(255) - encrypted lanman password
identifier:nt pass column - varchar(255) - encrypted nt passwd
identifier:plain pass column - varchar(255) - plaintext password
identifier:acct control column - int(9) - nt user data
identifier:unknown 3 column - int(9) - unknown
identifier:logon divs column - int(9) - ?
identifier:hours len column - int(9) - ?
identifier:unknown 5 column - int(9) - unknown
identifier:unknown 6 column - int(9) - unknown
</programlisting></para>
<para>
Eventually, you can put a colon (:) after the name of each column, which
should specify the column to update when updating the table. You can also
specify nothing behind the colon - then the data from the field will not be
updated.
</para>
</sect2>
<sect2>
<title>Using plaintext passwords or encrypted password</title>
<para>
I strongly discourage the use of plaintext passwords, however, you can use them:
</para>
<para>
If you would like to use plaintext passwords, set
'identifier:lanman pass column' and 'identifier:nt pass column' to
'NULL' (without the quotes) and 'identifier:plain pass column' to the
name of the column containing the plaintext passwords.
</para>
<para>
If you use encrypted passwords, set the 'identifier:plain pass
column' to 'NULL' (without the quotes). This is the default.
</para>
</sect2>
<sect2>
<title>Getting non-column data from the table</title>
<para>
It is possible to have not all data in the database and making some 'constant'.
</para>
<para>
For example, you can set 'identifier:fullname column' to :
<command>CONCAT(First_name,' ',Sur_name)</command>
</para>
<para>
Or, set 'identifier:workstations column' to :
<command>NULL</command></para>
<para>See the MySQL documentation for more language constructs.</para>
</sect2>
</sect1>
<sect1>
<title>XML</title>
<para>This module requires libxml2 to be installed.</para>
<para>The usage of pdb_xml is pretty straightforward. To export data, use:
</para>
<para>
<userinput>pdbedit -e xml:filename</userinput>
</para>
<para>
(where filename is the name of the file to put the data in)
</para>
<para>
To import data, use:
<userinput>pdbedit -i xml:filename -e current-pdb</userinput>
</para>
<para>
Where filename is the name to read the data from and current-pdb to put it in.
</para>
</sect1>
</chapter>

1038
docs/docbook/projdoc/printer_driver2.sgml
View File

File diff suppressed because it is too large Load Diff

129
docs/docbook/projdoc/samba-doc.sgml
View File

@ -1,129 +0,0 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY % globalentities SYSTEM '../global.ent'> %globalentities;
]>
<book id="Samba-HOWTO-Collection">
<title>SAMBA Project Documentation</title>
<bookinfo>
<author>
<othername>SAMBA Team</othername>
<affiliation><address><email>samba@samba.org</email></address></affiliation>
</author>
<editor>&person.jelmer;</editor>
<editor>&person.jht;</editor>
<editor>&person.jerry;</editor>
<pubdate>Monday April 21, 2003</pubdate>
<abstract>
<para>
This book is a collection of HOWTOs added to Samba documentation over the years.
Samba is always under development, and so is its' documentation. This release of the
documentation represents a major revision or layout as well as contents.
The most recent version of this document can be found at
<ulink url="http://www.samba.org/">http://www.samba.org/</ulink>
on the "Documentation" page. Please send updates to
<ulink url="mailto:jelmer@samba.org">jelmer@samba.org</ulink>,
<ulink url="mailto:jht@samba.org">jht@samba.org</ulink> or
<ulink url="mailto:jerry@samba.org">jerry@samba.org</ulink>.
</para>
<para>
The Samba-Team would like to express sincere thanks to the many people who have with
or without their knowledge contributed to this update. The size and scope of this
project would not have been possible without significant community contribution. A not
insignificant number of ideas for inclusion (if not content itself) has been obtained
from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered.
Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and
application knowledge that is most to be desired by many Samba users and administrators.
</para>
</abstract>
<legalnotice>
<para>
This documentation is distributed under the GNU General Public License (GPL)
version 2. A copy of the license is included with the Samba source
distribution. A copy can be found on-line at <ulink
url="http://www.fsf.org/licenses/gpl.txt">http://www.fsf.org/licenses/gpl.txt</ulink>
</para>
</legalnotice>
</bookinfo>
<!-- Chapters -->
<part id="introduction">
<title>General Installation</title>
<partintro>
<title>Preparing Samba for Configuration</title>
<para>This section of the Samba-HOWTO-Collection contains general info on how to install samba
and how to configure the parts of samba you will most likely need.
PLEASE read this.</para>
</partintro>
&IntroSMB;
&UNIX-INSTALL;
</part>
<part id="type">
<title>Server Configuration Basics</title>
<partintro>
<title>First Steps in Server Configuration</title>
<para>
Samba can operate in various modes within SMB networks. This HOWTO section contains information on
configuring samba to function as the type of server your network requires. Please read this
section carefully.
</para>
</partintro>
&ServerType;
&SECURITY-LEVEL;
&Samba-PDC-HOWTO;
&Samba-BDC-HOWTO;
&ADS-HOWTO;
&DOMAIN-MEMBER;
</part>
<part id="optional">
<title>Advanced Configuration</title>
<partintro>
<title>Valuable Nuts and Bolts Information</title>
<para>
Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features.
</para>
</partintro>
&NetworkBrowsing;
&Passdb;
&NT-Security;
&GROUP-MAPPING-HOWTO;
&PRINTER-DRIVER2;
&CUPS;
&WINBIND;
&AdvancedNetworkAdmin;
&PolicyMgmt;
&ProfileMgmt;
&Trusts;
&Samba-PAM;
&VFS;
&MS-Dfs-Setup;
&IntegratingWithWindows;
&SecuringSamba;
&unicode;
&locking;
</part>
<part id="troubleshooting">
<title>Troubleshooting</title>
&Diagnosis;
&problems;
&BUGS;
</part>
<part id="Appendixes">
<title>Appendixes</title>
&Compiling;
&NT4Migration;
&Portability;
&Other-Clients;
&SWAT;
&SPEED;
</part>
</book>

205
docs/docbook/projdoc/securing-samba.sgml
View File

@ -1,205 +0,0 @@
<chapter id="securing-samba">
<chapterinfo>
&author.tridge;
&author.jht;
<pubdate>17 March 2003</pubdate>
</chapterinfo>
<title>Securing Samba</title>
<sect1>
<title>Introduction</title>
<para>
This note was attached to the Samba 2.2.8 release notes as it contained an
important security fix. The information contained here applies to Samba
installations in general.
</para>
</sect1>
<sect1>
<title>Using host based protection</title>
<para>
In many installations of Samba the greatest threat comes for outside
your immediate network. By default Samba will accept connections from
any host, which means that if you run an insecure version of Samba on
a host that is directly connected to the Internet you can be
especially vulnerable.
</para>
<para>
One of the simplest fixes in this case is to use the <command>hosts allow</command> and
<command>hosts deny</command> options in the Samba &smb.conf; configuration file to only
allow access to your server from a specific range of hosts. An example
might be:
</para>
<para><programlisting>
hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
hosts deny = 0.0.0.0/0
</programlisting></para>
<para>
The above will only allow SMB connections from 'localhost' (your own
computer) and from the two private networks 192.168.2 and
192.168.3. All other connections will be refused as soon
as the client sends its first packet. The refusal will be marked as a
'not listening on called name' error.
</para>
</sect1>
<sect1>
<title>Using interface protection</title>
<para>
By default Samba will accept connections on any network interface that
it finds on your system. That means if you have a ISDN line or a PPP
connection to the Internet then Samba will accept connections on those
links. This may not be what you want.
</para>
<para>
You can change this behaviour using options like the following:
</para>
<para><programlisting>
interfaces = eth* lo
bind interfaces only = yes
</programlisting></para>
<para>
This tells Samba to only listen for connections on interfaces with a
name starting with 'eth' such as eth0, eth1, plus on the loopback
interface called 'lo'. The name you will need to use depends on what
OS you are using, in the above I used the common name for Ethernet
adapters on Linux.
</para>
<para>
If you use the above and someone tries to make a SMB connection to
your host over a PPP interface called 'ppp0' then they will get a TCP
connection refused reply. In that case no Samba code is run at all as
the operating system has been told not to pass connections from that
interface to any samba process.
</para>
</sect1>
<sect1>
<title>Using a firewall</title>
<para>
Many people use a firewall to deny access to services that they don't
want exposed outside their network. This can be a very good idea,
although I would recommend using it in conjunction with the above
methods so that you are protected even if your firewall is not active
for some reason.
</para>
<para>
If you are setting up a firewall then you need to know what TCP and
UDP ports to allow and block. Samba uses the following:
</para>
<para><programlisting>
UDP/137 - used by nmbd
UDP/138 - used by nmbd
TCP/139 - used by smbd
TCP/445 - used by smbd
</programlisting></para>
<para>
The last one is important as many older firewall setups may not be
aware of it, given that this port was only added to the protocol in
recent years.
</para>
</sect1>
<sect1>
<title>Using a IPC$ share deny</title>
<para>
If the above methods are not suitable, then you could also place a
more specific deny on the IPC$ share that is used in the recently
discovered security hole. This allows you to offer access to other
shares while denying access to IPC$ from potentially untrustworthy
hosts.
</para>
<para>
To do that you could use:
</para>
<para><programlisting>
[ipc$]
hosts allow = 192.168.115.0/24 127.0.0.1
hosts deny = 0.0.0.0/0
</programlisting></para>
<para>
this would tell Samba that IPC$ connections are not allowed from
anywhere but the two listed places (localhost and a local
subnet). Connections to other shares would still be allowed. As the
IPC$ share is the only share that is always accessible anonymously
this provides some level of protection against attackers that do not
know a username/password for your host.
</para>
<para>
If you use this method then clients will be given a 'access denied'
reply when they try to access the IPC$ share. That means that those
clients will not be able to browse shares, and may also be unable to
access some other resources.
</para>
<para>
This is not recommended unless you cannot use one of the other
methods listed above for some reason.
</para>
</sect1>
<sect1>
<title>NTLMv2 Security</title>
<para>
To configure NTLMv2 authentication the following registry keys are worth knowing about:
</para>
<para>
<programlisting>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"lmcompatibilitylevel"=dword:00000003
0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
use NTLMv2 session security if the server supports it. Domain
controllers accept LM, NTLM and NTLMv2 authentication.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
"NtlmMinClientSec"=dword:00080000
0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
session security is not negotiated.
</programlisting>
</para>
</sect1>
<sect1>
<title>Upgrading Samba</title>
<para>
Please check regularly on <ulink url="http://www.samba.org/">http://www.samba.org/</ulink> for updates and
important announcements. Occasionally security releases are made and
it is highly recommended to upgrade Samba when a security vulnerability
is discovered.
</para>
</sect1>
</chapter>

340
docs/docbook/projdoc/security_level.sgml
View File

@ -1,340 +0,0 @@
<chapter id="securitylevels">
<chapterinfo>
&author.tridge;
&author.jelmer;
</chapterinfo>
<title>Samba as Stand-Alone Server</title>
<para>
In this section the function and purpose of Samba's <emphasis>security</emphasis>
modes are described.
</para>
<sect1>
<title>User and Share security level</title>
<para>
A SMB server tells the client at startup what "security level" it is
running. There are two options "share level" and "user level". Which
of these two the client receives affects the way the client then tries
to authenticate itself. It does not directly affect (to any great
extent) the way the Samba server does security. I know this is
strange, but it fits in with the client/server approach of SMB. In SMB
everything is initiated and controlled by the client, and the server
can only tell the client what is available and whether an action is
allowed.
</para>
<sect2>
<title>User Level Security</title>
<para>
I'll describe user level security first, as its simpler. In user level
security the client will send a "session setup" command directly after
the protocol negotiation. This contains a username and password. The
server can either accept or reject that username/password
combination. Note that at this stage the server has no idea what
share the client will eventually try to connect to, so it can't base
the "accept/reject" on anything other than:
</para>
<orderedlist>
<listitem><para>the username/password</para></listitem>
<listitem><para>the machine that the client is coming from</para></listitem>
</orderedlist>
<para>
If the server accepts the username/password then the client expects to
be able to mount any share (using a "tree connection") without
specifying a password. It expects that all access rights will be as
the username/password specified in the "session setup".
</para>
<para>
It is also possible for a client to send multiple "session setup"
requests. When the server responds it gives the client a "uid" to use
as an authentication tag for that username/password. The client can
maintain multiple authentication contexts in this way (WinDD is an
example of an application that does this)
</para>
</sect2>
<sect2>
<title>Share Level Security</title>
<para>
Ok, now for share level security. In share level security the client
authenticates itself separately for each share. It will send a
password along with each "tree connection" (share mount). It does not
explicitly send a username with this operation. The client is
expecting a password to be associated with each share, independent of
the user. This means that samba has to work out what username the
client probably wants to use. It is never explicitly sent the
username. Some commercial SMB servers such as NT actually associate
passwords directly with shares in share level security, but samba
always uses the unix authentication scheme where it is a
username/password that is authenticated, not a "share/password".
</para>
<para>
Many clients send a "session setup" even if the server is in share
level security. They normally send a valid username but no
password. Samba records this username in a list of "possible
usernames". When the client then does a "tree connection" it also adds
to this list the name of the share they try to connect to (useful for
home directories) and any users listed in the <command>user =</command> &smb.conf;
line. The password is then checked in turn against these "possible
usernames". If a match is found then the client is authenticated as
that user.
</para>
</sect2>
<sect2>
<title>Server Level Security</title>
<para>
Finally "server level" security. In server level security the samba
server reports to the client that it is in user level security. The
client then does a "session setup" as described earlier. The samba
server takes the username/password that the client sends and attempts
to login to the "password server" by sending exactly the same
username/password that it got from the client. If that server is in
user level security and accepts the password then samba accepts the
clients connection. This allows the samba server to use another SMB
server as the "password server".
</para>
<para>
You should also note that at the very start of all this, where the
server tells the client what security level it is in, it also tells
the client if it supports encryption. If it does then it supplies the
client with a random "cryptkey". The client will then send all
passwords in encrypted form. You have to compile samba with encryption
enabled to support this feature, and you have to maintain a separate
smbpasswd file with SMB style encrypted passwords. It is
cryptographically impossible to translate from unix style encryption
to SMB style encryption, although there are some fairly simple management
schemes by which the two could be kept in sync.
</para>
<para>
"security = server" means that Samba reports to clients that
it is running in "user mode" but actually passes off all authentication
requests to another "user mode" server. This requires an additional
parameter "password server =" that points to the real authentication server.
That real authentication server can be another Samba server or can be a
Windows NT server, the later natively capable of encrypted password support.
</para>
<note><para>
<emphasis>Server</emphasis> level security is incompatible with what is known
as <emphasis>schannel</emphasis> or "sign and seal" protocols. This means that
if you want to use <emphasis>server</emphasis> level security you must disable
the use of "sign and seal" on all machines on your network.
</para></note>
<sect3>
<title>Configuring Samba for Seemless Windows Network Integration</title>
<para>
MS Windows clients may use encrypted passwords as part of a challenege/response
authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple
password based authentication. It should be realized that with the SMB protocol
the password is passed over the network either in plain text or encrypted, but
not both in the same authentication request.
</para>
<para>
When encrypted passwords are used a password that has been entered by the user
is encrypted in two ways:
</para>
<itemizedlist>
<listitem><para>An MD4 hash of the UNICODE of the password
string. This is known as the NT hash.
</para></listitem>
<listitem><para>The password is converted to upper case,
and then padded or trucated to 14 bytes. This string is
then appended with 5 bytes of NULL characters and split to
form two 56 bit DES keys to encrypt a "magic" 8 byte value.
The resulting 16 bytes for the LanMan hash.
</para></listitem>
</itemizedlist>
<para>
MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0
pre-service pack 3 will use either mode of password authentication. All
versions of MS Windows that follow these versions no longer support plain
text passwords by default.
</para>
<para>
MS Windows clients have a habit of dropping network mappings that have been idle
for 10 minutes or longer. When the user attempts to use the mapped drive
connection that has been dropped, the client re-establishes the connection using
a cached copy of the password.
</para>
<para>
When Microsoft changed the default password mode, support was dropped for caching
of the plain text password. This means that when the registry parameter is changed
to re-enable use of plain text passwords it appears to work, but when a dropped
service connection mapping attempts to revalidate it will fail if the remote
authentication server does not support encrypted passwords. This means that it
is definitely not a good idea to re-enable plain text password support in such clients.
</para>
<para>
The following parameters can be used to work around the issue of Windows 9x client
upper casing usernames and password before transmitting them to the SMB server
when using clear text authentication.
</para>
<para><programlisting>
<ulink url="smb.conf.5.html#PASSWORDLEVEL">passsword level</ulink> = <replaceable>integer</replaceable>
<ulink url="smb.conf.5.html#USERNAMELEVEL">username level</ulink> = <replaceable>integer</replaceable>
</programlisting></para>
<para>
By default Samba will lower case the username before attempting to lookup the user
in the database of local system accounts. Because UNIX usernames conventionally
only contain lower case character, the <parameter>username level</parameter> parameter
is rarely needed.
</para>
<para>
However, passwords on UNIX systems often make use of mixed case characters.
This means that in order for a user on a Windows 9x client to connect to a Samba
server using clear text authentication, the <parameter>password level</parameter>
must be set to the maximum number of upper case letter which <emphasis>could</emphasis>
appear is a password. Note that the server OS uses the traditional DES version
of crypt(), a <parameter>password level</parameter> of 8 will result in case
insensitive passwords as seen from Windows users. This will also result in longer
login times as Samba has to compute the permutations of the password string and
try them one by one until a match is located (or all combinations fail).
</para>
<para>
The best option to adopt is to enable support for encrypted passwords
where ever Samba is used. There are three configuration possibilities
for support of encrypted passwords:
</para>
</sect3>
<sect3>
<title>Use MS Windows NT as an authentication server</title>
<para>
This method involves the additions of the following parameters in the &smb.conf; file:
</para>
<para><programlisting>
encrypt passwords = Yes
security = server
password server = "NetBIOS_name_of_PDC"
</programlisting></para>
<para>
There are two ways of identifying whether or not a username and
password pair was valid or not. One uses the reply information provided
as part of the authentication messaging process, the other uses
just an error code.
</para>
<para>
The down-side of this mode of configuration is the fact that
for security reasons Samba will send the password server a bogus
username and a bogus password and if the remote server fails to
reject the username and password pair then an alternative mode
of identification of validation is used. Where a site uses password
lock out after a certain number of failed authentication attempts
this will result in user lockouts.
</para>
<para>
Use of this mode of authentication does require there to be
a standard Unix account for the user, this account can be blocked
to prevent logons by other than MS Windows clients.
</para>
</sect3>
</sect2>
<sect2>
<title>Domain Level Security</title>
<para>
When samba is operating in <emphasis>security = domain</emphasis> mode this means that
the Samba server has a domain security trust account (a machine account) and will cause
all authentication requests to be passed through to the domain controllers.
</para>
<sect3>
<title>Samba as a member of an MS Windows NT security domain</title>
<para>
This method involves addition of the following parameters in the &smb.conf; file:
</para>
<para><programlisting>
encrypt passwords = Yes
security = domain
workgroup = "name of NT domain"
password server = *
</programlisting></para>
<para>
The use of the "*" argument to <command>password server</command> will cause samba to locate the
domain controller in a way analogous to the way this is done within MS Windows NT.
This is the default behaviour.
</para>
<para>
In order for this method to work the Samba server needs to join the
MS Windows NT security domain. This is done as follows:
</para>
<itemizedlist>
<listitem><para>On the MS Windows NT domain controller using
the Server Manager add a machine account for the Samba server.
</para></listitem>
<listitem><para>Next, on the Linux system execute:
<command>smbpasswd -r PDC_NAME -j DOMAIN_NAME</command> (samba 2.x)
<command>net join -U administrator%password</command> (samba-3)
</para></listitem>
</itemizedlist>
<para>
Use of this mode of authentication does require there to be a standard Unix account
for the user in order to assign a uid once the account has been authenticated by
the remote Windows DC. This account can be blocked to prevent logons by clients other than
MS Windows through things such as setting an invalid shell in the
<filename>/etc/passwd</filename> entry.
</para>
<para>
An alternative to assigning UIDs to Windows users on a Samba member server is
presented in the <ulink url="winbind.html">Winbind Overview</ulink> chapter
in this HOWTO collection.
</para>
</sect3>
</sect2>
<sect2>
<title>ADS Level Security</title>
<para>
For information about the configuration option please refer to the entire section entitled
<emphasis>Samba as an ADS Domain Member.</emphasis>
</para>
</sect2>
</sect1>
</chapter>

128
docs/docbook/projdoc/unicode.sgml
View File

@ -1,128 +0,0 @@
<chapter id="unicode">
<chapterinfo>
&author.jelmer;
<author>
<firstname>TAKAHASHI</firstname><surname>Motonobu</surname>
<affiliation>
<address><email>monyo@home.monyo.com</email></address>
</affiliation>
</author>
<pubdate>25 March 2003</pubdate>
</chapterinfo>
<title>Unicode/Charsets</title>
<sect1>
<title>What are charsets and unicode?</title>
<para>
Computers communicate in numbers. In texts, each number will be
translated to a corresponding letter. The meaning that will be assigned
to a certain number depends on the <emphasis>character set(charset)
</emphasis> that is used.
A charset can be seen as a table that is used to translate numbers to
letters. Not all computers use the same charset (there are charsets
with German umlauts, Japanese characters, etc). Usually a charset contains
256 characters, which means that storing a character with it takes
exactly one byte. </para>
<para>
There are also charsets that support even more characters,
but those need twice(or even more) as much storage space. These
charsets can contain <command>256 * 256 = 65536</command> characters, which
is more then all possible characters one could think of. They are called
multibyte charsets (because they use more then one byte to
store one character).
</para>
<para>
A standardised multibyte charset is unicode, info is available at
<ulink url="http://www.unicode.org/">www.unicode.org</ulink>.
A big advantage of using a multibyte charset is that you only need one; no
need to make sure two computers use the same charset when they are
communicating.
</para>
<para>Old windows clients used to use single-byte charsets, named
'codepages' by microsoft. However, there is no support for
negotiating the charset to be used in the smb protocol. Thus, you
have to make sure you are using the same charset when talking to an old client.
Newer clients (Windows NT, 2K, XP) talk unicode over the wire.
</para>
</sect1>
<sect1>
<title>Samba and charsets</title>
<para>
As of samba 3.0, samba can (and will) talk unicode over the wire. Internally,
samba knows of three kinds of character sets:
</para>
<variablelist>
<varlistentry>
<term>unix charset</term>
<listitem><para>
This is the charset used internally by your operating system.
The default is <constant>ASCII</constant>, which is fine for most
systems.
</para></listitem>
</varlistentry>
<varlistentry>
<term>display charset</term>
<listitem><para>This is the charset samba will use to print messages
on your screen. It should generally be the same as the <command>unix charset</command>.
</para></listitem>
</varlistentry>
<varlistentry>
<term>dos charset</term>
<listitem><para>This is the charset samba uses when communicating with
DOS and Windows 9x clients. It will talk unicode to all newer clients.
The default depends on the charsets you have installed on your system.
Run <command>testparm -v | grep "dos charset"</command> to see
what the default is on your system.
</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1>
<title>Conversion from old names</title>
<para>Because previous samba versions did not do any charset conversion,
characters in filenames are usually not correct in the unix charset but only
for the local charset used by the DOS/Windows clients.</para>
<para>The following script from Steve Langasek converts all
filenames from CP850 to the iso8859-15 charset.</para>
<para>
<prompt>#</prompt><userinput>find <replaceable>/path/to/share</replaceable> -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \
-t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;
</userinput>
</para>
</sect1>
<sect1>
<title>Japanese charsets</title>
<para>Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:</para>
<simplelist>
<member>You should set <command>mangling method = hash</command></member>
<member>There are various iconv() implementations around and not all of
them work equally well. glibc2's iconv() has a critical problem in CP932.
libiconv-1.8 works with CP932 but still has some problems and does not
work with EUC-JP. </member>
<member>You should set <command>dos charset = CP932</command>, not Shift_JIS, SJIS...</member>
<member>Currently only <command>unix charset = CP932</command> will work (but still has some problems...) because of iconv() issues. <command>unix charset = EUC-JP</command> doesn't work well because of iconv() issues.</member>
<member>Currently Samba 3.0 does not support <command>unix charset = UTF8-MAC/CAP/HEX/JIS*</command></member>
</simplelist>
<para>More information (in Japanese) is available at: <ulink url="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html">http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</ulink>.</para>
</sect1>
</chapter>

41
docs/docbook/projdoc/upgrading-to-3.0.sgml
View File

@ -1,41 +0,0 @@
<chapter id="upgrading-to-3.0">
<chapterinfo>
&author.jelmer;
<pubdate>25 October 2002</pubdate>
</chapterinfo>
<title>Issues when upgrading from 2.2 to 3.0</title>
<sect1>
<title>Charsets</title>
<para>You might experience problems with special characters
when communicating with old DOS clients. Codepage
support has changed in samba 3.0. Read the chapter
<link linkend="unicode">Unicode support</link> for details.
</para>
</sect1>
<sect1>
<title>add machine script</title>
</sect1>
<sect1>
<title>Obsolete configuration options</title>
<para>
In 3.0, the following configuration options have been removed.
</para>
<simplelist>
<member>printer driver (replaced by new driver procedures) </member>
<member>printer driver file (replaced by new driver procedures)</member>
<member>printer driver location (replaced by new driver procedures)</member>
<member>use rhosts</member>
<member>postscript</member>
<member>client code page (replaced by dos charset)</member>
</simplelist>
</sect1>
</chapter>

1136
docs/docbook/projdoc/winbind.sgml
View File

File diff suppressed because it is too large Load Diff