1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-04 05:18:06 +03:00

Convert GOTCHAS to SGML

This commit is contained in:
Jelmer Vernooij 0001-01-01 00:00:00 +00:00
parent 5e96448348
commit c48207ef0e
23 changed files with 795 additions and 340 deletions

Binary file not shown.

View File

@ -145,4 +145,27 @@ You should then remove the line:
<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>
</chapter>

View File

@ -5,11 +5,10 @@
>Reporting Bugs</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="BUGREPORT">Chapter 19. Reporting Bugs</H1
NAME="BUGREPORT"
></A
>Chapter 20. Reporting Bugs</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3029">19.1. Introduction</H1
NAME="AEN3111"
></A
>20.1. Introduction</H1
><P
>The email address for bug reports is samba@samba.org</P
><P
@ -106,7 +109,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3036">19.2. General info</H1
NAME="AEN3118"
></A
>20.2. General info</H1
><P
>Before submitting a bug report check your config for silly
errors. Look in your log files for obvious messages that tell you that
@ -129,7 +134,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3042">19.3. Debug levels</H1
NAME="AEN3124"
></A
>20.3. Debug levels</H1
><P
>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
@ -197,7 +204,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3059">19.4. Internal errors</H1
NAME="AEN3141"
></A
>20.4. Internal errors</H1
><P
>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
@ -239,7 +248,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3069">19.5. Attaching to a running process</H1
NAME="AEN3151"
></A
>20.5. Attaching to a running process</H1
><P
>Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
@ -254,7 +265,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3072">19.6. Patches</H1
NAME="AEN3154"
></A
>20.6. Patches</H1
><P
>The best sort of bug report is one that includes a fix! If you send us
patches please use <B
@ -294,7 +307,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>HOWTO Access Samba source code via CVS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="CVS-ACCESS">Chapter 18. HOWTO Access Samba source code via CVS</H1
NAME="CVS-ACCESS"
></A
>Chapter 19. HOWTO Access Samba source code via CVS</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2981">18.1. Introduction</H1
NAME="AEN3063"
></A
>19.1. Introduction</H1
><P
>Samba is developed in an open environment. Developers use CVS
(Concurrent Versioning System) to "checkin" (also known as
@ -96,7 +99,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2986">18.2. CVS Access to samba.org</H1
NAME="AEN3068"
></A
>19.2. CVS Access to samba.org</H1
><P
>The machine samba.org runs a publicly accessible CVS
repository for access to the source code of several packages,
@ -107,7 +112,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2989">18.2.1. Access via CVSweb</H2
NAME="AEN3071"
></A
>19.2.1. Access via CVSweb</H2
><P
>You can access the source code via your
favourite WWW browser. This allows you to access the contents of
@ -126,7 +133,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2994">18.2.2. Access via cvs</H2
NAME="AEN3076"
></A
>19.2.2. Access via cvs</H2
><P
>You can also access the source code via a
normal cvs client. This gives you much more control over you can
@ -253,7 +262,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Diagnosing your samba server</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="How to Install and Test SAMBA"
HREF="install.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="DIAGNOSIS">Chapter 2. Diagnosing your samba server</H1
NAME="DIAGNOSIS"
></A
>Chapter 2. Diagnosing your samba server</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN223">2.1. Introduction</H1
NAME="AEN223"
></A
>2.1. Introduction</H1
><P
>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
@ -96,7 +99,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN228">2.2. Assumptions</H1
NAME="AEN228"
></A
>2.2. Assumptions</H1
><P
>In all of the tests I assume you have a Samba server called BIGSERVER
and a PC called ACLIENT both in workgroup TESTGROUP. I also assume the
@ -135,13 +140,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN238">2.3. Tests</H1
NAME="AEN238"
></A
>2.3. Tests</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN240">2.3.1. Test 1</H2
NAME="AEN240"
></A
>2.3.1. Test 1</H2
><P
>In the directory in which you store your smb.conf file, run the command
"testparm smb.conf". If it reports any errors then your smb.conf
@ -161,7 +170,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN246">2.3.2. Test 2</H2
NAME="AEN246"
></A
>2.3.2. Test 2</H2
><P
>Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
the unix box. If you don't get a valid response then your TCP/IP
@ -185,7 +196,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN252">2.3.3. Test 3</H2
NAME="AEN252"
></A
>2.3.3. Test 3</H2
><P
>Run the command "smbclient -L BIGSERVER" on the unix box. You
should get a list of available shares back. </P
@ -254,7 +267,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN267">2.3.4. Test 4</H2
NAME="AEN267"
></A
>2.3.4. Test 4</H2
><P
>Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
IP address of your Samba server back.</P
@ -273,7 +288,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN272">2.3.5. Test 5</H2
NAME="AEN272"
></A
>2.3.5. Test 5</H2
><P
>run the command <B
CLASS="COMMAND"
@ -292,7 +309,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN278">2.3.6. Test 6</H2
NAME="AEN278"
></A
>2.3.6. Test 6</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -324,7 +343,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN286">2.3.7. Test 7</H2
NAME="AEN286"
></A
>2.3.7. Test 7</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -411,7 +432,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN312">2.3.8. Test 8</H2
NAME="AEN312"
></A
>2.3.8. Test 8</H2
><P
>On the PC type the command <B
CLASS="COMMAND"
@ -469,7 +492,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN329">2.3.9. Test 9</H2
NAME="AEN329"
></A
>2.3.9. Test 9</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -484,14 +509,26 @@ and other config lines in smb.conf are correct.</P
connect you as. To see if this is the problem add the line "user =
USERNAME" to the [tmp] section of smb.conf where "USERNAME" is the
username corresponding to the password you typed. If you find this
fixes things you may need the username mapping option.</P
fixes things you may need the username mapping option. </P
><P
>It might also be the case that your client only sends encrypted passwords
and you have <B
CLASS="COMMAND"
>encrypt passwords = no</B
> in <TT
CLASS="FILENAME"
>smb.conf</TT
>.
Turn it back on to fix.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN334">2.3.10. Test 10</H2
NAME="AEN337"
></A
>2.3.10. Test 10</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -515,7 +552,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN340">2.3.11. Test 11</H2
NAME="AEN343"
></A
>2.3.11. Test 11</H2
><P
>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
@ -541,7 +580,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN345">2.4. Still having troubles?</H1
NAME="AEN348"
></A
>2.4. Still having troubles?</H1
><P
>Try the mailing list or newsgroup, or use the ethereal utility to
sniff the problem. The official samba mailing list can be reached at
@ -586,7 +627,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>security = domain in Samba 2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Security levels"
HREF="securitylevels.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="DOMAIN-SECURITY">Chapter 10. security = domain in Samba 2.x</H1
NAME="DOMAIN-SECURITY"
></A
>Chapter 10. security = domain in Samba 2.x</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1272">10.1. Joining an NT Domain with Samba 2.2</H1
NAME="AEN1275"
></A
>10.1. Joining an NT Domain with Samba 2.2</H1
><P
>Assume you have a Samba 2.x server with a NetBIOS name of
<TT
@ -305,7 +308,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1336">10.2. Samba and Windows 2000 Domains</H1
NAME="AEN1339"
></A
>10.2. Samba and Windows 2000 Domains</H1
><P
>Many people have asked regarding the state of Samba's ability to participate in
a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows
@ -328,7 +333,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1341">10.3. Why is this better than security = server?</H1
NAME="AEN1344"
></A
>10.3. Why is this better than security = server?</H1
><P
>Currently, domain security in Samba doesn't free you from
having to create local Unix users to represent the users attaching
@ -437,7 +444,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Group mapping HOWTO</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Reporting Bugs"
HREF="bugreport.html"><LINK
@ -70,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="GROUPMAPPING">Chapter 20. Group mapping HOWTO</H1
NAME="GROUPMAPPING"
></A
>Chapter 21. Group mapping HOWTO</H1
><P
>
Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
@ -190,7 +191,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,14 +5,13 @@
>Improved browsing in samba</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
HREF="samba-ldap-howto.html"><LINK
TITLE="Using samba 3.0 with ActiveDirectory support"
HREF="ads.html"><LINK
REL="NEXT"
TITLE="Samba performance issues"
HREF="speed.html"></HEAD
@ -43,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="samba-ldap-howto.html"
HREF="ads.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="IMPROVED-BROWSING">Chapter 15. Improved browsing in samba</H1
NAME="IMPROVED-BROWSING"
></A
>Chapter 16. Improved browsing in samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2577">15.1. Overview of browsing</H1
NAME="AEN2659"
></A
>16.1. Overview of browsing</H1
><P
>SMB networking provides a mechanism by which clients can access a list
of machines in a network, a so-called "browse list". This list
@ -98,7 +101,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2581">15.2. Browsing support in samba</H1
NAME="AEN2663"
></A
>16.2. Browsing support in samba</H1
><P
>Samba now fully supports browsing. The browsing is supported by nmbd
and is also controlled by options in the smb.conf file (see smb.conf(5)).</P
@ -141,7 +146,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2590">15.3. Problem resolution</H1
NAME="AEN2672"
></A
>16.3. Problem resolution</H1
><P
>If something doesn't work then hopefully the log.nmb file will help
you track down the problem. Try a debug level of 2 or 3 for finding
@ -173,7 +180,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2597">15.4. Browsing across subnets</H1
NAME="AEN2679"
></A
>16.4. Browsing across subnets</H1
><P
>With the release of Samba 1.9.17(alpha1 and above) Samba has been
updated to enable it to support the replication of browse lists
@ -202,7 +211,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2602">15.4.1. How does cross subnet browsing work ?</H2
NAME="AEN2684"
></A
>16.4.1. How does cross subnet browsing work ?</H2
><P
>Cross subnet browsing is a complicated dance, containing multiple
moving parts. It has taken Microsoft several years to get the code
@ -412,7 +423,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2637">15.5. Setting up a WINS server</H1
NAME="AEN2719"
></A
>16.5. Setting up a WINS server</H1
><P
>Either a Samba machine or a Windows NT Server machine may be set up
as a WINS server. To set a Samba machine to be a WINS server you must
@ -493,7 +506,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2656">15.6. Setting up Browsing in a WORKGROUP</H1
NAME="AEN2738"
></A
>16.6. Setting up Browsing in a WORKGROUP</H1
><P
>To set up cross subnet browsing on a network containing machines
in up to be in a WORKGROUP, not an NT Domain you need to set up one
@ -575,7 +590,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2674">15.7. Setting up Browsing in a DOMAIN</H1
NAME="AEN2756"
></A
>16.7. Setting up Browsing in a DOMAIN</H1
><P
>If you are adding Samba servers to a Windows NT Domain then
you must not set up a Samba server as a domain master browser.
@ -624,7 +641,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2684">15.8. Forcing samba to be the master</H1
NAME="AEN2766"
></A
>16.8. Forcing samba to be the master</H1
><P
>Who becomes the "master browser" is determined by an election process
using broadcasts. Each election packet contains a number of parameters
@ -670,7 +689,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2693">15.9. Making samba the domain master</H1
NAME="AEN2775"
></A
>16.9. Making samba the domain master</H1
><P
>The domain master is responsible for collating the browse lists of
multiple subnets so that browsing can occur between subnets. You can
@ -741,7 +762,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2711">15.10. Note about broadcast addresses</H1
NAME="AEN2793"
></A
>16.10. Note about broadcast addresses</H1
><P
>If your network uses a "0" based broadcast address (for example if it
ends in a 0) then you will strike problems. Windows for Workgroups
@ -753,7 +776,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2714">15.11. Multiple interfaces</H1
NAME="AEN2796"
></A
>16.11. Multiple interfaces</H1
><P
>Samba now supports machines with multiple network interfaces. If you
have multiple interfaces then you will need to use the "interfaces"
@ -776,7 +801,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="samba-ldap-howto.html"
HREF="ads.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -785,7 +810,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD
@ -804,7 +829,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Storing Samba's User/Machine Account information in an LDAP Directory</TD
>Using samba 3.0 with ActiveDirectory support</TD
><TD
WIDTH="34%"
ALIGN="center"

View File

@ -5,14 +5,13 @@
>How to Install and Test SAMBA</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="NEXT"
TITLE="Diagnosing your samba server"
HREF="diagnosis.html"></HEAD
@ -43,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="INSTALL">Chapter 1. How to Install and Test SAMBA</H1
NAME="INSTALL"
></A
>Chapter 1. How to Install and Test SAMBA</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN20">1.1. Step 0: Read the man pages</H1
NAME="AEN20"
></A
>1.1. Step 0: Read the man pages</H1
><P
>The man pages distributed with SAMBA contain
lots of useful info that will help to get you started.
@ -106,7 +109,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN28">1.2. Step 1: Building the Binaries</H1
NAME="AEN28"
></A
>1.2. Step 1: Building the Binaries</H1
><P
>To do this, first run the program <B
CLASS="COMMAND"
@ -203,7 +208,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN56">1.3. Step 2: The all important step</H1
NAME="AEN56"
></A
>1.3. Step 2: The all important step</H1
><P
>At this stage you must fetch yourself a
coffee or other drink you find stimulating. Getting the rest
@ -218,7 +225,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN60">1.4. Step 3: Create the smb configuration file.</H1
NAME="AEN60"
></A
>1.4. Step 3: Create the smb configuration file.</H1
><P
>There are sample configuration files in the examples
subdirectory in the distribution. I suggest you read them
@ -272,7 +281,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN74">1.5. Step 4: Test your config file with
NAME="AEN74"
></A
>1.5. Step 4: Test your config file with
<B
CLASS="COMMAND"
>testparm</B
@ -294,7 +305,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN80">1.6. Step 5: Starting the smbd and nmbd</H1
NAME="AEN80"
></A
>1.6. Step 5: Starting the smbd and nmbd</H1
><P
>You must choose to start smbd and nmbd either
as daemons or from <B
@ -332,7 +345,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN90">1.6.1. Step 5a: Starting from inetd.conf</H2
NAME="AEN90"
></A
>1.6.1. Step 5a: Starting from inetd.conf</H2
><P
>NOTE; The following will be different if
you use NIS or NIS+ to distributed services maps.</P
@ -434,7 +449,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN119">1.6.2. Step 5b. Alternative: starting it as a daemon</H2
NAME="AEN119"
></A
>1.6.2. Step 5b. Alternative: starting it as a daemon</H2
><P
>To start the server as a daemon you should create
a script something like this one, perhaps calling
@ -489,7 +506,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN135">1.7. Step 6: Try listing the shares available on your
NAME="AEN135"
></A
>1.7. Step 6: Try listing the shares available on your
server</H1
><P
><TT
@ -528,7 +547,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN144">1.8. Step 7: Try connecting with the unix client</H1
NAME="AEN144"
></A
>1.8. Step 7: Try connecting with the unix client</H1
><P
><TT
CLASS="PROMPT"
@ -589,7 +610,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN160">1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
NAME="AEN160"
></A
>1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
Win2k, OS/2, etc... client</H1
><P
>Try mounting disks. eg:</P
@ -636,7 +659,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN174">1.10. What If Things Don't Work?</H1
NAME="AEN174"
></A
>1.10. What If Things Don't Work?</H1
><P
>If nothing works and you start to think "who wrote
this pile of trash" then I suggest you do step 2 again (and
@ -657,7 +682,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN179">1.10.1. Diagnosing Problems</H2
NAME="AEN179"
></A
>1.10.1. Diagnosing Problems</H2
><P
>If you have installation problems then go to
<TT
@ -671,7 +698,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN183">1.10.2. Scope IDs</H2
NAME="AEN183"
></A
>1.10.2. Scope IDs</H2
><P
>By default Samba uses a blank scope ID. This means
all your windows boxes must also have a blank scope ID.
@ -685,7 +714,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN186">1.10.3. Choosing the Protocol Level</H2
NAME="AEN186"
></A
>1.10.3. Choosing the Protocol Level</H2
><P
>The SMB protocol has many dialects. Currently
Samba supports 5, called CORE, COREPLUS, LANMAN1,
@ -724,7 +755,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN195">1.10.4. Printing from UNIX to a Client PC</H2
NAME="AEN195"
></A
>1.10.4. Printing from UNIX to a Client PC</H2
><P
>To use a printer that is available via a smb-based
server from a unix host with LPR you will need to compile the
@ -743,7 +776,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN200">1.10.5. Locking</H2
NAME="AEN200"
></A
>1.10.5. Locking</H2
><P
>One area which sometimes causes trouble is locking.</P
><P
@ -801,7 +836,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN209">1.10.6. Mapping Usernames</H2
NAME="AEN209"
></A
>1.10.6. Mapping Usernames</H2
><P
>If you have different usernames on the PCs and
the unix server then take a look at the "username map" option.
@ -825,7 +862,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -834,7 +871,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Integrating MS Windows networks with Samba</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Diagnosing your samba server"
HREF="diagnosis.html"><LINK
@ -71,13 +70,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="INTEGRATE-MS-NETWORKS">Chapter 3. Integrating MS Windows networks with Samba</H1
NAME="INTEGRATE-MS-NETWORKS"
></A
>Chapter 3. Integrating MS Windows networks with Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN362">3.1. Agenda</H1
NAME="AEN365"
></A
>3.1. Agenda</H1
><P
>To identify the key functional mechanisms of MS Windows networking
to enable the deployment of Samba as a means of extending and/or
@ -142,7 +145,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN384">3.2. Name Resolution in a pure Unix/Linux world</H1
NAME="AEN387"
></A
>3.2. Name Resolution in a pure Unix/Linux world</H1
><P
>The key configuration files covered in this section are:</P
><P
@ -182,7 +187,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN400">3.2.1. <TT
NAME="AEN403"
></A
>3.2.1. <TT
CLASS="FILENAME"
>/etc/hosts</TT
></H2
@ -261,7 +268,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN416">3.2.2. <TT
NAME="AEN419"
></A
>3.2.2. <TT
CLASS="FILENAME"
>/etc/resolv.conf</TT
></H2
@ -297,7 +306,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN427">3.2.3. <TT
NAME="AEN430"
></A
>3.2.3. <TT
CLASS="FILENAME"
>/etc/host.conf</TT
></H2
@ -324,7 +335,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN435">3.2.4. <TT
NAME="AEN438"
></A
>3.2.4. <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
></H2
@ -391,7 +404,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN447">3.3. Name resolution as used within MS Windows networking</H1
NAME="AEN450"
></A
>3.3. Name resolution as used within MS Windows networking</H1
><P
>MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
@ -474,7 +489,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN459">3.3.1. The NetBIOS Name Cache</H2
NAME="AEN462"
></A
>3.3.1. The NetBIOS Name Cache</H2
><P
>All MS Windows machines employ an in memory buffer in which is
stored the NetBIOS names and IP addresses for all external
@ -499,7 +516,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN464">3.3.2. The LMHOSTS file</H2
NAME="AEN467"
></A
>3.3.2. The LMHOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or
2000 in <TT
@ -600,7 +619,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN472">3.3.3. HOSTS file</H2
NAME="AEN475"
></A
>3.3.3. HOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or 2000 in
<TT
@ -620,7 +641,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN477">3.3.4. DNS Lookup</H2
NAME="AEN480"
></A
>3.3.4. DNS Lookup</H2
><P
>This capability is configured in the TCP/IP setup area in the network
configuration facility. If enabled an elaborate name resolution sequence
@ -638,7 +661,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN480">3.3.5. WINS Lookup</H2
NAME="AEN483"
></A
>3.3.5. WINS Lookup</H2
><P
>A WINS (Windows Internet Name Server) service is the equivaent of the
rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
@ -679,7 +704,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN492">3.4. How browsing functions and how to deploy stable and
NAME="AEN495"
></A
>3.4. How browsing functions and how to deploy stable and
dependable browsing using Samba</H1
><P
>As stated above, MS Windows machines register their NetBIOS names
@ -744,7 +771,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN502">3.5. MS Windows security options and how to configure
NAME="AEN505"
></A
>3.5. MS Windows security options and how to configure
Samba for seemless integration</H1
><P
>MS Windows clients may use encrypted passwords as part of a
@ -879,7 +908,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN530">3.5.1. Use MS Windows NT as an authentication server</H2
NAME="AEN533"
></A
>3.5.1. Use MS Windows NT as an authentication server</H2
><P
>This method involves the additions of the following parameters
in the smb.conf file:</P
@ -913,7 +944,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN538">3.5.2. Make Samba a member of an MS Windows NT security domain</H2
NAME="AEN541"
></A
>3.5.2. Make Samba a member of an MS Windows NT security domain</H2
><P
>This method involves additon of the following paramters in the smb.conf file:</P
><P
@ -974,7 +1007,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN555">3.5.3. Configure Samba as an authentication server</H2
NAME="AEN558"
></A
>3.5.3. Configure Samba as an authentication server</H2
><P
>This mode of authentication demands that there be on the
Unix/Linux system both a Unix style account as well as an
@ -1009,7 +1044,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN562">3.5.3.1. Users</H3
NAME="AEN565"
></A
>3.5.3.1. Users</H3
><P
>A user account that may provide a home directory should be
created. The following Linux system commands are typical of
@ -1030,7 +1067,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN567">3.5.3.2. MS Windows NT Machine Accounts</H3
NAME="AEN570"
></A
>3.5.3.2. MS Windows NT Machine Accounts</H3
><P
>These are required only when Samba is used as a domain
controller. Refer to the Samba-PDC-HOWTO for more details.</P
@ -1049,7 +1088,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN572">3.6. Conclusions</H1
NAME="AEN575"
></A
>3.6. Conclusions</H1
><P
>Samba provides a flexible means to operate as...</P
><P
@ -1104,7 +1145,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Hosting a Microsoft Distributed File System tree on Samba</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Configuring PAM for distributed but centrally
managed authentication"
@ -71,13 +70,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="MSDFS">Chapter 5. Hosting a Microsoft Distributed File System tree on Samba</H1
NAME="MSDFS"
></A
>Chapter 5. Hosting a Microsoft Distributed File System tree on Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN664">5.1. Instructions</H1
NAME="AEN667"
></A
>5.1. Instructions</H1
><P
>The Distributed File System (or Dfs) provides a means of
separating the logical view of files and directories that users
@ -223,7 +226,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN699">5.1.1. Notes</H2
NAME="AEN702"
></A
>5.1.1. Notes</H2
><P
></P
><UL
@ -275,7 +280,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Samba and other CIFS clients</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Samba performance issues"
HREF="speed.html"><LINK
@ -70,7 +69,9 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="OTHER-CLIENTS">Chapter 17. Samba and other CIFS clients</H1
NAME="OTHER-CLIENTS"
></A
>Chapter 18. Samba and other CIFS clients</H1
><P
>This chapter contains client-specific information.</P
><DIV
@ -78,7 +79,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2871">17.1. Macintosh clients?</H1
NAME="AEN2953"
></A
>18.1. Macintosh clients?</H1
><P
>Yes. <A
HREF="http://www.thursby.com/"
@ -122,13 +125,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2880">17.2. OS2 Client</H1
NAME="AEN2962"
></A
>18.2. OS2 Client</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2882">17.2.1. How can I configure OS/2 Warp Connect or
NAME="AEN2964"
></A
>18.2.1. How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</H2
><P
>A more complete answer to this question can be
@ -185,7 +192,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2897">17.2.2. How can I configure OS/2 Warp 3 (not Connect),
NAME="AEN2979"
></A
>18.2.2. How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</H2
><P
>You can use the free Microsoft LAN Manager 2.2c Client
@ -227,7 +236,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2906">17.2.3. Are there any other issues when OS/2 (any version)
NAME="AEN2988"
></A
>18.2.3. Are there any other issues when OS/2 (any version)
is used as a client?</H2
><P
>When you do a NET VIEW or use the "File and Print
@ -247,7 +258,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2910">17.2.4. How do I get printer driver download working
NAME="AEN2992"
></A
>18.2.4. How do I get printer driver download working
for OS/2 clients?</H2
><P
>First, create a share called [PRINTDRV] that is
@ -296,13 +309,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2920">17.3. Windows for Workgroups</H1
NAME="AEN3002"
></A
>18.3. Windows for Workgroups</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2922">17.3.1. Use latest TCP/IP stack from Microsoft</H2
NAME="AEN3004"
></A
>18.3.1. Use latest TCP/IP stack from Microsoft</H2
><P
>Use the latest TCP/IP stack from microsoft if you use Windows
for workgroups.</P
@ -322,7 +339,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2927">17.3.2. Delete .pwl files after password change</H2
NAME="AEN3009"
></A
>18.3.2. Delete .pwl files after password change</H2
><P
>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
@ -340,7 +359,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2932">17.3.3. Configure WfW password handling</H2
NAME="AEN3014"
></A
>18.3.3. Configure WfW password handling</H2
><P
>There is a program call admincfg.exe
on the last disk (disk 8) of the WFW 3.11 disk set. To install it
@ -357,7 +378,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2936">17.3.4. Case handling of passwords</H2
NAME="AEN3018"
></A
>18.3.4. Case handling of passwords</H2
><P
>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
HREF="smb.conf.5.html"
@ -374,7 +397,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2941">17.4. Windows '95/'98</H1
NAME="AEN3023"
></A
>18.4. Windows '95/'98</H1
><P
>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
@ -420,7 +445,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2957">17.5. Windows 2000 Service Pack 2</H1
NAME="AEN3039"
></A
>18.5. Windows 2000 Service Pack 2</H1
><P
>
There are several annoyances with Windows 2000 SP2. One of which
@ -521,7 +548,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -6,11 +6,10 @@
managed authentication</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"><LINK
@ -71,14 +70,18 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="PAM">Chapter 4. Configuring PAM for distributed but centrally
NAME="PAM"
></A
>Chapter 4. Configuring PAM for distributed but centrally
managed authentication</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN593">4.1. Samba and PAM</H1
NAME="AEN596"
></A
>4.1. Samba and PAM</H1
><P
>A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
@ -290,7 +293,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN637">4.2. Distributed Authentication</H1
NAME="AEN640"
></A
>4.2. Distributed Authentication</H1
><P
>The astute administrator will realize from this that the
combination of <TT
@ -321,7 +326,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN644">4.3. PAM Configuration in smb.conf</H1
NAME="AEN647"
></A
>4.3. PAM Configuration in smb.conf</H1
><P
>There is an option in smb.conf called <A
HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
@ -380,7 +387,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Portability</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"></HEAD
@ -63,7 +62,9 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="PORTABILITY">Chapter 21. Portability</H1
NAME="PORTABILITY"
></A
>Chapter 22. Portability</H1
><P
>Samba works on a wide range of platforms but the interface all the
platforms provide is not always compatible. This chapter contains
@ -73,7 +74,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3119">21.1. HPUX</H1
NAME="AEN3201"
></A
>22.1. HPUX</H1
><P
>HP's implementation of supplementary groups is, er, non-standard (for
hysterical reasons). There are two group files, /etc/group and
@ -97,7 +100,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3124">21.2. SCO Unix</H1
NAME="AEN3206"
></A
>22.2. SCO Unix</H1
><P
>
If you run an old version of SCO Unix then you may need to get important
@ -112,7 +117,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3128">21.3. DNIX</H1
NAME="AEN3210"
></A
>22.3. DNIX</H1
><P
>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
@ -212,6 +219,30 @@ CLASS="FILENAME"
>includes.h</TT
></P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3239"
></A
>22.4. RedHat Linux Rembrandt-II</H1
><P
>By default RedHat Rembrandt-II during installation adds an
entry to /etc/hosts as follows:
<PRE
CLASS="PROGRAMLISTING"
> 127.0.0.1 loopback "hostname"."domainname"</PRE
></P
><P
>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.</P
><P
>Corrective Action: Delete the entry after the word loopback
in the line starting 127.0.0.1</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
@ -238,7 +269,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Printing Support in Samba 2.2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="PRINTING">Chapter 7. Printing Support in Samba 2.2.x</H1
NAME="PRINTING"
></A
>Chapter 7. Printing Support in Samba 2.2.x</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN902">7.1. Introduction</H1
NAME="AEN905"
></A
>7.1. Introduction</H1
><P
>Beginning with the 2.2.0 release, Samba supports
the native Windows NT printing mechanisms implemented via
@ -162,7 +165,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN924">7.2. Configuration</H1
NAME="AEN927"
></A
>7.2. Configuration</H1
><DIV
CLASS="WARNING"
><P
@ -177,7 +182,7 @@ WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
SRC="/docbook-dsssl/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TH
@ -240,7 +245,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN935">7.2.1. Creating [print$]</H2
NAME="AEN938"
></A
>7.2.1. Creating [print$]</H2
><P
>In order to support the uploading of printer driver
files, you must first configure a file share named [print$].
@ -319,7 +326,7 @@ WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
SRC="/docbook-dsssl/note.gif"
HSPACE="5"
ALT="Note"></TD
><TH
@ -390,7 +397,7 @@ WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
SRC="/docbook-dsssl/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TH
@ -461,7 +468,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN970">7.2.2. Setting Drivers for Existing Printers</H2
NAME="AEN973"
></A
>7.2.2. Setting Drivers for Existing Printers</H2
><P
>The initial listing of printers in the Samba host's
Printers folder will have no real printer driver assigned
@ -539,7 +548,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN987">7.2.3. Support a large number of printers</H2
NAME="AEN990"
></A
>7.2.3. Support a large number of printers</H2
><P
>One issue that has arisen during the development
phase of Samba 2.2 is the need to support driver downloads for
@ -603,7 +614,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN998">7.2.4. Adding New Printers via the Windows NT APW</H2
NAME="AEN1001"
></A
>7.2.4. Adding New Printers via the Windows NT APW</H2
><P
>By default, Samba offers all printer shares defined in <TT
CLASS="FILENAME"
@ -770,7 +783,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1028">7.2.5. Samba and Printer Ports</H2
NAME="AEN1031"
></A
>7.2.5. Samba and Printer Ports</H2
><P
>Windows NT/2000 print servers associate a port with each printer. These normally
take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
@ -805,7 +820,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1036">7.3. The Imprints Toolset</H1
NAME="AEN1039"
></A
>7.3. The Imprints Toolset</H1
><P
>The Imprints tool set provides a UNIX equivalent of the
Windows NT Add Printer Wizard. For complete information, please
@ -821,7 +838,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1040">7.3.1. What is Imprints?</H2
NAME="AEN1043"
></A
>7.3.1. What is Imprints?</H2
><P
>Imprints is a collection of tools for supporting the goals
of</P
@ -851,7 +870,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1050">7.3.2. Creating Printer Driver Packages</H2
NAME="AEN1053"
></A
>7.3.2. Creating Printer Driver Packages</H2
><P
>The process of creating printer driver packages is beyond
the scope of this document (refer to Imprints.txt also included
@ -865,7 +886,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1053">7.3.3. The Imprints server</H2
NAME="AEN1056"
></A
>7.3.3. The Imprints server</H2
><P
>The Imprints server is really a database server that
may be queried via standard HTTP mechanisms. Each printer
@ -887,7 +910,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1057">7.3.4. The Installation Client</H2
NAME="AEN1060"
></A
>7.3.4. The Installation Client</H2
><P
>More information regarding the Imprints installation client
is available in the <TT
@ -979,7 +1004,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1079">7.4. <A
NAME="AEN1082"
></A
>7.4. <A
NAME="MIGRATION"
></A
>Migration to from Samba 2.0.x to 2.2.x</H1
@ -1061,7 +1088,7 @@ WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
SRC="/docbook-dsssl/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TH
@ -1166,7 +1193,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Debugging Printing Problems</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Printing Support in Samba 2.2.x"
HREF="printing.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="PRINTINGDEBUG">Chapter 8. Debugging Printing Problems</H1
NAME="PRINTINGDEBUG"
></A
>Chapter 8. Debugging Printing Problems</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1125">8.1. Introduction</H1
NAME="AEN1128"
></A
>8.1. Introduction</H1
><P
>This is a short description of how to debug printing problems with
Samba. This describes how to debug problems with printing from a SMB
@ -149,7 +152,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1141">8.2. Debugging printer problems</H1
NAME="AEN1144"
></A
>8.2. Debugging printer problems</H1
><P
>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
@ -204,7 +209,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1150">8.3. What printers do I have?</H1
NAME="AEN1153"
></A
>8.3. What printers do I have?</H1
><P
>You can use the 'testprns' program to check to see if the printer
name you are using is recognized by Samba. For example, you can
@ -231,7 +238,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1158">8.4. Setting up printcap and print servers</H1
NAME="AEN1161"
></A
>8.4. Setting up printcap and print servers</H1
><P
>You may need to set up some printcaps for your Samba system to use.
It is strongly recommended that you use the facilities provided by
@ -313,7 +322,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1186">8.5. Job sent, no output</H1
NAME="AEN1189"
></A
>8.5. Job sent, no output</H1
><P
>This is the most frustrating part of printing. You may have sent the
job, verified that the job was forwarded, set up a wrapper around
@ -356,7 +367,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1197">8.6. Job sent, strange output</H1
NAME="AEN1200"
></A
>8.6. Job sent, strange output</H1
><P
>Once you have the job printing, you can then start worrying about
making it print nicely.</P
@ -400,7 +413,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1209">8.7. Raw PostScript printed</H1
NAME="AEN1212"
></A
>8.7. Raw PostScript printed</H1
><P
>This is a problem that is usually caused by either the print spooling
system putting information at the start of the print job that makes
@ -413,7 +428,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1212">8.8. Advanced Printing</H1
NAME="AEN1215"
></A
>8.8. Advanced Printing</H1
><P
>Note that you can do some pretty magic things by using your
imagination with the "print command" option and some shell scripts.
@ -427,7 +444,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1215">8.9. Real debugging</H1
NAME="AEN1218"
></A
>8.9. Real debugging</H1
><P
>If the above debug tips don't help, then maybe you need to bring in
the bug guns, system tracing. See Tracing.txt in this directory.</P
@ -458,7 +477,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="How to Configure Samba 2.2 as a Primary Domain Controller"
HREF="samba-pdc.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="SAMBA-BDC">Chapter 13. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
NAME="SAMBA-BDC"
></A
>Chapter 13. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2287">13.1. Prerequisite Reading</H1
NAME="AEN2290"
></A
>13.1. Prerequisite Reading</H1
><P
>Before you continue reading in this chapter, please make sure
that you are comfortable with configuring a Samba PDC
@ -91,7 +94,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2291">13.2. Background</H1
NAME="AEN2294"
></A
>13.2. Background</H1
><P
>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
@ -134,7 +139,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2299">13.3. What qualifies a Domain Controller on the network?</H1
NAME="AEN2302"
></A
>13.3. What qualifies a Domain Controller on the network?</H1
><P
>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
@ -149,7 +156,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2302">13.3.1. How does a Workstation find its domain controller?</H2
NAME="AEN2305"
></A
>13.3.1. How does a Workstation find its domain controller?</H2
><P
>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
@ -166,7 +175,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2305">13.3.2. When is the PDC needed?</H2
NAME="AEN2308"
></A
>13.3.2. When is the PDC needed?</H2
><P
>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
@ -180,7 +191,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2308">13.4. Can Samba be a Backup Domain Controller?</H1
NAME="AEN2311"
></A
>13.4. Can Samba be a Backup Domain Controller?</H1
><P
>With version 2.2, no. The native NT SAM replication protocols have
not yet been fully implemented. The Samba Team is working on
@ -197,7 +210,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2312">13.5. How do I set up a Samba BDC?</H1
NAME="AEN2315"
></A
>13.5. How do I set up a Samba BDC?</H1
><P
>Several things have to be done:</P
><P
@ -262,7 +277,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2329">13.5.1. How do I replicate the smbpasswd file?</H2
NAME="AEN2332"
></A
>13.5.1. How do I replicate the smbpasswd file?</H2
><P
>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
@ -303,7 +320,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,17 +5,16 @@
>Storing Samba's User/Machine Account information in an LDAP Directory</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain"
HREF="samba-bdc.html"><LINK
REL="NEXT"
TITLE="Improved browsing in samba"
HREF="improved-browsing.html"></HEAD
TITLE="Using samba 3.0 with ActiveDirectory support"
HREF="ads.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -57,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="improved-browsing.html"
HREF="ads.html"
ACCESSKEY="N"
>Next</A
></TD
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="SAMBA-LDAP-HOWTO">Chapter 14. Storing Samba's User/Machine Account information in an LDAP Directory</H1
NAME="SAMBA-LDAP-HOWTO"
></A
>Chapter 14. Storing Samba's User/Machine Account information in an LDAP Directory</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2350">14.1. Purpose</H1
NAME="AEN2353"
></A
>14.1. Purpose</H1
><P
>This document describes how to use an LDAP directory for storing Samba user
account information traditionally stored in the smbpasswd(5) file. It is
@ -142,7 +145,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2370">14.2. Introduction</H1
NAME="AEN2373"
></A
>14.2. Introduction</H1
><P
>Traditionally, when configuring <A
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
@ -257,7 +262,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2399">14.3. Supported LDAP Servers</H1
NAME="AEN2402"
></A
>14.3. Supported LDAP Servers</H1
><P
>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP
2.0 server and client libraries. The same code should be able to work with
@ -280,7 +287,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2404">14.4. Schema and Relationship to the RFC 2307 posixAccount</H1
NAME="AEN2407"
></A
>14.4. Schema and Relationship to the RFC 2307 posixAccount</H1
><P
>Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
<TT
@ -337,13 +346,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2416">14.5. Configuring Samba with LDAP</H1
NAME="AEN2419"
></A
>14.5. Configuring Samba with LDAP</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2418">14.5.1. OpenLDAP configuration</H2
NAME="AEN2421"
></A
>14.5.1. OpenLDAP configuration</H2
><P
>To include support for the sambaAccount object in an OpenLDAP directory
server, first copy the samba.schema file to slapd's configuration directory.</P
@ -423,7 +436,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2435">14.5.2. Configuring Samba</H2
NAME="AEN2438"
></A
>14.5.2. Configuring Samba</H2
><P
>The following parameters are available in smb.conf only with <TT
CLASS="PARAMETER"
@ -541,7 +556,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2463">14.6. Accounts and Groups management</H1
NAME="AEN2466"
></A
>14.6. Accounts and Groups management</H1
><P
>As users accounts are managed thru the sambaAccount objectclass, you should
modify you existing administration tools to deal with sambaAccount attributes.</P
@ -564,7 +581,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2468">14.7. Security and sambaAccount</H1
NAME="AEN2471"
></A
>14.7. Security and sambaAccount</H1
><P
>There are two important points to remember when discussing the security
of sambaAccount entries in the directory.</P
@ -641,7 +660,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2488">14.8. LDAP specials attributes for sambaAccounts</H1
NAME="AEN2491"
></A
>14.8. LDAP specials attributes for sambaAccounts</H1
><P
>The sambaAccount objectclass is composed of the following attributes:</P
><P
@ -850,7 +871,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2558">14.9. Example LDIF Entries for a sambaAccount</H1
NAME="AEN2561"
></A
>14.9. Example LDIF Entries for a sambaAccount</H1
><P
>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
><P
@ -906,7 +929,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2566">14.10. Comments</H1
NAME="AEN2569"
></A
>14.10. Comments</H1
><P
>Please mail all comments regarding this HOWTO to <A
HREF="mailto:jerry@samba.org"
@ -941,7 +966,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD
@ -950,7 +975,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="improved-browsing.html"
HREF="ads.html"
ACCESSKEY="N"
>Next</A
></TD
@ -970,7 +995,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Improved browsing in samba</TD
>Using samba 3.0 with ActiveDirectory support</TD
></TR
></TABLE
></DIV

View File

@ -5,11 +5,10 @@
>Security levels</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Debugging Printing Problems"
HREF="printingdebug.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="SECURITYLEVELS">Chapter 9. Security levels</H1
NAME="SECURITYLEVELS"
></A
>Chapter 9. Security levels</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1228">9.1. Introduction</H1
NAME="AEN1231"
></A
>9.1. Introduction</H1
><P
>Samba supports the following options to the global smb.conf parameter</P
><P
@ -120,7 +123,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1239">9.2. More complete description of security levels</H1
NAME="AEN1242"
></A
>9.2. More complete description of security levels</H1
><P
>A SMB server tells the client at startup what "security level" it is
running. There are two options "share level" and "user level". Which
@ -233,7 +238,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Samba performance issues</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Improved browsing in samba"
HREF="improved-browsing.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="SPEED">Chapter 16. Samba performance issues</H1
NAME="SPEED"
></A
>Chapter 17. Samba performance issues</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2732">16.1. Comparisons</H1
NAME="AEN2814"
></A
>17.1. Comparisons</H1
><P
>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
@ -105,13 +108,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2738">16.2. Oplocks</H1
NAME="AEN2820"
></A
>17.2. Oplocks</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2740">16.2.1. Overview</H2
NAME="AEN2822"
></A
>17.2.1. Overview</H2
><P
>Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
@ -145,7 +152,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2748">16.2.2. Level2 Oplocks</H2
NAME="AEN2830"
></A
>17.2.2. Level2 Oplocks</H2
><P
>With Samba 2.0.5 a new capability - level2 (read only) oplocks is
supported (although the option is off by default - see the smb.conf
@ -167,7 +176,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2754">16.2.3. Old 'fake oplocks' option - deprecated</H2
NAME="AEN2836"
></A
>17.2.3. Old 'fake oplocks' option - deprecated</H2
><P
>Samba can also fake oplocks, by granting a oplock whenever a client
asks for one. This is controlled using the smb.conf option "fake
@ -186,7 +197,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2758">16.3. Socket options</H1
NAME="AEN2840"
></A
>17.3. Socket options</H1
><P
>There are a number of socket options that can greatly affect the
performance of a TCP based server like Samba.</P
@ -212,7 +225,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2765">16.4. Read size</H1
NAME="AEN2847"
></A
>17.4. Read size</H1
><P
>The option "read size" affects the overlap of disk reads/writes with
network reads/writes. If the amount of data being transferred in
@ -236,7 +251,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2770">16.5. Max xmit</H1
NAME="AEN2852"
></A
>17.5. Max xmit</H1
><P
>At startup the client and server negotiate a "maximum transmit" size,
which limits the size of nearly all SMB commands. You can set the
@ -257,7 +274,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2775">16.6. Locking</H1
NAME="AEN2857"
></A
>17.6. Locking</H1
><P
>By default Samba does not implement strict locking on each read/write
call (although it did in previous versions). If you enable strict
@ -272,7 +291,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2779">16.7. Share modes</H1
NAME="AEN2861"
></A
>17.7. Share modes</H1
><P
>Some people find that opening files is very slow. This is often
because of the "share modes" code needed to fully implement the dos
@ -300,7 +321,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2784">16.8. Log level</H1
NAME="AEN2866"
></A
>17.8. Log level</H1
><P
>If you set the log level (also known as "debug level") higher than 2
then you may suffer a large drop in performance. This is because the
@ -312,7 +335,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2787">16.9. Wide lines</H1
NAME="AEN2869"
></A
>17.9. Wide lines</H1
><P
>The "wide links" option is now enabled by default, but if you disable
it (for better security) then you may suffer a performance hit in
@ -324,7 +349,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2790">16.10. Read raw</H1
NAME="AEN2872"
></A
>17.10. Read raw</H1
><P
>The "read raw" operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
@ -344,7 +371,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2795">16.11. Write raw</H1
NAME="AEN2877"
></A
>17.11. Write raw</H1
><P
>The "write raw" operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
@ -359,7 +388,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2799">16.12. Read prediction</H1
NAME="AEN2881"
></A
>17.12. Read prediction</H1
><P
>Samba can do read prediction on some of the SMB commands. Read
prediction means that Samba reads some extra data on the last file it
@ -383,7 +414,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2806">16.13. Memory mapping</H1
NAME="AEN2888"
></A
>17.13. Memory mapping</H1
><P
>Samba supports reading files via memory mapping them. One some
machines this can give a large boost to performance, on others it
@ -402,7 +435,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2811">16.14. Slow Clients</H1
NAME="AEN2893"
></A
>17.14. Slow Clients</H1
><P
>One person has reported that setting the protocol to COREPLUS rather
than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
@ -417,7 +452,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2815">16.15. Slow Logins</H1
NAME="AEN2897"
></A
>17.15. Slow Logins</H1
><P
>Slow logins are almost always due to the password checking time. Using
the lowest practical "password level" will improve things a lot. You
@ -428,7 +465,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2818">16.16. Client tuning</H1
NAME="AEN2900"
></A
>17.16. Client tuning</H1
><P
>Often a speed problem can be traced to the client. The client (for
example Windows for Workgroups) can often be tuned for better TCP
@ -530,7 +569,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2850">16.17. My Results</H1
NAME="AEN2932"
></A
>17.17. My Results</H1
><P
>Some people want to see real numbers in a document like this, so here
they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b
@ -578,7 +619,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>UNIX Permission Bits and Windows NT Access Control Lists</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="UNIX-PERMISSIONS">Chapter 6. UNIX Permission Bits and Windows NT Access Control Lists</H1
NAME="UNIX-PERMISSIONS"
></A
>Chapter 6. UNIX Permission Bits and Windows NT Access Control Lists</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN719">6.1. Viewing and changing UNIX permissions using the NT
NAME="AEN722"
></A
>6.1. Viewing and changing UNIX permissions using the NT
security dialogs</H1
><P
>New in the Samba 2.0.4 release is the ability for Windows
@ -113,7 +116,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN728">6.2. How to view file security on a Samba share</H1
NAME="AEN731"
></A
>6.2. How to view file security on a Samba share</H1
><P
>From an NT 4.0 client, single-click with the right
mouse button on any file or directory in a Samba mounted
@ -181,7 +186,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN739">6.3. Viewing file ownership</H1
NAME="AEN742"
></A
>6.3. Viewing file ownership</H1
><P
>Clicking on the <B
CLASS="COMMAND"
@ -273,7 +280,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN759">6.4. Viewing file or directory permissions</H1
NAME="AEN762"
></A
>6.4. Viewing file or directory permissions</H1
><P
>The third button is the <B
CLASS="COMMAND"
@ -333,7 +342,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN774">6.4.1. File Permissions</H2
NAME="AEN777"
></A
>6.4.1. File Permissions</H2
><P
>The standard UNIX user/group/world triple and
the corresponding "read", "write", "execute" permissions
@ -393,7 +404,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN788">6.4.2. Directory Permissions</H2
NAME="AEN791"
></A
>6.4.2. Directory Permissions</H2
><P
>Directories on an NT NTFS file system have two
different sets of permissions. The first set of permissions
@ -423,7 +436,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN795">6.5. Modifying file or directory permissions</H1
NAME="AEN798"
></A
>6.5. Modifying file or directory permissions</H1
><P
>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
@ -519,7 +534,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN817">6.6. Interaction with the standard Samba create mask
NAME="AEN820"
></A
>6.6. Interaction with the standard Samba create mask
parameters</H1
><P
>Note that with Samba 2.0.5 there are four new parameters
@ -794,7 +811,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN881">6.7. Interaction with the standard Samba file attribute
NAME="AEN884"
></A
>6.7. Interaction with the standard Samba file attribute
mapping</H1
><P
>Samba maps some of the DOS attribute bits (such as "read
@ -860,7 +879,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -5,11 +5,10 @@
>Unified Logons between Windows NT and UNIX using Winbind</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="Samba-HOWTO.html"><LINK
HREF="samba-project-documentation.html"><LINK
REL="PREVIOUS"
TITLE="security = domain in Samba 2.x"
HREF="domain-security.html"><LINK
@ -70,13 +69,17 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
NAME="WINBIND">Chapter 11. Unified Logons between Windows NT and UNIX using Winbind</H1
NAME="WINBIND"
></A
>Chapter 11. Unified Logons between Windows NT and UNIX using Winbind</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1394">11.1. Abstract</H1
NAME="AEN1397"
></A
>11.1. Abstract</H1
><P
>Integration of UNIX and Microsoft Windows NT through
a unified logon has been considered a "holy grail" in heterogeneous
@ -101,7 +104,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1398">11.2. Introduction</H1
NAME="AEN1401"
></A
>11.2. Introduction</H1
><P
>It is well known that UNIX and Microsoft Windows NT have
different models for representing user and group information and
@ -153,7 +158,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1411">11.3. What Winbind Provides</H1
NAME="AEN1414"
></A
>11.3. What Winbind Provides</H1
><P
>Winbind unifies UNIX and Windows NT account management by
allowing a UNIX box to become a full member of a NT domain. Once
@ -193,7 +200,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1418">11.3.1. Target Uses</H2
NAME="AEN1421"
></A
>11.3.1. Target Uses</H2
><P
>Winbind is targeted at organizations that have an
existing NT based domain infrastructure into which they wish
@ -215,7 +224,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1422">11.4. How Winbind Works</H1
NAME="AEN1425"
></A
>11.4. How Winbind Works</H1
><P
>The winbind system is designed around a client/server
architecture. A long running <B
@ -233,7 +244,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1427">11.4.1. Microsoft Remote Procedure Calls</H2
NAME="AEN1430"
></A
>11.4.1. Microsoft Remote Procedure Calls</H2
><P
>Over the last two years, efforts have been underway
by various Samba Team members to decode various aspects of
@ -257,7 +270,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1431">11.4.2. Name Service Switch</H2
NAME="AEN1434"
></A
>11.4.2. Name Service Switch</H2
><P
>The Name Service Switch, or NSS, is a feature that is
present in many UNIX operating systems. It allows system
@ -335,7 +350,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1447">11.4.3. Pluggable Authentication Modules</H2
NAME="AEN1450"
></A
>11.4.3. Pluggable Authentication Modules</H2
><P
>Pluggable Authentication Modules, also known as PAM,
is a system for abstracting authentication and authorization
@ -382,7 +399,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1455">11.4.4. User and Group ID Allocation</H2
NAME="AEN1458"
></A
>11.4.4. User and Group ID Allocation</H2
><P
>When a user or group is created under Windows NT
is it allocated a numerical relative identifier (RID). This is
@ -406,7 +425,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1459">11.4.5. Result Caching</H2
NAME="AEN1462"
></A
>11.4.5. Result Caching</H2
><P
>An active system can generate a lot of user and group
name lookups. To reduce the network cost of these lookups winbind
@ -427,7 +448,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1462">11.5. Installation and Configuration</H1
NAME="AEN1465"
></A
>11.5. Installation and Configuration</H1
><P
>Many thanks to John Trostel <A
HREF="mailto:jtrostel@snapserver.com"
@ -452,7 +475,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1469">11.5.1. Introduction</H2
NAME="AEN1472"
></A
>11.5.1. Introduction</H2
><P
>This HOWTO describes the procedures used to get winbind up and
running on my RedHat 7.1 system. Winbind is capable of providing access
@ -509,7 +534,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1482">11.5.2. Requirements</H2
NAME="AEN1485"
></A
>11.5.2. Requirements</H2
><P
>If you have a samba configuration file that you are currently
using... <SPAN
@ -577,7 +604,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1496">11.5.3. Testing Things Out</H2
NAME="AEN1499"
></A
>11.5.3. Testing Things Out</H2
><P
>Before starting, it is probably best to kill off all the SAMBA
related daemons running on your server. Kill off all <B
@ -620,7 +649,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1507">11.5.3.1. Configure and compile SAMBA</H3
NAME="AEN1510"
></A
>11.5.3.1. Configure and compile SAMBA</H3
><P
>The configuration and compilation of SAMBA is pretty straightforward.
The first three steps may not be necessary depending upon
@ -684,7 +715,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1526">11.5.3.2. Configure <TT
NAME="AEN1529"
></A
>11.5.3.2. Configure <TT
CLASS="FILENAME"
>nsswitch.conf</TT
> and the
@ -787,7 +820,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1559">11.5.3.3. Configure smb.conf</H3
NAME="AEN1562"
></A
>11.5.3.3. Configure smb.conf</H3
><P
>Several parameters are needed in the smb.conf file to control
the behavior of <B
@ -860,7 +895,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1575">11.5.3.4. Join the SAMBA server to the PDC domain</H3
NAME="AEN1578"
></A
>11.5.3.4. Join the SAMBA server to the PDC domain</H3
><P
>Enter the following command to make the SAMBA server join the
PDC domain, where <TT
@ -904,7 +941,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1586">11.5.3.5. Start up the winbindd daemon and test it!</H3
NAME="AEN1589"
></A
>11.5.3.5. Start up the winbindd daemon and test it!</H3
><P
>Eventually, you will want to modify your smb startup script to
automatically invoke the winbindd daemon when the other parts of
@ -1025,13 +1064,17 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1622">11.5.3.6. Fix the init.d startup scripts</H3
NAME="AEN1625"
></A
>11.5.3.6. Fix the init.d startup scripts</H3
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1624">11.5.3.6.1. Linux</H4
NAME="AEN1627"
></A
>11.5.3.6.1. Linux</H4
><P
>The <B
CLASS="COMMAND"
@ -1125,7 +1168,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1641">11.5.3.6.2. Solaris</H4
NAME="AEN1644"
></A
>11.5.3.6.2. Solaris</H4
><P
>On solaris, you need to modify the
<TT
@ -1194,7 +1239,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1648">11.5.3.6.3. Restarting</H4
NAME="AEN1651"
></A
>11.5.3.6.3. Restarting</H4
><P
>If you restart the <B
CLASS="COMMAND"
@ -1216,7 +1263,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1654">11.5.3.7. Configure Winbind and PAM</H3
NAME="AEN1657"
></A
>11.5.3.7. Configure Winbind and PAM</H3
><P
>If you have made it this far, you know that winbindd and samba are working
together. If you want to use winbind to provide authentication for other
@ -1272,7 +1321,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1671">11.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
NAME="AEN1674"
></A
>11.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
><P
>The <TT
CLASS="FILENAME"
@ -1399,7 +1450,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1704">11.5.3.7.2. Solaris-specific configuration</H4
NAME="AEN1707"
></A
>11.5.3.7.2. Solaris-specific configuration</H4
><P
>The /etc/pam.conf needs to be changed. I changed this file so that my Domain
users can logon both locally as well as telnet.The following are the changes
@ -1484,7 +1537,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1711">11.6. Limitations</H1
NAME="AEN1714"
></A
>11.6. Limitations</H1
><P
>Winbind has a number of limitations in its current
released version that we hope to overcome in future
@ -1523,7 +1578,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1721">11.7. Conclusion</H1
NAME="AEN1724"
></A
>11.7. Conclusion</H1
><P
>The winbind system, through the use of the Name Service
Switch, Pluggable Authentication Modules, and appropriate
@ -1558,7 +1615,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Samba-HOWTO.html"
HREF="samba-project-documentation.html"
ACCESSKEY="H"
>Home</A
></TD

View File

@ -1,22 +0,0 @@
This file lists Gotchas to watch out for:
=========================================================================
Item Number: 1.0
Description: Problem Detecting Interfaces
Symptom: Workstations do NOT see Samba server in Browse List
OS: RedHat - Rembrandt Beta 2
Platform: Intel
Date: August 16, 1996
Submitted By: John H Terpstra
Details:
By default RedHat Rembrandt-II during installation adds an
entry to /etc/hosts as follows:-
127.0.0.1 loopback "hostname"."domainname"
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.
Corrective Action: Delete the entry after the word loopback
in the line starting 127.0.0.1
=========================================================================