mirror of
https://github.com/samba-team/samba.git
synced 2025-02-21 01:59:07 +03:00
566 lines
12 KiB
HTML
566 lines
12 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>How to Install and Test SAMBA</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="SAMBA Project Documentation"
|
|
HREF="samba-howto-collection.html"><LINK
|
|
REL="UP"
|
|
TITLE="General installation"
|
|
HREF="introduction.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="General installation"
|
|
HREF="introduction.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
|
|
HREF="browsing-quick.html"></HEAD
|
|
><BODY
|
|
CLASS="CHAPTER"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>SAMBA Project Documentation</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="introduction.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="browsing-quick.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="CHAPTER"
|
|
><H1
|
|
><A
|
|
NAME="INSTALL"
|
|
></A
|
|
>Chapter 1. How to Install and Test SAMBA</H1
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="AEN65"
|
|
>1.1. Obtaining and installing samba</A
|
|
></H1
|
|
><P
|
|
>Binary packages of samba are included in almost any Linux or
|
|
Unix distribution. There are also some packages available at
|
|
<A
|
|
HREF="http://samba.org/"
|
|
TARGET="_top"
|
|
>the samba homepage</A
|
|
>.
|
|
</P
|
|
><P
|
|
>If you need to compile samba from source, check the
|
|
<A
|
|
HREF="compiling.html"
|
|
>appropriate appendix chapter</A
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="AEN71"
|
|
>1.2. Configuring samba</A
|
|
></H1
|
|
><P
|
|
>Samba's configuration is stored in the smb.conf file,
|
|
that usually resides in <TT
|
|
CLASS="FILENAME"
|
|
>/etc/samba/smb.conf</TT
|
|
>
|
|
or <TT
|
|
CLASS="FILENAME"
|
|
>/usr/local/samba/lib/smb.conf</TT
|
|
>. 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.</P
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN76"
|
|
>1.2.1. Editing the <TT
|
|
CLASS="FILENAME"
|
|
>smb.conf</TT
|
|
> file</A
|
|
></H2
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>The simplest useful configuration file would be
|
|
something like this:</P
|
|
><P
|
|
><PRE
|
|
CLASS="PROGRAMLISTING"
|
|
>[global]
|
|
workgroup = MYGROUP
|
|
|
|
[homes]
|
|
guest ok = no
|
|
read only = no
|
|
</PRE
|
|
></P
|
|
><P
|
|
>which would allow connections by anyone with an
|
|
account on the server, using either their login name or
|
|
"<B
|
|
CLASS="COMMAND"
|
|
>homes</B
|
|
>" as the service name. (Note that I also set the
|
|
workgroup that Samba is part of. See BROWSING.txt for details)</P
|
|
><P
|
|
>Make sure you put the <TT
|
|
CLASS="FILENAME"
|
|
>smb.conf</TT
|
|
> file in the same place
|
|
you specified in the<TT
|
|
CLASS="FILENAME"
|
|
>Makefile</TT
|
|
> (the default is to
|
|
look for it in <TT
|
|
CLASS="FILENAME"
|
|
>/usr/local/samba/lib/</TT
|
|
>).</P
|
|
><P
|
|
>For more information about security settings for the
|
|
<B
|
|
CLASS="COMMAND"
|
|
>[homes]</B
|
|
> share please refer to the chapter
|
|
<A
|
|
HREF="securing-samba.html"
|
|
>Securing Samba</A
|
|
>.</P
|
|
><DIV
|
|
CLASS="SECT3"
|
|
><H3
|
|
CLASS="SECT3"
|
|
><A
|
|
NAME="AEN92"
|
|
>1.2.1.1. Test your config file with
|
|
<B
|
|
CLASS="COMMAND"
|
|
>testparm</B
|
|
></A
|
|
></H3
|
|
><P
|
|
>It's important that you test the validity of your
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>smb.conf</TT
|
|
> file using the <SPAN
|
|
CLASS="APPLICATION"
|
|
>testparm</SPAN
|
|
> program.
|
|
If testparm runs OK then it will list the loaded services. If
|
|
not it will give an error message.</P
|
|
><P
|
|
>Make sure it runs OK and that the services look
|
|
reasonable before proceeding. </P
|
|
><P
|
|
>Always run testparm again when you change
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>smb.conf</TT
|
|
>!</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN101"
|
|
>1.2.2. SWAT</A
|
|
></H2
|
|
><P
|
|
> 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 seperate package. Please read the swat manpage
|
|
on compiling, installing and configuring swat from source.
|
|
</P
|
|
><P
|
|
>To launch SWAT just run your favorite web browser and
|
|
point it at "http://localhost:901/". Replace <VAR
|
|
CLASS="REPLACEABLE"
|
|
>localhost</VAR
|
|
> with the name of the computer you are running samba on if you
|
|
are running samba on a different computer then your browser.</P
|
|
><P
|
|
>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. </P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="AEN107"
|
|
>1.3. Try listing the shares available on your
|
|
server</A
|
|
></H1
|
|
><P
|
|
><SAMP
|
|
CLASS="PROMPT"
|
|
>$ </SAMP
|
|
><KBD
|
|
CLASS="USERINPUT"
|
|
>smbclient -L
|
|
<VAR
|
|
CLASS="REPLACEABLE"
|
|
>yourhostname</VAR
|
|
></KBD
|
|
></P
|
|
><P
|
|
>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).</P
|
|
><P
|
|
>If you choose user level security then you may find
|
|
that Samba requests a password before it will list the shares.
|
|
See the <B
|
|
CLASS="COMMAND"
|
|
>smbclient</B
|
|
> 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)</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="AEN116"
|
|
>1.4. Try connecting with the unix client</A
|
|
></H1
|
|
><P
|
|
><SAMP
|
|
CLASS="PROMPT"
|
|
>$ </SAMP
|
|
><KBD
|
|
CLASS="USERINPUT"
|
|
>smbclient <VAR
|
|
CLASS="REPLACEABLE"
|
|
> //yourhostname/aservice</VAR
|
|
></KBD
|
|
></P
|
|
><P
|
|
>Typically the <VAR
|
|
CLASS="REPLACEABLE"
|
|
>yourhostname</VAR
|
|
>
|
|
would be the name of the host where you installed <SPAN
|
|
CLASS="APPLICATION"
|
|
>smbd</SPAN
|
|
>.
|
|
The <VAR
|
|
CLASS="REPLACEABLE"
|
|
>aservice</VAR
|
|
> is
|
|
any service you have defined in the <TT
|
|
CLASS="FILENAME"
|
|
>smb.conf</TT
|
|
>
|
|
file. Try your user name if you just have a <B
|
|
CLASS="COMMAND"
|
|
>[homes]</B
|
|
>
|
|
section
|
|
in <TT
|
|
CLASS="FILENAME"
|
|
>smb.conf</TT
|
|
>.</P
|
|
><P
|
|
>For example if your unix host is <VAR
|
|
CLASS="REPLACEABLE"
|
|
>bambi</VAR
|
|
>
|
|
and your login name is <VAR
|
|
CLASS="REPLACEABLE"
|
|
>fred</VAR
|
|
> you would type:</P
|
|
><P
|
|
><SAMP
|
|
CLASS="PROMPT"
|
|
>$ </SAMP
|
|
><KBD
|
|
CLASS="USERINPUT"
|
|
>smbclient //<VAR
|
|
CLASS="REPLACEABLE"
|
|
>bambi</VAR
|
|
>/<VAR
|
|
CLASS="REPLACEABLE"
|
|
>fred</VAR
|
|
>
|
|
</KBD
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="AEN137"
|
|
>1.5. Try connecting from a DOS, WfWg, Win9x, WinNT,
|
|
Win2k, OS/2, etc... client</A
|
|
></H1
|
|
><P
|
|
>Try mounting disks. eg:</P
|
|
><P
|
|
><SAMP
|
|
CLASS="PROMPT"
|
|
>C:\WINDOWS\> </SAMP
|
|
><KBD
|
|
CLASS="USERINPUT"
|
|
>net use d: \\servername\service
|
|
</KBD
|
|
></P
|
|
><P
|
|
>Try printing. eg:</P
|
|
><P
|
|
><SAMP
|
|
CLASS="PROMPT"
|
|
>C:\WINDOWS\> </SAMP
|
|
><KBD
|
|
CLASS="USERINPUT"
|
|
>net use lpt1:
|
|
\\servername\spoolservice</KBD
|
|
></P
|
|
><P
|
|
><SAMP
|
|
CLASS="PROMPT"
|
|
>C:\WINDOWS\> </SAMP
|
|
><KBD
|
|
CLASS="USERINPUT"
|
|
>print filename
|
|
</KBD
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="AEN150"
|
|
>1.6. What If Things Don't Work?</A
|
|
></H1
|
|
><P
|
|
>Then you might read the file chapter
|
|
<A
|
|
HREF="diagnosis.html"
|
|
>Diagnosis</A
|
|
> and the
|
|
FAQ. If you are still stuck then try the mailing list or
|
|
newsgroup (look in the README for details). Samba has been
|
|
successfully installed at thousands of sites worldwide, so maybe
|
|
someone else has hit your problem and has overcome it. You could
|
|
also use the WWW site to scan back issues of the samba-digest.</P
|
|
><P
|
|
>When you fix the problem <SPAN
|
|
CLASS="emphasis"
|
|
><I
|
|
CLASS="EMPHASIS"
|
|
>please</I
|
|
></SPAN
|
|
> send some
|
|
updates of the documentation (or source code) to one of
|
|
the documentation maintainers or the list.
|
|
</P
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN156"
|
|
>1.6.1. Scope IDs</A
|
|
></H2
|
|
><P
|
|
>By default Samba uses a blank scope ID. This means
|
|
all your windows boxes must also have a blank scope ID.
|
|
If you really want to use a non-blank scope ID then you will
|
|
need to use the 'netbios scope' smb.conf option.
|
|
All your PCs will need to have the same setting for
|
|
this to work. I do not recommend scope IDs.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN159"
|
|
>1.6.2. Locking</A
|
|
></H2
|
|
><P
|
|
>One area which sometimes causes trouble is locking.</P
|
|
><P
|
|
>There are two types of locking which need to be
|
|
performed by a SMB server. The first is "record locking"
|
|
which allows a client to lock a range of bytes in a open file.
|
|
The second is the "deny modes" that are specified when a file
|
|
is open.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>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.</P
|
|
><P
|
|
>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 "strict locking = yes" then it will
|
|
make lock checking calls on every read and write. </P
|
|
><P
|
|
>You can also disable by range locking completely
|
|
using "locking = no". 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.</P
|
|
><P
|
|
>The second class of locking is the "deny modes". 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.</P
|
|
></DIV
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="introduction.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="samba-howto-collection.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="browsing-quick.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>General installation</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="introduction.html"
|
|
ACCESSKEY="U"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |