sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-27 03:21:53 +03:00
Code

large sync up with 2.2

Browse Source
This commit is contained in:
Gerald Carter 0001-01-01 00:00:00 +00:00
parent dd83f412e9
commit 96523293da
49 changed files with 16082 additions and 3388 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

63
docs/htmldocs/DOMAIN_MEMBER.html
View File

@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
></TITLE
>security = domain in Samba 2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
@ -15,11 +15,20 @@ ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>security = domain in Samba 2.x</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2"
NAME="AEN3"
>Joining an NT Domain with Samba 2.2</A
></H1
><P
@ -85,6 +94,11 @@ TARGET="_top"
> smbpasswd(8)</A
> man page for more details.</P
><P
>There is existing development code to join a domain
without having to create the machine trust account on the PDC
beforehand. This code will hopefully be available soon
in release branches as well.</P
><P
>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
@ -104,11 +118,11 @@ CLASS="REPLACEABLE"
><I
>&lt;NT DOMAIN NAME&gt;</I
></TT
>.
<TT
>.<TT
CLASS="REPLACEABLE"
><I
>&lt;Samba Server Name&gt;</I
>&lt;Samba
Server Name&gt;</I
></TT
>.mac</TT
></P
@ -242,7 +256,32 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN65"
NAME="AEN67"
>Samba and Windows 2000 Domains</A
></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
2000 domain operating in mixed or native mode.</P
><P
>There is much confusion between the circumstances that require a "mixed" mode
Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode
Win2k domain controller is only needed if Windows NT BDCs must exist in the same
domain. By default, a Win2k DC in "native" mode will still support
NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and
NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server.</P
><P
>The steps for adding a Samba 2.2 host to a Win2k domain are the same as those
for adding a Samba server to a Windows NT 4.0 domain. The only exception is that
the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and
Computers" MMC (Microsoft Management Console) plugin.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN72"
>Why is this better than security = server?</A
></H1
><P
@ -256,7 +295,7 @@ CLASS="CONSTANT"
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
<A
HREF="smb.conf.5.html#SECURITYEQUALSERVER"
HREF="smb.conf.5.html#SECURITYEQUALSSERVER"
TARGET="_top"
>security = server</A
>,
@ -264,6 +303,16 @@ TARGET="_top"
NT server in the same way as a Windows 95 or Windows 98 server would.
</P
><P
>Please refer to the <A
HREF="winbind.html"
TARGET="_top"
>Winbind
paper</A
> for information on a system to automatically
assign UNIX uids and gids to Windows NT Domain users and groups.
This code is available in development branches only at the moment,
but will be moved to release branches soon.</P
><P
>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

656
docs/htmldocs/ENCRYPTION.html Normal file
View File

@ -0,0 +1,656 @@
<HTML
><HEAD
><TITLE
>LanMan and NT Password Encryption in Samba 2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>LanMan and NT Password Encryption in Samba 2.x</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Introduction</A
></H1
><P
>With the development of LanManager and Windows NT
compatible password encryption for Samba, it is now able
to validate user connections in exactly the same way as
a LanManager or Windows NT server.</P
><P
>This document describes how the SMB password encryption
algorithm works and what issues there are in choosing whether
you want to use it. You should read it carefully, especially
the part about security and the "PROS and CONS" section.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN7"
>How does it work?</A
></H1
><P
>LanManager encryption is somewhat similar to UNIX
password encryption. The server uses a file containing a
hashed value of a user's password. This is created by taking
the user's plaintext password, capitalising it, and either
truncating to 14 bytes or padding to 14 bytes with null bytes.
This 14 byte value is used as two 56 bit DES keys to encrypt
a 'magic' eight byte value, forming a 16 byte value which is
stored by the server and client. Let this value be known as
the "hashed password".</P
><P
>Windows NT encryption is a higher quality mechanism,
consisting of doing an MD4 hash on a Unicode version of the user's
password. This also produces a 16 byte hash value that is
non-reversible.</P
><P
>When a client (LanManager, Windows for WorkGroups, Windows
95 or Windows NT) wishes to mount a Samba drive (or use a Samba
resource), it first requests a connection and negotiates the
protocol that the client and server will use. In the reply to this
request the Samba server generates and appends an 8 byte, random
value - this is stored in the Samba server after the reply is sent
and is known as the "challenge". The challenge is different for
every client connection.</P
><P
>The client then uses the hashed password (16 byte values
described above), appended with 5 null bytes, as three 56 bit
DES keys, each of which is used to encrypt the challenge 8 byte
value, forming a 24 byte value known as the "response".</P
><P
>In the SMB call SMBsessionsetupX (when user level security
is selected) or the call SMBtconX (when share level security is
selected), the 24 byte response is returned by the client to the
Samba server. For Windows NT protocol levels the above calculation
is done on both hashes of the user's password and both responses are
returned in the SMB call, giving two 24 byte values.</P
><P
>The Samba server then reproduces the above calculation, using
its own stored value of the 16 byte hashed password (read from the
<TT
CLASS="FILENAME"
>smbpasswd</TT
> file - described later) and the challenge
value that it kept from the negotiate protocol reply. It then checks
to see if the 24 byte value it calculates matches the 24 byte value
returned to it from the client.</P
><P
>If these values match exactly, then the client knew the
correct password (or the 16 byte hashed value - see security note
below) and is thus allowed access. If not, then the client did not
know the correct password and is denied access.</P
><P
>Note that the Samba server never knows or stores the cleartext
of the user's password - just the 16 byte hashed values derived from
it. Also note that the cleartext password or 16 byte hashed values
are never transmitted over the network - thus increasing security.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN18"
>Important Notes About Security</A
></H1
><P
>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 nextwork 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 smbpasswd file as though it contained the
cleartext passwords of all your users. Its contents must be kept
secret, and the file should be protected accordingly.</P
><P
>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). </P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
>Note that Windows NT 4.0 Service pack 3 changed the
default for permissible authentication so that plaintext
passwords are <I
CLASS="EMPHASIS"
>never</I
> 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.</P
><P
>Other Microsoft operating systems which also exhibit
this behavior includes</P
><P
></P
><UL
><LI
><P
>MS DOS Network client 3.0 with
the basic network redirector installed</P
></LI
><LI
><P
>Windows 95 with the network redirector
update installed</P
></LI
><LI
><P
>Windows 98 [se]</P
></LI
><LI
><P
>Windows 2000</P
></LI
></UL
><P
><I
CLASS="EMPHASIS"
>Note :</I
>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 particpate in encrypted authentication.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN37"
>Advantages of SMB Encryption</A
></H2
><P
></P
><UL
><LI
><P
>plain text passwords are not passed across
the network. Someone using a network sniffer cannot just
record passwords going to the SMB server.</P
></LI
><LI
><P
>WinNT doesn't like talking to a server
that isn't using SMB 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.
</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN44"
>Advantages of non-encrypted passwords</A
></H2
><P
></P
><UL
><LI
><P
>plain text passwords are not kept
on disk. </P
></LI
><LI
><P
>uses same password file as other unix
services such as login and ftp</P
></LI
><LI
><P
>you are probably already using 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.</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN53"
><A
NAME="SMBPASSWDFILEFORMAT"
></A
>The smbpasswd file</A
></H1
><P
>In order for Samba to participate in the above protocol
it must be able to look up the 16 byte hashed values given a user name.
Unfortunately, as the UNIX password value is also a one way hash
function (ie. it is impossible to retrieve the cleartext of the user's
password given the UNIX hash of it), a separate password file
containing this 16 byte value must be kept. To minimise problems with
these two password files, getting out of sync, the UNIX <TT
CLASS="FILENAME"
> /etc/passwd</TT
> and the <TT
CLASS="FILENAME"
>smbpasswd</TT
> file,
a utility, <B
CLASS="COMMAND"
>mksmbpasswd.sh</B
>, is provided to generate
a smbpasswd file from a UNIX <TT
CLASS="FILENAME"
>/etc/passwd</TT
> file.
</P
><P
>To generate the smbpasswd file from your <TT
CLASS="FILENAME"
>/etc/passwd
</TT
> file use the following command :</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>cat /etc/passwd | mksmbpasswd.sh
&gt; /usr/local/samba/private/smbpasswd</B
></TT
></P
><P
>If you are running on a system that uses NIS, use</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>ypcat passwd | mksmbpasswd.sh
&gt; /usr/local/samba/private/smbpasswd</B
></TT
></P
><P
>The <B
CLASS="COMMAND"
>mksmbpasswd.sh</B
> program is found in
the Samba source directory. By default, the smbpasswd file is
stored in :</P
><P
><TT
CLASS="FILENAME"
>/usr/local/samba/private/smbpasswd</TT
></P
><P
>The owner of the <TT
CLASS="FILENAME"
>/usr/local/samba/private/</TT
>
directory should be set to root, and the permissions on it should
be set to 0500 (<B
CLASS="COMMAND"
>chmod 500 /usr/local/samba/private</B
>).
</P
><P
>Likewise, the smbpasswd file inside the private directory should
be owned by root and the permissions on is should be set to 0600
(<B
CLASS="COMMAND"
>chmod 600 smbpasswd</B
>).</P
><P
>The format of the smbpasswd file is (The line has been
wrapped here. It should appear as one entry per line in
your smbpasswd file.)</P
><P
><PRE
CLASS="PROGRAMLISTING"
>username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
[Account type]:LCT-&lt;last-change-time&gt;:Long name
</PRE
></P
><P
>Although only the <TT
CLASS="REPLACEABLE"
><I
>username</I
></TT
>,
<TT
CLASS="REPLACEABLE"
><I
>uid</I
></TT
>, <TT
CLASS="REPLACEABLE"
><I
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</I
></TT
>,
[<TT
CLASS="REPLACEABLE"
><I
>Account type</I
></TT
>] and <TT
CLASS="REPLACEABLE"
><I
> last-change-time</I
></TT
> sections are significant
and are looked at in the Samba code.</P
><P
>It is <I
CLASS="EMPHASIS"
>VITALLY</I
> important that there by 32
'X' characters between the two ':' characters in the XXX sections -
the smbpasswd and Samba code will fail to validate any entries that
do not have 32 characters between ':' characters. The first XXX
section is for the Lanman password hash, the second is for the
Windows NT version.</P
><P
>When the password file is created all users have password entries
consisting of 32 'X' characters. By default this disallows any access
as this user. When a user has a password set, the 'X' characters change
to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii
representation of the 16 byte hashed value of a user's password.</P
><P
>To set a user to have no password (not recommended), edit the file
using vi, and replace the first 11 characters with the ascii text
<TT
CLASS="CONSTANT"
>"NO PASSWORD"</TT
> (minus the quotes).</P
><P
>For example, to clear the password for user bob, his smbpasswd file
entry would look like :</P
><P
><PRE
CLASS="PROGRAMLISTING"
> bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
</PRE
></P
><P
>If you are allowing users to use the smbpasswd command to set
their own passwords, you may want to give users NO PASSWORD initially
so they do not have to enter a previous password when changing to their
new password (not recommended). In order for you to allow this the
<B
CLASS="COMMAND"
>smbpasswd</B
> program must be able to connect to the
<B
CLASS="COMMAND"
>smbd</B
> daemon as that user with no password. Enable this
by adding the line :</P
><P
><B
CLASS="COMMAND"
>null passwords = yes</B
></P
><P
>to the [global] section of the smb.conf file (this is why
the above scenario is not recommended). Preferably, allocate your
users a default password to begin with, so you do not have
to enable this on your server.</P
><P
><I
CLASS="EMPHASIS"
>Note : </I
>This file should be protected very
carefully. Anyone with access to this file can (with enough knowledge of
the protocols) gain access to your SMB server. The file is thus more
sensitive than a normal unix <TT
CLASS="FILENAME"
>/etc/passwd</TT
> file.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN105"
>The smbpasswd Command</A
></H1
><P
>The smbpasswd command maintains the two 32 byte password fields
in the smbpasswd file. If you wish to make it similar to the unix
<B
CLASS="COMMAND"
>passwd</B
> or <B
CLASS="COMMAND"
>yppasswd</B
> programs,
install it in <TT
CLASS="FILENAME"
>/usr/local/samba/bin/</TT
> (or your
main Samba binary directory).</P
><P
>Note that as of Samba 1.9.18p4 this program <I
CLASS="EMPHASIS"
>MUST NOT
BE INSTALLED</I
> setuid root (the new <B
CLASS="COMMAND"
>smbpasswd</B
>
code enforces this restriction so it cannot be run this way by
accident).</P
><P
><B
CLASS="COMMAND"
>smbpasswd</B
> now 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.</P
><P
></P
><UL
><LI
><P
>smbpasswd no longer has to be setuid root -
an enormous range of potential security problems is
eliminated.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>smbpasswd</B
> now 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).</P
></LI
></UL
><P
>To run smbpasswd as a normal user just type :</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>smbpasswd</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>Old SMB password: </TT
><TT
CLASS="USERINPUT"
><B
>&lt;type old value here -
or hit return if there was no old password&gt;</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>New SMB Password: </TT
><TT
CLASS="USERINPUT"
><B
>&lt;type new value&gt;
</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>Repeat New SMB Password: </TT
><TT
CLASS="USERINPUT"
><B
>&lt;re-type new value
</B
></TT
></P
><P
>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.</P
><P
>If invoked by an ordinary user it will only allow the user
to change his or her own Samba password.</P
><P
>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.</P
><P
><B
CLASS="COMMAND"
>smbpasswd</B
> is designed to work in the same way
and be familiar to UNIX users who use the <B
CLASS="COMMAND"
>passwd</B
> or
<B
CLASS="COMMAND"
>yppasswd</B
> commands.</P
><P
>For more details on using <B
CLASS="COMMAND"
>smbpasswd</B
> refer
to the man page which will always be the definitive reference.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN144"
>Setting up Samba to support LanManager Encryption</A
></H1
><P
>This is a very brief description on how to setup samba to
support password encryption. </P
><P
></P
><OL
TYPE="1"
><LI
><P
>compile and install samba as usual</P
></LI
><LI
><P
>enable encrypted passwords in <TT
CLASS="FILENAME"
> smb.conf</TT
> by adding the line <B
CLASS="COMMAND"
>encrypt
passwords = yes</B
> in the [global] section</P
></LI
><LI
><P
>create the initial <TT
CLASS="FILENAME"
>smbpasswd</TT
>
password file in the place you specified in the Makefile
(--prefix=&lt;dir&gt;). See the notes under the <A
HREF="#SMBPASSWDFILEFORMAT"
>The smbpasswd File</A
>
section earlier in the document for details.</P
></LI
></OL
><P
>Note that you can test things using smbclient.</P
></DIV
></DIV
></BODY
></HTML
>

29
docs/htmldocs/NT_Security.html
View File

@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
></TITLE
>UNIX Permission Bits and WIndows NT Access Control Lists</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
@ -15,11 +15,20 @@ ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>UNIX Permission Bits and WIndows NT Access Control Lists</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2"
NAME="AEN3"
>Viewing and changing UNIX permissions using the NT
security dialogs</A
></H1
@ -58,7 +67,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN11"
NAME="AEN12"
>How to view file security on a Samba share</A
></H1
><P
@ -110,7 +119,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN22"
NAME="AEN23"
>Viewing file ownership</A
></H1
><P
@ -198,7 +207,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN42"
NAME="AEN43"
>Viewing file or directory permissions</A
></H1
><P
@ -260,7 +269,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN57"
NAME="AEN58"
>File Permissions</A
></H2
><P
@ -322,7 +331,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN71"
NAME="AEN72"
>Directory Permissions</A
></H2
><P
@ -354,7 +363,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN78"
NAME="AEN79"
>Modifying file or directory permissions</A
></H1
><P
@ -452,7 +461,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN100"
NAME="AEN101"
>Interaction with the standard Samba create mask
parameters</A
></H1
@ -726,7 +735,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN164"
NAME="AEN165"
>Interaction with the standard Samba file attribute
mapping</A
></H1

210
docs/htmldocs/OS2-Client-HOWTO.html Normal file
View File

@ -0,0 +1,210 @@
<HTML
><HEAD
><TITLE
>OS2 Client HOWTO</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>OS2 Client HOWTO</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>FAQs</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN5"
>How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</A
></H2
><P
>A more complete answer to this question can be
found on <A
HREF="http://carol.wins.uva.nl/~leeuw/samba/warp.html"
TARGET="_top"
> http://carol.wins.uva.nl/~leeuw/samba/warp.html</A
>.</P
><P
>Basically, you need three components:</P
><P
></P
><UL
><LI
><P
>The File and Print Client ('IBM Peer')
</P
></LI
><LI
><P
>TCP/IP ('Internet support')
</P
></LI
><LI
><P
>The "NetBIOS over TCP/IP" driver ('TCPBEUI')
</P
></LI
></UL
><P
>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.</P
><P
>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.</P
><P
>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.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN20"
>How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</A
></H2
><P
>You can use the free Microsoft LAN Manager 2.2c Client
for OS/2 from
<A
HREF="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/"
TARGET="_top"
> ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</A
>.
See <A
HREF="http://carol.wins.uva.nl/~leeuw/lanman.html"
TARGET="_top"
> http://carol.wins.uva.nl/~leeuw/lanman.html</A
> 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:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> 20=setup.exe
20=netwksta.sys
20=netvdd.sys
</PRE
></P
><P
>before you install the client. Also, don't use the
included NE2000 driver because it is buggy. Try the NE2000
or NS2000 driver from
<A
HREF="ftp://ftp.cdrom.com/pub/os2/network/ndis/"
TARGET="_top"
> ftp://ftp.cdrom.com/pub/os2/network/ndis/</A
> instead.
</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN29"
>Are there any other issues when OS/2 (any version)
is used as a client?</A
></H2
><P
>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 <A
HREF="http://carol.wins.uva.nl/~leeuw/samba/fix.html"
TARGET="_top"
> http://carol.wins.uva.nl/~leeuw/samba/fix.html</A
>.
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. </P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN33"
>How do I get printer driver download working
for OS/2 clients?</A
></H2
><P
>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.</P
><P
>Install the NT driver first for that printer. Then,
add to your smb.conf a paramater, "os2 driver map =
<TT
CLASS="REPLACEABLE"
><I
>filename</I
></TT
>". Then, in the file
specified by <TT
CLASS="REPLACEABLE"
><I
>filename</I
></TT
>, map the
name of the NT driver name to the OS/2 driver name as
follows:</P
><P
>&lt;nt driver name&gt; = &lt;os2 driver
name&gt;.&lt;device name&gt;, e.g.:
HP LaserJet 5L = LASERJET.HP LaserJet 5L</P
><P
>You can have multiple drivers mapped in this file.</P
><P
>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.
</P
></DIV
></DIV
></DIV
></BODY
></HTML
>

