From 50c54ae56f8e50efcdcf72b54b9aeef6201499ac Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Sat, 5 Apr 2003 07:42:29 +0000 Subject: Merging HEAD to 3.0.0 (This used to be commit 0160a8c1ea1aefbbbaaeeccb8f3ab3487d588df2) --- docs/docbook/projdoc/ADS-HOWTO.sgml | 45 ++-- docs/docbook/projdoc/AdvancedNetworkAdmin.sgml | 91 ++++--- docs/docbook/projdoc/Browsing-Quickguide.sgml | 82 ++++--- docs/docbook/projdoc/Browsing.sgml | 7 +- docs/docbook/projdoc/Bugs.sgml | 5 +- docs/docbook/projdoc/CUPS-printing.sgml | 77 +++--- docs/docbook/projdoc/Compiling.sgml | 1 + docs/docbook/projdoc/DOMAIN_MEMBER.sgml | 22 +- docs/docbook/projdoc/Diagnosis.sgml | 80 +++---- docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml | 4 +- docs/docbook/projdoc/Integrating-with-Windows.sgml | 13 +- docs/docbook/projdoc/NT4Migration.sgml | 4 +- docs/docbook/projdoc/NT_Security.sgml | 10 +- docs/docbook/projdoc/Other-Clients.sgml | 17 +- .../projdoc/PAM-Authentication-And-Samba.sgml | 16 +- docs/docbook/projdoc/PolicyMgmt.sgml | 63 ++--- docs/docbook/projdoc/Portability.sgml | 4 +- docs/docbook/projdoc/ProfileMgmt.sgml | 264 +++++++++++++++++++-- docs/docbook/projdoc/SWAT.sgml | 4 +- docs/docbook/projdoc/Samba-BDC-HOWTO.sgml | 9 +- docs/docbook/projdoc/Samba-PDC-HOWTO.sgml | 15 +- docs/docbook/projdoc/ServerType.sgml | 8 +- docs/docbook/projdoc/Speed.sgml | 7 +- docs/docbook/projdoc/UNIX_INSTALL.sgml | 7 + docs/docbook/projdoc/VFS.sgml | 4 +- docs/docbook/projdoc/passdb.sgml | 55 +---- docs/docbook/projdoc/printer_driver2.sgml | 30 +-- docs/docbook/projdoc/samba-doc.sgml | 29 +-- docs/docbook/projdoc/securing-samba.sgml | 5 +- docs/docbook/projdoc/security_level.sgml | 9 +- docs/docbook/projdoc/unicode.sgml | 8 +- docs/docbook/projdoc/upgrading-to-3.0.sgml | 11 +- docs/docbook/projdoc/winbind.sgml | 24 +- 33 files changed, 533 insertions(+), 497 deletions(-) (limited to 'docs/docbook/projdoc') diff --git a/docs/docbook/projdoc/ADS-HOWTO.sgml b/docs/docbook/projdoc/ADS-HOWTO.sgml index a98fe14e31..5e93c62876 100644 --- a/docs/docbook/projdoc/ADS-HOWTO.sgml +++ b/docs/docbook/projdoc/ADS-HOWTO.sgml @@ -1,10 +1,9 @@ - - AndrewTridgell - - 2002 + &author.tridge; + &author.jelmer; + 2002/2003 Samba as a ADS domain member @@ -33,18 +32,19 @@ In case samba can't figure out your ads server using your realm name, use the -You do *not* need a smbpasswd file, and older clients will - be authenticated as if "security = domain", although it won't do any harm +You do *not* need a smbpasswd file, and older clients will + be authenticated as if security = domain, + although it won't do any harm and allows you to have local users not in the domain. I expect that the above required options will change soon when we get better - active directory integration. + active directory integration. Setup your <filename>/etc/krb5.conf</filename> -The minimal configuration for krb5.conf is: +The minimal configuration for krb5.conf is: [realms] @@ -53,10 +53,10 @@ In case samba can't figure out your ads server using your realm name, use the } -Test your config by doing a "kinit USERNAME@REALM" and making sure that +Test your config by doing a kinit USERNAME@REALM and making sure that your password is accepted by the Win2000 KDC. -NOTE: The realm must be uppercase. +The realm must be uppercase. You also must ensure that you can do a reverse DNS lookup on the IP @@ -67,27 +67,30 @@ followed by the realm. -The easiest way to ensure you get this right is to add a /etc/hosts -entry mapping the IP address of your KDC to its netbios name. If you -don't get this right then you will get a "local error" when you try -to join the realm. +The easiest way to ensure you get this right is to add a +/etc/hosts entry mapping the IP address of your KDC to +its netbios name. If you don't get this right then you will get a +"local error" when you try to join the realm. If all you want is kerberos support in smbclient then you can skip -straight to step 5 now. Step 3 is only needed if you want kerberos +straight to Test with smbclient now. +Creating a computer account +and testing your servers +is only needed if you want kerberos support for smbd and winbindd. - + Create the computer account As a user that has write permission on the Samba private directory (usually root) run: -net ads join +net ads join @@ -104,19 +107,19 @@ As a user that has write permission on the Samba private directory - + Test your server setup -On a Windows 2000 client try net use * \\server\share. You should +On a Windows 2000 client try net use * \\server\share. You should be logged in with kerberos without needing to know a password. If -this fails then run klist tickets. Did you get a ticket for the +this fails then run klist tickets. Did you get a ticket for the server? Does it have an encoding type of DES-CBC-MD5 ? - + Testing with smbclient diff --git a/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml b/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml index fe0774810b..58bc9a444e 100644 --- a/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml +++ b/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml @@ -1,15 +1,7 @@ - - John HTerpstra - - Samba Team -
- jht@samba.org -
- - - April 3 2003 + &author.jht; + April 3 2003 Advanced Network Manangement @@ -43,7 +35,7 @@ Samba stores the per share access control settings in a file called sh The location of this file on your system will depend on how samba was compiled. The default location for samba's tdb files is under /usr/local/samba/var. If the tdbdump utility has been compiled and installed on your system then you can examine the contents of this file -by: tdbdump share_info.tdb. +by: tdbdump share_info.tdb. @@ -61,19 +53,18 @@ Server Manager is shipped with Windows NT4 Server products but not with Windows You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below. - -Instructions: - - - - Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu - select Computer, then click on the Shared Directories entry. - + +Instructions + +Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu +select Computer, then click on the Shared Directories entry. + - + Now click on the share that you wish to manage, then click on the Properties tab, next click on the Permissions tab. Now you can Add or change access control settings as you wish. - + + @@ -93,37 +84,37 @@ Microsoft Management Console (MMC). This tool is located by clicking on Computer Management. - -Instructions: - - + +Instructions + After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', select 'Connect to another computer'. If you are not logged onto a domain you will be prompted to enter a domain login user identifier and a password. This will authenticate you to the domain. If you where already logged in with administrative privilidge this step is not offered. - - - - If the Samba server is not shown in the Select Computer box, then type in the name of the target - Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] - next to 'Shared Folders' in the left panel. - - - - Now in the right panel, double-click on the share you wish to set access control permissions on. - Then click on the tab 'Share Permissions'. It is now possible to add access control entities - to the shared folder. Do NOT forget to set what type of access (full control, change, read) you - wish to assign for each entry. - - - - - Be careful. If you take away all permissions from the Everyone user without removing this user - then effectively no user will be able to access the share. This is a result of what is known as - ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone - will have no access even if this user is given explicit full control access. - - + + + +If the Samba server is not shown in the Select Computer box, then type in the name of the target +Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] +next to 'Shared Folders' in the left panel. + + + +Now in the right panel, double-click on the share you wish to set access control permissions on. +Then click on the tab 'Share Permissions'. It is now possible to add access control entities +to the shared folder. Do NOT forget to set what type of access (full control, change, read) you +wish to assign for each entry. + + + + + +Be careful. If you take away all permissions from the Everyone user without removing this user +then effectively no user will be able to access the share. This is a result of what is known as +ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone +will have no access even if this user is given explicit full control access. + + @@ -148,9 +139,7 @@ systems. The tools set includes: Server Manager - User Manager for Domains - Event Viewer @@ -171,7 +160,7 @@ from ftp://ft This section needs work. Volunteer contributions most welcome. Please send your patches or updates -to jht@samba.org. +to John Terpstra. diff --git a/docs/docbook/projdoc/Browsing-Quickguide.sgml b/docs/docbook/projdoc/Browsing-Quickguide.sgml index adf20b7386..a2b67983f8 100644 --- a/docs/docbook/projdoc/Browsing-Quickguide.sgml +++ b/docs/docbook/projdoc/Browsing-Quickguide.sgml @@ -1,8 +1,6 @@ - - John HTerpstra - + &author.jht; July 5, 1998 Updated: March 15, 2003 @@ -17,10 +15,10 @@ of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling except by way of name to address mapping. - -Note: MS Windows 2000 and later can be configured to operate with NO NetBIOS + +MS Windows 2000 and later can be configured to operate with NO NetBIOS over TCP/IP. Samba-3 and later also supports this mode of operation. - + @@ -37,9 +35,11 @@ TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast. Normally, only unicast UDP messaging can be forwarded by routers. The -"remote announce" parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the "remote browse sync" -parameter of smb.conf implements browse list collation using unicast UDP. +remote announce +parameter to smb.conf helps to project browse announcements +to remote network segments via unicast UDP. Similarly, the +remote browse sync parameter of smb.conf +implements browse list collation using unicast UDP. @@ -47,18 +47,19 @@ Secondly, in those networks where Samba is the only SMB server technology wherever possible nmbd should be configured on one (1) machine as the WINS server. This makes it easy to manage the browsing environment. If each network segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the "remote announce" and -the "remote browse sync" parameters to your smb.conf file. +get cross segment browsing to work is by using the +remote announce and the remote browse sync +parameters to your smb.conf file. If only one WINS server is used for an entire multi-segment network then -the use of the "remote announce" and the "remote browse sync" parameters -should NOT be necessary. +the use of the remote announce and the +remote browse sync parameters should NOT be necessary. -As of Samba-3 WINS replication is being worked on. The bulk of the code has +As of Samba 3 WINS replication is being worked on. The bulk of the code has been committed, but it still needs maturation. @@ -66,8 +67,9 @@ been committed, but it still needs maturation. Right now samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS server there must only be one nmbd configured as a WINS server on the network. Some sites have used multiple Samba WINS -servers for redundancy (one server per subnet) and then used "remote browse -sync" and "remote announce" to affect browse list collation across all +servers for redundancy (one server per subnet) and then used +remote browse sync and remote announce +to affect browse list collation across all segments. Note that this means clients will only resolve local names, and must be configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers they can see on other @@ -104,7 +106,8 @@ well as name lookups are done by UDP broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP addresses. In such situations Samba provides a means by which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the "remote announce" parameter). +list of a remote MS Windows network (using the +remote announce parameter). @@ -142,14 +145,14 @@ inability to use the network services. Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the "remote -browse sync" parameter in the smb.conf file. This causes Samba -to contact the local master browser on a remote network and +of browse lists across routed networks using the remote +browse sync parameter in the smb.conf file. +This causes Samba to contact the local master browser on a remote network and to request browse list synchronisation. This effectively bridges two networks that are separated by routers. The two remote networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the "remote -browse sync" parameter provides browse list synchronisation - and +based name resolution, but it should be noted that the remote +browse sync parameter provides browse list synchronisation - and that is distinct from name to address resolution, in other words, for cross subnet browsing to function correctly it is essential that a name to address resolution mechanism be provided. @@ -160,22 +163,24 @@ and so on. -Use of the "Remote Announce" parameter +Use of the <command>Remote Announce</command> parameter -The "remote announce" parameter of smb.conf can be used to forcibly ensure +The remote announce parameter of +smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. -The syntax of the "remote announce" parameter is: +The syntax of the remote announce parameter is: - remote announce = a.b.c.d [e.f.g.h] ... + remote announce = a.b.c.d [e.f.g.h] ... _or_ - remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ... + remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ... where: -a.b.c.d and e.f.g.h +a.b.c.d and +e.f.g.h is either the LMB (Local Master Browser) IP address or the broadcst address of the remote network. ie: the LMB is at 192.168.1.10, or the address @@ -189,7 +194,7 @@ the IP address of the remote LMB. -WORKGROUP +WORKGROUP is optional and can be either our own workgroup or that of the remote network. If you use the workgroup name of the remote network then our @@ -204,23 +209,24 @@ name resolution problems and should be avoided. -Use of the "Remote Browse Sync" parameter +Use of the <command>Remote Browse Sync</command> parameter -The "remote browse sync" parameter of smb.conf is used to announce to +The remote browse sync parameter of +smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on it's network segment. -The syntax of the "remote browse sync" parameter is: +The syntax of the remote browse sync parameter is: -remote browse sync = a.b.c.d +remote browse sync = a.b.c.d -where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment. +where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment. @@ -253,7 +259,8 @@ of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast name resolution can not be used across network segments this type of information can only be provided via WINS _or_ via statically configured -"lmhosts" files that must reside on all clients in the absence of WINS. +lmhosts files that must reside on all clients in the +absence of WINS. @@ -277,8 +284,9 @@ errors. -To configure Samba as a WINS server just add "wins support = yes" to the -smb.conf file [globals] section. +To configure Samba as a WINS server just add +wins support = yes to the smb.conf +file [globals] section. diff --git a/docs/docbook/projdoc/Browsing.sgml b/docs/docbook/projdoc/Browsing.sgml index 60512c3cd1..2de0f446a6 100644 --- a/docs/docbook/projdoc/Browsing.sgml +++ b/docs/docbook/projdoc/Browsing.sgml @@ -6,7 +6,6 @@ - (5 July 1998) @@ -69,15 +68,15 @@ regardless of whether it is NT, Samba or any other type of domain master that is providing this service. - -[Note that nmbd can be configured as a WINS server, but it is not + +Nmbd can be configured as a WINS server, but it is not necessary to specifically use samba as your WINS server. MS Windows NT4, Server or Advanced Server 2000 or 2003 can be configured as your WINS server. In a mixed NT/2000/2003 server and samba environment on a Wide Area Network, it is recommended that you use the Microsoft WINS server capabilities. In a samba-only environment, it is recommended that you use one and only one Samba server as your WINS server. - + To get browsing to work you need to run nmbd as usual, but will need diff --git a/docs/docbook/projdoc/Bugs.sgml b/docs/docbook/projdoc/Bugs.sgml index a9493b07d4..4e4f7b9084 100644 --- a/docs/docbook/projdoc/Bugs.sgml +++ b/docs/docbook/projdoc/Bugs.sgml @@ -1,6 +1,7 @@ + &author.jelmer; Samba Team @@ -15,7 +16,7 @@ Introduction -The email address for bug reports for stable releases is samba@samba.org. +The email address for bug reports for stable releases is samba@samba.org. Bug reports for alpha releases should go to samba-technical@samba.org. @@ -61,7 +62,7 @@ file for correct syntax. -Have you run through the diagnosis? +Have you run through the diagnosis? This is very important. diff --git a/docs/docbook/projdoc/CUPS-printing.sgml b/docs/docbook/projdoc/CUPS-printing.sgml index 65f18dc385..eb59695b04 100644 --- a/docs/docbook/projdoc/CUPS-printing.sgml +++ b/docs/docbook/projdoc/CUPS-printing.sgml @@ -2,15 +2,7 @@ - - John HTerpstra - - Samba Team -
- jht@samba.org -
- - + &author.jht; KurtPfeifle @@ -1310,7 +1302,7 @@ It is *not* working for Win9x/ME clients. But it: - >it guarantees to not write an PJL-header + it guarantees to not write an PJL-header it guarantees to still read and support all PJL-options named in the driver PPD with its own means it guarantees the file going thru the "pstops" filter on the CUPS/Samba server it guarantees to page-count correctly the printfile @@ -1326,29 +1318,30 @@ current with CUPS 1.1.16). These are the items CUPS logs in the "page_log" for every single *page* of a job: - - * Printer name - * User name - * Job ID - * Time of printing - * the page number - * the number of copies - * a billing info string (optional) - + +Printer name +User name +Job ID +Time of printing +the page number +the number of copies +a billing info string (optional) + + Here is an extract of my CUPS server's page_log file to illustrate the format and included items: - + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing - + This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job @@ -1397,7 +1390,7 @@ huge improvements under development: page counting will go into the "backends" (these talk directly to the printer and will increase the count in sync with the - actual printing process -- a jam at the 5th sheet will lead to a stop in the counting) + actual printing process -- a jam at the 5th sheet will lead to a stop in the counting) quotas will be handled more flexibly @@ -1421,13 +1414,13 @@ the files: - + cups-samba.install cups-samba.license cups-samba.readme cups-samba.remove cups-samba.ss - + @@ -1438,26 +1431,24 @@ into /usr/share/cups/drivers/. Its contents are 3 files: - + cupsdrvr.dll cupsui.dll cups.hlp - + - -ATTENTION: due to a bug one CUPS release puts the cups.hlp + +Due to a bug one CUPS release puts the cups.hlp into /usr/share/drivers/ instead of /usr/share/cups/drivers/. To work around this, copy/move the file after running the "./cups-samba.install" script manually to the right place: - - cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ - - - + cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ + + @@ -1485,19 +1476,19 @@ Win NT/2k/XP clients. - NOTE 1: Win 9x/ME clients won't work with this driver. For these you'd + Win 9x/ME clients won't work with this driver. For these you'd still need to use the ADOBE*.* drivers as previously. - NOTE 2: It is not harming if you've still the ADOBE*.* driver files from + It is not harming if you've still the ADOBE*.* driver files from previous installations in the "/usr/share/cups/drivers/" directory. The new cupsaddsmb (from 1.1.16) will automatically use the "newest" installed driver (which here then is the CUPS drivers). - NOTE 3: Should your Win clients have had the old ADOBE*.* files and the + Should your Win clients have had the old ADOBE*.* files and the Adobe PostScript drivers installed, the download and installation of the new CUPS PostScript driver for Windows NT/2k/XP will fail at first. @@ -1685,11 +1676,11 @@ it is most likely the Samba part. For the CUPS part, you may want to consult: - - http://localhost:631/sam.html#PreserveJobFiles and - http://localhost:631/sam.html#PreserveJobHistory and - http://localhost:631/sam.html#MaxJobs - + +http://localhost:631/sam.html#PreserveJobFiles +http://localhost:631/sam.html#PreserveJobHistory +http://localhost:631/sam.html#MaxJobs + There are the settings described for your CUPS daemon, which could lead to completed @@ -1773,10 +1764,10 @@ If you have more problems, post the output of these commands: - + grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;" - + diff --git a/docs/docbook/projdoc/Compiling.sgml b/docs/docbook/projdoc/Compiling.sgml index ac98f34a32..a5ff783244 100644 --- a/docs/docbook/projdoc/Compiling.sgml +++ b/docs/docbook/projdoc/Compiling.sgml @@ -5,6 +5,7 @@ Samba Team + &author.jelmer; (22 May 2001) 18 March 2003 diff --git a/docs/docbook/projdoc/DOMAIN_MEMBER.sgml b/docs/docbook/projdoc/DOMAIN_MEMBER.sgml index 8ac3520384..1a97e6f5a8 100644 --- a/docs/docbook/projdoc/DOMAIN_MEMBER.sgml +++ b/docs/docbook/projdoc/DOMAIN_MEMBER.sgml @@ -1,26 +1,8 @@ - - JeremyAllison - - Samba Team -
- samba@samba.org -
- - - - JerryCarter - - Samba Team -
- jerry@samba.org -
- - - - + &author.jeremy; + &author.jerry; 16 Apr 2001 diff --git a/docs/docbook/projdoc/Diagnosis.sgml b/docs/docbook/projdoc/Diagnosis.sgml index 1e2e6d7598..2a771c23d1 100644 --- a/docs/docbook/projdoc/Diagnosis.sgml +++ b/docs/docbook/projdoc/Diagnosis.sgml @@ -1,19 +1,7 @@ - - AndrewTridgell - - Samba Team -
tridge@samba.org
- - - - JelmerVernooij - - Samba Team -
jelmer@samba.org
- - + &author.tridge; + &author.jelmer; Wed Jan 15 @@ -92,10 +80,11 @@ best way to check this is with "testparm smb.conf" -Tests +The tests + +Diagnosing your samba server - -Test 1 + In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -106,11 +95,9 @@ configuration file is faulty. Note: Your smb.conf file may be located in: /etc/samba Or in: /usr/local/samba/lib - - - -Test 2 + + Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -135,11 +122,9 @@ software. You will need to relax the rules to let in the workstation in question, perhaps by allowing access from another subnet (on Linux this is done via the ipfwadm program.) - - - -Test 3 + + Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back. @@ -218,10 +203,9 @@ network interface IP Address / Broadcast Address / Subnet Mask settings are correct and that Samba has correctly noted these in the log.nmb file. - + - -Test 4 + Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the @@ -241,10 +225,9 @@ one-line script that contains the right parameters and run that from inetd. - + - -Test 5 + run the command nmblookup -B ACLIENT '*' @@ -259,10 +242,9 @@ If ACLIENT doesn't resolve via DNS then use the IP address of the client in the above test. - + - -Test 6 + Run the command nmblookup -d 2 '*' @@ -296,10 +278,9 @@ This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to TEST 3 notes above). - + - -Test 7 + Run the command smbclient //BIGSERVER/TMP. You should @@ -369,10 +350,9 @@ especially check that the amount of free disk space shown is correct when you type dir. - + - -Test 8 + On the PC type the command net view \\BIGSERVER. You will @@ -429,10 +409,9 @@ Check to see if the host is running tcp wrappers, and if so add an entry in the hosts.allow file for your client (or subnet, etc.) - + - -Test 9 + Run the command net use x: \\BIGSERVER\TMP. You should @@ -456,10 +435,9 @@ and you have encrypt passwords = no in smb.conf - + - -Test 10 + Run the command nmblookup -M TESTGROUP where @@ -476,10 +454,9 @@ sure you have preferred master = yes to ensure that an election is held at startup. - + - -Test 11 + From file manager try to browse the server. Your samba server should @@ -495,7 +472,8 @@ smb.conf file, or enable encrypted passwords AFTER compiling in support for encrypted passwords (refer to the Makefile). - + + @@ -507,7 +485,7 @@ sniff the problem. The official samba mailing list can be reached at samba@samba.org. To find out more about samba and how to subscribe to the mailing list check out the samba web page at -http://samba.org/samba +http://samba.org/samba/ diff --git a/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml b/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml index a2d16541ef..8aea87fe24 100644 --- a/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml +++ b/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml @@ -57,7 +57,7 @@ domadm:x:502:joe,john,mary Map this domadm group to the domain admins group by running the command: -smbgroupedit -c "Domain Admins" -u domadm +smbgroupedit -c "Domain Admins" -u domadm @@ -74,6 +74,6 @@ your samba PDC. Flag that group as a domain group by running: smbgroupedit -a unixgroup -td You can list the various groups in the mapping database like this -smbgroupedit -v +smbgroupedit -v diff --git a/docs/docbook/projdoc/Integrating-with-Windows.sgml b/docs/docbook/projdoc/Integrating-with-Windows.sgml index 8a5c0c40f2..b48fc3b305 100644 --- a/docs/docbook/projdoc/Integrating-with-Windows.sgml +++ b/docs/docbook/projdoc/Integrating-with-Windows.sgml @@ -1,18 +1,7 @@ - - - JohnTerpstra - - Samba Team -
- jht@samba.org -
- - - - + &author.jht; (Jan 01 2001) diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml index 1a4499038d..253de8aea0 100644 --- a/docs/docbook/projdoc/NT4Migration.sgml +++ b/docs/docbook/projdoc/NT4Migration.sgml @@ -1,8 +1,6 @@ - - John HTerpstra - + &author.jht; April 3, 2003 diff --git a/docs/docbook/projdoc/NT_Security.sgml b/docs/docbook/projdoc/NT_Security.sgml index c5e3b9b9f9..65072ef4ff 100644 --- a/docs/docbook/projdoc/NT_Security.sgml +++ b/docs/docbook/projdoc/NT_Security.sgml @@ -1,14 +1,6 @@ - - JeremyAllison - - Samba Team -
- samba@samba.org -
- - + &author.jeremy; 12 Apr 1999 diff --git a/docs/docbook/projdoc/Other-Clients.sgml b/docs/docbook/projdoc/Other-Clients.sgml index e4d7e34185..6177b4dcb6 100644 --- a/docs/docbook/projdoc/Other-Clients.sgml +++ b/docs/docbook/projdoc/Other-Clients.sgml @@ -1,16 +1,7 @@ - - JimMcDonough - - IBM - - JelmerVernooij - - Samba Team -
jelmer@samba.org
- - + &author.jmcd; + &author.jelmer; 5 Mar 2001 @@ -334,8 +325,8 @@ for the profile. This default ACL includes DOMAIN\user "Full Control" -NOTE : This bug does not occur when using winbind to -create accounts on the Samba host for Domain users. +This bug does not occur when using winbind to +create accounts on the Samba host for Domain users. diff --git a/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml b/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml index f2a6fc06ac..e13a81eac5 100644 --- a/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml +++ b/docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml @@ -1,15 +1,7 @@ - - JohnTerpstra - - Samba Team -
- jht@samba.org -
- - - (Jun 21 2001) + &author.jht; + (Jun 21 2001) PAM Configuration for Centrally Managed Authentication @@ -80,8 +72,8 @@ PAM allows use of replacable modules. Those available on a sample system include: - - $ /bin/ls /lib/security +$/bin/ls /lib/security + pam_access.so pam_ftp.so pam_limits.so pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so pam_cracklib.so pam_group.so pam_listfile.so diff --git a/docs/docbook/projdoc/PolicyMgmt.sgml b/docs/docbook/projdoc/PolicyMgmt.sgml index 1dc4dd435d..9dee288b1f 100644 --- a/docs/docbook/projdoc/PolicyMgmt.sgml +++ b/docs/docbook/projdoc/PolicyMgmt.sgml @@ -1,15 +1,7 @@ - - John HTerpstra - - Samba Team -
- jht@samba.org -
- - - April 3 2003 + &author.jht; + April 3 2003 System and Account Policies @@ -203,40 +195,33 @@ exists with NT4 style policy files. Administration of Win2K / XP Policies + +Instructions Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console -(MMC) snap-in as follows: - +(MMC) snap-in as follows: - - - - Go to the Windows 200x / XP menu Start->Programs->Administrative Tools + + +Go to the Windows 200x / XP menu Start->Programs->Administrative Tools and select the MMC snap-in called "Active Directory Users and Computers" - - - - - - Select the domain or organizational unit (OU) that you wish to manage, then right click - to open the context menu for that object, select the properties item. - - - - - - Now left click on the Group Policy tab, then left click on the New tab. Type a name - for the new policy you will create. - - - - - - Now left click on the Edit tab to commence the steps needed to create the GPO. - - - + + + +Select the domain or organizational unit (OU) that you wish to manage, then right click +to open the context menu for that object, select the properties item. + + + +Now left click on the Group Policy tab, then left click on the New tab. Type a name +for the new policy you will create. + + + +Now left click on the Edit tab to commence the steps needed to create the GPO. + + All policy configuration options are controlled through the use of policy administrative diff --git a/docs/docbook/projdoc/Portability.sgml b/docs/docbook/projdoc/Portability.sgml index dae267e8b5..61a694e130 100644 --- a/docs/docbook/projdoc/Portability.sgml +++ b/docs/docbook/projdoc/Portability.sgml @@ -1,8 +1,6 @@ - - JelmerVernooij - + &author.jelmer; Portability diff --git a/docs/docbook/projdoc/ProfileMgmt.sgml b/docs/docbook/projdoc/ProfileMgmt.sgml index 72eac8635a..8eded5e9fb 100644 --- a/docs/docbook/projdoc/ProfileMgmt.sgml +++ b/docs/docbook/projdoc/ProfileMgmt.sgml @@ -1,15 +1,7 @@ - - John HTerpstra - - Samba Team -
- jht@samba.org -
- - - April 3 2003 + &author.jht; + April 3 2003 Desktop Profile Management @@ -420,7 +412,7 @@ nominated. Done. You now have a profile that can be editted using the samba-3.0.0 -profiles tool. +profiles tool. @@ -627,9 +619,29 @@ subkey, you will see a string value named ProfileImagePath. Mandatory profiles -The above method can be used to create mandatory profiles also. To convert -a group profile into a mandatory profile simply locate the NTUser.DAT file -in the copied profile and rename it to NTUser.MAN. +A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. +During the user's session it may be possible to change the desktop environment, but +as the user logs out all changes made will be lost. If it is desired to NOT allow the +user any ability to change the desktop environment then this must be done through +policy settings. See previous chapter. + + + + +Under NO circumstances should the profile directory (or it's contents) be made read-only +as this may render the profile un-usable. + + + + +For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles +also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT +file in the copied profile and rename it to NTUser.MAN. + + + +For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to +affect a mandatory profile. @@ -638,7 +650,229 @@ in the copied profile and rename it to NTUser.MAN. Creating/Managing Group Profiles -Blah goes here. +Most organisations are arranged into departments. There is a nice benenfit in +this fact since usually most users in a department will require the same desktop +applications and the same desktop layout. MS Windows NT4/200x/XP will allow the +use of Group Profiles. A Group Profile is a profile that is created firstly using +a template (example) user. Then using the profile migration tool (see above) the +profile is assigned access rights for the user group that needs to be given access +to the group profile. + + + +The next step is rather important. PLEASE NOTE: Instead of assigning a group profile +to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned +the now modified profile. + + + + Be careful with group profiles, if the user who is a member of a group also + has a personal profile, then the result will be a fusion (merge) of the two. + + + + + +Default Profile for Windows Users + + +MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom +a profile does not already exist. Armed with a knowledge of where the default profile +is located on the Windows workstation, and knowing which registry keys affect the path +from which the default profile is created, it is possible to modify the default profile +to one that has been optimised for the site. This has significant administrative +advantages. + + + +MS Windows 9x/Me + + +To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System +Policy Editor or change the registry directly. + + + +To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then +select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, +select User Profiles, click on the enable box. Do not forget to save the registry changes. + + + +To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive +HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name +"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. + + + + + +MS Windows NT4 Workstation + + +Document NT4 default profile handling stuff here! Someone - please contribute appropriate +material here. Email your contribution to jht@samba.org. + + + + + +MS Windows 200x/XP + + + + MS Windows XP Home Edition does use default per user profiles, but can not participate + in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile + only from itself. While there are benefits in doing this the beauty of those MS Windows + clients that CAN participate in domain logon processes allows the administrator to create + a global default profile and to enforce it through the use of Group Policy Objects (GPOs). + + + + +When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from +C:\Documents and Settings\Default User. The administrator can modify (or change +the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum +arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client +workstation. + + + +When MS Windows 200x/XP participate in a domain security context, and if the default user +profile is not found, then the client will search for a default profile in the NETLOGON share +of the authenticating server. ie: In MS Windows parlance: +%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this +to the workstation to the C:\Documents and Settings\ under the Windows +login name of the user. + + + + + This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory + should be created at the root of this share and msut be called Default Profile. + + + + +If a default profile does not exist in this location then MS Windows 200x/XP will use the local +default profile. + + + +On loging out, the users' desktop profile will be stored to the location specified in the registry +settings that pertain to the user. If no specific policies have been created, or passed to the client +during the login process (as Samba does automatically), then the user's profile will be written to +the local machine only under the path C:\Documents and Settings\%USERNAME%. + + + +Those wishing to modify the default behaviour can do so through up to three methods: + + + + + + Modify the registry keys on the local machine manually and place the new default profile in the + NETLOGON share root - NOT recommended as it is maintenance intensive. + + + + + + Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file + in the root of the NETLOGON share along with the new default profile. + + + + + + Create a GPO that enforces this through Active Directory, and place the new default profile + in the NETLOGON share. + + + + + +The Registry Hive key that affects the behaviour of folders that are part of the default user profile +are controlled by entries on Windows 200x/XP is: + + + + + HKEY_CURRENT_USER + \Software + \Microsoft + \Windows NT + \CurrentVersion + \Explorer + \User Shell Folders\ + + + + +The above hive key contains a list of automatically managed folders. The default entries are: + + + + + Name Default Value + -------------- ----------------------------------------- + AppData %USERPROFILE%\Application Data + Cache %USERPROFILE%\Local Settings\Temporary Internet Files + Cookies %USERPROFILE%\Cookies + Desktop %USERPROFILE%\Desktop + Favorites %USERPROFILE%\Favorites + History %USERPROFILE%\Local Settings\History + Local AppData %USERPROFILE%\Local Settings\Application Data + Local Settings %USERPROFILE%\Local Settings + My Pictures %USERPROFILE%\My Documents\My Pictures + NetHood %USERPROFILE%\NetHood + Personal %USERPROFILE%\My Documents + PrintHood %USERPROFILE%\PrintHood + Programs %USERPROFILE%\Start Menu\Programs + Recent %USERPROFILE%\Recent + SendTo %USERPROFILE%\SendTo + Start Menu %USERPROFILE%\Start Menu + Startup %USERPROFILE%\Start Menu\Programs\Startup + Templates %USERPROFILE%\Templates + + + + +There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all +the others are of type REG_EXPAND_SZ. + + + +It makes a huge difference to the speed of handling roaming user profiles if all the folders are +stored on a dedicated location on a network server. This means that it will NOT be necessary to +write Outlook PST file over the network for every login and logout. + + + +To set this to a network location you could use the followin examples: + + %LOGONSERVER%\%USERNAME%\Default Folders + +This would store the folders in the user's home directory under a directory called "Default Folders" + +You could also use: + + \\SambaServer\FolderShare\%USERNAME% + +in which case the default folders will be stored in the server named SambaServer +in the share called FolderShare under a directory that has the name of the MS Windows +user as seen by the Linux/Unix file system. + + + +Please note that once you have created a default profile share, you MUST migrate a user's profile +(default or custom) to it. + + + + diff --git a/docs/docbook/projdoc/SWAT.sgml b/docs/docbook/projdoc/SWAT.sgml index 9df94b9aee..7326a49874 100644 --- a/docs/docbook/projdoc/SWAT.sgml +++ b/docs/docbook/projdoc/SWAT.sgml @@ -1,8 +1,6 @@ - - John HTerpstra - + &author.jht; April 3, 2003 diff --git a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml index 46e69e4ba9..8dbc007e4f 100644 --- a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml @@ -1,14 +1,7 @@ - - - VolkerLendecke - - Samba Team -
Volker.Lendecke@SerNet.DE
- - + &author.vl; (26 Apr 2001) diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml index 7aabca948f..451ab02762 100644 --- a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml @@ -2,23 +2,14 @@ + &author.jerry; + &author.jht; - Gerald (Jerry)Carter - - VA Linux Systems/Samba Team -
jerry@samba.org
- DavidBannon Samba Team
dbannon@samba.org
 - John HTerpstra - - Samba Team -
