From 56c5bc58c8478f7ac2859f8fc87cabd1f1586465 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 12:12:39 +0000 Subject: Put in documentation update by jht (This used to be commit 38424c522ab2ddbf6d6c61274d692b14e574023a) --- docs/docbook/projdoc/Browsing-Quickguide.sgml | 64 +++++++++++++++++-------- docs/docbook/projdoc/Browsing.sgml | 68 ++++++++++++++++----------- docs/docbook/projdoc/GroupProfiles.sgml | 16 ++++--- 3 files changed, 94 insertions(+), 54 deletions(-) (limited to 'docs/docbook/projdoc') diff --git a/docs/docbook/projdoc/Browsing-Quickguide.sgml b/docs/docbook/projdoc/Browsing-Quickguide.sgml index 8e3fbce6d3..0a5cf72038 100644 --- a/docs/docbook/projdoc/Browsing-Quickguide.sgml +++ b/docs/docbook/projdoc/Browsing-Quickguide.sgml @@ -1,9 +1,10 @@ - JohnTerpstra + John HTerpstra July 5, 1998 + Updated: March 15, 2003 Quick Cross Subnet Browsing / Cross Workgroup Browsing guide @@ -16,16 +17,22 @@ 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 +over TCP/IP. Samba-3 and later also supports this mode of operation. + + + Discussion Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging is implemented using NetBIOS. Samba -implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can -do likewise. NetBIOS based networking uses broadcast messaging to affect -browse list management. When running NetBIOS over TCP/IP this uses UDP -based messaging. UDP messages can be broadcast or unicast. +Block) based messaging. SMB messaging may be implemented using NetBIOS or +without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. +MS Windows products can do likewise. NetBIOS based networking uses broadcast +messaging to affect browse list management. When running NetBIOS over +TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast. @@ -45,20 +52,27 @@ the "remote browse sync" parameters to your smb.conf file. -If only one WINS server is used then the use of the "remote announce" and the -"remote browse sync" parameters should NOT be necessary. +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. -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 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 subnets. This setup is not recommended, but is -mentioned as a practical consideration (ie: an 'if all else fails' scenario). +As of Samba-3 WINS replication is being worked on. The bulk of the code has +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 +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 +subnets. This setup is not recommended, but is mentioned as a practical +consideration (ie: an 'if all else fails' scenario). @@ -198,8 +212,9 @@ To configure Samba to register with a WINS server just add -DO NOT EVER use both "wins support = yes" together with "wins server = a.b.c.d" -particularly not using it's own IP address. +DO NOT EVER use both "wins support = yes" together +with "wins server = a.b.c.d" particularly not using it's own IP address. +Specifying both will cause nmbd to refuse to start! @@ -213,7 +228,7 @@ one protocol on an MS Windows machine. -Every NetBIOS machine take part in a process of electing the LMB (and DMB) +Every NetBIOS machine takes part in a process of electing the LMB (and DMB) every 15 minutes. A set of election criteria is used to determine the order of precidence for winning this election process. A machine running Samba or Windows NT will be biased so that the most suitable machine will predictably @@ -232,6 +247,15 @@ as an LMB and thus browse list operation on all TCP/IP only machines will fail. + +Windows 95, 98, 98se, Me are referred to generically as Windows 9x. +The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly +referred to as the WinNT family, but it should be recognised that 2000 and +XP/2003 introduce new protocol extensions that cause them to behave +differently from MS Windows NT4. Generally, where a server does NOT support +the newer or extended protocol, these will fall back to the NT4 protocols. + + The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! diff --git a/docs/docbook/projdoc/Browsing.sgml b/docs/docbook/projdoc/Browsing.sgml index 13d6fce917..aeb3b477c5 100644 --- a/docs/docbook/projdoc/Browsing.sgml +++ b/docs/docbook/projdoc/Browsing.sgml @@ -27,8 +27,15 @@ document. -Browsing will NOT work if name resolution from NetBIOS names to IP -addresses does not function correctly. Use of a WINS server is highly +MS Windows 2000 and later, as with Samba-3 and later, can be +configured to not use NetBIOS over TCP/IP. When configured this way +it is imperative that name resolution (using DNS/LDAP/ADS) be correctly +configured and operative. Browsing will NOT work if name resolution +from SMB machine names to IP addresses does not function correctly. + + + +Where NetBIOS over TCP/IP is enabled use of a WINS server is highly recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. WINS allows remote segment clients to obtain NetBIOS name_type information that can NOT be provided by any other means of name resolution. @@ -40,14 +47,10 @@ that can NOT be provided by any other means of name resolution. Browsing support in samba -Samba now fully supports browsing. The browsing is supported by nmbd +Samba facilitates browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file (see smb.conf(5)). - - - Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available. See -DOMAIN.txt for more information on domain logons. +for samba to support domain logons and scripts is now available. @@ -68,12 +71,12 @@ that is providing this service. [Note that nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. NTAS can -be configured as your WINS server. In a mixed NT server and -samba environment on a Wide Area Network, it is recommended that -you use the NT server's WINS server capabilities. In a samba-only -environment, it is recommended that you use one and only one nmbd -as your WINS server]. +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. @@ -113,6 +116,15 @@ connection that lists the shares is done as guest, and thus you must have a valid guest account. + +MS Windows 2000 and upwards (as with Samba) can be configured to disallow +anonymous (ie: Guest account) access to the IPC$ share. In that case, the +MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the +name of the currently logged in user to query the IPC$ share. MS Windows +9X clients are not able to do this and thus will NOT be able to browse +server resources. + + Also, a lot of people are getting bitten by the problem of too many parameters on the command line of nmbd in inetd.conf. This trick is to @@ -132,7 +144,7 @@ in smb.conf) Browsing across subnets -With the release of Samba 1.9.17(alpha1 and above) Samba has been +Since the release of Samba 1.9.17(alpha1) Samba has been updated to enable it to support the replication of browse lists across subnet boundaries. New code and options have been added to achieve this. This section describes how to set this feature up @@ -167,8 +179,7 @@ settings) for Samba this is in the smb.conf file. Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. -However, with the 1.9.17 release, Samba is capable of cross subnet -browsing when configured correctly. +Samba is capable of cross subnet browsing when configured correctly. @@ -419,9 +430,9 @@ in the [globals] section add the line -Versions of Samba previous to 1.9.17 had this parameter default to +Versions of Samba prior to 1.9.17 had this parameter default to yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to 1.9.17 or above, or at the very +strongly suggested you upgrade to a recent version, or at the very least set the parameter to 'no' on all these machines. @@ -473,7 +484,7 @@ machine or its IP address. Note that this line MUST NOT BE SET in the smb.conf file of the Samba server acting as the WINS server itself. If you set both the "wins support = yes" option and the -"wins server = >name<" option then +"wins server = <name>" option then nmbd will fail to start. @@ -538,11 +549,12 @@ server, if you require. Next, you should ensure that each of the subnets contains a machine that can act as a local master browser for the -workgroup. Any NT machine should be able to do this, as will -Windows 95 machines (although these tend to get rebooted more -often, so it's not such a good idea to use these). To make a -Samba server a local master browser set the following -options in the [global] section of the smb.conf file : +workgroup. Any MS Windows NT/2K/XP/2003 machine should be +able to do this, as will Windows 9x machines (although these +tend to get rebooted more often, so it's not such a good idea +to use these). To make a Samba server a local master browser +set the following options in the [global] section of the +smb.conf file : @@ -594,7 +606,7 @@ you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a Domain name is also the Domain master browser for that name, and many things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC. +browser NetBIOS name (DOMAIN<1B>) with WINS instead of the PDC. @@ -661,8 +673,8 @@ samba systems!) -A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A -NTAS domain controller uses level 32. +A "os level" of 2 would make it beat WfWg and Win95, but not MS Windows +NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32. The maximum os level is 255 diff --git a/docs/docbook/projdoc/GroupProfiles.sgml b/docs/docbook/projdoc/GroupProfiles.sgml index e5120aed9b..8bdf98059a 100644 --- a/docs/docbook/projdoc/GroupProfiles.sgml +++ b/docs/docbook/projdoc/GroupProfiles.sgml @@ -14,7 +14,7 @@ -Creating Group Profiles +Creating Group Prolicy Files Windows '9x @@ -34,7 +34,7 @@ stuff. You then save these settings in a file called Config.POL that needs to be placed in the root of the [NETLOGON] share. If your Win98 is configured to log onto the Samba Domain, it will automatically read this file and update the -Win98 registry of the machine that is logging on. +Win9x/Me registry of the machine that is logging on. @@ -42,19 +42,23 @@ All of this is covered in the Win98 Resource Kit documentation. -If you do not do it this way, then every so often Win98 will check the +If you do not do it this way, then every so often Win9x/Me will check the integrity of the registry and will restore it's settings from the back-up -copy of the registry it stores on each Win98 machine. Hence, you will notice -things changing back to the original settings. +copy of the registry it stores on each Win9x/Me machine. Hence, you will +occasionally notice things changing back to the original settings. + +The following all refers to Windows NT/200x profile migration - not to policies. +We need a separate section on policies (NTConfig.Pol) for NT4/200x. + Windows NT 4 -Unfortunately, the Resource Kit info is Win NT4/2K version specific. +Unfortunately, the Resource Kit info is Win NT4 or 200x specific. -- cgit From a92806b651e49c33bafe3242c643c9395632c76a Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 15:49:05 +0000 Subject: - Move instructions on compiling samba to appendix - Add notes about binary packages - Some small fixes (typos, remove outdated stuff) (This used to be commit 7759686230e2512e7c79ca512f501f8bac084aef) --- docs/docbook/projdoc/CVS-Access.sgml | 157 ---------------- docs/docbook/projdoc/Compiling.sgml | 321 +++++++++++++++++++++++++++++++++ docs/docbook/projdoc/UNIX_INSTALL.sgml | 179 +----------------- docs/docbook/projdoc/samba-doc.sgml | 4 +- 4 files changed, 333 insertions(+), 328 deletions(-) delete mode 100644 docs/docbook/projdoc/CVS-Access.sgml create mode 100644 docs/docbook/projdoc/Compiling.sgml (limited to 'docs/docbook/projdoc') diff --git a/docs/docbook/projdoc/CVS-Access.sgml b/docs/docbook/projdoc/CVS-Access.sgml deleted file mode 100644 index 3c1adfd17a..0000000000 --- a/docs/docbook/projdoc/CVS-Access.sgml +++ /dev/null @@ -1,157 +0,0 @@ - - - - - - - Samba Team - - - - - (22 May 2001) - - -Access Samba source code via CVS - - -Introduction - - -Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can -be accessed via anonymous CVS using the instructions -detailed in this chapter. - - - -This document is a modified version of the instructions found at -http://samba.org/samba/cvs.html - - - - - - -CVS Access to samba.org - - -The machine samba.org runs a publicly accessible CVS -repository for access to the source code of several packages, -including samba, rsync and jitterbug. There are two main ways of -accessing the CVS server on this host. - - - -Access via CVSweb - - -You can access the source code via your -favourite WWW browser. This allows you to access the contents of -individual files in the repository and also to look at the revision -history and commit logs of individual files. You can also ask for a diff -listing between any two versions on the repository. - - - -Use the URL : http://samba.org/cgi-bin/cvsweb - - - - -Access via cvs - - -You can also access the source code via a -normal cvs client. This gives you much more control over you can -do with the repository and allows you to checkout whole source trees -and keep them up to date via normal cvs commands. This is the -preferred method of access if you are a developer and not -just a casual browser. - - - -To download the latest cvs source code, point your -browser at the URL : http://www.cyclic.com/. -and click on the 'How to get cvs' link. CVS is free software under -the GNU GPL (as is Samba). Note that there are several graphical CVS clients -which provide a graphical interface to the sometimes mundane CVS commands. -Links to theses clients are also available from http://www.cyclic.com. - - - -To gain access via anonymous cvs use the following steps. -For this example it is assumed that you want a copy of the -samba source code. For the other source code repositories -on this system just substitute the correct package name - - - - - - Install a recent copy of cvs. All you really need is a - copy of the cvs client binary. - - - - - - - Run the command - - - - cvs -d :pserver:cvs@samba.org:/cvsroot login - - - - When it asks you for a password type cvs. - - - - - - - Run the command - - - - cvs -d :pserver:cvs@samba.org:/cvsroot co samba - - - - This will create a directory called samba containing the - latest samba source code (i.e. the HEAD tagged cvs branch). This - currently corresponds to the 3.0 development tree. - - - - CVS branches other HEAD can be obtained by using the -r - and defining a tag name. A list of branch tag names can be found on the - "Development" page of the samba web site. A common request is to obtain the - latest 2.2 release code. This could be done by using the following command. - - - - cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba - - - - - - Whenever you want to merge in the latest code changes use - the following command from within the samba directory: - - - - cvs update -d -P - - - - - - - - diff --git a/docs/docbook/projdoc/Compiling.sgml b/docs/docbook/projdoc/Compiling.sgml new file mode 100644 index 0000000000..49aafebec0 --- /dev/null +++ b/docs/docbook/projdoc/Compiling.sgml @@ -0,0 +1,321 @@ + + + + + Samba Team + + + + (22 May 2001) + 18 March 2003 + + +How to compile SAMBA + +You can obtain the samba source from the samba website. To obtain a development version, +you can download samba from CVS or using rsync. + + +Access Samba source code via CVS + + +Introduction + + +Samba is developed in an open environment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymous CVS using the instructions +detailed in this chapter. + + + +This chapter is a modified version of the instructions found at +http://samba.org/samba/cvs.html + + + + + +CVS Access to samba.org + + +The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host. + + + +Access via CVSweb + + +You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository. + + + +Use the URL : http://samba.org/cgi-bin/cvsweb + + + + +Access via cvs + + +You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them up to date via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser. + + + +To download the latest cvs source code, point your +browser at the URL : http://www.cyclic.com/. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com. + + + +To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name + + + + + + Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + + + + + + + Run the command + + + + cvs -d :pserver:cvs@samba.org:/cvsroot login + + + + When it asks you for a password type cvs. + + + + + + + Run the command + + + + cvs -d :pserver:cvs@samba.org:/cvsroot co samba + + + + This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + + + + CVS branches other HEAD can be obtained by using the -r + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. + + + + cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba + + + + + + Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + + + + cvs update -d -P + + + + + + + + + + + Accessing the samba sources via rsync and ftp + + + pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. + See the rsync homepage for more info on rsync. + + + + The disadvantage of the unpacked trees + is that they do not support automatic + merging of local changes like CVS does. + rsync access is most convenient for an + initial install. + + + + + Building the Binaries + + To do this, first run the program ./configure + in the source directory. This should automatically + configure Samba for your operating system. If you have unusual + needs then you may wish to run + + root# ./configure --help + + + first to see what special options you can enable. + Then executing + + root# make + + will create the binaries. Once it's successfully + compiled you can use + + root# make install + + to install the binaries and manual pages. You can + separately install the binaries and/or man pages using + + root# make installbin + + + and + + root# make installman + + + 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 + + root# make revert + + + if you find this version a disaster! + + + + Starting the smbd and nmbd + + You must choose to start smbd and nmbd either + as daemons or from inetd. Don't try + to do both! Either you can put them in + inetd.conf and have them started on demand + by inetd, or you can start them as + daemons either from the command line or in + /etc/rc.local. 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. + + The main advantage of starting smbd + and nmbd using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request. + + + Starting from inetd.conf + + NOTE; The following will be different if + you use NIS, NIS+ or LDAP to distribute services maps. + + Look at your /etc/services. + What is defined at port 139/tcp. If nothing is defined + then add a line like this: + + netbios-ssn 139/tcp + + similarly for 137/udp you should have an entry like: + + netbios-ns 137/udp + + Next edit your /etc/inetd.conf + and add two lines something like this: + + + netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd + netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd + + + The exact syntax of /etc/inetd.conf + varies between unixes. Look at the other entries in inetd.conf + for a guide. + + NOTE: Some unixes already have entries like netbios_ns + (note the underscore) in /etc/services. + You must either edit /etc/services or + /etc/inetd.conf to make them consistent. + + 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 ifconfig + as root if you don't know what the broadcast is for your + net. nmbd tries to determine it at run + time, but fails on some unixes. See the section on "testing nmbd" + for a method of finding if you need to do this. + + !!!WARNING!!! Many unixes only accept around 5 + parameters on the command line in inetd.conf. + This means you shouldn't use spaces between the options and + arguments, or you should use a script, and start the script + from inetd. + + Restart inetd, perhaps just send + it a HUP. If you have installed an earlier version of + nmbd then you may need to kill nmbd as well. + + + + Alternative: starting it as a daemon + + To start the server as a daemon you should create + a script something like this one, perhaps calling + it startsmb. + + + #!/bin/sh + /usr/local/samba/bin/smbd -D + /usr/local/samba/bin/nmbd -D + + + then make it executable with chmod + +x startsmb + + You can then run startsmb by + hand or execute it from /etc/rc.local + + + To kill it send a kill signal to the processes + nmbd and smbd. + + NOTE: If you use the SVR4 style init system then + you may like to look at the examples/svr4-startup + script to make Samba fit into that system. + + + diff --git a/docs/docbook/projdoc/UNIX_INSTALL.sgml b/docs/docbook/projdoc/UNIX_INSTALL.sgml index 1ff735a656..254b0d0974 100644 --- a/docs/docbook/projdoc/UNIX_INSTALL.sgml +++ b/docs/docbook/projdoc/UNIX_INSTALL.sgml @@ -3,80 +3,21 @@ How to Install and Test SAMBA - Read the man pages - - 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: - - $ man smbd.8 - or - $ nroff -man smbd.8 | more - on older unixes. - - Other sources of information are pointed to - by the Samba web site, - http://www.samba.org - - - - Building the Binaries - - To do this, first run the program ./configure - in the source directory. This should automatically - configure Samba for your operating system. If you have unusual - needs then you may wish to run - - root# ./configure --help - - - first to see what special options you can enable. - Then executing - - root# make - - will create the binaries. Once it's successfully - compiled you can use - - root# make install - - to install the binaries and manual pages. You can - separately install the binaries and/or man pages using - - root# make installbin - - - and - - root# make installman - - - 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 - - root# make revert - - - if you find this version a disaster! - + Obtaining and installing samba - - The all important step - - 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. + Binary packages of samba are included in almost any Linux or + Unix distribution. There are also some packages available at + the samba homepage + - If you have installed samba before then you can skip - this step. + If you need to compile samba from source, check the + appropriate appendix chapter. Create the smb configuration file. + + There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them @@ -129,106 +70,6 @@ - - Starting the smbd and nmbd - - You must choose to start smbd and nmbd either - as daemons or from inetd. Don't try - to do both! Either you can put them in - inetd.conf and have them started on demand - by inetd, or you can start them as - daemons either from the command line or in - /etc/rc.local. 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. - - The main advantage of starting smbd - and nmbd using the recommended daemon method - is that they will respond slightly more quickly to an initial connection - request. - - - Starting from inetd.conf - - NOTE; The following will be different if - you use NIS or NIS+ to distributed services maps. - - Look at your /etc/services. - What is defined at port 139/tcp. If nothing is defined - then add a line like this: - - netbios-ssn 139/tcp - - similarly for 137/udp you should have an entry like: - - netbios-ns 137/udp - - Next edit your /etc/inetd.conf - and add two lines something like this: - - - netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd - netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd - - - The exact syntax of /etc/inetd.conf - varies between unixes. Look at the other entries in inetd.conf - for a guide. - - NOTE: Some unixes already have entries like netbios_ns - (note the underscore) in /etc/services. - You must either edit /etc/services or - /etc/inetd.conf to make them consistent. - - 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 ifconfig - as root if you don't know what the broadcast is for your - net. nmbd tries to determine it at run - time, but fails on some unixes. See the section on "testing nmbd" - for a method of finding if you need to do this. - - !!!WARNING!!! Many unixes only accept around 5 - parameters on the command line in inetd.conf. - This means you shouldn't use spaces between the options and - arguments, or you should use a script, and start the script - from inetd. - - Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of - nmbd then you may need to kill nmbd as well. - - - - Alternative: starting it as a daemon - - To start the server as a daemon you should create - a script something like this one, perhaps calling - it startsmb. - - - #!/bin/sh - /usr/local/samba/bin/smbd -D - /usr/local/samba/bin/nmbd -D - - - then make it executable with chmod - +x startsmb - - You can then run startsmb by - hand or execute it from /etc/rc.local - - - To kill it send a kill signal to the processes - nmbd and smbd. - - NOTE: If you use the SVR4 style init system then - you may like to look at the examples/svr4-startup - script to make Samba fit into that system. - - - Try listing the shares available on your server @@ -296,7 +137,7 @@ this pile of trash" then I suggest you do step 2 again (and again) till you calm down. - Then you might read the file DIAGNOSIS.txt and the + Then you might read the file HOWTO chapter Diagnosis 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 diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index 246fba1228..efb14d4b6c 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -7,7 +7,6 @@ - @@ -24,6 +23,7 @@ + ]> @@ -112,7 +112,6 @@ part each cover one specific feature. &WINBIND; &BROWSING; &VFS; -&CVS-Access; &GROUP-MAPPING-HOWTO; &SPEED; &GroupProfiles; @@ -123,6 +122,7 @@ part each cover one specific feature. Appendixes &Portability; &Other-Clients; +&Compiling; &BUGS; &Diagnosis; -- cgit From b19116db971f0e14af29a55ef9569aa44e57df01 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Mar 2003 16:29:57 +0000 Subject: More updates: - Add SWAT as way to configure samba - Remove some duplicated information - Move some information to the part of the howto it belongs (This used to be commit f78c98120be81100adbfee01a07283d014c425d4) --- docs/docbook/projdoc/Diagnosis.sgml | 2 +- docs/docbook/projdoc/Other-Clients.sgml | 10 +++ docs/docbook/projdoc/UNIX_INSTALL.sgml | 121 +++++++++++--------------------- 3 files changed, 52 insertions(+), 81 deletions(-) (limited to 'docs/docbook/projdoc') diff --git a/docs/docbook/projdoc/Diagnosis.sgml b/docs/docbook/projdoc/Diagnosis.sgml index 8c1b784433..1e2e6d7598 100644 --- a/docs/docbook/projdoc/Diagnosis.sgml +++ b/docs/docbook/projdoc/Diagnosis.sgml @@ -17,7 +17,7 @@ Wed Jan 15 -Diagnosing your samba server +The samba checklist Introduction diff --git a/docs/docbook/projdoc/Other-Clients.sgml b/docs/docbook/projdoc/Other-Clients.sgml index f790024c3a..6ba04b01d3 100644 --- a/docs/docbook/projdoc/Other-Clients.sgml +++ b/docs/docbook/projdoc/Other-Clients.sgml @@ -233,6 +233,16 @@ for use with security = user + +Use TCP/IP as default protocol + +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. + + diff --git a/docs/docbook/projdoc/UNIX_INSTALL.sgml b/docs/docbook/projdoc/UNIX_INSTALL.sgml index 254b0d0974..5d0d388c08 100644 --- a/docs/docbook/projdoc/UNIX_INSTALL.sgml +++ b/docs/docbook/projdoc/UNIX_INSTALL.sgml @@ -15,10 +15,18 @@ - Create the smb configuration file. + Configuring samba + + Samba's configuration is stored in the smb.conf file, + that usually resides in /etc/samba/smb.conf + or /usr/local/samba/lib/smb.conf. You can either + edit this file yourself or do it using one of the many graphical + tools that are available, such as the web-based interface swat, that + is included with samba. + + + Editing the smb.conf file - - 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 @@ -51,9 +59,8 @@ For more information about security settings for the [homes] share please refer to the document UNIX_SECURITY.txt. - - + Test your config file with <command>testparm</command> @@ -68,6 +75,28 @@ Always run testparm again when you change smb.conf! + + + + + SWAT + + + SWAT is a web-based interface that helps you configure samba. + SWAT might not be available in the samba package on your platform, + but in a seperate package. Please read the swat manpage + on compiling, installing and configuring swat from source. + + + To launch SWAT just run your favorite web browser and + point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you + are running samba on a different computer then your browser. + + Note that you can attach to SWAT from any IP connected + machine but connecting from a remote machine leaves your + connection open to password sniffing as passwords will be sent + in the clear over the wire. + @@ -121,6 +150,8 @@ Try printing. eg: + + C:\WINDOWS\> net use lpt1: \\servername\spoolservice @@ -133,10 +164,6 @@ What If Things Don't Work? - 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. - Then you might read the file HOWTO chapter Diagnosis and the FAQ. If you are still stuck then try the mailing list or newsgroup (look in the README for details). Samba has been @@ -144,18 +171,11 @@ 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. - 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. - - - Diagnosing Problems + When you fix the problem please send some + updates of the documentation (or source code) to one of + the documentation maintainers or the list. + - If you have installation problems then go to the - Diagnosis chapter to try to find the - problem. - - Scope IDs @@ -163,60 +183,10 @@ all your windows boxes must also have a blank scope ID. If you really want to use a non-blank scope ID then you will need to use the 'netbios scope' smb.conf option. - All your PCs will need to have the same setting for + All your PCs will need to have the same setting for this to work. I do not recommend scope IDs. - - - Choosing the Protocol Level - - The SMB protocol has many dialects. Currently - Samba supports 5, called CORE, COREPLUS, LANMAN1, - LANMAN2 and NT1. - - You can choose what maximum protocol to support - in the smb.conf file. The default is - NT1 and that is the best for the vast majority of sites. - - 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. - - The main advantage of LANMAN2 and NT1 is support for - long filenames with some clients (eg: smbclient, Windows NT - or Win95). - - See the smb.conf(5) manual page for more details. - - 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. - - - - Printing from UNIX to a Client PC - - To use a printer that is available via a smb-based - server from a unix host with LPR you will need to compile the - smbclient program. You then need to install the script - "smbprint". Read the instruction in smbprint for more details. - - - There is also a SYSV style script that does much - the same thing called smbprint.sysv. It contains instructions. - - See the CUPS manual for information about setting up - printing from a unix host with CUPS to a smb-based server. - - Locking @@ -273,14 +243,5 @@ - - - Mapping Usernames - - 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. - - -- cgit