5936
docs/htmldocs/Samba-HOWTO-Collection.html Normal file
View File

File diff suppressed because it is too large Load Diff

1252
docs/htmldocs/Samba-PDC-HOWTO.html Normal file
View File

File diff suppressed because it is too large Load Diff

815
docs/htmldocs/UNIX_INSTALL.html Normal file
View File

@ -0,0 +1,815 @@
<HTML
><HEAD
><TITLE
>How to Install and Test SAMBA</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>How to Install and Test SAMBA</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Step 0: Read the man pages</A
></H1
><P
>The man pages distributed with SAMBA contain
lots of useful info that will help to get you started.
If you don't know how to read man pages then try
something like:</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>nroff -man smbd.8 | more
</B
></TT
></P
><P
>Other sources of information are pointed to
by the Samba web site,<A
HREF="http://www.samba.org/"
TARGET="_top"
> http://www.samba.org</A
></P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN11"
>Step 1: Building the Binaries</A
></H1
><P
>To do this, first run the program <B
CLASS="COMMAND"
>./configure
</B
> in the source directory. This should automatically
configure Samba for your operating system. If you have unusual
needs then you may wish to run</P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>./configure --help
</B
></TT
></P
><P
>first to see what special options you can enable.
Then exectuting</P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>make</B
></TT
></P
><P
>will create the binaries. Once it's successfully
compiled you can use </P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>make install</B
></TT
></P
><P
>to install the binaries and manual pages. You can
separately install the binaries and/or man pages using</P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>make installbin
</B
></TT
></P
><P
>and</P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>make installman
</B
></TT
></P
><P
>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</P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>make revert
</B
></TT
></P
><P
>if you find this version a disaster!</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN39"
>Step 2: The all important step</A
></H1
><P
>At this stage you must fetch yourself a
coffee or other drink you find stimulating. Getting the rest
of the install right can sometimes be tricky, so you will
probably need it.</P
><P
>If you have installed samba before then you can skip
this step.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN43"
>Step 3: Create the smb configuration file.</A
></H1
><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
"homes" as the service name. (Note that I also set the
workgroup that Samba is part of. See BROWSING.txt for defails)</P
><P
>Note that <B
CLASS="COMMAND"
>make install</B
> will not install
a <TT
CLASS="FILENAME"
>smb.conf</TT
> file. You need to create it
yourself. </P
><P
>Make sure you put the smb.conf 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
[homes] share please refer to the document UNIX_SECURITY.txt.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN57"
>Step 4: Test your config file with
<B
CLASS="COMMAND"
>testparm</B
></A
></H1
><P
>It's important that you test the validity of your
<TT
CLASS="FILENAME"
>smb.conf</TT
> file using the testparm 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
resonable before proceeding. </P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN63"
>Step 5: Starting the smbd and nmbd</A
></H1
><P
>You must choose to start smbd and nmbd either
as daemons or from <B
CLASS="COMMAND"
>inetd</B
>. Don't try
to do both! Either you can put them in <TT
CLASS="FILENAME"
> inetd.conf</TT
> and have them started on demand
by <B
CLASS="COMMAND"
>inetd</B
>, or you can start them as
daemons either from the command line or in <TT
CLASS="FILENAME"
> /etc/rc.local</TT
>. 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.</P
><P
>The main advantage of starting <B
CLASS="COMMAND"
>smbd</B
>
and <B
CLASS="COMMAND"
>nmbd</B
> as a daemon is that they will
respond slightly more quickly to an initial connection
request. This is, however, unlikely to be a problem.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN73"
>Step 5a: Starting from inetd.conf</A
></H2
><P
>NOTE; The following will be different if
you use NIS or NIS+ to distributed services maps.</P
><P
>Look at your <TT
CLASS="FILENAME"
>/etc/services</TT
>.
What is defined at port 139/tcp. If nothing is defined
then add a line like this:</P
><P
><TT
CLASS="USERINPUT"
><B
>netbios-ssn 139/tcp</B
></TT
></P
><P
>similarly for 137/udp you should have an entry like:</P
><P
><TT
CLASS="USERINPUT"
><B
>netbios-ns 137/udp</B
></TT
></P
><P
>Next edit your <TT
CLASS="FILENAME"
>/etc/inetd.conf</TT
>
and add two lines something like this:</P
><P
><PRE
CLASS="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
</PRE
></P
><P
>The exact syntax of <TT
CLASS="FILENAME"
>/etc/inetd.conf</TT
>
varies between unixes. Look at the other entries in inetd.conf
for a guide.</P
><P
>NOTE: Some unixes already have entries like netbios_ns
(note the underscore) in <TT
CLASS="FILENAME"
>/etc/services</TT
>.
You must either edit <TT
CLASS="FILENAME"
>/etc/services</TT
> or
<TT
CLASS="FILENAME"
>/etc/inetd.conf</TT
> to make them consistant.</P
><P
>NOTE: On many systems you may need to use the
"interfaces" option in smb.conf to specify the IP address
and netmask of your interfaces. Run <B
CLASS="COMMAND"
>ifconfig</B
>
as root if you don't know what the broadcast is for your
net. <B
CLASS="COMMAND"
>nmbd</B
> tries to determine it at run
time, but fails on somunixes. See the section on "testing nmbd"
for a method of finding if you need to do this.</P
><P
>!!!WARNING!!! Many unixes only accept around 5
parameters on the command line in <TT
CLASS="FILENAME"
>inetd.conf</TT
>.
This means you shouldn't use spaces between the options and
arguments, or you should use a script, and start the script
from <B
CLASS="COMMAND"
>inetd</B
>.</P
><P
>Restart <B
CLASS="COMMAND"
>inetd</B
>, perhaps just send
it a HUP. If you have installed an earlier version of <B
CLASS="COMMAND"
> nmbd</B
> then you may need to kill nmbd as well.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN102"
>Step 5b. Alternative: starting it as a daemon</A
></H2
><P
>To start the server as a daemon you should create
a script something like this one, perhaps calling
it <TT
CLASS="FILENAME"
>startsmb</TT
>.</P
><P
><PRE
CLASS="PROGRAMLISTING"
> #!/bin/sh
/usr/local/samba/bin/smbd -D
/usr/local/samba/bin/nmbd -D
</PRE
></P
><P
>then make it executable with <B
CLASS="COMMAND"
>chmod
+x startsmb</B
></P
><P
>You can then run <B
CLASS="COMMAND"
>startsmb</B
> by
hand or execute it from <TT
CLASS="FILENAME"
>/etc/rc.local</TT
>
</P
><P
>To kill it send a kill signal to the processes
<B
CLASS="COMMAND"
>nmbd</B
> and <B
CLASS="COMMAND"
>smbd</B
>.</P
><P
>NOTE: If you use the SVR4 style init system then
you may like to look at the <TT
CLASS="FILENAME"
>examples/svr4-startup</TT
>
script to make Samba fit into that system.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN118"
>Step 6: Try listing the shares available on your
server</A
></H1
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>smbclient -L
<TT
CLASS="REPLACEABLE"
><I
>yourhostname</I
></TT
></B
></TT
></P
><P
>Your 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"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN127"
>Step 7: Try connecting with the unix client</A
></H1
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>smbclient <TT
CLASS="REPLACEABLE"
><I
> //yourhostname/aservice</I
></TT
></B
></TT
></P
><P
>Typically the <TT
CLASS="REPLACEABLE"
><I
>yourhostname</I
></TT
>
would be the name of the host where you installed <B
CLASS="COMMAND"
> smbd</B
>. The <TT
CLASS="REPLACEABLE"
><I
>aservice</I
></TT
> is
any service you have defined in the <TT
CLASS="FILENAME"
>smb.conf</TT
>
file. Try your user name if you just have a [homes] section
in <TT
CLASS="FILENAME"
>smb.conf</TT
>.</P
><P
>For example if your unix host is bambi and your login
name is fred you would type:</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>smbclient //bambi/fred
</B
></TT
></P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN143"
>Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
Win2k, OS/2, etc... client</A
></H1
><P
>Try mounting disks. eg:</P
><P
><TT
CLASS="PROMPT"
>C:\WINDOWS\&#62; </TT
><TT
CLASS="USERINPUT"
><B
>net use d: \\servername\service
</B
></TT
></P
><P
>Try printing. eg:</P
><P
><TT
CLASS="PROMPT"
>C:\WINDOWS\&#62; </TT
><TT
CLASS="USERINPUT"
><B
>net use lpt1:
\\servername\spoolservice</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>C:\WINDOWS\&#62; </TT
><TT
CLASS="USERINPUT"
><B
>print filename
</B
></TT
></P
><P
>Celebrate, or send me a bug report!</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN157"
>What If Things Don't Work?</A
></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
again) till you calm down.</P
><P
>Then you might read the file DIAGNOSIS.txt 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 PLEASE send me some updates to the
documentation (or source code) so that the next person will find it
easier. </P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN162"
>Diagnosing Problems</A
></H2
><P
>If you have instalation problems then go to
<TT
CLASS="FILENAME"
>DIAGNOSIS.txt</TT
> to try to find the
problem.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN166"
>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 -i &lt;scope&gt; option to nmbd, smbd, and
smbclient. 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"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN169"
>Choosing the Protocol Level</A
></H2
><P
>The SMB protocol has many dialects. Currently
Samba supports 5, called CORE, COREPLUS, LANMAN1,
LANMAN2 and NT1.</P
><P
>You can choose what maximum protocol to support
in the <TT
CLASS="FILENAME"
>smb.conf</TT
> file. The default is
NT1 and that is the best for the vast majority of sites.</P
><P
>In older versions of Samba you may have found it
necessary to use COREPLUS. The limitations that led to
this have mostly been fixed. It is now less likely that you
will want to use less than LANMAN1. The only remaining advantage
of COREPLUS is that for some obscure reason WfWg preserves
the case of passwords in this protocol, whereas under LANMAN1,
LANMAN2 or NT1 it uppercases all passwords before sending them,
forcing you to use the "password level=" option in some cases.</P
><P
>The main advantage of LANMAN2 and NT1 is support for
long filenames with some clients (eg: smbclient, Windows NT
or Win95). </P
><P
>See the smb.conf(5) manual page for more details.</P
><P
>Note: 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.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN178"
>Printing from UNIX to a Client PC</A
></H2
><P
>To use a printer that is available via a smb-based
server from a unix host you will need to compile the
smbclient program. You then need to install the script
"smbprint". Read the instruction in smbprint for more details.
</P
><P
>There is also a SYSV style script that does much
the same thing called smbprint.sysv. It contains instructions.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN182"
>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
>Samba supports "record locking" using the fcntl() unix system
call. This is often implemented using rpc calls to a rpc.lockd process
running on the system that owns the filesystem. Unfortunately many
rpc.lockd implementations are very buggy, particularly when made to
talk to versions from other vendors. It is not uncommon for the
rpc.lockd to crash.</P
><P
>There is also a problem translating the 32 bit lock
requests generated by PC clients to 31 bit requests supported
by most unixes. Unfortunately many PC applications (typically
OLE2 applications) use byte ranges with the top bit set
as semaphore sets. Samba attempts translation to support
these types of applications, and the translation has proved
to be quite successful.</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 compatability modes called
DENY_FCB and DENY_DOS.</P
><P
>You can disable share modes using "share modes = no".
This may be useful on a heavily loaded server as the share
modes code is very slow. See also the FAST_SHARE_MODES
option in the Makefile for a way to do full share modes
very fast using shared memory (if your OS supports it).</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN192"
>Mapping Usernames</A
></H2
><P
>If you have different usernames on the PCs and
the unix server then take a look at the "username map" option.
See the smb.conf man page for details.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN195"
>Other Character Sets</A
></H2
><P
>If you have problems using filenames with accented
characters in them (like the German, French or Scandinavian
character sets) then I recommmend you look at the "valid chars"
option in smb.conf and also take a look at the validchars
package in the examples directory.</P
></DIV
></DIV
></DIV
></BODY
></HTML
>

4
docs/htmldocs/lmhosts.5.html
View File

@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
NAME="LMHOSTS"
>lmhosts</A
></H1
><DIV
@ -108,7 +108,7 @@ NAME="AEN20"
><PRE
CLASS="PROGRAMLISTING"
>#
#Sample Samba lmhosts file.
# Sample Samba lmhosts file.
#
192.9.200.1 TESTPC
192.9.200.20 NTSERVER#20

210
docs/htmldocs/msdfs_setup.html Normal file
View File

@ -0,0 +1,210 @@
<HTML
><HEAD
><TITLE
>Hosting a Microsoft Distributed File System tree on Samba</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>Hosting a Microsoft Distributed File System tree on Samba</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Instructions</A
></H1
><P
>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 <A
HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
TARGET="_top"
> Microsoft documentation</A
>. </P
><P
>This document explains how to host a Dfs tree on a Unix
machine (for Dfs-aware clients to browse) using Samba.</P
><P
>To enable SMB-based DFS for Samba, configure it with the
<TT
CLASS="PARAMETER"
><I
>--with-msdfs</I
></TT
> option. Once built, a
Samba server can be made a Dfs server by setting the global
boolean <A
HREF="smb.conf.5.html#HOSTMSDFS"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
> host msdfs</I
></TT
></A
> parameter in the <TT
CLASS="FILENAME"
>smb.conf
</TT
> file. You designate a share as a Dfs root using the share
level boolean <A
HREF="smb.conf.5.html#MSDFSROOT"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
> msdfs root</I
></TT
></A
> 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
<TT
CLASS="FILENAME"
>junction-&gt;msdfs:storage1\share1</TT
> 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).</P
><P
>Dfs trees on Samba work with all Dfs-aware clients ranging
from Windows 95 to 2000.</P
><P
>Here's an example of setting up a Dfs tree on a Samba
server.</P
><P
><PRE
CLASS="PROGRAMLISTING"
># The smb.conf file:
[global]
netbios name = SAMBA
host msdfs = yes
[dfs]
path = /export/dfsroot
msdfs root = yes
</PRE
></P
><P
>In the /export/dfsroot directory we set up our dfs links to
other servers on the network.</P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>cd /export/dfsroot</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>chown root /export/dfsroot</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>chmod 755 /export/dfsroot</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>ln -s msdfs:storageA\\shareA linka</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>root# </TT
><TT
CLASS="USERINPUT"
><B
>ln -s msdfs:serverB\\share,serverC\\share linkb</B
></TT
></P
><P
>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.</P
><P
>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.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN38"
>Notes</A
></H2
><P
></P
><UL
><LI
><P
>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.</P
></LI
><LI
><P
>Currently there's a restriction that msdfs
symlink names should all be lowercase.</P
></LI
><LI
><P
>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.</P
></LI
></UL
></DIV
></DIV
></DIV
></BODY
></HTML
>

744
docs/htmldocs/printer_driver2.html Normal file
View File