jht@samba.org
- - (26 Apr 2001) @@ -243,7 +234,7 @@ There are a couple of points to emphasize in the above configuration. Encrypted passwords must be enabled. For more details on how - to do this, refer to ENCRYPTION.html. + to do this, refer to ENCRYPTION.html. diff --git a/docs/docbook/projdoc/ServerType.sgml b/docs/docbook/projdoc/ServerType.sgml index 239880160e..7df1eb03fc 100644 --- a/docs/docbook/projdoc/ServerType.sgml +++ b/docs/docbook/projdoc/ServerType.sgml @@ -1,12 +1,6 @@ - - John HTerpstra - - Samba Team -
jht@samba.org
- - + &author.jht; Nomenclature of Server Types diff --git a/docs/docbook/projdoc/Speed.sgml b/docs/docbook/projdoc/Speed.sgml index 55d8b9492b..78b5935a9c 100644 --- a/docs/docbook/projdoc/Speed.sgml +++ b/docs/docbook/projdoc/Speed.sgml @@ -1,12 +1,6 @@ - - - Samba Team -
samba@samba.org
- - PaulCochrane @@ -14,6 +8,7 @@
paulc@dth.scot.nhs.uk
 + &author.jelmer; Samba performance issues diff --git a/docs/docbook/projdoc/UNIX_INSTALL.sgml b/docs/docbook/projdoc/UNIX_INSTALL.sgml index 5d0d388c08..df038510af 100644 --- a/docs/docbook/projdoc/UNIX_INSTALL.sgml +++ b/docs/docbook/projdoc/UNIX_INSTALL.sgml @@ -1,4 +1,11 @@ + + &author.tridge; + &author.jelmer; + KarlAuer + + + How to Install and Test SAMBA diff --git a/docs/docbook/projdoc/VFS.sgml b/docs/docbook/projdoc/VFS.sgml index 7aa280f4ef..0a88543c6e 100644 --- a/docs/docbook/projdoc/VFS.sgml +++ b/docs/docbook/projdoc/VFS.sgml @@ -1,10 +1,10 @@ - JelmerVernooij + &author.jelmer; + &author.jht; AlexanderBokovoy TimPotter SimoSorce - John HTerpstra Stackable VFS modules diff --git a/docs/docbook/projdoc/passdb.sgml b/docs/docbook/projdoc/passdb.sgml index 7e4b9bcbd0..362cf97064 100644 --- a/docs/docbook/projdoc/passdb.sgml +++ b/docs/docbook/projdoc/passdb.sgml @@ -1,19 +1,9 @@ - - JelmerVernooij - - The Samba Team -