@ -0,0 +1,744 @@
<HTML
><HEAD
><TITLE
>Printing Support in Samba 2.2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>Printing Support in Samba 2.2.x</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Introduction</A
></H1
><P
>Beginning with the 2.2.0 release, Samba supports
the native Windows NT printing mechanisms implemented via
MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of
Samba only supported LanMan printing calls.</P
><P
>The additional functionality provided by the new
SPOOLSS support includes:</P
><P
></P
><UL
><LI
><P
>Support for downloading printer driver
files to Windows 95/98/NT/2000 clients upon demand.
</P
></LI
><LI
><P
>Uploading of printer drivers via the
Windows NT Add Printer Wizard (APW) or the <A
HREF="http://imprints.sourceforge.net"
TARGET="_top"
>Imprints tool set
</A
></P
></LI
><LI
><P
>Support for the native MS-RPC printing
calls such as StartDocPrinter, EnumJobs(), etc... (See
the <A
HREF="http://msdn.microsoft.com/"
TARGET="_top"
>MSDN documentation
</A
> for more information on the Win32 printing API)
</P
></LI
><LI
><P
>Support for NT Access Control Lists (ACL)
on printer objects</P
></LI
><LI
><P
>Improved support for printer queue manipulation
through the use of an internal databases for spooled job
information</P
></LI
></UL
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN20"
>Configuration</A
></H1
><P
>In order to support the uploading of printer driver
files, you must first configure a file share named [print$].
The name of this share is hard coded in Samba's internals so
the name is very important (print$ is the service used by
Windows NT print servers to provide support for printer driver
download).</P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
>Previous versions of Samba recommended using
a share named [printer$]. This name was taken from the
printer$ service created by Windows 9x clients when a
printer was shared. Windows 9x printer servers always have
a printer$ service which provides read-only access via no
password in order to support printer driver downloads.</P
><P
>However, the initial implementation allowed for a
parameter named <TT
CLASS="PARAMETER"
><I
>printer driver location</I
></TT
>
to be used on a per share basis to specify the location of
the driver files associated with that printer. Another
parameter named <TT
CLASS="PARAMETER"
><I
>printer driver</I
></TT
> provided
a means of defining the printer driver name to be sent to
the client.</P
><P
>These parameters, including <TT
CLASS="PARAMETER"
><I
>printer driver
file</I
></TT
> parameter, are being depreciated and should not
be used in new installations. For more information on this change,
you should refer to the <A
HREF="#MIGRATION"
>Migration section
</A
>of this document.</P
></TD
></TR
></TABLE
></DIV
><P
>You should modify the server's smb.conf file to create the
following file share (of course, some of the parameter values,
such as 'path' are arbitrary and should be replaced with
appropriate values for your site):</P
><P
><PRE
CLASS="PROGRAMLISTING"
>[print$]
path = /usr/local/samba/printers
guest ok = yes
browseable = yes
read only = yes
write list = ntadmin
</PRE
></P
><P
>The <A
HREF="smb.conf.5.html#WRITELIST"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
> write list</I
></TT
></A
> is used to allow administrative
level user accounts to have write access in order to update files
on the share. See the <A
HREF="smb./conf.5.html"
TARGET="_top"
> smb.conf(5) man page</A
> for more information on
configuring file shares.</P
><P
>The requirement for <A
HREF="smb.conf.5.html#GUESTOK"
TARGET="_top"
><B
CLASS="COMMAND"
> guest ok = yes</B
></A
> depends upon how your
site is configured. If users will be guaranteed to have
an account on the Samba host, then this is a non-issue.</P
><P
><I
CLASS="EMPHASIS"
>author's note: </I
>The non-issue is that
if all your Windows NT users are guarenteed to be authenticated
by the Samba server (such as a domain member server and the NT
user has already been validated by the Domain Controller in
order to logon to the Windows NT console), then guest access
is not necessary. Of course, in a workgroup environment where
you just want to be able to print without worrying about
silly accounts and security, then configure the share for
guest access. You'll probably want to add <A
HREF="smb.conf.5.html#MAPTOGUEST"
TARGET="_top"
><B
CLASS="COMMAND"
>map to guest = Bad User
</B
></A
> in the [global] section as well. Make sure
you understand what this parameter does before using it
though. --jerry]</P
><P
>In order for a Windows NT print server to support
the downloading of driver files by multiple client architectures,
it must create subdirectories within the [print$] service
which correspond to each of the supported client architectures.
Samba follows this model as well.</P
><P
>Next create the directory tree below the [print$] share
for each architecture you wish to support.</P
><P
><PRE
CLASS="PROGRAMLISTING"
> [print$]-----
|-W32X86 ; "Windows NT x86"
|-WIN40 ; "Windows 95/98"
|-W32ALPHA ; "Windows NT Alpha_AXP"
|-W32MIPS ; "Windows NT R4000"
|-W32PPC ; "Windows NT PowerPC"
</PRE
></P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
><I
CLASS="EMPHASIS"
>ATTENTION! REQUIRED PERMISSIONS</I
></P
><P
>In order to currently add a new driver to you Samba host,
one of two conditions must hold true:</P
><P
></P
><UL
><LI
><P
>The account used to connect to the Samba host
must have a uid of 0 (i.e. a root account)</P
></LI
><LI
><P
>The account used to connect to the Samba host
must be a member of the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
> printer admin</I
></TT
></A
> list.</P
></LI
></UL
><P
>Of course, the connected account must still possess access
to add files to the subdirectories beneath [print$].</P
></TD
></TR
></TABLE
></DIV
><P
>Once you have created the required [print$] service and
associated subdirectories, simply log onto the Samba server using
a root (or <TT
CLASS="PARAMETER"
><I
>printer admin</I
></TT
>) account
from a Windows NT 4.0 client. Navigate to the "Printers" folder
on the Samba server. You should see an initial listing of printers
that matches the printer shares defined on your Samba host.</P
><P
>The initial listing of printers in the Samba host's
Printers folder will have no printer driver assigned to them.
The way assign a driver to a printer is to view the Properties
of the printer and either</P
><P
></P
><UL
><LI
><P
>Use the "New Driver..." button to install
a new printer driver, or</P
></LI
><LI
><P
>Select a driver from the popup list of
installed drivers. Initially this list will be empty.</P
></LI
></UL
><P
>If you wish to install printer drivers for client
operating systems other than "Windows NT x86", you will need
to use the "Sharing" tab of the printer properties dialog.</P
><P
>Assuming you have connected with a root account, you
will also be able modify other printer properties such as
ACLs and device settings using this dialog box.</P
><P
>A few closing comments for this section, it is possible
on a Windows NT print server to have printers
listed in the Printers folder which are not shared. Samba does
not make this distinction. By definition, the only printers of
which Samba is aware are those which are specified as shares in
<TT
CLASS="FILENAME"
>smb.conf</TT
>.</P
><P
>Another interesting side note is that Windows NT clients do
not use the SMB printer share, but rather can print directly
to any printer on another Windows NT host using MS-RPC. This
of course assumes that the printing client has the necessary
privileges on the remote host serving the printer. The default
permissions assigned by Windows NT to a printer gives the "Print"
permissions to the "Everyone" well-known group.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN74"
>Support a large number of printers</A
></H2
><P
>One issue that has arisen during the development
phase of Samba 2.2 is the need to support driver downloads for
100's of printers. Using the Windows NT APW is somewhat
awkward to say the list. If more than one printer are using the
same driver, the <A
HREF="rpcclient.1.html"
TARGET="_top"
><B
CLASS="COMMAND"
>rpcclient's
setdriver command</B
></A
> can be used to set the driver
associated with an installed driver. The following is example
of how this could be accomplished:</P
><P
><PRE
CLASS="PROGRAMLISTING"
>
<TT
CLASS="PROMPT"
>$ </TT
>rpcclient pogo -U root%secret -c "enumdrivers"
Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
[Windows NT x86]
Printer Driver Info 1:
Driver Name: [HP LaserJet 4000 Series PS]
Printer Driver Info 1:
Driver Name: [HP LaserJet 2100 Series PS]
Printer Driver Info 1:
Driver Name: [HP LaserJet 4Si/4SiMX PS]
<TT
CLASS="PROMPT"
>$ </TT
>rpcclient pogo -U root%secret -c "enumprinters"
Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
flags:[0x800000]
name:[\\POGO\hp-print]
description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
comment:[]
<TT
CLASS="PROMPT"
>$ </TT
>rpcclient pogo -U root%bleaK.er \
<TT
CLASS="PROMPT"
>&gt; </TT
> -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
Succesfully set hp-print to driver HP LaserJet 4000 Series PS.
</PRE
></P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN85"
>The Imprints Toolset</A
></H1
><P
>The Imprints tool set provides a UNIX equivalent of the
Windows NT Add Printer Wizard. For complete information, please
refer to the Imprints web site at <A
HREF="http://imprints.sourceforge.net/"
TARGET="_top"
> http://imprints.sourceforge.net/</A
> as well as the documentation
included with the imprints source distribution. This section will
only provide a brief introduction to the features of Imprints.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN89"
>What is Imprints?</A
></H2
><P
>Imprints is a collection of tools for supporting the goals
of</P
><P
></P
><UL
><LI
><P
>Providing a central repository information
regarding Windows NT and 95/98 printer driver packages</P
></LI
><LI
><P
>Providing the tools necessary for creating
the Imprints printer driver packages.</P
></LI
><LI
><P
>Providing an installation client which
will obtain and install printer drivers on remote Samba
and Windows NT 4 print servers.</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN99"
>Creating Printer Driver Packages</A
></H2
><P
>The process of creating printer driver packages is beyond
the scope of this document (refer to Imprints.txt also included
with the Samba distribution for more information). In short,
an Imprints driver package is a gzipped tarball containing the
driver files, related INF files, and a control file needed by the
installation client.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN102"
>The Imprints server</A
></H2
><P
>The Imprints server is really a database server that
may be queried via standard HTTP mechanisms. Each printer
entry in the database has an associated URL for the actual
downloading of the package. Each package is digitally signed
via GnuPG which can be used to verify that package downloaded
is actually the one referred in the Imprints database. It is
<I
CLASS="EMPHASIS"
>not</I
> recommended that this security check
be disabled.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN106"
>The Installation Client</A
></H2
><P
>More information regarding the Imprints installation client
is available in the <TT
CLASS="FILENAME"
>Imprints-Client-HOWTO.ps</TT
>
file included with the imprints source package.</P
><P
>The Imprints installation client comes in two forms.</P
><P
></P
><UL
><LI
><P
>a set of command line Perl scripts</P
></LI
><LI
><P
>a GTK+ based graphical interface to
the command line perl scripts</P
></LI
></UL
><P
>The installation client (in both forms) provides a means
of querying the Imprints database server for a matching
list of known printer model names as well as a means to
download and install the drivers on remote Samba and Windows
NT print servers.</P
><P
>The basic installation process is in four steps and
perl code is wrapped around <B
CLASS="COMMAND"
>smbclient</B
>
and <B
CLASS="COMMAND"
>rpcclient</B
>.</P
><P
><PRE
CLASS="PROGRAMLISTING"
>
foreach (supported architecture for a given driver)
{
1. rpcclient: Get the appropriate upload directory
on the remote server
2. smbclient: Upload the driver files
3. rpcclient: Issues an AddPrinterDriver() MS-RPC
}
4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually
create the printer
</PRE
></P
><P
>One of the problems encountered when implementing
the Imprints tool set was the name space issues between
various supported client architectures. For example, Windows
NT includes a driver named "Apple LaserWriter II NTX v51.8"
and Windows 95 callsits version of this driver "Apple
LaserWriter II NTX"</P
><P
>The problem is how to know what client drivers have
been uploaded for a printer. As astute reader will remember
that the Windows NT Printer Properties dialog only includes
space for one printer driver name. A quick look in the
Windows NT 4.0 system registry at</P
><P
><TT
CLASS="FILENAME"
>HKLM\System\CurrentControlSet\Control\Print\Environment
</TT
></P
><P
>will reveal that Windows NT always uses the NT driver
name. The is ok as Windows NT always requires that at least
the Windows NT version of the printer driver is present.
However, Samba does not have the requirement internally.
Therefore, how can you use the NT driver name if is has not
already been installed?</P
><P
>The way of sidestepping this limitation is to require
that all Imprints printer driver packages include both the Intel
Windows NT and 95/98 printer drivers and that NT driver is
installed first.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN128"
><A
NAME="MIGRATION"
></A
>Migration to from Samba 2.0.x to
2.2.x</A
></H1
><P
>Given that printer driver management has changed
(we hope improved :) ) in 2.2.0 over prior releases,
migration from an existing setup to 2.2.0 can follow
several paths.</P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
>The following smb.conf parameters are considered to be
depreciated and will be removed soon. Do not use them
in new installations</P
><P
></P
><UL
><LI
><P
><TT
CLASS="PARAMETER"
><I
>printer driver file (G)</I
></TT
>
</P
></LI
><LI
><P
><TT
CLASS="PARAMETER"
><I
>printer driver (S)</I
></TT
>
</P
></LI
><LI
><P
><TT
CLASS="PARAMETER"
><I
>printer driver location (S)</I
></TT
>
</P
></LI
></UL
></TD
></TR
></TABLE
></DIV
><P
>Here are the possible scenarios for supporting migration:</P
><P
></P
><UL
><LI
><P
>If you do not desire the new Windows NT
print driver support, nothing needs to be done.
All existing parameters work the same.</P
></LI
><LI
><P
>If you want to take advantage of NT printer
driver support but do not want to migrate the
9x drivers to the new setup, the leave the existing
printers.def file. When smbd attempts to locate a
9x driver for the printer in the TDB and fails it
will drop down to using the printers.def (and all
associated parameters). The <B
CLASS="COMMAND"
>make_printerdef</B
>
tool will also remain for backwards compatibility but will
be moved to the "this tool is the old way of doing it"
pile.</P
></LI
><LI
><P
>If you install a Windows 9x driver for a printer
on your Samba host (in the printing TDB), this information will
take precedence and the three old printing parameters
will be ignored (including print driver location).</P
></LI
><LI
><P
>If you want to migrate an existing <TT
CLASS="FILENAME"
> printers.def</TT
> file into the new setup, the current only
solution is to use the Windows NT APW to install the NT drivers
and the 9x drivers. This can be scripted using smbclient and
rpcclient. See the <A
HREF="http://imprints.sourceforge.net/"
TARGET="_top"
> Imprints insrallation client</A
> for an example.
</P
></LI
></UL
></DIV
></DIV
></BODY
></HTML
>

642
docs/htmldocs/rpcclient.1.html
View File

@ -24,7 +24,7 @@ NAME="AEN5"
></A
><H2
>Name</H2
>rpcclient&nbsp;--&nbsp;developer's tool to testing client side
>rpcclient&nbsp;--&nbsp;tool for executing client side
MS-RPC functions</DIV
><DIV
CLASS="REFSYNOPSISDIV"
@ -36,13 +36,13 @@ NAME="AEN8"
><P
><B
CLASS="COMMAND"
>nmblookup</B
> [-d debuglevel] [-S server] [-U username] [-W workgroup] [-n &lt;netbios name&gt;] [-A authfile] [-N] [-l logfile] [-I destinationIP] [-E &lt;terminal code&gt;] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-s &lt;smb config file&gt;]</P
>rpcclient</B
> {server} [-A authfile] [-c &lt;command string&gt;] [-d debuglevel] [-h] [-l logfile] [-N] [-s &lt;smb config file&gt;] [-U username[%password]] [-W workgroup] [-N]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN25"
NAME="AEN22"
></A
><H2
>DESCRIPTION</H2
@ -56,16 +56,16 @@ TARGET="_top"
><B
CLASS="COMMAND"
>rpcclient</B
> is a utility for developers for
executing various MS-RPC functions. It's primary use is for testing
Samba's own MS-RPC server implementation, however many administrators
have written scripts around it to manage Windows NT clients from
> is a utility initially developed
to test MS-RPC functionality in Samba itself. It has undergone
several stages of development and stability. Many system administrators
have now written scripts around it to manage Windows NT clients from
their UNIX workstation. </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN31"
NAME="AEN28"
></A
><H2
>OPTIONS</H2
@ -75,27 +75,68 @@ NAME="AEN31"
CLASS="VARIABLELIST"
><DL
><DT
>server</DT
><DD
><P
>NetBIOS name of Server to which to connect.
The server can be any SMB/CIFS server. The name is
resolved using the <A
HREF="smb.conf.5.html#NAMERESOLVEORDER"
TARGET="_top"
> <TT
CLASS="PARAMETER"
><I
>name resolve order</I
></TT
></A
> line from
<TT
CLASS="FILENAME"
>smb.conf(5)</TT
>.</P
></DD
><DT
>-A filename</DT
><DD
><P
>This option allows
you to specify a file from which to read the username and
password used in the connection. The format of the file is
</P
><P
><PRE
CLASS="PROGRAMLISTING"
> username = &lt;value&gt;
password = &lt;value&gt;
domain = &lt;value&gt;
</PRE
></P
><P
>Make certain that the permissions on the file restrict
access from unwanted users. </P
></DD
><DT
>-c 'command string'</DT
><DD
><P
>execute semicolon separated commands (listed
below)) </P
></DD
><DT
>-d debuglevel</DT
><DD
><P
>set the debuglevel. Debug level 0 is the lowest
and 100 being the highest. This should be set to 100 if you are
planning on submitting a bug report to the Samba team
(see BUGS.txt). </P
planning on submitting a bug report to the Samba team (see BUGS.txt).
</P
></DD
><DT
>-S server</DT
>-h</DT
><DD
><P
>NetBIOS name of Server to which you wish to
connect. The server can be any SMB/CIFS server. The name is
resolved using either the <TT
CLASS="PARAMETER"
><I
>name resolve order</I
></TT
>
line or by using the -R option. </P
>Print a summary of command line options.
</P
></DD
><DT
>-l logbasename</DT
@ -106,74 +147,54 @@ CLASS="PARAMETER"
</P
></DD
><DT
>-n netbios name</DT
><DD
><P
>NetBIOS name of the
local machine. This option is only needed if your Samba client
cannot find it automatically. Samba should use the uppercase
of the machine's hostname. </P
></DD
><DT
>-N</DT
><DD
><P
>tells rpcclient not to ask for a password.
<B
>instruct <B
CLASS="COMMAND"
>rpcclient</B
> will prompt the user by default.
</P
></DD
><DT
>-I destinationIP</DT
><DD
><P
>The IP address of the server specified with
the -S option. Only needed when the server's NetBIOS name cannot
be resolved using WINS or broadcast and isn't found in the LMHOSTS
file. </P
></DD
><DT
>-E</DT
><DD
><P
>causes <B
> not to ask
for a password. By default, <B
CLASS="COMMAND"
>rpcclient</B
> to write
messages to stderr instead of stdout. </P
></DD
><DT
>-U username[%pass]</DT
><DD
><P
>Sets the SMB username or username and password.
If %pass is not specified, The user will be prompted. The client
will first check the USER environment variable, then the
<TT
> will prompt
for a password. See also the <TT
CLASS="PARAMETER"
><I
>$LOGNAME</I
>-U</I
></TT
> option.</P
></DD
><DT
>-s smb.conf</DT
><DD
><P
>Specifies the location of the all important
<TT
CLASS="FILENAME"
>smb.conf</TT
> file. </P
></DD
><DT
>-U username[%password]</DT
><DD
><P
>Sets the SMB username or username and password. </P
><P
>If %password is not specified, The user will be prompted. The
client will first check the <TT
CLASS="ENVAR"
>USER</TT
> environment variable, then the
<TT
CLASS="ENVAR"
>LOGNAME</TT
> variable and if either exist, the
string is uppercased. Anything in these variables following a '%'
sign will be treated as the password. If these environmental
variables are not found, the username <TT
string is uppercased. If these environmental variables are not
found, the username <TT
CLASS="CONSTANT"
>GUEST</TT
>
is used. </P
><P
>If the password is not included in these environment
variables (using the %pass syntax), rpcclient will look for
a <TT
CLASS="PARAMETER"
><I
>$PASSWD</I
></TT
> environment variable from which
to read the password. </P
> is used. </P
><P
>A third option is to use a credentials file which
contains the plaintext of the username and password. This
@ -188,18 +209,12 @@ CLASS="PARAMETER"
></TT
> for more details. </P
><P
>Be cautious about including passwords in scripts or in
the <TT
CLASS="PARAMETER"
><I
>$PASSWD</I
></TT
> environment variable. Also, on
>Be cautious about including passwords in scripts. Also, on
many systems the command line of a running process may be seen
via the <B
CLASS="COMMAND"
>ps</B
> command to be safe always allow
> command. To be safe always allow
<B
CLASS="COMMAND"
>rpcclient</B
@ -207,25 +222,6 @@ CLASS="COMMAND"
it in directly. </P
></DD
><DT
>-A filename</DT
><DD
><P
>This option allows
you to specify a file from which to read the username and
password used in the connection. The format of the file is
</P
><P
><PRE
CLASS="PROGRAMLISTING"
>username = &lt;value&gt;
password = &lt;value&gt;
</PRE
></P
><P
>Make certain that the permissions on the file restrict
access from unwanted users. </P
></DD
><DT
>-W domain</DT
><DD
><P
@ -241,82 +237,20 @@ CLASS="PARAMETER"
it causes the client to log on using the server's local SAM (as
opposed to the Domain SAM). </P
></DD
><DT
>-P</DT
><DD
><P
>operate in promptless mode. Without this
mode (the default) <B
CLASS="COMMAND"
>rpcclient</B
> displays a
prompt of the form '[domain\username@host]$' </P
></DD
><DT
>-c 'command string'</DT
><DD
><P
>execute semicolon separated commands (listed
below)) </P
></DD
><DT
>-t terminalcode</DT
><DD
><P
>This tells the Samba client how to interpret
the incoming filenames, in regards to character sets. The list
here is not complete. For a complete list see your local Samba
source. Some valid options are sjis, euc, jis7, jis8, junet
and hex. </P
></DD
><DT
>-O socket options</DT
><DD
><P
>These socket options are the same as in
<TT
CLASS="FILENAME"
>smb.conf</TT
> (under the <TT
CLASS="PARAMETER"
><I
>socket options
</I
></TT
> section). </P
></DD
><DT
>-s smb.conf</DT
><DD
><P
>Specifies the location of the all important
<TT
CLASS="FILENAME"
>smb.conf</TT
> file. </P
></DD
><DT
>-i scope</DT
><DD
><P
>Defines the NetBIOS scope. For more
information on NetBIOS scopes, see rfc1001 and rfc1002. NetBIOS
scopes are rarely used. </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN119"
NAME="AEN91"
></A
><H2
>COMMANDS</H2
><P
><I
CLASS="EMPHASIS"
>SPOOLSS Commands</I
>LSARPC</I
></P
><P
></P
@ -325,116 +259,94 @@ CLASS="EMPHASIS"
><P
><B
CLASS="COMMAND"
>spoolenum</B
> - Execute an EnumPrinters()
call. This lists the various installed and share printers. Refer
to the MS Platform SDK documentation for more details of the various
flags and calling options. </P
>lsaquery</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spoolenumports level
</B
> - Executes an EnumPorts() call using the specified
info level. Currently only info level 1 and 2 are supported.
</P
>lookupsids</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spoolenumdata</B
> - Enumerate all
printer setting data stored on the server. On Windows NT clients,
these values are stored in the registry, while Samba servers
store them in the printers TDB. This command corresponds
to the MS Platform SDK GetPrinterData() function. </P
>lookupnames</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spooljobs printer</B
> - List the jobs
and status of a given printer.
This command corresponds to the MS Platform SDK EnumJobs()
function. </P
>enumtrusts</B
></P
></LI
><LI
></UL
><P
><B
CLASS="COMMAND"
>spoolopen printer
</B
> - Execute an OpenPrinterEx() and ClosePrinter() RPC
against a given printer. </P
></LI
><LI
> </P
><P
><B
CLASS="COMMAND"
>spoolgetdata printer
</B
> - Retrieve the data for a given printer setting. See
the <B
CLASS="COMMAND"
>spoolenumdata</B
> command for more information.
This command corresponds to the GetPrinterData() MS Platform
SDK function. </P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spoolgetprinter printer
</B
> - Retrieve the current printer information. This command
corresponds to the GetPrinter() MS Platform SDK function.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spoolgetprinterdriver
printer</B
> - Retrieve the printer driver information
(such as driver file, config file, dependent files, etc...) for
the given printer. This command corresponds to the GetPrinterDriver()
MS Platform SDK function. </P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spoolgetprinterdriverdir
arch</B
> - Execute a GetPrinterDriverDirectory()
RPC to retreive the SMB share name and subdirectory for
storing printer driver files for a given architecture. Possible
values for <TT
CLASS="PARAMETER"
><I
>arch</I
></TT
> are "Windows 4.0"
(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
Alpha_AXP", and "Windows NT R4000". </P
CLASS="EMPHASIS"
>SAMR</I
></P
><P
></P
><UL
><LI
><P
><B
CLASS="COMMAND"
>queryuser</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>spooladdprinterdriver
arch config</B
> - Execute an
AddPrinterDriver() RPC to install the printer driver information
on the server. Note that the driver files should already exist
in the directory returned by spoolgetprinterdriverdir. Possible
values for <TT
>querygroup</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>queryusergroups</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>querygroupmem</B
></P
></LI
></UL
><P
> </P
><P
><I
CLASS="EMPHASIS"
>SPOOLSS</I
></P
><P
></P
><UL
><LI
><P
><B
CLASS="COMMAND"
>adddriver &lt;arch&gt; &lt;config&gt;</B
>
- Execute an AddPrinterDriver() RPC to install the printer driver
information on the server. Note that the driver files should
already exist in the directory returned by
<B
CLASS="COMMAND"
>getdriverdir</B
>. Possible values for
<TT
CLASS="PARAMETER"
><I
>arch</I
@ -442,7 +354,7 @@ CLASS="PARAMETER"
> are the same as those for
the <B
CLASS="COMMAND"
>spooolgetprintedriverdir</B
>getdriverdir</B
> command.
The <TT
CLASS="PARAMETER"
@ -454,14 +366,14 @@ CLASS="PARAMETER"
><P
><PRE
CLASS="PROGRAMLISTING"
>Long Printer Name:\
Driver File Name:\
Data File Name:\
Config File Name:\
Help File Name:\
Language Monitor Name:\
Default Data Type:\
Comma Separated list of Files
> Long Printer Name:\
Driver File Name:\
Data File Name:\
Config File Name:\
Help File Name:\
Language Monitor Name:\
Default Data Type:\
Comma Separated list of Files
</PRE
></P
><P
@ -478,24 +390,168 @@ Comma Separated list of Files
><P
><B
CLASS="COMMAND"
>spooladdprinter printername
sharename drivername port
</B
> - Add a printer on the remote server. This printer
>addprinter &lt;printername&gt;
&lt;sharename&gt; &lt;drivername&gt; &lt;port&gt;</B
>
- Add a printer on the remote server. This printer
will be automatically shared. Be aware that the printer driver
must already be installed on the server (see addprinterdriver)
must already be installed on the server (see <B
CLASS="COMMAND"
>adddriver</B
>)
and the <TT
CLASS="PARAMETER"
><I
>port</I
></TT
>must be a valid port name. </P
>must be a valid port name (see
<B
CLASS="COMMAND"
>enumports</B
>.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumdata</B
> - Enumerate all
printer setting data stored on the server. On Windows NT clients,
these values are stored in the registry, while Samba servers
store them in the printers TDB. This command corresponds
to the MS Platform SDK GetPrinterData() function (* This
command is currently unimplemented).</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumjobs &lt;printer&gt;</B
>
- List the jobs and status of a given printer.
This command corresponds to the MS Platform SDK EnumJobs()
function (* This command is currently unimplemented).</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumports [level]</B
>
- Executes an EnumPorts() call using the specified
info level. Currently only info levels 1 and 2 are supported.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumdrivers [level]</B
>
- Execute an EnumPrinterDrivers() call. This lists the various installed
printer drivers for all architectures. Refer to the MS Platform SDK
documentation for more details of the various flags and calling
options. Currently supported info levels are 1, 2, and 3.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumprinters [level]</B
>
- Execute an EnumPrinters() call. This lists the various installed
and share printers. Refer to the MS Platform SDK documentation for
more details of the various flags and calling options. Currently
supported info levels are 0, 1, and 2.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>getdata &lt;printername&gt;</B
>
- Retrieve the data for a given printer setting. See
the <B
CLASS="COMMAND"
>enumdata</B
> command for more information.
This command corresponds to the GetPrinterData() MS Platform
SDK function (* This command is currently unimplemented). </P
></LI
><LI
><P
><B
CLASS="COMMAND"
>getdriver &lt;printername&gt;</B
>
- Retrieve the printer driver information (such as driver file,
config file, dependent files, etc...) for
the given printer. This command corresponds to the GetPrinterDriver()
MS Platform SDK function. Currently info level 1, 2, and 3 are supported.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>getdriverdir &lt;arch&gt;</B
>
- Execute a GetPrinterDriverDirectory()
RPC to retreive the SMB share name and subdirectory for
storing printer driver files for a given architecture. Possible
values for <TT
CLASS="PARAMETER"
><I
>arch</I
></TT
> are "Windows 4.0"
(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
Alpha_AXP", and "Windows NT R4000". </P
></LI
><LI
><P
><B
CLASS="COMMAND"
>getprinter &lt;printername&gt;</B
>
- Retrieve the current printer information. This command
corresponds to the GetPrinter() MS Platform SDK function.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>openprinter &lt;printername&gt;</B
>
- Execute an OpenPrinterEx() and ClosePrinter() RPC
against a given printer. </P
></LI
><LI
><P
><B
CLASS="COMMAND"
>setdriver &lt;printername&gt; &lt;drivername&gt;</B
>
- Execute a SetPrinter() command to update the printer driver associated
with an installed printer. The printer driver must already be correctly
installed on the print server. </P
><P
>See also the <B
CLASS="COMMAND"
>enumprinters</B
> and
<B
CLASS="COMMAND"
>enumdrivers</B
> commands for obtaining a list of
of installed printers and drivers.</P
></LI
></UL
><P
><I
CLASS="EMPHASIS"
>General Commands</I
>GENERAL OPTIONS</I
></P
><P
></P
@ -504,31 +560,15 @@ CLASS="EMPHASIS"
><P
><B
CLASS="COMMAND"
>set</B
> - Set miscellaneous
<B
CLASS="COMMAND"
>rpcclient</B
> command line options during a
running session. </P
>debuglevel</B
> - Set the current debug level
used to log information.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>use</B
> - Connect to a rmeote SMB
server. <B
CLASS="COMMAND"
>rpcclient</B
> has the ability to
maintain connections to multiple server simulaneously. </P
></LI
><LI
><P
><B
CLASS="COMMAND"
>help</B
>help (?)</B
> - Print a listing of all
known commands or extended help on a particular command.
</P
@ -537,20 +577,19 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>quit</B
>quit (exit)</B
> - Exit <B
CLASS="COMMAND"
>rpcclient
</B
>
</P
>.</P
></LI
></UL
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN185"
NAME="AEN196"
></A
><H2
>BUGS</H2
@ -582,7 +621,7 @@ CLASS="COMMAND"
>smbd(8)</B
> and <B
CLASS="COMMAND"
>rpcclient</B
>rpcclient(1)</B
>
that are incompatible for some commands or services. Additionally,
the developers are sending reports to Microsoft, and problems found
@ -592,18 +631,18 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN195"
NAME="AEN206"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
the Samba suite.</P
>This man page is correct for version 2.2 of the Samba
suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN198"
NAME="AEN209"
></A
><H2
>AUTHOR</H2
@ -613,9 +652,10 @@ NAME="AEN198"
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</P
><P
>The original rpcclient man page was written by Matthew Geddes,
Luke Kenneth Casson, and Gerald Carter. The conversion to
DocBook for Samba 2.2 was done by Gerald Carter</P
>The original rpcclient man page was written by Matthew
Geddes, Luke Kenneth Casson, and rewriten by Gerald Carter.
The conversion to DocBook for Samba 2.2 was done by Gerald
Carter.</P
></DIV
></BODY
></HTML

1513
docs/htmldocs/samba-pdc-faq.html
View File

File diff suppressed because it is too large Load Diff

4038
docs/htmldocs/smb.conf.5.html
View File

File diff suppressed because it is too large Load Diff

2
docs/htmldocs/smbcacls.1.html
View File

@ -35,7 +35,7 @@ NAME="AEN8"
><P
><B
CLASS="COMMAND"
>nmblookup</B
>smbcacls</B
> {//server/share} {filename} [-U username] [-A acls] [-M acls] [-D acls] [-S acls] [-C name] [-G name] [-n] [-h]</P
></DIV
><DIV

4
docs/htmldocs/smbclient.1.html
View File

@ -37,7 +37,7 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>smbclient</B
> {servicename} [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-S server] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E &lt;terminal code&gt;] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan] [password]</P
> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-S server] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E &lt;terminal code&gt;] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan]</P
></DIV
><DIV
CLASS="REFSECT1"
@ -189,7 +189,7 @@ CLASS="FILENAME"
options. </P
></DD
><DT
>name resolve order (G)</DT
>-R &lt;name resolve order&gt;</DT
><DD
><P
>This option is used by the programs in the Samba

32
docs/htmldocs/smbmnt.8.html
View File

@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="SMBUMOUNT"
NAME="SMBMNT"
>smbmnt</A
></H1
><DIV
@ -35,13 +35,13 @@ NAME="AEN8"
><P
><B
CLASS="COMMAND"
>smbumount</B
> {mount-point} [-s &lt;share&gt;] [-r] [-u &lt;uid&gt;] [-g &lt;gid&gt;] [-f &lt;mask&gt;] [-d &lt;mask&gt;]</P
>smbmnt</B
> {mount-point} [-s &lt;share&gt;] [-r] [-u &lt;uid&gt;] [-g &lt;gid&gt;] [-f &lt;mask&gt;] [-d &lt;mask&gt;] [-o &lt;options&gt;]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN18"
NAME="AEN19"
></A
><H2
>DESCRIPTION</H2
@ -76,7 +76,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN27"
NAME="AEN28"
></A
><H2
>OPTIONS</H2
@ -120,17 +120,28 @@ CLASS="VARIABLELIST"
>specify the octal directory mask
applied </P
></DD
><DT
>-o options</DT
><DD
><P
> list of options that are passed as-is to smbfs, if this
command is run on a 2.4 or higher linux kernel.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN50"
NAME="AEN55"
></A
><H2
>AUTHOR</H2
><P
>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.</P
><P
>The current maintainer of smbfs and the userspace
tools <B
CLASS="COMMAND"
@ -146,7 +157,14 @@ CLASS="COMMAND"
HREF="mailto:urban@teststation.com"
TARGET="_top"
>Urban Widmark</A
>.</P
>.
The <A
HREF="mailto:samba@samba.org"
TARGET="_top"
>SAMBA Mailing list</A
>
is the preferred place to ask questions regarding these programs.
</P
><P
>The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter</P

190
docs/htmldocs/smbmount.8.html
View File

@ -24,7 +24,7 @@ NAME="AEN5"
></A
><H2
>Name</H2
>smbmount&nbsp;--&nbsp;mount and smbfs filesystem</DIV
>smbmount&nbsp;--&nbsp;mount an smbfs filesystem</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
@ -60,8 +60,17 @@ CLASS="COMMAND"
> command when using the
"-t smb" option. The kernel must support the smbfs filesystem. </P
><P
>Options to smbmount are specified as a comma separated list
of key=value pairs.</P
>Options to smbmount are specified as a comma separated
list of key=value pairs. It is possible to send options other
than those listed here, assuming that smbfs supports them. If
you get mount failures, check your kernel log for errors on
unknown options.</P
><P
>smbmount is a daemon. After mounting it keeps running until
the mounted smbfs is umounted. It will log things that happen
when in daemon mode using the "machine name" smbmount, so
typically this output will end up in log.smbmount. The
smbmount process may also be called mount.smbfs.</P
><P
><I
CLASS="EMPHASIS"
@ -83,7 +92,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN26"
NAME="AEN27"
></A
><H2
>OPTIONS</H2
@ -97,26 +106,50 @@ CLASS="VARIABLELIST"
><DD
><P
>specifies the username to connect as. If
this is not given then the environment variable <TT
CLASS="PARAMETER"
><I
> $USER</I
></TT
> is used. This option can also take the
form "user%password" or "user/workgroup" or
"user/workgroup%password" to allow the password and workgroup
this is not given, then the environment variable <TT
CLASS="ENVAR"
> USER</TT
> is used. This option can also take the
form "user%password" or "user/workgroup" or
"user/workgroup%password" to allow the password and workgroup
to be specified as part of the username.</P
></DD
><DT
>password=&lt;arg&gt;</DT
><DD
><P
>specifies the SMB password. If not given then
<B
>specifies the SMB password. If this
option is not given then the environment variable
<TT
CLASS="ENVAR"
>PASSWD</TT
> is used. If it can find
no password <B
CLASS="COMMAND"
>smbmount</B
> will prompt for a passeword, unless
the guest option is given. </P
> will prompt
for a passeword, unless the guest option is
given. </P
></DD
><DT
>credentials=&lt;filename&gt;</DT
><DD
><P
>specifies a file that contains a username
and/or password. The format of the file is:</P
><P
> <PRE
CLASS="PROGRAMLISTING"
> username = &lt;value&gt;
password = &lt;value&gt;
</PRE
>
</P
><P
>This is preferred over having passwords in plaintext in a
shared file, such as /etc/fstab. Be sure to protect any
credentials file properly.
</P
></DD
><DT
>netbiosname=&lt;arg&gt;</DT
@ -129,7 +162,8 @@ CLASS="COMMAND"
>uid=&lt;arg&gt;</DT
><DD
><P
>sets the uid that files will be mounted as.
>sets the uid that will own all files on
the mounted filesystem.
It may be specified as either a username or a numeric uid.
</P
></DD
@ -137,7 +171,8 @@ CLASS="COMMAND"
>gid=&lt;arg&gt;</DT
><DD
><P
>sets the gid that files will be mounted as.
>sets the gid that will own all files on
the mounted filesystem.
It may be specified as either a groupname or a numeric
gid. </P
></DD
@ -228,17 +263,125 @@ CLASS="PARAMETER"
><P
>mount read-write </P
></DD
><DT
>iocharset=&lt;arg&gt;</DT
><DD
><P
> sets the charset used by the linux side for codepage
to charset translations (NLS). Argument should be the
name of a charset, like iso8859-1. (Note: only kernel
2.4.0 or later)
</P
></DD
><DT
>codepage=&lt;arg&gt;</DT
><DD
><P
> sets the codepage the server uses. See the iocharset
option. Example value cp850. (Note: only kernel 2.4.0
or later)
</P
></DD
><DT
>ttl=&lt;arg&gt;</DT
><DD
><P
> how long a directory listing is cached in milliseconds
(also affects visibility of file size and date
changes). A higher value means that changes on the
server take longer to be noticed but it can give
better performance on large directories, especially
over long distances. Default is 1000ms but something
like 10000ms (10 seconds) is probably more reasonable
in many cases.
(Note: only kernel 2.4.2 or later)
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN98"
NAME="AEN119"
></A
><H2
>ENVIRONMENT VARIABLES</H2
><P
>The variable <TT
CLASS="ENVAR"
>USER</TT
> may contain the username of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords. The variable can be used to set both username and
password by using the format username%password.</P
><P
>The variable <TT
CLASS="ENVAR"
>PASSWD</TT
> may contain the password of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords.</P
><P
>The variable <TT
CLASS="ENVAR"
>PASSWD_FILE</TT
> may contain the pathname of
a file to read the password from. A single line of input is
read and used as password.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN127"
></A
><H2
>BUGS</H2
><P
>Not many known smbmount bugs. But one smbfs bug is
important enough to mention here anyway:</P
><P
></P
><UL
><LI
><P
>Mounts sometimes stop working. This is usually
caused by smbmount terminating. Since smbfs needs smbmount to
reconnect when the server disconnects, the mount will go
dead. A re-mount normally fixes this. At least 2 ways to
trigger this bug are known.</P
></LI
></UL
><P
>Note that the typical response to a bugreport is suggestion
to try the latest version first. So please try doing that first,
and always include which versions you use of relevant software
when reporting bugs (minimum: samba, kernel, distribution)</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN134"
></A
><H2
>SEE ALSO</H2
><P
>Documentation/filesystems/smbfs.txt in the kernel source tree
may contain additional options and information.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN137"
></A
><H2
>AUTHOR</H2
><P
>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.</P
><P
>The current maintainer of smbfs and the userspace
tools <B
CLASS="COMMAND"
@ -254,7 +397,14 @@ CLASS="COMMAND"
HREF="mailto:urban@teststation.com"
TARGET="_top"
>Urban Widmark</A
></P
>.
The <A
HREF="mailto:samba@samba.org"
TARGET="_top"
>SAMBA Mailing list</A
>
is the preferred place to ask questions regarding these programs.
</P
><P
>The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter</P