jelmer@samba.org
- - - - Gerald (Jerry)Carter - - Samba Team -
jerry@samba.org
- - + &author.jelmer; + &author.jerry; + &author.jeremy; + &author.jht; Olivier (lem)Lemaire @@ -21,24 +11,6 @@
olem@IDEALX.org
 - - JeremyAllison - - Samba Team -
- jra@samba.org -
- - - - John HTerpstra - - Samba Team -
- jht@samba.org -
- - February 2003 @@ -137,13 +109,9 @@ Windows NT 3.5x - Windows NT 4.0 - Windows 2000 Professional - Windows 200x Server/Advanced Server - Windows XP Professional @@ -393,6 +361,8 @@ the details of configuring these packages are beyond the scope of this document. Supported LDAP Servers + + The LDAP samdb code in 2.2.3 (and later) has been developed and tested using the OpenLDAP 2.0 server and client libraries. @@ -400,8 +370,8 @@ The same code should be able to work with Netscape's Directory Server and client SDK. However, due to lack of testing so far, there are bound to be compile errors and bugs. These should not be hard to fix. If you are so inclined, please be sure to forward all patches to -samba-patches@samba.org and -jerry@samba.org. +samba-patches@samba.org and +jerry@samba.org. @@ -430,7 +400,7 @@ The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are owned by the Samba Team and as such is legal to be openly published. If you translate the schema to be used with Netscape DS, please submit the modified schema file as a patch to jerry@samba.org +url="mailto:jerry@samba.org">jerry@samba.org @@ -470,7 +440,7 @@ server, first copy the samba.schema file to slapd's configuration directory. -root# cp samba.schema /etc/openldap/schema/ +root# cp samba.schema /etc/openldap/schema/ @@ -525,7 +495,6 @@ index rid eq Configuring Samba - The following parameters are available in smb.conf only with --with-ldapsam @@ -972,14 +941,14 @@ Or, set 'identifier:workstations column' to : The usage of pdb_xml is pretty straightforward. To export data, use: -pdbedit -e xml:filename +pdbedit -e xml:filename (where filename is the name of the file to put the data in) To import data, use: -pdbedit -i xml:filename -e current-pdb +pdbedit -i xml:filename -e current-pdb Where filename is the name to read the data from and current-pdb to put it in. diff --git a/docs/docbook/projdoc/printer_driver2.sgml b/docs/docbook/projdoc/printer_driver2.sgml index 8d15e437b2..da3eb838f2 100644 --- a/docs/docbook/projdoc/printer_driver2.sgml +++ b/docs/docbook/projdoc/printer_driver2.sgml @@ -1,16 +1,7 @@ - - - Gerald (Jerry)Carter - - Samba Team -
- jerry@samba.org -
- - + &author.jerry; PatrickPowell @@ -183,14 +174,14 @@ Samba follows this model as well. Next create the directory tree below the [print$] share for each architecture you wish to support. - + [print$]----- |-W32X86 ; "Windows NT x86" |-WIN40 ; "Windows 95/98" |-W32ALPHA ; "Windows NT Alpha_AXP" |-W32MIPS ; "Windows NT R4000" |-W32PPC ; "Windows NT PowerPC" - + ATTENTION! REQUIRED PERMISSIONS @@ -302,8 +293,9 @@ setdriver command can be used to set the driver associated with an installed driver. The following is example of how this could be accomplished: - -$ rpcclient pogo -U root%secret -c "enumdrivers" + +$ rpcclient pogo -U root%secret -c "enumdrivers" + Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] [Windows NT x86] @@ -315,16 +307,18 @@ Printer Driver Info 1: Printer Driver Info 1: Driver Name: [HP LaserJet 4Si/4SiMX PS] - -$ rpcclient pogo -U root%secret -c "enumprinters" + +$ 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:[] -$ rpcclient pogo -U root%secret \ -> -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" + +$ rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" + Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] Successfully set hp-print to driver HP LaserJet 4000 Series PS. diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index 7a8c4b6d06..9c3861b8c3 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -1,4 +1,5 @@ %globalentities; @@ -34,23 +35,20 @@ ]> - SAMBA Project Documentation - SAMBA Team + SAMBA Team +
samba@samba.org
 -