2
docs/htmldocs/smbpasswd.8.html
View File

@ -314,7 +314,7 @@ CLASS="EMPHASIS"
>-R name resolve order</DT
><DD
><P
>This option allows the user of smbclient to determine
>This option allows the user of smbpasswd to determine
what name resolution services to use when looking up the NetBIOS
name of the host being connected to. </P
><P

4
docs/htmldocs/smbspool.8.html
View File

@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="SMBSPOOL"
NAME="FINDSMB"
>smbspool</A
></H1
><DIV
@ -24,7 +24,7 @@ NAME="AEN5"
></A
><H2
>Name</H2
>smbspool&nbsp;--&nbsp;send print file to an SMB printer</DIV
>nmblookup&nbsp;--&nbsp;send print file to an SMB printer</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A

12
docs/htmldocs/smbumount.8.html
View File

@ -105,6 +105,9 @@ NAME="AEN28"
><H2
>AUTHOR</H2
><P
>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.</P
><P
>The current maintainer of smbfs and the userspace
tools <B
CLASS="COMMAND"
@ -120,7 +123,14 @@ CLASS="COMMAND"
HREF="mailto:urban@teststation.com"
TARGET="_top"
>Urban Widmark</A
>.</P
>.
The <A
HREF="mailto:samba@samba.org"
TARGET="_top"
>SAMBA Mailing list</A
>
is the preferred place to ask questions regarding these programs.
</P
><P
>The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter</P

490
docs/htmldocs/winbind.html Normal file
View File

@ -0,0 +1,490 @@
<HTML
><HEAD
><TITLE
>Unifed Logons between Windows NT and UNIX using Winbind</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN1"
>Unifed Logons between Windows NT and UNIX using Winbind</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Abstract</A
></H1
><P
>Integration of UNIX and Microsoft Windows NT through
a unified logon has been considered a "holy grail" in heterogeneous
computing environments for a long time. We present <I
CLASS="EMPHASIS"
>winbind
</I
>, a component of the Samba suite of programs as a
solution to the unied logon problem. Winbind uses a UNIX implementation
of Microsoft RPC calls, Pluggable Authentication Modules, and the Name
Service Switch to allow Windows NT domain users to appear and operate
as UNIX users on a UNIX machine. This paper describes the winbind
system, explaining the functionality it provides, how it is configured,
and how it works internally.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN7"
>Introduction</A
></H1
><P
>It is well known that UNIX and Microsoft Windows NT have
different models for representing user and group information and
use different technologies for implementing them. This fact has
made it difficult to integrate the two systems in a satisfactory
manner.</P
><P
>One common solution in use today has been to create
identically named user accounts on both the UNIX and Windows systems
and use the Samba suite of programs to provide file and print services
between the two. This solution is far from perfect however, as
adding and deleting users on both sets of machines becomes a chore
and two sets of passwords are required both of which which
can lead to synchronization problems between the UNIX and Windows
systems and confusion for users.</P
><P
>We divide the unifed logon problem for UNIX machines into
three smaller problems:</P
><P
></P
><UL
><LI
><P
>Obtaining Windows NT user and group information
</P
></LI
><LI
><P
>Authenticating Windows NT users
</P
></LI
><LI
><P
>Password changing for Windows NT users
</P
></LI
></UL
><P
>Ideally, a prospective solution to the unified logon problem
would satisfy all the above components without duplication of
information on the UNIX machines and without creating additional
tasks for the system administrator when maintaining users and
groups on either system. The winbind system provides a simple
and elegant solution to all three components of the unifed logon
problem.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN20"
>What Winbind Provides</A
></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
this is done the UNIX box will see NT users and groups as if
they were native UNIX users and groups, allowing the NT domain
to be used in much the same manner that NIS+ is used within
UNIX-only environments.</P
><P
>The end result is that whenever any
program on the UNIX machine asks the operating system to lookup
a user or group name, the query will be resolved by asking the
NT domain controller for the specied domain to do the lookup.
Because Winbind hooks into the operating system at a low level
(via the NSS name resolution modules in the C library) this
redirection to the NT domain controller is completely
transparent.</P
><P
>Users on the UNIX machine can then use NT user and group
names as they would use "native" UNIX names. They can chown files
so that they are owned by NT domain users or even login to the
UNIX machine and run a UNIX X-Window session as a domain user.</P
><P
>The only obvious indication that Winbind is being used is
that user and group names take the form DOMAIN\user and
DOMAIN\group. This is necessary as it allows Winbind to determine
that redirection to a domain controller is wanted for a particular
lookup and which trusted domain is being referenced.</P
><P
>Additionally, Winbind provides a authentication service
that hooks into the Pluggable Authentication Modules (PAM) system
to provide authentication via a NT domain to any PAM enabled
applications. This capability solves the problem of synchronizing
passwords between systems as all passwords are stored in a single
location (on the domain controller).</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN27"
>Target Uses</A
></H2
><P
>Winbind is targeted at organizations that have an
existing NT based domain infrastructure into which they wish
to put UNIX workstations or servers. Winbind will allow these
organizations to deploy UNIX workstations without having to
maintain a separate account infrastructure. This greatly simplies
the administrative overhead of deploying UNIX workstations into
a NT based organization.</P
><P
>Another interesting way in which we expect Winbind to
be used is as a central part of UNIX based appliances. Appliances
that provide file and print services to Microsoft based networks
will be able to use Winbind to provide seamless integration of
the appliance into the domain.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN31"
>How Winbind Works</A
></H1
><P
>The winbind system is designed around a client/server
architecture. A long running <B
CLASS="COMMAND"
>winbindd</B
> daemon
listens on a UNIX domain socket waiting for requests
to arrive. These requests are generated by the NSS and PAM
clients and processed sequentially.</P
><P
>The technologies used to implement winbind are described
in detail below.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN36"
>Microsoft Remote Procedure Calls</A
></H2
><P
>Over the last two years, efforts have been underway
by various Samba Team members to decode various aspects of
the Microsoft Remote Procedure Call (MSRPC) system. This
system is used for most network related operations between
Windows NT machines including remote management, user authentication
and print spooling. Although initially this work was done
to aid the implementation of Primary Domain Controller (PDC)
functionality in Samba, it has also yielded a body of code which
can be used for other purposes.</P
><P
>Winbind uses various MSRPC calls to enumerate domain users
and groups and to obtain detailed information about individual
users or groups. Other MSRPC calls can be used to authenticate
NT domain users and to change user passwords. By directly querying
a Windows PDC for user and group information, winbind maps the
NT account information onto UNIX user and group names.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN40"
>Name Service Switch</A
></H2
><P
>The Name Service Switch, or NSS, is a feature that is
present in many UNIX operating systems. It allows system
information such as hostnames, mail aliases and user information
to be resolved from dierent sources. For example, a standalone
UNIX workstation may resolve system information from a series of
flat files stored on the local lesystem. A networked workstation
may first attempt to resolve system information from local files,
then consult a NIS database for user information or a DNS server
for hostname information.</P
><P
>The NSS application programming interface allows winbind
to present itself as a source of system information when
resolving UNIX usernames and groups. Winbind uses this interface,
and information obtained from a Windows NT server using MSRPC
calls to provide a new source of account enumeration. Using standard
UNIX library calls, one can enumerate the users and groups on
a UNIX machine running winbind and see all users and groups in
a NT domain plus any trusted domain as though they were local
users and groups.</P
><P
>The primary control le for NSS is <TT
CLASS="FILENAME"
>/etc/nsswitch.conf
</TT
>. When a UNIX application makes a request to do a lookup
the C library looks in <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
>
for a line which matches the service type being requested, for
example the "passwd" service type is used when user or group names
are looked up. This config line species which implementations
of that service should be tried andin what order. If the passwd
config line is:</P
><P
><B
CLASS="COMMAND"
>passwd: files example</B
></P
><P
>then the C library will first load a module called
<TT
CLASS="FILENAME"
>/lib/libnss_files.so</TT
> followed by
the module <TT
CLASS="FILENAME"
>/lib/libnss_example.so</TT
>. The
C library will dynamically load each of these modules in turn
and call resolver functions within the modules to try to resolve
the request. Once the request is resolved the C library returns the
result to the application.</P
><P
>This NSS interface provides a very easy way for Winbind
to hook into the operating system. All that needs to be done
is to put <TT
CLASS="FILENAME"
>libnss_winbind.so</TT
> in <TT
CLASS="FILENAME"
>/lib/</TT
>
then add "winbind" into <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
> at
the appropriate place. The C library will then call Winbind to
resolve user and group names.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN56"
>Pluggable Authentication Modules</A
></H2
><P
>Pluggable Authentication Modules, also known as PAM,
is a system for abstracting authentication and authorization
technologies. With a PAM module it is possible to specify different
authentication methods for dierent system applications without
having to recompile these applications. PAM is also useful
for implementing a particular policy for authorization. For example,
a system administrator may only allow console logins from users
stored in the local password file but only allow users resolved from
a NIS database to log in over the network.</P
><P
>Winbind uses the authentication management and password
management PAM interface to integrate Windows NT users into a
UNIX system. This allows Windows NT users to log in to a UNIX
machine and be authenticated against a suitable Primary Domain
Controller. These users can also change their passwords and have
this change take eect directly on the Primary Domain Controller.
</P
><P
>PAM is congured by providing control files in the directory
<TT
CLASS="FILENAME"
>/etc/pam.d/</TT
> for each of the services that
require authentication. When an authentication request is made
by an application the PAM code in the C library looks up this
control file to determine what modules to load to do the
authentication check and in what order. This interface makes adding
a new authentication service for Winbind very easy, all that needs
to be done is that the <TT
CLASS="FILENAME"
>pam_winbind.so</TT
> module
is copied to <TT
CLASS="FILENAME"
>/lib/security/</TT
> and the pam
control files for relevant services are updated to allow
authentication via winbind. See the PAM documentation
for more details.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN64"
>User and Group ID Allocation</A
></H2
><P
>When a user or group is created under Windows NT
is it allocated a numerical relative identier (RID). This is
slightly dierent to UNIX which has a range of numbers which are
used to identify users, and the same range in which to identify
groups. It is winbind's job to convert RIDs to UNIX id numbers and
vice versa. When winbind is congured it is given part of the UNIX
user id space and a part of the UNIX group id space in which to
store Windows NT users and groups. If a Windows NT user is
resolved for the first time, it is allocated the next UNIX id from
the range. The same process applies for Windows NT groups. Over
time, winbind will have mapped all Windows NT users and groups
to UNIX user ids and group ids.</P
><P
>The results of this mapping are stored persistently in
a ID mapping database held in a tdb database). This ensures that
RIDs are mapped to UNIX IDs in a consistent way.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN68"
>Result Caching</A
></H2
><P
>An active system can generate a lot of user and group
name lookups. To reduce the network cost of these lookups winbind
uses a caching scheme based on the SAM sequence number supplied
by NT domain controllers. User or group information returned
by a PDC is cached by winbind along with a sequence number also
returned by the PDC. This sequence number is incremented by
Windows NT whenever any user or group information is modied. If
a cached entry has expired, the sequence number is requested from
the PDC and compared against the sequence number of the cached entry.
If the sequence numbers do not match, then the cached information
is discarded and up to date information is requested directly
from the PDC.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN71"
>Installation and Configuration</A
></H1
><P
>The easiest way to install winbind is by using the packages
provided in the <TT
CLASS="FILENAME"
>pub/samba/appliance/</TT
>
directory on your nearest
Samba mirror. These packages provide snapshots of the Samba source
code and binaries already setup to provide the full functionality
of winbind. This setup is a little more complex than a normal Samba
build as winbind needs a small amount of functionality from a
development code branch called SAMBA_TNG.</P
><P
>Once you have installed the packages you should read
the <B
CLASS="COMMAND"
>winbindd(8)</B
> man page which will provide you
with conguration information and give you sample conguration files.
You may also wish to update the main Samba daemons smbd and nmbd)
with a more recent development release, such as the recently
announced Samba 2.2 alpha release.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN77"
>Limitations</A
></H1
><P
>Winbind has a number of limitations in its current
released version which we hope to overcome in future
releases:</P
><P
></P
><UL
><LI
><P
>Winbind is currently only available for
the Linux operating system, although ports to other operating
systems are certainly possible. For such ports to be feasible,
we require the C library of the target operating system to
support the Name Service Switch and Pluggable Authentication
Modules systems. This is becoming more common as NSS and
PAM gain support among UNIX vendors.</P
></LI
><LI
><P
>The mappings of Windows NT RIDs to UNIX ids
is not made algorithmically and depends on the order in which
unmapped users or groups are seen by winbind. It may be difficult
to recover the mappings of rid to UNIX id mapping if the file
containing this information is corrupted or destroyed.</P
></LI
><LI
><P
>Currently the winbind PAM module does not take
into account possible workstation and logon time restrictions
that may be been set for Windows NT users.</P
></LI
><LI
><P
>Building winbind from source is currently
quite tedious as it requires combining source code from two Samba
branches. Work is underway to solve this by providing all
the necessary functionality in the main Samba code branch.</P
></LI
></UL
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN89"
>Conclusion</A
></H1
><P
>The winbind system, through the use of the Name Service
Switch, Pluggable Authentication Modules, and appropriate
Microsoft RPC calls have allowed us to provide seamless
integration of Microsoft Windows NT domain users on a
UNIX system. The result is a great reduction in the administrative
cost of running a mixed UNIX and NT network.</P
></DIV
></DIV
></BODY
></HTML
>

13
docs/manpages/findsmb.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "FINDSMB" "1" "23 February 2001" "" ""
.TH FINDSMB 1 "24 Mar 2001" "findsmb 2.2.0-alpha3"
.SH NAME
findsmb \- list info about machines that respond to SMB name queries on a subnet
.SH SYNOPSIS
@ -11,12 +11,12 @@ findsmb \- list info about machines that respond to SMB name queries on a subne
\fBfindsmb\fR [ \fBsubnet broadcast address\fR ]
.SH "DESCRIPTION"
.PP
This perl script is part of the Samba <URL:samba.7.html> suite.
This perl script is part of the Sambasuite.
.PP
\fBfindsmb\fR is a perl script that
prints out several pieces of information about machines
on a subnet that respond to SMB name query requests.
It uses \fB nmblookup(1)\fR <URL:nmblookup.1.html> and \fBsmbclient(1)\fR <URL:smbclient.1.html> to obtain this information.
It uses \fB nmblookup(1)\fRto obtain this information.
.SH "OPTIONS"
.TP
\fBsubnet broadcast address\fR
@ -40,7 +40,7 @@ Machines that are running Windows, Windows 95 or Windows 98 will
not show any information about the operating system or server
version.
.PP
The command must be run on a system without \fBnmbd\fR <URL:nmbd.8.html> running.
The command must be run on a system without \fBnmbd\fRrunning.
If \fBnmbd\fR is running on the system, you will
only get the IP address and the DNS name of the machine. To
get proper responses from Windows 95 and Windows 98 machines,
@ -72,10 +72,9 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBnmbd(8)\fR <URL:nmbd.8.html>,
\fBnmbd(8)\fR,
\fBsmbclient(1)
\fR <URL:smbclient.1.html>, and \fBnmblookup(1)\fR <URL:nmblookup.1.html>
.SH "AUTHOR"
\fR.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

13
docs/manpages/lmhosts.5
View File

@ -3,15 +3,15 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "LMHOSTS" "5" "23 February 2001" "" ""
.TH LMHOSTS 5 "24 Mar 2001" "lmhosts 2.2.0-alpha3"
.SH NAME
lmhosts \- The Samba NetBIOS hosts file
.SH SYNOPSIS
.PP
\fIlmhosts\fR is the Samba <URL:samba.7.html> NetBIOS name to IP address mapping file.
\fIlmhosts\fR is the SambaNetBIOS name to IP address mapping file.
.SH "DESCRIPTION"
.PP
This file is part of the < Samba <URL:samba.7.html> suite.
This file is part of the < Sambasuite.
.PP
\fIlmhosts\fR is the \fBSamba
\fRNetBIOS name to IP address mapping file. It
@ -44,7 +44,7 @@ An example follows :
.sp
.nf
#
#Sample Samba lmhosts file.
# Sample Samba lmhosts file.
#
192.9.200.1 TESTPC
192.9.200.20 NTSERVER#20
@ -67,7 +67,7 @@ be resolved.
.PP
The default location of the \fIlmhosts\fR file
is in the same directory as the
smb.conf(5)> <URL:smb.conf.5.html> file.
smb.conf(5)>file.
.PP
.SH "VERSION"
.PP
@ -76,8 +76,7 @@ the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbclient(1)
\fR <URL:smbclient.1.html>, smb.conf(5) <URL:smb.conf.5.html#NAMERESOLVEORDER>, and \fB smbpasswd(8)\fR <URL:smbpasswd.8.html>
.SH "AUTHOR"
\fR.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

9
docs/manpages/make_smbcodepage.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "MAKE_SMBCODEPAGE" "1" "23 February 2001" "" ""
.TH MAKE_SMBCODEPAGE 1 "24 Mar 2001" "make_smbcodepage 2.2.0-alpha3"
.SH NAME
make_smbcodepage \- construct a codepage file for Samba
.SH SYNOPSIS
@ -11,7 +11,7 @@ make_smbcodepage \- construct a codepage file for Samba
\fBmake_smbcodepage\fR \fBc|d\fR \fBcodepage\fR \fBinputfile\fR \fBoutputfile\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBmake_smbcodepage\fR compiles or de-compiles
codepage files for use with the internationalization features
@ -123,9 +123,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html>,
smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
\fBsmbd(8)\fR,
smb.conf(5).SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

2
docs/manpages/make_unicodemap.1
View File

@ -1,4 +1,4 @@
.TH MAKE_UNICODEMAP 1 "26 Apr 2000" "make_unicodemap 2.0.7"
.TH MAKE_UNICODEMAP 1 "24 Mar 2001" "make_unicodemap 2.2.0-alpha3"
.PP
.SH "NAME"
make_unicodemap \- Construct a unicode map file for Samba

33
docs/manpages/nmbd.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "NMBD" "8" "23 February 2001" "" ""
.TH NMBD 8 "24 Mar 2001" "nmbd 2.2.0-alpha3"
.SH NAME
nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
.SH SYNOPSIS
@ -33,7 +33,7 @@ but this can be overridden with the \fB-n\fR
option (see OPTIONS below). Thus \fBnmbd\fR will
reply to broadcast queries for its own name(s). Additional
names for \fBnmbd\fR to respond on can be set
via parameters in the \fI smb.conf(5)\fR <URL:smb.conf.5.html> configuration file.
via parameters in the \fI smb.conf(5)\fRconfiguration file.
.PP
\fBnmbd\fR can also be used as a WINS
(Windows Internet Name Server) server. What this basically means
@ -75,8 +75,7 @@ for \fBnmbd\fR.
NetBIOS lmhosts file. The lmhosts
file is a list of NetBIOS names to IP addresses that
is loaded by the nmbd server and used via the name
resolution mechanism name resolve order <URL:smb.conf.5.html#nameresolveorder> described in \fIsmb.conf(5)\fR <URL:smb.conf.5.html>
to resolve any NetBIOS name queries needed by the server. Note
resolution mechanism name resolve orderto resolve any NetBIOS name queries needed by the server. Note
that the contents of this file are \fBNOT\fR
used by \fBnmbd\fR to answer any name queries.
Adding a line to this file affects name NetBIOS resolution
@ -86,7 +85,7 @@ The default path to this file is compiled into
Samba as part of the build process. Common defaults
are \fI/usr/local/samba/lib/lmhosts\fR,
\fI/usr/samba/lib/lmhosts\fR or
\fI/etc/lmhosts\fR. See the \fIlmhosts(5)\fR <URL:lmhosts.5.html> man page for details on the
\fI/etc/lmhosts\fR. See the \fIlmhosts(5)\fRman page for details on the
contents of this file.
.TP
\fB-V\fR
@ -112,8 +111,7 @@ and generate HUGE amounts of log data, most of which is extremely
cryptic.
Note that specifying this parameter here will override
the log level <URL:smb.conf.5.html#loglevel>
parameter in the \fI smb.conf\fR <URL:smb.conf.5.html> file.
the log levelparameter in the \fI smb.conf\fRfile.
.TP
\fB-l <log file>\fR
The -l parameter specifies a path
@ -131,8 +129,8 @@ part of the build process. Common defaults are \fI /usr/local/samba/var/log.nmb\
\fB-n <primary NetBIOS name>\fR
This option allows you to override
the NetBIOS name that Samba uses for itself. This is identical
to setting the NetBIOS name <URL:smb.conf.5.html#netbiosname> parameter in the
\fIsmb.conf\fR <URL:smb.conf.5.html> file. However, a command
to setting the NetBIOS nameparameter in the
\fIsmb.conf\fRfile. However, a command
line setting will take precedence over settings in
\fIsmb.conf\fR.
.TP
@ -150,7 +148,7 @@ this may be changed when Samba is autoconfigured.
The file specified contains the configuration details
required by the server. See
\fIsmb.conf(5)\fR <URL:smb.conf.5.html> for more information.
\fIsmb.conf(5)\fRfor more information.
.SH "FILES"
.TP
\fB\fI/etc/inetd.conf\fB\fR
@ -177,20 +175,17 @@ See the section INSTALLATION below.
.TP
\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
This is the default location of the
\fIsmb.conf\fR <URL:smb.conf.5.html>
server configuration file. Other common places that systems
\fIsmb.conf\fRserver configuration file. Other common places that systems
install this file are \fI/usr/samba/lib/smb.conf\fR
and \fI/etc/smb.conf\fR.
When run as a WINS server (see the
wins support <URL:smb.conf.5.html#winssupport>
parameter in the \fI smb.conf(5)\fR <URL:smb.conf.5.html> man page), \fBnmbd\fR
wins supportparameter in the \fI smb.conf(5)\fRman page), \fBnmbd\fR
will store the WINS database in the file \fIwins.dat\fR
in the \fIvar/locks\fR directory configured under
wherever Samba was configured to install itself.
If \fBnmbd\fR is acting as a \fB browse master\fR (see the local master <URL:smb.conf.5.html#localmaster>
parameter in the \fI smb.conf(5)\fR <URL:smb.conf.5.html> man page), \fBnmbd\fR
If \fBnmbd\fR is acting as a \fB browse master\fR (see the local masterparameter in the \fI smb.conf(5)\fRman page), \fBnmbd\fR
will store the browsing database in the file \fIbrowse.dat
\fRin the \fIvar/locks\fR directory
configured under wherever Samba was configured to install itself.
@ -220,10 +215,10 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBinetd(8)\fR, \fBsmbd(8)\fR <URL:smbd.8.html>,
\fBinetd(8)\fR, \fBsmbd(8)\fR,
\fIsmb.conf(5)\fR
<URL:smb.conf.5.html>, \fBsmbclient(1)
\fR <URL:smbclient.1.html>, \fB testparm(1)\fR <URL:testparm.1.html>, \fBtestprns(1)\fR <URL:testprns.1.html>, and the Internet RFC's
, \fBsmbclient(1)
\fR, and the Internet RFC's
\fIrfc1001.txt\fR, \fIrfc1002.txt\fR.
In addition the CIFS (formerly SMB) specification is available
as a link from the Web page

18
docs/manpages/nmblookup.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "NMBLOOKUP" "1" "23 February 2001" "" ""
.TH NMBLOOKUP 1 "24 Mar 2001" "nmblookup 2.2.0-alpha3"
.SH NAME
nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
.SH SYNOPSIS
@ -11,7 +11,7 @@ nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
\fBnmblookup\fR [ \fB-M\fR ] [ \fB-R\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B <broadcast address>\fR ] [ \fB-U <unicast address>\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-i <NetBIOS scope>\fR ] [ \fB-T\fR ] \fBname\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBnmblookup\fR is used to query NetBIOS names
and map them to IP addresses in a network using NetBIOS over TCP/IP
@ -45,8 +45,7 @@ datagrams. The reason for this option is a bug in Windows 95
where it ignores the source port of the requesting packet
and only replies to UDP port 137. Unfortunately, on most UNIX
systems root privilage is needed to bind to this port, and
in addition, if the nmbd(8) <URL:nmbd.8.html>
daemon is running on this machine it also binds to this port.
in addition, if the nmbd(8)daemon is running on this machine it also binds to this port.
.TP
\fB-A\fR
Interpret \fIname\fR as
@ -60,7 +59,7 @@ Send the query to the given broadcast address. Without
this option the default behavior of nmblookup is to send the
query to the broadcast address of the network interfaces as
either auto-detected or defined in the \fIinterfaces\fR
<URL:smb.conf.5.html#INTERFACES> parameter of the \fIsmb.conf (5)\fR file.
parameter of the \fIsmb.conf (5)\fR file.
.TP
\fB-U <unicast address>\fR
Do a unicast query to the specified address or
@ -84,11 +83,11 @@ Levels above 3 are designed for use only by developers and
generate HUGE amounts of data, most of which is extremely cryptic.
Note that specifying this parameter here will override
the \fI log level\fR <URL:smb.conf.5.html#LOGLEVEL> parameter in the \fI smb.conf(5)\fR file.
the \fI log level\fRparameter in the \fI smb.conf(5)\fR file.
.TP
\fB-s <smb.conf>\fR
This parameter specifies the pathname to
the Samba configuration file, smb.conf(5) <URL:smb.conf.5.html>. This file controls all aspects of
the Samba configuration file, smb.conf(5). This file controls all aspects of
the Samba setup on the machine.
.TP
\fB-i <scope>\fR
@ -137,9 +136,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBnmbd(8)\fR <URL:nmbd.8.html>,
samba(7) <URL:samba.7.html>, and smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
\fBnmbd(8)\fR,
samba(7).SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

355
docs/manpages/rpcclient.1
View File