samba@samba.org
- - - -Abstract + &person.jht; + &person.jelmer; + &person.jerry; - -Last Update : Wed Jan 15 - + Friday 4 April + This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job @@ -61,18 +59,17 @@ url="mailto:jerry@samba.org">jerry@samba.org or jelmer@samba.org. + + This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt + + - -Cheers, jerry - - - @@ -140,5 +137,3 @@ part each cover one specific feature. &BUGS; &Diagnosis; - - diff --git a/docs/docbook/projdoc/securing-samba.sgml b/docs/docbook/projdoc/securing-samba.sgml index bfedc5456f..03d0c3d9e7 100644 --- a/docs/docbook/projdoc/securing-samba.sgml +++ b/docs/docbook/projdoc/securing-samba.sgml @@ -1,10 +1,7 @@ - - AndrewTridgell - Samba Team - + &author.tridge; 17 March 2003 diff --git a/docs/docbook/projdoc/security_level.sgml b/docs/docbook/projdoc/security_level.sgml index e3d7c6ac1f..1c4c3f61ca 100644 --- a/docs/docbook/projdoc/security_level.sgml +++ b/docs/docbook/projdoc/security_level.sgml @@ -1,12 +1,7 @@ - - AndrewTridgell - - Samba Team -
samba@samba.org
- - + &author.tridge; + &author.jelmer; Samba as Stand-Alone Server - - JelmerVernooij - - Samba Team -
jelmer@samba.org
- - + &author.jelmer; 25 March 2003 diff --git a/docs/docbook/projdoc/upgrading-to-3.0.sgml b/docs/docbook/projdoc/upgrading-to-3.0.sgml index cd0ec2064d..ec4b29386a 100644 --- a/docs/docbook/projdoc/upgrading-to-3.0.sgml +++ b/docs/docbook/projdoc/upgrading-to-3.0.sgml @@ -1,9 +1,6 @@ - - JelmerVernooij - Samba Team - + &author.jelmer; 25 October 2002 @@ -12,7 +9,11 @@ Charsets -FIXME +You might experience problems with special characters +when communicating with old DOS clients. Codepage +support has changed in samba 3.0. Read the chapter +Unicode support for details. + diff --git a/docs/docbook/projdoc/winbind.sgml b/docs/docbook/projdoc/winbind.sgml index 2d38ea44d4..460038aea9 100644 --- a/docs/docbook/projdoc/winbind.sgml +++ b/docs/docbook/projdoc/winbind.sgml @@ -1,6 +1,5 @@ - @@ -10,32 +9,15 @@
tpot@linuxcare.com.au
 - - AndrewTridgell - - Samba Team -
tridge@linuxcare.com.au
- - - - JohnTrostel - - Snapserver -
jtrostel@snapserver.com
- - + &author.tridge; + &author.jht; NaagMummaneni
getnag@rediffmail.com
 - - JelmerVernooij - -
jelmer@nl.linux.org
- - + &author.jelmer; 27 June 2002 -- cgit