@ -3,73 +3,79 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "RPCCLIENT" "1" "28 February 2001" "" ""
.TH "RPCCLIENT" "1" "28 March 2001" "" ""
.SH NAME
rpcclient \- developer's tool to testing client side MS-RPC functions
rpcclient \- tool for executing client side MS-RPC functions
.SH SYNOPSIS
.sp
\fBnmblookup\fR [ \fB-d debuglevel\fR ] [ \fB-S server\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-n <netbios name>\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-I destinationIP\fR ] [ \fB-E <terminal code>\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-s <smb config file>\fR ]
\fBrpcclient\fR \fBserver\fR [ \fB-A authfile\fR ] [ \fB-c <command string>\fR ] [ \fB-d debuglevel\fR ] [ \fB-h\fR ] [ \fB-l logfile\fR ] [ \fB-N\fR ] [ \fB-s <smb config file>\fR ] [ \fB-U username[%password]\fR ] [ \fB-W workgroup\fR ] [ \fB-N\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBrpcclient\fR is a utility for developers for
executing various MS-RPC functions. It's primary use is for testing
Samba's own MS-RPC server implementation, however many administrators
have written scripts around it to manage Windows NT clients from
\fBrpcclient\fR is a utility initially developed
to test MS-RPC functionality in Samba itself. It has undergone
several stages of development and stability. Many system administrators
have now written scripts around it to manage Windows NT clients from
their UNIX workstation.
.SH "OPTIONS"
.TP
\fBserver\fR
NetBIOS name of Server to which to connect.
The server can be any SMB/CIFS server. The name is
resolved using the \fIname resolve order\fRline from
\fIsmb.conf(5)\fR.
.TP
\fB-A filename\fR
This option allows
you to specify a file from which to read the username and
password used in the connection. The format of the file is
.sp
.nf
username = <value>
password = <value>
domain = <value>
.sp
.fi
Make certain that the permissions on the file restrict
access from unwanted users.
.TP
\fB-c 'command string'\fR
execute semicolon separated commands (listed
below))
.TP
\fB-d debuglevel\fR
set the debuglevel. Debug level 0 is the lowest
and 100 being the highest. This should be set to 100 if you are
planning on submitting a bug report to the Samba team
(see BUGS.txt).
planning on submitting a bug report to the Samba team (see BUGS.txt).
.TP
\fB-S server\fR
NetBIOS name of Server to which you wish to
connect. The server can be any SMB/CIFS server. The name is
resolved using either the \fIname resolve order\fR
line or by using the -R option.
\fB-h\fR
Print a summary of command line options.
.TP
\fB-l logbasename\fR
File name for log/debug files. .client will be
appended. The log file is never removed by the client.
.TP
\fB-n netbios name\fR
NetBIOS name of the
local machine. This option is only needed if your Samba client
cannot find it automatically. Samba should use the uppercase
of the machine's hostname.
.TP
\fB-N\fR
tells rpcclient not to ask for a password.
\fBrpcclient\fR will prompt the user by default.
instruct \fBrpcclient\fR not to ask
for a password. By default, \fBrpcclient\fR will prompt
for a password. See also the \fI-U\fR option.
.TP
\fB-I destinationIP\fR
The IP address of the server specified with
the -S option. Only needed when the server's NetBIOS name cannot
be resolved using WINS or broadcast and isn't found in the LMHOSTS
file.
\fB-s smb.conf\fR
Specifies the location of the all important
\fIsmb.conf\fR file.
.TP
\fB-E\fR
causes \fBrpcclient\fR to write
messages to stderr instead of stdout.
.TP
\fB-U username[%pass]\fR
\fB-U username[%password]\fR
Sets the SMB username or username and password.
If %pass is not specified, The user will be prompted. The client
will first check the USER environment variable, then the
\fI$LOGNAME\fR variable and if either exist, the
string is uppercased. Anything in these variables following a '%'
sign will be treated as the password. If these environmental
variables are not found, the username GUEST
is used.
If the password is not included in these environment
variables (using the %pass syntax), rpcclient will look for
a \fI$PASSWD\fR environment variable from which
to read the password.
If %password is not specified, The user will be prompted. The
client will first check the \fBUSER\fR environment variable, then the
\fBLOGNAME\fR variable and if either exist, the
string is uppercased. If these environmental variables are not
found, the username GUEST is used.
A third option is to use a credentials file which
contains the plaintext of the username and password. This
@ -79,29 +85,12 @@ variables. If this method is used, make certain that the permissions
on the file restrict access from unwanted users. See the
\fI-A\fR for more details.
Be cautious about including passwords in scripts or in
the \fI$PASSWD\fR environment variable. Also, on
Be cautious about including passwords in scripts. Also, on
many systems the command line of a running process may be seen
via the \fBps\fR command to be safe always allow
via the \fBps\fR command. To be safe always allow
\fBrpcclient\fR to prompt for a password and type
it in directly.
.TP
\fB-A filename\fR
This option allows
you to specify a file from which to read the username and
password used in the connection. The format of the file is
.sp
.nf
username = <value>
password = <value>
.sp
.fi
Make certain that the permissions on the file restrict
access from unwanted users.
.TP
\fB-W domain\fR
Set the SMB domain of the username. This
overrides the default domain which is the domain of the
@ -109,118 +98,65 @@ server specified with the \fI-S\fR option.
If the domain specified is the same as the server's NetBIOS name,
it causes the client to log on using the server's local SAM (as
opposed to the Domain SAM).
.TP
\fB-P\fR
operate in promptless mode. Without this
mode (the default) \fBrpcclient\fR displays a
prompt of the form '[domain\\username@host]$'
.TP
\fB-c 'command string'\fR
execute semicolon separated commands (listed
below))
.TP
\fB-t terminalcode\fR
This tells the Samba client how to interpret
the incoming filenames, in regards to character sets. The list
here is not complete. For a complete list see your local Samba
source. Some valid options are sjis, euc, jis7, jis8, junet
and hex.
.TP
\fB-O socket options\fR
These socket options are the same as in
\fIsmb.conf\fR (under the \fIsocket options
\fRsection).
.TP
\fB-s smb.conf\fR
Specifies the location of the all important
\fIsmb.conf\fR file.
.TP
\fB-i scope\fR
Defines the NetBIOS scope. For more
information on NetBIOS scopes, see rfc1001 and rfc1002. NetBIOS
scopes are rarely used.
.SH "COMMANDS"
.PP
\fBSPOOLSS Commands\fR
\fBLSARPC\fR
.TP 0.2i
\(bu
\fBspoolenum\fR - Execute an EnumPrinters()
call. This lists the various installed and share printers. Refer
to the MS Platform SDK documentation for more details of the various
flags and calling options.
\fBlsaquery\fR
.TP 0.2i
\(bu
\fBspoolenumports level
\fR- Executes an EnumPorts() call using the specified
info level. Currently only info level 1 and 2 are supported.
\fBlookupsids\fR
.TP 0.2i
\(bu
\fBspoolenumdata\fR - Enumerate all
printer setting data stored on the server. On Windows NT clients,
these values are stored in the registry, while Samba servers
store them in the printers TDB. This command corresponds
to the MS Platform SDK GetPrinterData() function.
\fBlookupnames\fR
.TP 0.2i
\(bu
\fBspooljobs printer\fR - List the jobs
and status of a given printer.
This command corresponds to the MS Platform SDK EnumJobs()
function.
\fBenumtrusts\fR
.PP
.PP
.PP
\fBSAMR\fR
.PP
.TP 0.2i
\(bu
\fBspoolopen printer
\fR- Execute an OpenPrinterEx() and ClosePrinter() RPC
against a given printer.
\fBqueryuser\fR
.TP 0.2i
\(bu
\fBspoolgetdata printer
\fR- Retrieve the data for a given printer setting. See
the \fBspoolenumdata\fR command for more information.
This command corresponds to the GetPrinterData() MS Platform
SDK function.
\fBquerygroup\fR
.TP 0.2i
\(bu
\fBspoolgetprinter printer
\fR- Retrieve the current printer information. This command
corresponds to the GetPrinter() MS Platform SDK function.
\fBqueryusergroups\fR
.TP 0.2i
\(bu
\fBspoolgetprinterdriver
printer\fR - Retrieve the printer driver information
(such as driver file, config file, dependent files, etc...) for
the given printer. This command corresponds to the GetPrinterDriver()
MS Platform SDK function.
\fBquerygroupmem\fR
.PP
.PP
.PP
\fBSPOOLSS\fR
.PP
.TP 0.2i
\(bu
\fBspoolgetprinterdriverdir
arch\fR - Execute a GetPrinterDriverDirectory()
RPC to retreive the SMB share name and subdirectory for
storing printer driver files for a given architecture. Possible
values for \fIarch\fR are "Windows 4.0"
(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
Alpha_AXP", and "Windows NT R4000".
.TP 0.2i
\(bu
\fBspooladdprinterdriver
arch config\fR - Execute an
AddPrinterDriver() RPC to install the printer driver information
on the server. Note that the driver files should already exist
in the directory returned by spoolgetprinterdriverdir. Possible
values for \fIarch\fR are the same as those for
the \fBspooolgetprintedriverdir\fR command.
\fBadddriver <arch> <config>\fR
- Execute an AddPrinterDriver() RPC to install the printer driver
information on the server. Note that the driver files should
already exist in the directory returned by
\fBgetdriverdir\fR. Possible values for
\fIarch\fR are the same as those for
the \fBgetdriverdir\fR command.
The \fIconfig\fR parameter is defined as
follows:
.sp
.nf
Long Printer Name:\\
Driver File Name:\\
Data File Name:\\
Config File Name:\\
Help File Name:\\
Language Monitor Name:\\
Default Data Type:\\
Comma Separated list of Files
Long Printer Name:\\
Driver File Name:\\
Data File Name:\\
Config File Name:\\
Help File Name:\\
Language Monitor Name:\\
Default Data Type:\\
Comma Separated list of Files
.sp
.fi
@ -235,33 +171,105 @@ driver must already be installed prior to adding the driver or
else the RPC will fail.
.TP 0.2i
\(bu
\fBspooladdprinter printername
sharename drivername port
\fR- Add a printer on the remote server. This printer
\fBaddprinter <printername>
<sharename> <drivername> <port>\fR
- Add a printer on the remote server. This printer
will be automatically shared. Be aware that the printer driver
must already be installed on the server (see addprinterdriver)
and the \fIport\fRmust be a valid port name.
must already be installed on the server (see \fBadddriver\fR)
and the \fIport\fRmust be a valid port name (see
\fBenumports\fR.
.TP 0.2i
\(bu
\fBenumdata\fR - Enumerate all
printer setting data stored on the server. On Windows NT clients,
these values are stored in the registry, while Samba servers
store them in the printers TDB. This command corresponds
to the MS Platform SDK GetPrinterData() function (* This
command is currently unimplemented).
.TP 0.2i
\(bu
\fBenumjobs <printer>\fR
- List the jobs and status of a given printer.
This command corresponds to the MS Platform SDK EnumJobs()
function (* This command is currently unimplemented).
.TP 0.2i
\(bu
\fBenumports [level]\fR
- Executes an EnumPorts() call using the specified
info level. Currently only info levels 1 and 2 are supported.
.TP 0.2i
\(bu
\fBenumdrivers [level]\fR
- Execute an EnumPrinterDrivers() call. This lists the various installed
printer drivers for all architectures. Refer to the MS Platform SDK
documentation for more details of the various flags and calling
options. Currently supported info levels are 1, 2, and 3.
.TP 0.2i
\(bu
\fBenumprinters [level]\fR
- Execute an EnumPrinters() call. This lists the various installed
and share printers. Refer to the MS Platform SDK documentation for
more details of the various flags and calling options. Currently
supported info levels are 0, 1, and 2.
.TP 0.2i
\(bu
\fBgetdata <printername>\fR
- Retrieve the data for a given printer setting. See
the \fBenumdata\fR command for more information.
This command corresponds to the GetPrinterData() MS Platform
SDK function (* This command is currently unimplemented).
.TP 0.2i
\(bu
\fBgetdriver <printername>\fR
- Retrieve the printer driver information (such as driver file,
config file, dependent files, etc...) for
the given printer. This command corresponds to the GetPrinterDriver()
MS Platform SDK function. Currently info level 1, 2, and 3 are supported.
.TP 0.2i
\(bu
\fBgetdriverdir <arch>\fR
- Execute a GetPrinterDriverDirectory()
RPC to retreive the SMB share name and subdirectory for
storing printer driver files for a given architecture. Possible
values for \fIarch\fR are "Windows 4.0"
(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
Alpha_AXP", and "Windows NT R4000".
.TP 0.2i
\(bu
\fBgetprinter <printername>\fR
- Retrieve the current printer information. This command
corresponds to the GetPrinter() MS Platform SDK function.
.TP 0.2i
\(bu
\fBopenprinter <printername>\fR
- Execute an OpenPrinterEx() and ClosePrinter() RPC
against a given printer.
.TP 0.2i
\(bu
\fBsetdriver <printername> <drivername>\fR
- Execute a SetPrinter() command to update the printer driver associated
with an installed printer. The printer driver must already be correctly
installed on the print server.
See also the \fBenumprinters\fR and
\fBenumdrivers\fR commands for obtaining a list of
of installed printers and drivers.
.PP
\fBGeneral Commands\fR
\fBGENERAL OPTIONS\fR
.PP
.TP 0.2i
\(bu
\fBset\fR - Set miscellaneous
\fBrpcclient\fR command line options during a
running session.
\fBdebuglevel\fR - Set the current debug level
used to log information.
.TP 0.2i
\(bu
\fBuse\fR - Connect to a rmeote SMB
server. \fBrpcclient\fR has the ability to
maintain connections to multiple server simulaneously.
.TP 0.2i
\(bu
\fBhelp\fR - Print a listing of all
\fBhelp (?)\fR - Print a listing of all
known commands or extended help on a particular command.
.TP 0.2i
\(bu
\fBquit\fR - Exit \fBrpcclient
\fR.SH "BUGS"
\fBquit (exit)\fR - Exit \fBrpcclient
\fR\&.
.SH "BUGS"
.PP
\fBrpcclient\fR is designed as a developer testing tool
and may not be robust in certain areas (such as command line parsing).
@ -279,15 +287,15 @@ to be... a bit flakey in places.
.PP
The development of Samba's implementation is also a bit rough,
and as more of the services are understood, it can even result in
versions of \fBsmbd(8)\fR and \fBrpcclient\fR
versions of \fBsmbd(8)\fR and \fBrpcclient(1)\fR
that are incompatible for some commands or services. Additionally,
the developers are sending reports to Microsoft, and problems found
or reported to Microsoft are fixed in Service Packs, which may
result in incompatibilities."
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
the Samba suite.
This man page is correct for version 2.2 of the Samba
suite.
.SH "AUTHOR"
.PP
The original Samba software and related utilities
@ -295,6 +303,7 @@ were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.
.PP
The original rpcclient man page was written by Matthew Geddes,
Luke Kenneth Casson, and Gerald Carter. The conversion to
DocBook for Samba 2.2 was done by Gerald Carter
The original rpcclient man page was written by Matthew
Geddes, Luke Kenneth Casson, and rewriten by Gerald Carter.
The conversion to DocBook for Samba 2.2 was done by Gerald
Carter.

4
docs/manpages/samba.7
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SAMBA" "7" "23 February 2001" "" ""
.TH SAMBA 7 "24 Mar 2001" "samba 2.2.0-alpha3"
.SH NAME
SAMBA \- A Windows SMB/CIFS fileserver for UNIX
.SH SYNOPSIS
@ -125,7 +125,7 @@ Samba. The project would have been unmanageable without it.
.PP
In addition, several commercial organizations now help
fund the Samba Team with money and equipment. For details see
the Samba Web pages at http://samba.org/samba/samba-thanks.html <URL:http://samba.org/samba/samba-thanks.html>.
the Samba Web pages at http://samba.org/samba/samba-thanks.html.
.SH "AUTHOR"
.PP
The original Samba software and related utilities

1837
docs/manpages/smb.conf.5
View File

File diff suppressed because it is too large Load Diff

6
docs/manpages/smbcacls.1
View File

@ -3,15 +3,15 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBCACLS" "1" "23 February 2001" "" ""
.TH "SMBCACLS" "1" "19 April 2001" "" ""
.SH NAME
smbcacls \- Set or get ACLs on an NT file or directory names
.SH SYNOPSIS
.sp
\fBnmblookup\fR \fB//server/share\fR \fBfilename\fR [ \fB-U username\fR ] [ \fB-A acls\fR ] [ \fB-M acls\fR ] [ \fB-D acls\fR ] [ \fB-S acls\fR ] [ \fB-C name\fR ] [ \fB-G name\fR ] [ \fB-n\fR ] [ \fB-h\fR ]
\fBsmbcacls\fR \fB//server/share\fR \fBfilename\fR [ \fB-U username\fR ] [ \fB-A acls\fR ] [ \fB-M acls\fR ] [ \fB-D acls\fR ] [ \fB-S acls\fR ] [ \fB-C name\fR ] [ \fB-G name\fR ] [ \fB-n\fR ] [ \fB-h\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
The smbcacls program manipulates NT Access Control Lists
(ACLs) on SMB file shares.

10
docs/manpages/smbclient.1
View File

@ -3,15 +3,15 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBCLIENT" "1" "23 February 2001" "" ""
.TH SMBCLIENT 1 "24 Mar 2001" "smbclient 2.2.0-alpha3"
.SH NAME
smbclient \- ftp-like client to access SMB/CIFS resources on servers
.SH SYNOPSIS
.sp
\fBsmbclient\fR \fBservicename\fR [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-S server\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E <terminal code>\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ] [ \fBpassword\fR ]
\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-S server\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E <terminal code>\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBsmbclient\fR is a client that can
\&'talk' to an SMB/CIFS server. It offers an interface
@ -72,7 +72,7 @@ TCP socket options to set on the client
socket. See the socket options parameter in the \fI smb.conf (5)\fR manpage for the list of valid
options.
.TP
\fBname resolve order (G)\fR
\fB-R <name resolve order>\fR
This option is used by the programs in the Samba
suite to determine what naming services and in what order to resolve
host names to IP addresses. The option takes a space separated
@ -85,7 +85,7 @@ cause names to be resolved as follows :
\(bu
lmhosts : Lookup an IP
address in the Samba lmhosts file. If the line in lmhosts has
no name type attached to the NetBIOS name (see the lmhosts(5) <URL:lmhosts.5.html> for details) then
no name type attached to the NetBIOS name (see the lmhosts(5)for details) then
any name type matches for lookup.
.TP 0.2i
\(bu

12
docs/manpages/smbcontrol.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBCONTROL" "1" "23 February 2001" "" ""
.TH SMBCONTROL 1 "24 Mar 2001" "smbcontrol 2.2.0-alpha3"
.SH NAME
smbcontrol \- send messages to smbd or nmbd processes
.SH SYNOPSIS
@ -13,11 +13,11 @@ smbcontrol \- send messages to smbd or nmbd processes
\fBsmbcontrol\fR [ \fBdestination\fR ] [ \fBmessage-type\fR ] [ \fBparameter\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBsmbcontrol\fR is a very small program, which
sends messages to an smbd(8) <URL:smbd.8.html> or
an nmbd(8) <URL:nmbd.8.html> daemon running on the
sends messages to an smbd(8)or
an nmbd(8)daemon running on the
system.
.SH "OPTIONS"
.TP
@ -93,8 +93,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBnmbd(8)\fR <URL:nmbd.8.html>,
and \fBsmbd(8)\fR <URL:smbd.8.html>.
\fBnmbd(8)\fR,
and \fBsmbd(8)\fR.
.SH "AUTHOR"
.PP
The original Samba software and related utilities

36
docs/manpages/smbd.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBD" "8" "23 February 2001" "" ""
.TH SMBD 8 "24 Mar 2001" "smbd 2.2.0-alpha3"
.SH NAME
smbd \- server to provide SMB/CIFS services to clients
.SH SYNOPSIS
@ -26,13 +26,12 @@ An extensive description of the services that the
server can provide is given in the man page for the
configuration file controlling the attributes of those
services (see \fIsmb.conf(5)
\fR <URL:smb.conf.5.html>. This man page will not describe the
\fR. This man page will not describe the
services, but will concentrate on the administrative aspects
of running the server.
.PP
Please note that there are significant security
implications to running this server, and the \fIsmb.conf(5)\fR <URL:smb.conf.5.html>
manpage should be regarded as mandatory reading before
implications to running this server, and the \fIsmb.conf(5)\fRmanpage should be regarded as mandatory reading before
proceeding with installation.
.PP
A session is created whenever a client requests one.
@ -103,21 +102,19 @@ data, most of which is extremely cryptic.
Note that specifying this parameter here will
override the log
level <URL:smb.conf.5.html#loglevel> parameter in the \fIsmb.conf(5)\fR <URL:smb.conf.5.html> file.
levelfile.
.TP
\fB-l <log file>\fR
If specified, \fBlog file\fR
specifies a log filename into which informational and debug
messages from the running server will be logged. The log
file generated is never removed by the server although
its size may be controlled by the max log size <URL:smb.conf.5.html#maxlogsize>
option in the \fI smb.conf(5)\fR <URL:smb.conf.5.html> file. The default log
its size may be controlled by the max log sizeoption in the \fI smb.conf(5)\fRfile. The default log
file name is specified at compile time.
.TP
\fB-O <socket options>\fR
See the socket options <URL:smb.conf.5.html#socketoptions>
parameter in the \fIsmb.conf(5)
\fR <URL:smb.conf.5.html> file for details.
See the socket optionsparameter in the \fIsmb.conf(5)
\fRfile for details.
.TP
\fB-p <port number>\fR
port number is a positive integer
@ -148,7 +145,7 @@ configuration details required by the server. The
information in this file includes server-specific
information such as what printcap file to use, as well
as descriptions of all the services that the server is
to provide. See \fI smb.conf(5)\fR <URL:smb.conf.5.html> for more information.
to provide. See \fI smb.conf(5)\fRfor more information.
The default configuration file name is determined at
compile time.
.SH "FILES"
@ -177,13 +174,12 @@ See the section INSTALLATION below.
.TP
\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
This is the default location of the
\fIsmb.conf\fR <URL:smb.conf.5.html>
server configuration file. Other common places that systems
\fIsmb.conf\fRserver configuration file. Other common places that systems
install this file are \fI/usr/samba/lib/smb.conf\fR
and \fI/etc/smb.conf\fR.
This file describes all the services the server
is to make available to clients. See \fIsmb.conf(5)\fR <URL:smb.conf.5.html> for more information.
is to make available to clients. See \fIsmb.conf(5)\fRfor more information.
.SH "LIMITATIONS"
.PP
On some systems \fBsmbd\fR cannot change uid back
@ -315,10 +311,10 @@ need the assistance of your system administrator to modify the
system files.
.PP
You will probably want to set up the NetBIOS name server
\fBnmbd\fR <URL:nmbd.8.html> at
\fBnmbd\fRat
the same time as \fBsmbd\fR. To do this refer to the
man page for \fBnmbd(8)\fR
<URL:nmbd.8.html>.
.
.PP
First, ensure that a port is configured in the file
\fI/etc/services\fR. The well-known port 139
@ -387,7 +383,7 @@ to the service \fI\\\\fred\\mary\fR.
.PP
To properly test and experiment with the server, we
recommend using the \fBsmbclient\fR program (see
\fBsmbclient(1)\fR <URL:smbclient.1.html>)
\fBsmbclient(1)\fR)
and also going through the steps outlined in the file
\fIDIAGNOSIS.txt\fR in the \fIdocs/\fR
directory of your Samba installation.
@ -439,10 +435,10 @@ them after, however this would affect performance.
.SH "SEE ALSO"
.PP
hosts_access(5), \fBinetd(8)\fR,
\fBnmbd(8)\fR <URL:nmbd.8.html>,
\fBnmbd(8)\fR,
\fIsmb.conf(5)\fR
<URL:smb.conf.5.html>, \fBsmbclient(1)
\fR <URL:smbclient.1.html>, \fB testparm(1)\fR <URL:testparm.1.html>, \fBtestprns(1)\fR <URL:testprns.1.html>, and the Internet RFC's
, \fBsmbclient(1)
\fR, and the Internet RFC's
\fIrfc1001.txt\fR, \fIrfc1002.txt\fR.
In addition the CIFS (formerly SMB) specification is available
as a link from the Web page

15
docs/manpages/smbmnt.8
View File

@ -3,12 +3,12 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBMNT" "8" "23 February 2001" "" ""
.TH SMBMNT 8 "24 Mar 2001" "smbmnt 2.2.0-alpha3"
.SH NAME
smbmnt \- helper utility for mounting SMB filesystems
.SH SYNOPSIS
.sp
\fBsmbumount\fR \fBmount-point\fR [ \fB-s <share>\fR ] [ \fB-r\fR ] [ \fB-u <uid>\fR ] [ \fB-g <gid>\fR ] [ \fB-f <mask>\fR ] [ \fB-d <mask>\fR ]
\fBsmbmnt\fR \fBmount-point\fR [ \fB-s <share>\fR ] [ \fB-r\fR ] [ \fB-u <uid>\fR ] [ \fB-g <gid>\fR ] [ \fB-f <mask>\fR ] [ \fB-d <mask>\fR ] [ \fB-o <options>\fR ]
.SH "DESCRIPTION"
.PP
\fBsmbmnt\fR is a helper application used
@ -20,7 +20,7 @@ then mounts the directory.
.PP
The \fBsmbmnt\fR program is normally invoked
by \fBsmbmount(8)\fR
<URL:smbmount.8.html>. It should not be invoked directly by users.
. It should not be invoked directly by users.
.SH "OPTIONS"
.TP
\fB-r\fR
@ -40,11 +40,20 @@ specify the octal file mask applied
\fB-d mask\fR
specify the octal directory mask
applied
.TP
\fB-o options\fR
list of options that are passed as-is to smbfs, if this
command is run on a 2.4 or higher linux kernel.
.SH "AUTHOR"
.PP
Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.
.PP
The current maintainer of smbfs and the userspace
tools \fBsmbmount\fR, \fBsmbumount\fR,
and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
The SAMBA Mailing list <URL:mailto:samba@samba.org>
is the preferred place to ask questions regarding these programs.
.PP
The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter

122
docs/manpages/smbmount.8
View File

@ -3,9 +3,9 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBMOUNT" "8" "23 February 2001" "" ""
.TH SMBMOUNT 8 "24 Mar 2001" "smbmount 2.2.0-alpha3"
.SH NAME
smbmount \- mount and smbfs filesystem
smbmount \- mount an smbfs filesystem
.SH SYNOPSIS
.sp
\fBsmbumount\fR \fBservice\fR \fBmount-point\fR [ \fB-o options\fR ]
@ -16,8 +16,17 @@ is usually invoked as \fBmount.smb\fR from
the \fBmount(8)\fR command when using the
"-t smb" option. The kernel must support the smbfs filesystem.
.PP
Options to smbmount are specified as a comma separated list
of key=value pairs.
Options to smbmount are specified as a comma separated
list of key=value pairs. It is possible to send options other
than those listed here, assuming that smbfs supports them. If
you get mount failures, check your kernel log for errors on
unknown options.
.PP
smbmount is a daemon. After mounting it keeps running until
the mounted smbfs is umounted. It will log things that happen
when in daemon mode using the "machine name" smbmount, so
typically this output will end up in log.smbmount. The
smbmount process may also be called mount.smbfs.
.PP
\fBNOTE:\fR \fBsmbmount\fR
calls \fBsmbmnt(8)\fR to do the actual mount. You
@ -27,26 +36,47 @@ that it can be found.
.TP
\fBusername=<arg>\fR
specifies the username to connect as. If
this is not given then the environment variable \fI $USER\fR is used. This option can also take the
form "user%password" or "user/workgroup" or
"user/workgroup%password" to allow the password and workgroup
this is not given, then the environment variable \fB USER\fR is used. This option can also take the
form "user%password" or "user/workgroup" or
"user/workgroup%password" to allow the password and workgroup
to be specified as part of the username.
.TP
\fBpassword=<arg>\fR
specifies the SMB password. If not given then
\fBsmbmount\fR will prompt for a passeword, unless
the guest option is given.
specifies the SMB password. If this
option is not given then the environment variable
\fBPASSWD\fR is used. If it can find
no password \fBsmbmount\fR will prompt
for a passeword, unless the guest option is
given.
.TP
\fBcredentials=<filename>\fR
specifies a file that contains a username
and/or password. The format of the file is:
.sp
.nf
username = <value>
password = <value>
.sp
.fi
This is preferred over having passwords in plaintext in a
shared file, such as /etc/fstab. Be sure to protect any
credentials file properly.
.TP
\fBnetbiosname=<arg>\fR
sets the source NetBIOS name. It defaults
to the local hostname.
.TP
\fBuid=<arg>\fR
sets the uid that files will be mounted as.
sets the uid that will own all files on
the mounted filesystem.
It may be specified as either a username or a numeric uid.
.TP
\fBgid=<arg>\fR
sets the gid that files will be mounted as.
sets the gid that will own all files on
the mounted filesystem.
It may be specified as either a groupname or a numeric
gid.
.TP
@ -76,7 +106,7 @@ sets the workgroup on the destination
.TP
\fBsockopt=<arg>\fR
sets the TCP socket options. See the \fIsmb.conf
\fR <URL:smb.conf.5.html#SOCKETOPTIONS> \fIsocket options\fR option.
\fR\fIsocket options\fR option.
.TP
\fBscope=<arg>\fR
sets the NetBIOS scope
@ -89,11 +119,75 @@ mount read-only
.TP
\fBrw\fR
mount read-write
.TP
\fBiocharset=<arg>\fR
sets the charset used by the linux side for codepage
to charset translations (NLS). Argument should be the
name of a charset, like iso8859-1. (Note: only kernel
2.4.0 or later)
.TP
\fBcodepage=<arg>\fR
sets the codepage the server uses. See the iocharset
option. Example value cp850. (Note: only kernel 2.4.0
or later)
.TP
\fBttl=<arg>\fR
how long a directory listing is cached in milliseconds
(also affects visibility of file size and date
changes). A higher value means that changes on the
server take longer to be noticed but it can give
better performance on large directories, especially
over long distances. Default is 1000ms but something
like 10000ms (10 seconds) is probably more reasonable
in many cases.
(Note: only kernel 2.4.2 or later)
.SH "ENVIRONMENT VARIABLES"
.PP
The variable \fBUSER\fR may contain the username of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords. The variable can be used to set both username and
password by using the format username%password.
.PP
The variable \fBPASSWD\fR may contain the password of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords.
.PP
The variable \fBPASSWD_FILE\fR may contain the pathname of
a file to read the password from. A single line of input is
read and used as password.
.SH "BUGS"
.PP
Not many known smbmount bugs. But one smbfs bug is
important enough to mention here anyway:
.TP 0.2i
\(bu
Mounts sometimes stop working. This is usually
caused by smbmount terminating. Since smbfs needs smbmount to
reconnect when the server disconnects, the mount will go
dead. A re-mount normally fixes this. At least 2 ways to
trigger this bug are known.
.PP
Note that the typical response to a bugreport is suggestion
to try the latest version first. So please try doing that first,
and always include which versions you use of relevant software
when reporting bugs (minimum: samba, kernel, distribution)
.PP
.SH "SEE ALSO"
.PP
Documentation/filesystems/smbfs.txt in the kernel source tree
may contain additional options and information.
.SH "AUTHOR"
.PP
Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.
.PP
The current maintainer of smbfs and the userspace
tools \fBsmbmount\fR, \fBsmbumount\fR,
and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>
and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
The SAMBA Mailing list <URL:mailto:samba@samba.org>
is the preferred place to ask questions regarding these programs.
.PP
The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter

10
docs/manpages/smbpasswd.5
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBPASSWD" "5" "23 February 2001" "" ""
.TH SMBPASSWD 5 "24 Mar 2001" "smbpasswd 2.2.0-alpha3"
.SH NAME
smbpasswd \- The Samba encrypted password file
.SH SYNOPSIS
@ -11,7 +11,7 @@ smbpasswd \- The Samba encrypted password file
\fIsmbpasswd\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
smbpasswd is the Samba encrypted password file. It contains
the username, Unix user id and the SMB hashed passwords of the
@ -109,7 +109,7 @@ in the smbpasswd file.
account has no password (the passwords in the fields Lanman
Password Hash and NT Password Hash are ignored). Note that this
will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fIsmb.conf(5)
\fR <URL:smb.conf.5.html#NULLPASSWORDS> config file.
\fRconfig file.
.TP 0.2i
\(bu
\fBD\fR - This means the account
@ -141,8 +141,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbpasswd(8)\fR <URL:smbpasswd.8.html>,
samba(7) <URL:samba.7.html>, and
\fBsmbpasswd(8)\fR,
samba(7), and
the Internet RFC1321 for details on the MD4 algorithm.
.SH "AUTHOR"
.PP

13
docs/manpages/smbpasswd.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBPASSWD" "8" "23 February 2001" "" ""
.TH "SMBPASSWD" "8" "03 April 2001" "" ""
.SH NAME
smbpasswd \- change a users SMB password
.SH SYNOPSIS
@ -11,7 +11,7 @@ smbpasswd \- change a users SMB password
\fBsmbpasswd\fR [ \fB-a\fR ] [ \fB-x\fR ] [ \fB-d\fR ] [ \fB-e\fR ] [ \fB-D debuglevel\fR ] [ \fB-n\fR ] [ \fB-r <remote machine>\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-m\fR ] [ \fB-j DOMAIN\fR ] [ \fB-U username\fR ] [ \fB-h\fR ] [ \fB-s\fR ] [ \fBusername\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
The smbpasswd program has several different
functions, depending on whether it is run by the \fBroot\fR
@ -159,7 +159,7 @@ a real password database so it is not possible to change passwords
specifying a Win95/98 machine as remote machine target.
.TP
\fB-R name resolve order\fR
This option allows the user of smbclient to determine
This option allows the user of smbpasswd to determine
what name resolution services to use when looking up the NetBIOS
name of the host being connected to.
@ -170,7 +170,7 @@ names to be resolved as follows :
\(bu
lmhosts : Lookup an IP
address in the Samba lmhosts file. If the line in lmhosts has
no name type attached to the NetBIOS name (see the lmhosts(5) <URL:lmhosts.5.html> for details) then
no name type attached to the NetBIOS name (see the lmhosts(5)for details) then
any name type matches for lookup.
.TP 0.2i
\(bu
@ -284,9 +284,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fIsmbpasswd(5)\fR <URL:smbpasswd.5.html>,
samba(7) <URL:samba.7.html>
.SH "AUTHOR"
\fIsmbpasswd(5)\fR,
samba(7).SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

13
docs/manpages/smbrun.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBRUN" "1" "23 February 2001" "" ""
.TH SMBRUN 1 "24 Mar 2001" "smbrun 2.2.0-alpha3"
.SH NAME
smbrun \- interface program between smbd and external programs
.SH SYNOPSIS
@ -11,10 +11,10 @@ smbrun \- interface program between smbd and external programs
\fBsmbrun\fR \fB<shell command>\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBsmbrun\fR is a very small 'glue' program,
which runs shell commands for the \fB smbd(8)\fR <URL:smbd.8.html> daemon.
which runs shell commands for the \fB smbd(8)\fRdaemon.
.PP
It first changes to the highest effective user and group
ID that it can, then runs the command line provided using the
@ -35,7 +35,7 @@ is not given in the command.
.PP
If \fBsmbrun\fR cannot be located or cannot
be executed by \fBsmbd(8)\fR
<URL:smbd.8.html>, then appropriate messages will be found in the \fB smbd\fR logs. Other diagnostics are dependent on the shell-command
, then appropriate messages will be found in the \fB smbd\fR logs. Other diagnostics are dependent on the shell-command
being run. It is advisable for your shell commands to issue suitable
diagnostics to aid trouble-shooting.
.SH "VERSION"
@ -44,10 +44,9 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBnmbd(8)\fR <URL:nmbd.8.html>,
\fBnmbd(8)\fR,
\fBsmbclient(1)
\fR <URL:smbclient.1.html>, and \fBnmblookup(1)\fR <URL:nmblookup.1.html>
.SH "AUTHOR"
\fR.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

9
docs/manpages/smbsh.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBSH" "1" "23 February 2001" "" ""
.TH SMBSH 1 "24 Mar 2001" "smbsh 2.2.0-alpha3"
.SH NAME
smbsh \- Allows access to Windows NT filesystem using UNIX commands
.SH SYNOPSIS
@ -11,7 +11,7 @@ smbsh \- Allows access to Windows NT filesystem using UNIX commands
\fBsmbsh\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBsmbsh\fR allows you to access an NT filesystem
using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR. You must use a
@ -55,9 +55,8 @@ of UNIX have a \fBfile\fR command that will
describe how a program was linked.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html>,
smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
\fBsmbd(8)\fR,
smb.conf(5).SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

8
docs/manpages/smbspool.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBSPOOL" "8" "23 February 2001" "" ""
.TH SMBSPOOL 8 "24 Mar 2001" "smbspool 2.2.0-alpha3"
.SH NAME
nmblookup \- send print file to an SMB printer
.SH SYNOPSIS
@ -11,7 +11,7 @@ nmblookup \- send print file to an SMB printer
\fBsmbspool\fR [ \fBjob\fR ] [ \fBuser\fR ] [ \fBtitle\fR ] [ \fBcopies\fR ] [ \fBoptions\fR ] [ \fBfilename\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
smbspool is a very small print spooling program that
sends a print file to an SMB printer. The command-line arguments
@ -82,8 +82,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html>,
and samba(7) <URL:samba.7.html>.
\fBsmbd(8)\fR,
and samba(7).
.SH "AUTHOR"
.PP
\fBsmbspool\fR was written by Michael Sweet

12
docs/manpages/smbstatus.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBSTATUS" "1" "23 February 2001" "" ""
.TH SMBSTATUS 1 "24 Mar 2001" "smbstatus 2.2.0-alpha3"
.SH NAME
smbstatus \- report on current Samba connections
.SH SYNOPSIS
@ -11,7 +11,7 @@ smbstatus \- report on current Samba connections
\fBsmbstatus\fR [ \fB-P\fR ] [ \fB-b\fR ] [ \fB-d\fR ] [ \fB-L\fR ] [ \fB-p\fR ] [ \fB-S\fR ] [ \fB-s <configuration file>\fR ] [ \fB-u <username>\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBsmbstatus\fR is a very simple program to
list the current Samba connections.
@ -32,7 +32,7 @@ gives verbose output.
causes smbstatus to only list locks.
.TP
\fB-p\fR
print a list of \fBsmbd(8)\fR <URL:smbd.8.html> processes and exit.
print a list of \fBsmbd(8)\fRprocesses and exit.
Useful for scripting.
.TP
\fB-S\fR
@ -42,7 +42,7 @@ causes smbstatus to only list shares.
The default configuration file name is
determined at compile time. The file specified contains the
configuration details required by the server. See \fIsmb.conf(5)\fR
<URL:smb.conf.5.html> for more information.
for more information.
.TP
\fB-u <username>\fR
selects information relevant to
@ -53,8 +53,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html> and
smb.conf(5) <URL:smb.conf.5.html>.
\fBsmbd(8)\fRand
smb.conf(5).
.SH "AUTHOR"
.PP
The original Samba software and related utilities

15
docs/manpages/smbtar.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBTAR" "1" "23 February 2001" "" ""
.TH SMBTAR 1 "24 Mar 2001" "smbtar 2.2.0-alpha3"
.SH NAME
smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives
.SH SYNOPSIS
@ -11,11 +11,10 @@ smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape dri
\fBsmbtar\fR \fB-s server\fR [ \fB-p password\fR ] [ \fB-x services\fR ] [ \fB-X\fR ] [ \fB-d directory\fR ] [ \fB-u user\fR ] [ \fB-t tape\fR ] [ \fB-t tape\fR ] [ \fB-b blocksize\fR ] [ \fB-N filename\fR ] [ \fB-i\fR ] [ \fB-r\fR ] [ \fB-l loglevel\fR ] [ \fB-v\fR ] \fBfilenames\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBsmbtar\fR is a very small shell script on top
of \fBsmbclient(1)\fR <URL:smbclient.1.html>
which dumps SMB shares directly to tape.
of \fBsmbclient(1)\fRwhich dumps SMB shares directly to tape.
.SH "OPTIONS"
.TP
\fB-s server\fR
@ -92,16 +91,16 @@ with GNU tar and may not work well with other versions.
.PP
See the \fBDIAGNOSTICS\fR section for the
\fBsmbclient(1)\fR
<URL:smbclient.1.html> command.
command.
.SH "VERSION"
.PP
This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fBsmbd(8)\fR <URL:smbd.8.html>,
\fBsmbclient(1)\fR <URL:smbclient.1.html>,
smb.conf(5) <URL:smb.conf.5.html>,
\fBsmbd(8)\fR,
\fBsmbclient(1)\fR,
smb.conf(5),
.SH "AUTHOR"
.PP
The original Samba software and related utilities

8
docs/manpages/smbumount.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBUMOUNT" "8" "23 February 2001" "" ""
.TH SMBUMOUNT 8 "24 Mar 2001" "smbumount 2.2.0-alpha3"
.SH NAME
smbumount \- smbfs umount for normal users
.SH SYNOPSIS
@ -26,12 +26,16 @@ The directory to unmount.
.SH "SEE ALSO"
.PP
\fBsmbmount(8)\fR
<URL:smbmount.8.html>
.SH "AUTHOR"
.PP
Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.
.PP
The current maintainer of smbfs and the userspace
tools \fBsmbmount\fR, \fBsmbumount\fR,
and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
The SAMBA Mailing list <URL:mailto:samba@samba.org>
is the preferred place to ask questions regarding these programs.
.PP
The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter

11
docs/manpages/swat.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SWAT" "8" "23 February 2001" "" ""
.TH SWAT 8 "24 Mar 2001" "swat 2.2.0-alpha3"
.SH NAME
swat \- Samba Web Administration Tool
.SH SYNOPSIS
@ -11,10 +11,10 @@ swat \- Samba Web Administration Tool
\fBnmblookup\fR [ \fB-s <smb config file>\fR ] [ \fB-a\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBswat\fR allows a Samba administrator to
configure the complex \fI smb.conf(5)\fR <URL:smb.conf.5.html> file via a Web browser. In addition,
configure the complex \fI smb.conf(5)\fRfile via a Web browser. In addition,
a \fBswat\fR configuration page has help links
to all the configurable options in the smb.conf file allowing an
administrator to easily look up the effects of any change.
@ -123,9 +123,8 @@ the Samba suite.
.SH "SEE ALSO"
.PP
\fBinetd(5)\fR,
\fBsmbd(8)\fR <URL:smbd.8.html>,
smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
\fBsmbd(8)\fR,
smb.conf(5).SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

9
docs/manpages/testparm.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "TESTPARM" "1" "23 February 2001" "" ""
.TH TESTPARM 1 "24 Mar 2001" "testparm 2.2.0-alpha3"
.SH NAME
testparm \- check an smb.conf configuration file for internal correctness
.SH SYNOPSIS
@ -11,7 +11,7 @@ testparm \- check an smb.conf configuration file for internal correctness
\fBtestparm\fR [ \fB-s\fR ] [ \fB-h\fR ] [ \fB-L <servername>\fR ] \fBconfig filename\fR [ \fBhostname hostIP\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBtestparm\fR is a very simple test program
to check an \fBsmbd\fR configuration file for
@ -83,9 +83,8 @@ This man page is correct for version 2.2 of
the Samba suite.
.SH "SEE ALSO"
.PP
\fIsmb.conf(5)\fR <URL:smb.conf.5.html>,
\fBsmbd(8)\fR <URL:smbd.8.html>
.SH "AUTHOR"
\fIsmb.conf(5)\fR,
\fBsmbd(8)\fR.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

11
docs/manpages/testprns.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "TESTPRNS" "1" "23 February 2001" "" ""
.TH TESTPRNS 1 "24 Mar 2001" "testprns 2.2.0-alpha3"
.SH NAME
testprns \- check printer name for validity with smbd
.SH SYNOPSIS
@ -11,11 +11,11 @@ testprns \- check printer name for validity with smbd
\fBtestprns\fR \fBprintername\fR [ \fBprintcapname\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
\fBtestprns\fR is a very simple test program
to determine whether a given printer name is valid for use in
a service to be provided by \fB smbd(8)\fR <URL:smbd.8.html>.
a service to be provided by \fB smbd(8)\fR.
.PP
"Valid" in this context means "can be found in the
printcap specified". This program is very stupid - so stupid in
@ -73,9 +73,8 @@ the Samba suite.
.SH "SEE ALSO"
.PP
\fIprintcap(5)\fR,
\fBsmbd(8)\fR <URL:smbd.8.html>,
\fBsmbclient(1)\fR <URL:smbclient.1.html>
.SH "AUTHOR"
\fBsmbd(8)\fR,
\fBsmbclient(1)\fR.SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed

7
docs/manpages/wbinfo.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WBINFO" "1" "23 February 2001" "" ""
.TH WBINFO 1 "24 Mar 2001" "wbinfo 2.2.0-alpha3"
.SH NAME
wbinfo \- Query information from winbind daemon
.SH SYNOPSIS
@ -11,10 +11,10 @@ wbinfo \- Query information from winbind daemon
\fBnmblookup\fR [ \fB-u\fR ] [ \fB-g\fR ] [ \fB-n name\fR ] [ \fB-s sid\fR ] [ \fB-U uid\fR ] [ \fB-G gid\fR ] [ \fB-S sid\fR ] [ \fB-Y sid\fR ] [ \fB-t\fR ] [ \fB-m\fR ]
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite.
This tool is part of the Sambasuite.
.PP
The \fBwbinfo\fR program queries and returns information
created and used by the \fB winbindd(8)\fR <URL:winbindd.8.html> daemon.
created and used by the \fB winbindd(8)\fRdaemon.
.PP
The \fBwinbindd(8)\fR daemon must be configured
and running for the \fBwbinfo\fR program to be able
@ -96,7 +96,6 @@ stable release of Samba as of yet.
.SH "SEE ALSO"
.PP
\fBwinbindd(8)\fR
<URL:winbindd.8.html>
.SH "AUTHOR"
.PP
The original Samba software and related utilities

11
docs/manpages/winbindd.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WINBINDD" "8" "23 February 2001" "" ""
.TH WINBINDD 8 "24 Mar 2001" "winbindd 2.2.0-alpha3"
.SH NAME
winbindd \- Name Service Switch daemon for resolving names from NT servers
.SH SYNOPSIS
@ -11,7 +11,7 @@ winbindd \- Name Service Switch daemon for resolving names from NT servers
\fBnmblookup\fR [ \fB-d debuglevel\fR ] [ \fB-i\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B <broadcast address>\fR ] [ \fB-U <unicast address>\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-i <NetBIOS scope>\fR ] [ \fB-T\fR ] \fBname\fR
.SH "DESCRIPTION"
.PP
This tool is part of the Samba <URL:samba.7.html> suite version 3.0 and describes functionality not
This tool is part of the Sambasuite version 3.0 and describes functionality not
yet implemented in the main version of Samba.
.PP
\fBwinbindd\fR is a daemon that provides
@ -358,10 +358,9 @@ stable release of Samba as of yet.
.SH "SEE ALSO"
.PP
\fInsswitch.conf(5)\fR,
samba(7) <URL:samba.7.html>,
wbinfo(1) <URL:wbinfo.1.html>,
smb.conf(5) <URL:smb.conf.5.html>
.SH "AUTHOR"
samba(7),
wbinfo(1),
smb.conf(5).SH "AUTHOR"
.PP
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed