From 27aef6855f1543547b8190f06fd264d1b52a558d Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 8.1. Setup your smb.conf ads server = your.kerberos.server
You do *not* need a smbpasswd file, and older clients will - be authenticated as if "security = domain", although it won't do any harm + 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. |
The minimal configuration for krb5.conf is:
The minimal configuration for krb5.conf is: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 address of your KDC. Also, the name that this reverse lookup maps to @@ -151,13 +215,28 @@ must either be the netbios name of the KDC (ie. the hostname with no domain attached) or it can alternatively be the netbios name 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.
As a user that has write permission on the Samba private directory (usually root) run: -net ads joinnet ads join
On a Windows 2000 client try net use * \\server\shareOn 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 ticketsklist tickets. Did you get a ticket for the server? Does it have an encoding type of DES-CBC-MD5 ?
On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but -specify the -k option to choose kerberos authentication.
-k option to choose kerberos authentication.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. |
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.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.
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.
As of Samba-3 WINS replication is being worked on. The bulk of the code has +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 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 @@ -140,7 +198,7 @@ CLASS="SECT1" >
Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such packets can be routed @@ -185,14 +247,23 @@ will annoy users because they will have to put up with protracted 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. @@ -207,21 +278,40 @@ CLASS="SECT1" >
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: @@ -231,7 +321,14 @@ where: CLASS="VARIABLELIST" >
is either the LMB (Local Master Browser) IP address @@ -246,7 +343,10 @@ undesirable but may be necessary if we do NOT know the IP address of the remote LMB.
is optional and can be either our own workgroup @@ -265,30 +365,49 @@ CLASS="SECT1" >
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.dremote 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.a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.
lmhosts files that must reside on all clients in the +absence of WINS.
WINS also serves the purpose of forcing browse list synchronisation by all LMB's. LMB's must synchronise their browse list with the DMB (domain master @@ -330,8 +453,15 @@ machines that have not registered with a WINS server will fail name to address lookup attempts by other clients and will therefore cause workstation access 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.To configure Samba to register with a WINS server just add "wins server = a.b.c.d" to your smb.conf file [globals] section.
Chapter 27. Reporting BugsChapter 31. Reporting Bugs
The email address for bug reports for stable releases is samba@samba.org. @@ -125,8 +125,8 @@ CLASS="SECT1" >
Before submitting a bug report check your config for silly @@ -135,8 +135,7 @@ you've misconfigured something and run testparm to test your config file for correct syntax.
Have you run through the diagnosis? This is very important.
If the bug has anything to do with Samba behaving incorrectly as a @@ -181,9 +180,15 @@ include = /usr/local/samba/lib/smb.conf.%mthen create a file /usr/local/samba/lib/smb.conf.machine/usr/local/samba/lib/smb.conf.machine where -"machine" is the name of the client you wish to debug. In that file +machine is the name of the client you wish to debug. In that file put any smb.conf commands you want, for example debuglevel = that has been used in older versions of Samba and is being retained for backwards -compatibility of smb.conf files.
smb.conf files.As the 27.4. Internal errors31.4. Internal errors
If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software)
If the message came from smbd then it will probably be accompanied by a message which details the last SMB message received by smbd. This @@ -237,7 +245,10 @@ include it in your bug report.
You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed.You may also find that a core file appeared in a "corefiles" +>You may also find that a core file appeared in a corefiles subdirectory of the directory where you keep your samba log files. This file is the most useful tool for tracking down the bug. To use it you do this:
adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try "dbx". Then within the debugger use the -command "where" to give a stack trace of where the problem +don't have gdb then try dbx. Then within the debugger use the +command where to give a stack trace of where the problem occurred. Include this in your mail.
If you known any assembly language then do a "disass" of the routine +>If you known any assembly language then do a disass of the routine where the problem occurred (if its in a library routine then disassemble the routine that called it) and try to work out exactly where the problem is by looking at the surrounding code. Even if you @@ -264,15 +284,30 @@ CLASS="SECT1" >
Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd does often). To debug with this sort of system you could try to attach -to the running process using "gdb smbd PID" where you get PID from -smbstatus. Then use "c" to continue and try to cause the core dump +to the running process using gdb smbd PID where you get PID from +smbstatus. Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred.
The best sort of bug report is one that includes a fix! If you send us -patches please use diff -udiff -u format if your version of -diff supports it, otherwise use diff -c4diff -c4. Make sure your do the diff against a clean version of the source and let me know exactly what version you used.
Chapter 26. How to compile SAMBAChapter 30. How to compile SAMBAYou can obtain the samba source from the 26.1. Access Samba source code via CVS30.1. Access Samba source code via CVS
Samba is developed in an open environment. Developers use CVS @@ -117,8 +117,8 @@ CLASS="SECT2" >
The machine samba.org runs a publicly accessible CVS @@ -130,8 +130,8 @@ CLASS="SECT3" >
You can access the source code via your @@ -151,8 +151,8 @@ CLASS="SECT3" >
You can also access the source code via a @@ -192,9 +192,9 @@ TYPE="1" > Run the command
cvs -d :pserver:cvs@samba.org:/cvsroot login cvs -d :pserver:cvs@samba.org:/cvsroot login
Run the command
cvs -d :pserver:cvs@samba.org:/cvsroot co samba cvs -d :pserver:cvs@samba.org:/cvsroot co samba
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. + latest 2.2 release code. This could be done by using the following userinput.
cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba
cvs update -d -P cvs update -d -P
pserver.samba.org also exports unpacked copies of most parts of the CVS tree at 26.3. Building the Binaries30.3. Building the Binaries
To do this, first run the program 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
In order to compile samba with ADS support, you need to have installed @@ -420,8 +420,8 @@ CLASS="SECT3" >
On Debian you need to install the following packages:
On RedHat this means you should have at least:
You must choose to start smbd and nmbd either - as daemons or from inetd. Don't try + as daemons or from inetdDon't try to do both! Either you can put them in inetd.conf and have them started on demand - by inetdinetd, or you can start them as daemons either from the command line or in
The main advantage of starting smbdThe main advantage of starting smbd - and nmbdnmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection request.
NOTE; The following will be different if @@ -595,19 +595,39 @@ CLASS="FILENAME" >
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 ifconfigifconfig as root if you don't know what the broadcast is for your - net. nmbdnmbd 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 +>Many unixes only accept around 5 parameters on the command line in inetd.confinetd. |
Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of nmbd nmbd then you may need to kill nmbd as well.
To start the server as a daemon you should create @@ -676,13 +700,37 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd.
NOTE: If you use the SVR4 style init system then +>
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. |
This file contains a list of tests you can perform to validate your @@ -95,8 +95,8 @@ CLASS="SECT1" >
In all of the tests it is assumed you have a Samba server called @@ -133,17 +133,18 @@ CLASS="SECT1" >
Diagnosing your samba server
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 @@ -157,15 +158,8 @@ CLASS="FILENAME" CLASS="FILENAME" >/usr/local/samba/lib
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 @@ -183,15 +177,8 @@ you do have correct entries for the remainder of these tests.
Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back.
Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.
run the command
If ACLIENT doesn't resolve via DNS then use the IP address of the client in the above test.
Run the command
This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to TEST 3 notes above).
Run the command dir.
On the PC type the command
Run the command smb.conf. Turn it back on to fix.
Run the command preferred master = yes to ensure that an election is held at startup.
From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -566,6 +497,8 @@ CLASS="COMMAND" > in your smb.conf file, or enable encrypted passwords AFTER compiling in support for encrypted passwords (refer to the Makefile).
Try the mailing list or newsgroup, or use the ethereal utility to @@ -589,7 +522,7 @@ out the samba web page at http://samba.org/sambahttp://samba.org/samba/
Also look at the other docs in the Samba package!
Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -143,9 +142,9 @@ CLASS="COMMAND" >domain admins group by running the command:
smbgroupedit -c "Domain Admins" -u domadmsmbgroupedit -c "Domain Admins" -u domadm
You can list the various groups in the mapping database like this
smbgroupedit -vsmbgroupedit -v
SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called "browse list". This list +of machines in a network, a so-called browse list. This list contains machines that are ready to offer file and/or print services to other machines within the network. Thus it does not include machines which aren't currently able to do server tasks. The browse @@ -93,7 +96,7 @@ list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.
MS Windows 2000 and later, as with Samba-3 and later, can be +>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 @@ -109,8 +112,8 @@ CLASS="SECT1" >
Samba facilitates browsing. The browsing is supported by nmbd @@ -129,45 +132,91 @@ workgroup that has the same name as an NT Domain: on each wide area network, you must only ever have one domain master browser per workgroup, 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 -to use the "workgroup" option in smb.conf to control what workgroup -Samba becomes a part of.
workgroup option in smb.conf +to control what workgroup Samba becomes a part of.Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is recommended that this option is only used for 'unusual' purposes: announcements over the internet, for -example. See "remote announce" in the smb.conf man page.
remote announce in the +smb.conf man page.If something doesn't work then hopefully the log.nmb file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored -in text form in a file called browse.dat.
browse.dat.Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then hit enter and -filemanager should display the list of available shares.
\\SERVER in filemanager then +hit enter and filemanager should display the list of available shares.Some people find browsing fails because they don't have the global -"guest account" set to a valid account. Remember that the IPC$ -connection that lists the shares is done as guest, and thus you must +guest account set to a valid account. Remember that the +IPC$ connection that lists the shares is done as guest, and thus you must have a valid guest account.
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 -not use spaces between the option and the parameter (eg: -d2 instead -of -d 2), and to not use the -B and -N options. New versions of nmbd -are now far more likely to correctly find your broadcast and network -address, so in most cases these aren't needed.
The other big problem people have is that their broadcast address, netmask or IP address is wrong (specified with the "interfaces" option in smb.conf)
Since the release of Samba 1.9.17(alpha1) Samba has been @@ -230,8 +272,8 @@ CLASS="SECT2" >
Cross subnet browsing is a complicated dance, containing multiple @@ -441,8 +483,8 @@ CLASS="SECT1" >
Either a Samba machine or a Windows NT Server machine may be set up @@ -460,17 +502,17 @@ yes. If you have any older versions of Samba on your network it is strongly suggested you upgrade to a recent version, or at the very least set the parameter to 'no' on all these machines.
Machines with "Machines with wins support = yes" will keep a list of +> will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
You should set up only ONE wins server. Do NOT set the -"wins support = yes" option on more than one Samba +> option on more than one Samba server.
To set up a Windows NT Server as a WINS server you need to set up @@ -481,8 +523,11 @@ refuse to document these replication protocols Samba cannot currently participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the "wins support = yes" -parameter set.
wins support = yes parameter set.After the WINS server has been configured you must ensure that all machines participating on the network are configured with the address @@ -503,14 +548,14 @@ 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 -" option and the +wins server = <name>" option then +> option then nmbd will fail to start.
There are two possible scenarios for setting up cross subnet browsing. @@ -524,8 +569,8 @@ CLASS="SECT1" >
To set up cross subnet browsing on a network containing machines @@ -586,15 +631,31 @@ os level = 65
The "local master" parameter allows Samba to act as a local master -browser. The "preferred master" causes nmbd to force a browser -election on startup and the "os level" parameter sets Samba high -enough so that it should win any browser elections.
The local master parameter allows Samba to act as a +local master browser. The preferred master causes nmbd +to force a browser election on startup and the os level +parameter sets Samba high enough so that it should win any browser elections.If you have an NT machine on the subnet that you wish to be the local master browser then you can disable Samba from becoming a local master browser by setting the following -options in the [global] section of the smb.conf file :
[global] section of the +smb.conf file :18.7. Setting up Browsing in a DOMAIN22.7. Setting up Browsing in a DOMAIN
If you are adding Samba servers to a Windows NT Domain then @@ -618,13 +679,23 @@ 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.
DOMAIN<1B>) +with WINS instead of the PDC.For subnets other than the one containing the Windows NT PDC you may set up Samba servers as local master browsers as described. To make a Samba server a local master browser set -the following options in the [global] section of the smb.conf -file :
[global] section +of the smb.conf file :If you wish to have a Samba server fight the election with machines -on the same subnet you may set the "os level" parameter to lower -levels. By doing this you can tune the order of machines that +on the same subnet you may set the os level parameter +to lower levels. By doing this you can tune the order of machines that will become local master browsers if they are running. For -more details on this see the section "FORCING SAMBA TO BE THE MASTER" +more details on this see the section Forcing samba to be the master browser below.
If you have Windows NT machines that are members of the domain on all subnets, and you are sure they will always be running then you can disable Samba from taking part in browser elections and ever becoming a local master browser by setting following options -in the [global] section of the smb.conf file :
[global] section of the smb.conf +file :
18.8. Forcing samba to be the master22.8. Forcing samba to be the master
Who becomes the "master browser" is determined by an election process -using broadcasts. Each election packet contains a number of parameters +>Who becomes the master browser is determined by an election +process using broadcasts. Each election packet contains a number of parameters which determine what precedence (bias) a host should have in the election. By default Samba uses a very low precedence and thus loses elections to just about anyone else.
If you want Samba to win elections then just set the "os level" global -option in smb.conf to a higher number. It defaults to 0. Using 34 +>If you want Samba to win elections then just set the os level global +option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)
A "os level" of 2 would make it beat WfWg and Win95, but not MS Windows +>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
If you want samba to force an election on startup, then set the -"preferred master" global option in smb.conf to "yes". Samba will +preferred master global option in smb.conf to "yes". Samba will then have a slight advantage over other potential master browsers that are not preferred master browsers. Use this parameter with care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with "preferred master" to +samba) on the same local subnet both set with preferred master to "yes", then periodically and continually they will force an election in order to become the local master browser.
If you want samba to be a "domain master browser", then it is -recommended that you also set "preferred master" to "yes", because +>If you want samba to be a domain master browser, then it is +recommended that you also set preferred master to "yes", because samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet.
18.9. Making samba the domain master22.9. Making samba the domain master
The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting "domain master = yes" -in smb.conf. By default it will not be a domain master.
domain master = yes +in smb.conf. By default it will not be a domain master.Note that you should NOT set Samba to be the domain master for a workgroup that has the same name as an NT Domain.
If you want samba to be the domain master then I suggest you also set -the "os level" high enough to make sure it wins elections, and set -"preferred master" to "yes", to get samba to force an election on +the os level high enough to make sure it wins elections, and set +preferred master to "yes", to get samba to force an election on startup.
Note that all your servers (including samba) and clients should be @@ -781,8 +904,8 @@ CLASS="SECT1" >
18.10. Note about broadcast addresses22.10. Note about broadcast addresses
If your network uses a "0" based broadcast address (for example if it @@ -795,13 +918,19 @@ CLASS="SECT1" >
18.11. Multiple interfaces22.11. Multiple interfaces
Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the "interfaces" -option in smb.conf to configure them. See smb.conf(5) for details.
interfaces +option in smb.conf to configure them. See smb.conf(5) for details.
PrevChapter 17. Integrating MS Windows networks with SambaChapter 21. Integrating MS Windows networks with Samba
This section deals with NetBIOS over TCP/IP name to IP address resolution. If you your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this @@ -155,8 +155,8 @@ CLASS="SECT1" >
The key configuration files covered in this section are:
MS Windows networking is predicated about the name each machine @@ -499,8 +499,8 @@ CLASS="SECT2" >
All MS Windows machines employ an in memory buffer in which is @@ -526,8 +526,8 @@ CLASS="SECT2" >
This file is usually located in MS Windows NT 4.0 or @@ -629,8 +629,8 @@ CLASS="SECT2" >
This file is usually located in MS Windows NT 4.0 or 2000 in @@ -651,8 +651,8 @@ CLASS="SECT2" >
This capability is configured in the TCP/IP setup area in the network @@ -671,8 +671,8 @@ CLASS="SECT2" >
A WINS (Windows Internet Name Server) service is the equivaent of the @@ -724,7 +724,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevUnified Logons between Windows NT and UNIX using WinbindHosting a Microsoft Distributed File System tree on Samba
The Distributed File System (or Dfs) provides a means of @@ -212,8 +212,8 @@ CLASS="SECT2" >
If this parameter is specified, each new - connection will append log messages to the log file. - This is the default.
If this parameter is specified, the - log files will be overwritten when opened. By default, - smbd will append entries to the log - files.
Prints the help information (usage) - for nmbd.
Print a summary of command line options.Prints the version number for - nmbdsmbd.
debuglevel is an integer - from 0 to 10. The default value if this parameter is - not specified is zero.
The higher this value, the more detail will - be logged to the log files about the activities of the - server. At level 0, only critical errors and serious - warnings will be logged. Level 1 is a reasonable level for - day to day running - it generates a small amount of - information about operations carried out.
Levels above 1 will generate considerable amounts - of log data, and should only be used when investigating - a problem. Levels above 3 are designed for use only by developers - and generate HUGE amounts of log data, most of which is extremely - cryptic.
Note that specifying this parameter here will override - the The file specified contains the +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 log levelsmb.conf(5) - parameter in the smb.conf(5) file.
for more information. +The default configuration file name is determined at +compile time.The -l parameter specifies a directory - into which the "log.nmbd" log file will be created - for operational data from the running nmbd - server. The default log directory is compiled into Samba - as part of the build process. Common defaults are /usr/local/samba/var/log.nmb, /usr/samba/var/log.nmb or - debuglevel is an integer +from 0 to 10. The default value if this parameter is +not specified is zero.
The higher this value, the more detail will be +logged to the log files about the activities of the +server. At level 0, only critical errors and serious +warnings will be logged. Level 1 is a reasonable level for +day to day running - it generates a small amount of +information about operations carried out.
Levels above 1 will generate considerable +amounts of log data, and should only be used when +investigating a problem. Levels above 3 are designed for +use only by developers and generate HUGE amounts of log +data, most of which is extremely cryptic.
Note that specifying this parameter here will +override the log +level parameter in the /var/log/log.nmb. Beware: - If the directory specified does not exist, nmbd - will log to the default debug log location defined at compile time. -
smb.conf(5) file.This option allows you to override - the NetBIOS name that Samba uses for itself. This is identical - to setting the NetBIOS - name parameter in the smb.conf(5) file. However, a command - line setting will take precedence over settings in - smb.conf(5).
File name for log/debug files. The extension +".client"
will be appended. The log file is
+never removed by the client.The default configuration file name - is set at build time, typically as /usr/local/samba/lib/smb.conf, but - this may be changed when Samba is autoconfigured.
The file specified contains the configuration details - required by the server. See smb.conf(5) for more information. -
Print a help (usage) message.
This option allows you to override +the NetBIOS name that Samba uses for itself. This is identical +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command +line setting will take precedence over settings in +smb.conf(5).This specifies a NetBIOS scope that +nmblookup will use to communicate with when +generating NetBIOS names. For details on the use of NetBIOS +scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are +very rarely used, only set this parameter +if you are the system administrator in charge of all the +NetBIOS systems you communicate with.
Set the SMB domain of the username. This +overrides the default domain which is the domain defined in +smb.conf. If the domain specified is the same as the servers +NetBIOS name, it causes the client to log on using the servers local +SAM (as opposed to the Domain SAM).
TCP socket options to set on the client +socket. See the socket options parameter in +the smb.conf(5) manual page for the list of valid +options.
Print a summary of command line options.
debuglevel is an integer from 0 to 10.
The default value if this parameter is not specified - is zero.
The higher this value, the more detail will be logged - about the activities of Prints the version number for +nmblookup. At level - 0, only critical errors and serious warnings will be logged.
Levels above 1 will generate considerable amounts of - log data, and should only be used when investigating a problem. - Levels above 3 are designed for use only by developers and - generate HUGE amounts of data, most of which is extremely cryptic.
smbd.Note that specifying this parameter here will override - the The file specified contains the +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 log level parameter in the smb.conf(5) file.
smb.conf(5) for more information. +The default configuration file name is determined at +compile time.This parameter specifies the pathname to - the Samba configuration file, debuglevel is an integer +from 0 to 10. The default value if this parameter is +not specified is zero.
The higher this value, the more detail will be +logged to the log files about the activities of the +server. At level 0, only critical errors and serious +warnings will be logged. Level 1 is a reasonable level for +day to day running - it generates a small amount of +information about operations carried out.
Levels above 1 will generate considerable +amounts of log data, and should only be used when +investigating a problem. Levels above 3 are designed for +use only by developers and generate HUGE amounts of log +data, most of which is extremely cryptic.
Note that specifying this parameter here will +override the log +level parameter in the smb.conf(5). This file controls all aspects of - the Samba setup on the machine.
smb.conf(5) file.This specifies a NetBIOS scope that - nmblookup will use to communicate with when - generating NetBIOS names. For details on the use of NetBIOS - scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are - very rarely used, only set this parameter - if you are the system administrator in charge of all the - NetBIOS systems you communicate with.
File name for log/debug files. The extension +".client"
will be appended. The log file is
+never removed by the client.This chapter contains client-specific information.
Yes. 25.2. OS2 Client29.2. OS2 Client
Use the latest TCP/IP stack from microsoft if you use Windows @@ -338,8 +338,8 @@ CLASS="SECT2" >
WfWg does a lousy job with passwords. I find that if I change my @@ -358,8 +358,8 @@ CLASS="SECT2" >
There is a program call admincfg.exe @@ -377,8 +377,8 @@ CLASS="SECT2" >
Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the 25.3.5. Use TCP/IP as default protocol29.3.5. Use TCP/IP as default protocol
To support print queue reporting you may find @@ -411,8 +411,8 @@ CLASS="SECT1" >
When using Windows 95 OEM SR2 the following updates are recommended where Samba @@ -459,8 +459,8 @@ CLASS="SECT1" >
@@ -526,15 +526,49 @@ 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. |
If you have problems communicating across routers with Windows +NT 3.1 workstations, read this Microsoft Knowledge Base article.
A number of Unix systems (eg: Sun Solaris), as well as the @@ -150,7 +148,7 @@ CLASS="FILENAME"
eg: "auth required /other_path/pam_strange_module.so" +> auth required /other_path/pam_strange_module.soPAM 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_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 pam_nologin.so pam_rootok.so pam_tally.so @@ -289,10 +293,10 @@ CLASS="PROGRAMLISTING" > #%PAM-1.0 # The PAM configuration file for the `samba' service # - auth required /lib/security/pam_pwdb.so nullok nodelay shadow audit - account required /lib/security/pam_pwdb.so audit nodelay - session required /lib/security/pam_pwdb.so nodelay - password required /lib/security/pam_pwdb.so shadow md5In the following example the decision has been made to use the @@ -306,10 +310,10 @@ CLASS="PROGRAMLISTING" > #%PAM-1.0 # The PAM configuration file for the `samba' service # - auth required /lib/security/pam_smbpass.so nodelay - account required /lib/security/pam_pwdb.so audit nodelay - session required /lib/security/pam_pwdb.so nodelay - password required /lib/security/pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
The astute administrator will realize from this that the @@ -385,8 +389,8 @@ CLASS="SECT1" >
There is an option in smb.conf called PrevNextGroup mapping HOWTODesktop Profile Management
samba-patches@samba.org and jerry@samba.org.
jerry@samba.org
root# cp samba.schema /etc/openldap/schema/cp samba.schema /etc/openldap/schema/
Next, include the 3.6.5.2. Configuring Samba
To build the plugin, run make bin/pdb_mysql.so -in the source/ directory of samba distribution.
Next, copy pdb_mysql.so to any location you want. I -strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/
You either can set up your own table and specify the field names to pdb_mysql (see below @@ -1403,8 +1382,8 @@ CLASS="SECT2" >
This plugin lacks some good documentation, but here is some short info:
:passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]passdb backend = [other-plugins] mysql:identifier [other-plugins]
The identifier can be any string you like, as long as it doesn't collide with @@ -1514,8 +1493,8 @@ CLASS="SECT2" >
I strongly discourage the use of plaintext passwords, however, you can use them:
It is possible to have not all data in the database and making some 'constant'.
This module requires libxml2 to be installed.
To build pdb_xml, run: make bin/pdb_xml.so in -the directory source/.
The usage of pdb_xml is pretty straightforward. To export data, use: -pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filenamepdbedit -e xml:filename (where filename is the name of the file to put the data in)
To import data, use: -pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdbpdbedit -i xml:filename -e current-pdb Where filename is the name to read the data from and current-pdb to put it in.
If you specify -g, + then -i in-backend -e out-backend + applies to the group mapping instead of the user database. + +
This option will ease migration from one passdb backend to + another and will ease backing up.
If you specify -g, + then -i in-backend -e out-backend + applies to the group mapping instead of the user database. + +
This option will ease migration from one passdb backend to + another and will ease backing up.
Sets an account policy to a specified value. @@ -380,7 +418,7 @@ CLASS="PARAMETER" >
Example: pdbedit -P "bad lockout attempt" -V 3pdbedit -P "bad lockout attempt" -C 3
Print a summary of command line options.
Prints the version number for +smbd.
The file specified contains the +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 smb.conf(5) for more information. +The default configuration file name is determined at +compile time.
file.
Print a summary of command line options.
The file specified contains the -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 smb.conf(5) for more information. -The default configuration file name is determined at -compile time.
File name for log/debug files. The extension +".client"
will be appended. The log file is
+never removed by the client.Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains @@ -84,8 +84,8 @@ CLASS="SECT1" >
HP's implementation of supplementary groups is, er, non-standard (for @@ -114,8 +114,8 @@ CLASS="SECT1" >
@@ -131,8 +131,8 @@ CLASS="SECT1" >
DNIX has a problem with seteuid() and setegid(). These routines are @@ -238,8 +238,8 @@ CLASS="SECT1" >
By default RedHat Rembrandt-II during installation adds an @@ -262,16 +262,16 @@ CLASS="SECT1" >
Disabling Sequential Read Ahead using "vmtune -r 0" improves diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 7834e0d884..d30fa88b70 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -13,9 +13,8 @@ REL="UP" TITLE="Advanced Configuration" HREF="optional.html">PrevChapter 14. Printing SupportChapter 12. Printing Support
Beginning with the 2.2.0 release, Samba supports @@ -164,8 +163,8 @@ CLASS="SECT1" >
In order to support the uploading of printer driver @@ -353,14 +352,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"
The initial listing of printers in the Samba host's @@ -515,8 +514,8 @@ CLASS="SECT2" >
One issue that has arisen during the development @@ -535,13 +534,16 @@ setdriver command
-$ 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] @@ -552,27 +554,34 @@ Printer Driver Info 1: Driver Name: [HP LaserJet 2100 Series PS] Printer Driver Info 1: - Driver Name: [HP LaserJet 4Si/4SiMX PS] - + Driver Name: [HP LaserJet 4Si/4SiMX PS]$ rpcclient pogo -U root%secret -c "enumprinters" -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] +>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\"" -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] +>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.
By default, Samba offers all printer shares defined in 14.2.5. Samba and Printer Ports12.2.5. Samba and Printer Ports
Windows NT/2000 print servers associate a port with each printer. These normally @@ -771,8 +780,8 @@ CLASS="SECT1" >
The Imprints tool set provides a UNIX equivalent of the @@ -789,8 +798,8 @@ CLASS="SECT2" >
Imprints is a collection of tools for supporting the goals @@ -821,8 +830,8 @@ CLASS="SECT2" >
The process of creating printer driver packages is beyond @@ -837,8 +846,8 @@ CLASS="SECT2" >
The Imprints server is really a database server that @@ -861,8 +870,8 @@ CLASS="SECT2" >
More information regarding the Imprints installation client @@ -955,16 +964,16 @@ CLASS="SECT1" >
This is a short description of how to debug printing problems with @@ -1038,8 +1047,8 @@ CLASS="SECT2" >
One way to debug printing problems is to start by replacing these @@ -1095,8 +1104,8 @@ CLASS="SECT2" >
You can use the 'testprns' program to check to see if the printer @@ -1124,8 +1133,8 @@ CLASS="SECT2" >
You may need to set up some printcaps for your Samba system to use. @@ -1208,8 +1217,8 @@ CLASS="SECT2" >
This is the most frustrating part of printing. You may have sent the @@ -1253,8 +1262,8 @@ CLASS="SECT2" >
Once you have the job printing, you can then start worrying about @@ -1299,8 +1308,8 @@ CLASS="SECT2" >
This is a problem that is usually caused by either the print spooling @@ -1314,8 +1323,8 @@ CLASS="SECT2" >
Note that you can do some pretty magic things by using your @@ -1330,8 +1339,8 @@ CLASS="SECT2" >
If the above debug tips don't help, then maybe you need to bring in @@ -1355,7 +1364,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevConfiguring PAM for distributed but centrally -managed authenticationConfiguring Group Mapping
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 -
execute semicolon separated commands (listed + below))username = <value> -password = <value> -domain = <value>IP address is the address of the server to connect to. + It should be specified in standard "a.b.c.d" notation.
Make certain that the permissions on the file restrict - access from unwanted users.
Normally the client would attempt to locate a named + SMB/CIFS server by looking it up via the NetBIOS name resolution + mechanism described above in the name resolve order + parameter above. Using this parameter will force the client + to assume that the server is on the machine with the specified IP + address and the NetBIOS name component of the resource being + connected to will be ignored.There is no default for this parameter. If not supplied, + it will be determined automatically by the client as described + above.
execute semicolon separated commands (listed - below))
Prints the version number for +smbd.Print a summary of command line options.
The file specified contains the +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 smb.conf(5) for more information. +The default configuration file name is determined at +compile time.IP address is the address of the server to connect to. - It should be specified in standard "a.b.c.d" notation.
Normally the client would attempt to locate a named - SMB/CIFS server by looking it up via the NetBIOS name resolution - mechanism described above in the name resolve order - parameter above. Using this parameter will force the client - to assume that the server is on the machine with the specified IP - address and the NetBIOS name component of the resource being - connected to will be ignored.
There is no default for this parameter. If not supplied, - it will be determined automatically by the client as described - above.
File name for log/debug files. The extension +".client"
will be appended. The log file is
+never removed by the client.File name for log/debug files. The extension
- '.client'
will be appended. The log file is
- never removed by the client.
-
Unless a password is specified on the command line or +this parameter is specified, the client will request a +password.
instruct rpcclient not to ask - for a password. By default, rpcclient will - prompt for a password. See also the -U - option.
Try to authenticate with kerberos. Only useful in +an Active Directory environment.Specifies the location of the all-important - smb.conf file.
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 isusername = <value> +password = <value> +domain = <value>
Make certain that the permissions on the file restrict +access from unwanted users.
Sets the SMB username or username and password.
If %password is not specified, the user will be prompted. The
- client will first check the If %password is not specified, the user will be prompted. The
+client will first check the USER environment variable, then the
- environment variable, then the
+LOGNAME variable and if either exists, the
- string is uppercased. If these environmental variables are not
- found, the username variable and if either exists, 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 - option is mainly provided for scripts where the admin does not - wish to pass the credentials on the command line or via environment - variables. If this method is used, make certain that the permissions - on the file restrict access from unwanted users. See the - A third option is to use a credentials file which +contains the plaintext of the username and password. This +option is mainly provided for scripts where the admin does not +wish to pass the credentials on the command line or via environment +variables. If this method is used, make certain that the permissions +on the file restrict access from unwanted users. See the +-A for more details.
Be cautious about including passwords in scripts. Also, on - many systems the command line of a running process may be seen - via the Be cautious about including passwords in scripts. Also, on +many systems the command line of a running process may be seen +via the ps command. To be safe always allow - command. To be safe always allow +rpcclient to prompt for a password and type - it in directly.
to prompt for a password and type +it in directly.This option allows you to override +the NetBIOS name that Samba uses for itself. This is identical +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command +line setting will take precedence over settings in +smb.conf(5).
This specifies a NetBIOS scope that +nmblookup will use to communicate with when +generating NetBIOS names. For details on the use of NetBIOS +scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are +very rarely used, only set this parameter +if you are the system administrator in charge of all the +NetBIOS systems you communicate with.
Set the SMB domain of the username. This - overrides the default domain which is the domain defined in - smb.conf. 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).
Set the SMB domain of the username. This +overrides the default domain which is the domain defined in +smb.conf. If the domain specified is the same as the servers +NetBIOS name, it causes the client to log on using the servers local +SAM (as opposed to the Domain SAM).TCP socket options to set on the client +socket. See the socket options parameter in +the smb.conf(5) manual page for the list of valid +options.
Print a summary of command line options.
LSARPC
lsaquery
lookupsids - Resolve a list +>Resolve a list of SIDs to usernames.
lookupnames - Resolve a list +>Resolve a list of usernames to SIDs.
Enumerate trusted domains
Enumerate privileges
Get the privilege name
Enumerate the LSA SIDS
Enumerate the privileges of an SID
Enumerate the rights of an SID
Enumerate accounts with a right
Add rights to an account
Remove rights from an account
Get a privilege value given its name
Query LSA security object
enumtrusts
Get Primary Domain Information
SAMRDFS
Query DFS support
Add a DFS share
Remove a DFS share
Query DFS share info
Enumerate dfs shares
Server query info
Enumerate shares
Enumerate open files
Fetch remote time of day
querygroup
Query user info
Query group info
Query user groups
Query group membership
Query alias membership
Query display info
Query domain info
queryusergroups
querygroupmem
queryaliasmem
querydispinfo
querydominfo
enumdomgroups
Look up namesDelete domain user
SPOOLSS
Query SAMR security objectRetrieve domain password info
adddriver <arch> <config>
- - Execute an AddPrinterDriver() RPC to install the printer driver
+> 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
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 enumports.
deldriver - Delete the +>Delete the specified printer driver for all architectures. This does not delete the actual driver files from the server, only the entry from the server's list of drivers.
enumdata - Enumerate all +>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).
enumjobs <printer> - - List the jobs and status of a given printer. +>Enumerate printer data for a key
List the jobs and status of a given printer. This command corresponds to the MS Platform SDK EnumJobs() - function (* This command is currently unimplemented).
enumports [level] - - Executes an EnumPorts() call using the specified +>Enumerate printer keys
Executes an EnumPorts() call using the specified info level. Currently only info levels 1 and 2 are supported.
enumdrivers [level] - - Execute an EnumPrinterDrivers() call. This lists the various installed +> 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.
enumprinters [level] - - Execute an EnumPrinters() call. This lists the various installed +>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.
getdata <printername> - - Retrieve the data for a given printer setting. See +>Retrieve the data for a given printer setting. See the enumdata command for more information. This command corresponds to the GetPrinterData() MS Platform - SDK function (* This command is currently unimplemented).
getdriver <printername> - - Retrieve the printer driver information (such as driver file, +>Get printer driver data with keyname
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.
getdriverdir <arch> - - Execute a GetPrinterDriverDirectory() +> Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture. Possible values for are "Windows 4.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000".
getprinter <printername> - - Retrieve the current printer information. This command +>Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function.
openprinter <printername> - - Execute an OpenPrinterEx() and ClosePrinter() RPC - against a given printer.
Execute an OpenPrinterEx() and ClosePrinter() RPC + against a given printer.
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.
enumdrivers commands for obtaining a list of of installed printers and drivers.
Add form
Set form
Get form
Delete form
Enumerate form
Set printer comment
Set REG_SZ printer data
Rffpcnex test
SAMBA Team
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
Encrypted passwords must be enabled. For more details on how to do this, refer to ENCRYPTION.html.
This note was attached to the Samba 2.2.8 release notes as it contained an @@ -93,8 +93,8 @@ CLASS="SECT1" >
In many installations of Samba the greatest threat comes for outside @@ -125,8 +125,8 @@ CLASS="SECT1" >
By default Samba will accept connections on any network interface that @@ -161,8 +161,8 @@ CLASS="SECT1" >
Many people use a firewall to deny access to services that they don't @@ -191,8 +191,8 @@ CLASS="SECT1" >
If the above methods are not suitable, then you could also place a @@ -230,8 +230,8 @@ CLASS="SECT1" >
Please check regularly on http://www.samba.org/ for updates and @@ -256,7 +256,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevStackable VFS modulesImproved browsing in samba
NOTE: On SYSV systems which use lpstat to determine what +>
On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use "printcap name = lpstat" to automatically obtain a list of printers. See the "printcap name" option for more details. |
See the discussion in the section NAME MANGLING. See the section on NAME MANGLING. Also note the The default depends on which charsets you have instaled.
+>The default depends on which charsets you have installed.
Samba tries to use charset 850 but falls back to ASCII in
case it is not available. Run NOTE :A working NIS client is required on
the system for this option to work. See also hosts equiv may be useful for NT clients which will
not supply passwords to Samba. NOTE : The use of The use of hosts equiv
trust
them :-). Default: smbpasswd(8) This parameter specifies whether a delete
+ operation in the ldapsam deletes the complete entry or only the attributes
+ specific to Samba.
Default : noneldap delete dn = no See the section on NAME MANGLING See the section on NAME MANGLING for details on how to control the mangling process. magic character in name mangling. The default is a '~'
but this may interfere with some software. Use this option to set
@@ -11958,11 +12069,35 @@ NAME="NONUNIXACCOUNTRANGE"
This is most often used for machine account creation.
This range of ids should have no existing local or NIS users within
it as strange conflicts can occur otherwise. NOTE: These userids never appear on the system and Samba will never
+> These userids never appear on the system and Samba will never
'become' these users. They are used only to ensure that the algorithmic
RID mapping does not conflict with normal users.
Default: and so may resolved
by any method and order described in that parameter. The password server much be a machine capable of using
+>The password server must be a machine capable of using
the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
user level security mode. NOTE: Using a password server
+> Using a password server
means your UNIX box (running Samba) is only as secure as your
password server. . Never point a Samba server at itself for password
serving. This will cause a loop and could lock up your Samba
@@ -13631,6 +13784,30 @@ CLASS="COMMAND"
> This is a list of paths to modules that should
+ be loaded into smbd before a client connects. This improves
+ the speed of smbd when reacting to new connections somewhat. It is recommended to only use this option on heavy-performance
+ servers. Default: preload modules = Example: preload modules = /usr/lib/samba/passdb/mysql.so See the section on NAME
MANGLING for a fuller discussion. NOTE: Under AIX the default printcap
+> Under AIX the default printcap
name is /etc/qconfigqconfig appears in the printcap filename. Default: See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. parameter for details on doing this. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. parameter for details on doing this. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. parameter for details on doing this. See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. This controls whether the server offers or even
+ demands the use of the netlogon schannel.
+ server schannel = no does not
+ offer the schannel, server schannel =
+ auto offers the schannel but does not
+ enforce it, and server schannel =
+ yes denies access if the client is not
+ able to speak netlogon schannel. This is only the case
+ for Windows NT4 before SP4. Please note that with this set to
+ no you will have to apply the
+ WindowsXP requireSignOrSeal-Registry patch found in
+ the docs/Registry subdirectory. Default: server schannel = auto Example: server schannel = yes/para>
+ Thanks to the Posix subsystem in NT a
+ Windows User has a primary group in addition to the
+ auxiliary groups. This script sets the primary group
+ in the unix userdatase when an administrator sets the
+ primary group from the windows user manager or when
+ fetching a SAM with net rpc
+ vampire. %u will be
+ replaced with the user whose primary group is to be
+ set. %g will be replaced with
+ the group to set.
+
+ Default: No default value Example: set primary group script = /usr/sbin/usermod -g '%g' '%u' See the section on NAME MANGLING. See the section NOTE ABOUT
USERNAME/PASSWORD VALIDATION for more information on how
@@ -17868,22 +18150,45 @@ CLASS="REFENTRYTITLE"
>You should point this at your WINS server if you have a
multi-subnetted network. NOTE. You need to set up Samba to point
+>If you want to work in multiple namespaces, you can
+ give every wins server a 'tag'. For each tag, only one
+ (working) server will be queried for a name. The tag should be
+ seperated from the ip address by a colon.
+ You need to set up Samba to point
to a WINS server if you have multiple subnets and wish cross-subnet
browsing to work correctly. See the documentation file BROWSING
- in the docs/ directory of your Samba source distribution. Default: Example: wins server = 192.9.200.1wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61 For this example when querying a certain name, 192.19.200.1 will
+ be asked first and if that doesn't respond 192.168.2.61. If either
+ of those doesn't know the name 192.168.3.199 will be queried.
+ Example: wins server = 192.9.200.1 192.168.2.61 Print usage information on the Don't actually do anything, only validate the correctness of
+ the arguments.
+ Print a summary of command line options. Prints the version number for
+smbcacls
- program. The file specified contains the
+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 smb.conf(5) for more information.
+The default configuration file name is determined at
+compile time. debuglevel is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero. The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out. Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic. Note that specifying this parameter here will
+override the log
+level parameter in the smb.conf(5) file. File name for log/debug files. The extension
+ This man page is correct for version 2.2 of the Samba suite. Specifies the location of the all
- important smb.conf(5) file. TCP socket options to set on the client
- socket. See the socket options parameter in
- the smb.conf(5) manual page for the list of valid
- options. This specifies a NetBIOS scope that smbclient will
- use to communicate with when generating NetBIOS names. For details
- on the use of NetBIOS scopes, see rfc1001.txt
- and rfc1002.txt.
- NetBIOS scopes are very rarely used, only set
- this parameter if you are the system administrator in charge of all
- the NetBIOS systems you communicate with. If specified, this parameter suppresses the normal
- password prompt from the client to the user. This is useful when
- accessing a service that does not require a password. Unless a password is specified on the command line or
- this parameter is specified, the client will request a
- password. By default, the client will use the local
- machine's hostname (in uppercase) as its NetBIOS name. This parameter
- allows you to override the host name and use whatever NetBIOS
- name you wish. debuglevel is an integer from 0 to 10, or
- the letter 'A'. The default value if this parameter is not specified
- is zero. The higher this value, the more detail will be logged to
- the log files about the activities of the
- client. At level 0, only critical errors and serious warnings will
- be logged. Level 1 is a reasonable level for day to day running -
- it generates a small amount of information about operations
- carried out. Levels above 1 will generate considerable amounts of log
- data, and should only be used when investigating a problem.
- Levels above 3 are designed for use only by developers and
- generate HUGE amounts of log data, most of which is extremely
- cryptic. If debuglevel is set to the letter 'A', then all
- debug messages will be printed. This setting
- is for developers only (and people who really want
- to know how the code works internally). Note that specifying this parameter here will override
- the log level parameter in the smb.conf (5)
- file. Print the usage message for the client. 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
- LOGNAME variable and if either exists, the
- string is uppercased. Anything in these variables following a '%'
- sign will be treated as the password. If these environment
- variables are not found, the username If the password is not included in these environment
- variables (using the %pass syntax), smbclient will look for
- a PASSWD environment variable from which
- to read the password. A third option is to use a credentials file which
- contains the plaintext of the domain name, username and password. This
- option is mainly provided for scripts where the admin doesn't
- wish to pass the credentials on the command line or via environment
- variables. If this method is used, make certain that the permissions
- on the file restrict access from unwanted users. See the
- -A for more details. Be cautious about including passwords in scripts or in
- the PASSWD environment variable. Also, on
- many systems the command line of a running process may be seen
- via the ps command to be safe always allow
- smbclient to prompt for a password and type
- it in directly. This option allows
- you to specify a file from which to read the username, domain name, and
- password used in the connection. The format of the file is
- If the domain parameter is missing the current workgroup name
- is used instead. Make certain that the permissions on the file restrict
- access from unwanted users. Prints the version number for
+smbd. The file specified contains the
+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 smb.conf(5) for more information.
+The default configuration file name is determined at
+compile time. debuglevel is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero. The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out. Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic. Note that specifying this parameter here will
+override the log
+level parameter in the smb.conf(5) file. File name for log/debug files. The extension
+ If specified, this parameter suppresses the normal
+password prompt from the client to the user. This is useful when
+accessing a service that does not require a password. Unless a password is specified on the command line or
+this parameter is specified, the client will request a
+password. Try to authenticate with kerberos. Only useful in
+an Active Directory environment. Override the default workgroup (domain) specified
- in the workgroup parameter of the 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 Make certain that the permissions on the file restrict
+access from unwanted users. Sets the SMB username or username and password. If %password is not specified, the user will be prompted. The
+client will first check the USER environment variable, then the
+LOGNAME variable and if either exists, the
+string is uppercased. If these environmental variables are not
+found, the username A third option is to use a credentials file which
+contains the plaintext of the username and password. This
+option is mainly provided for scripts where the admin does not
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users. See the
+-A for more details. Be cautious about including passwords in scripts. Also, on
+many systems the command line of a running process may be seen
+via the ps command. To be safe always allow
+rpcclient to prompt for a password and type
+it in directly. This option allows you to override
+the NetBIOS name that Samba uses for itself. This is identical
+to setting the NetBIOS
+name parameter in the smb.conf(5) file for this connection. This may be
- needed to connect to some servers. This specifies a NetBIOS scope that
+nmblookup will use to communicate with when
+generating NetBIOS names. For details on the use of NetBIOS
+scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
+very rarely used, only set this parameter
+if you are the system administrator in charge of all the
+NetBIOS systems you communicate with. Set the SMB domain of the username. This
+overrides the default domain which is the domain defined in
+smb.conf. If the domain specified is the same as the servers
+NetBIOS name, it causes the client to log on using the servers local
+SAM (as opposed to the Domain SAM). TCP socket options to set on the client
+socket. See the socket options parameter in
+the smb.conf(5) manual page for the list of valid
+options. Try to authenticate with kerberos. Only useful in
- an Active Directory environment.
- Print a summary of command line options. The file specified contains the
+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 smb.conf(5) for more information.
+The default configuration file name is determined at
+compile time. message-type One of: The Available message types are: Order smbd to close the client
+ connections to the named share. Note that this doesn't affect client
+ connections to any other shares. This message-type takes an argument of the
+ share name for which client connections will be closed, or the
+ "*" character which will close all currently open shares.
+ This may be useful if you made changes to the access controls on the share.
+ This message can only be sent to The The The The The The Request profilelevel of a certain daemon and write it to stdout.
+ This can be sent to any smbd or nmbd destinations. Order smbd to send a printer notify message to any Windows NT clients
+ connected to a printer. This message-type takes the following arguments:
+ The Send a queue pause change notify
- message to the printer specified. Send a queue resume change notify
- message for the printer specified. Send a job pause change notify
- message for the printer and unix jobid
- specified. Send a job resume change notify
- message for the printer and unix jobid
- specified. Send a job delete change notify
- message for the printer and unix jobid
- specified. Note that this message only sends notification that an
+ event has occured. It doesn't actually cause the
+ event to happen.
+ This message can only be sent to any parameters required for the message-type Not working at the moment Send sam replication message, with specified serial. Can only be sent to Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. Dump the pointers that have changed since the mark set by dmalloc-mark.
+ Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. Shut down specified daemon. Can be sent to both smbd and nmbd. Print a human-readable description of all
+ talloc(pool) memory usage by the specified daemon/process. Available
+ for both smbd and nmbd. Force clients of printers using specified driver
+ to update their local version of the driver. Can only be
+ sent to smbd. This man page is correct for version 2.2 of
+>This man page is correct for version 3.0 of
the Samba suite. Prints the help information (usage)
- for smbd. Prints the version number for
- smbd. Prints information about how
- Samba was built. debuglevel is an integer
- from 0 to 10. The default value if this parameter is
- not specified is zero. The higher this value, the more detail will be
- logged to the log files about the activities of the
- server. At level 0, only critical errors and serious
- warnings will be logged. Level 1 is a reasonable level for
- day to day running - it generates a small amount of
- information about operations carried out. Levels above 1 will generate considerable
- amounts of log data, and should only be used when
- investigating a problem. Levels above 3 are designed for
- use only by developers and generate HUGE amounts of log
- data, most of which is extremely cryptic. Note that specifying this parameter here will
- override the log
- level parameter in the smb.conf(5) parameter in the smb.conf(5) file. File name for log/debug files. The extension
+ Print a summary of command line options. Prints information about how
+ Samba was built. See the socket options
- parameter in the smb.conf(5) file for details. This parameter is not normally specified except
in the above situation. The file specified contains the
- 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 smb.conf(5) for more information.
- The default configuration file name is determined at
- compile time. Use kerberos (Active Directory). dmask=<arg> sets the directory mask. This determines the
+>Sets the directory mask. This determines the
permissions that remote directories have in the local filesystem.
The default is based on the current umask. sets the debug level. This is useful for
+>Sets the debug level. This is useful for
tracking down SMB connection problems. A suggested value to
start with is 4. If set too high there will be a lot of
output, possibly hiding the useful output. sets the destination host or IP address.
+>Sets the destination host or IP address.
sets the workgroup on the destination sets the TCP socket options. See the Sets the TCP socket options. See the scope=<arg> sets the NetBIOS scope don't prompt for a password The file specified contains the
+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 smb.conf(5) for more information.
+The default configuration file name is determined at
+compile time. debuglevel is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero. The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out. Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic. Note that specifying this parameter here will
+override the log
+level parameter in the smb.conf(5) file. This option is used to determine what naming
- services and in what order to resolve
- host names to IP addresses. The option takes a space-separated
- string of different name resolution options. The options are: "lmhosts", "host", "wins" and "bcast".
- They cause names to be resolved as follows : host:
- Do a standard host name to IP address resolution, using
- the system /etc/hosts, NIS, or DNS
- lookups. This method of name resolution is operating
- system dependent, for instance on IRIX or Solaris this
- may be controlled by the /etc/nsswitch.conf
- /etc/nsswitch.conf file). Note that this method is only used
- if the NetBIOS name type being queried is the 0x20
- (server) name type, otherwise it is ignored.
- wins:
- Query a name with the IP address listed in the
- wins server parameter. If no
- WINS server has been specified this method will be
- ignored.
- bcast:
- Do a broadcast on each of the known local interfaces
- listed in the interfaces
- parameter. This is the least reliable of the name
- resolution methods as it depends on the target host
- being on a locally connected subnet.
- If this parameter is not set then the name resolve order
- defined in the smb.conf(5) file parameter
- (name resolve order) will be used. The default order is lmhosts, host, wins, bcast. Without
- this parameter or any entry in the name resolve order
- name resolve order parameter of the smb.conf(5) file, the name resolution methods
- will be attempted in this order. debug level is an integer from 0 to 10. The default value if this parameter is not specified
- is zero. The higher this value, the more detail will be logged
- about the activities of nmblookup(1). At level
- 0, only critical errors and serious warnings will be logged.
- If specified causes all debug messages to be
- written to the file specified by logfilename
- . If not specified then all messages will be
- written tostderr.
- This man page is correct for version 2.2 of the Samba suite. sets debugging to specified level The file specified contains the
+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 smb.conf(5) for more information.
+The default configuration file name is determined at
+compile time. debuglevel is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero. The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out. Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic. Note that specifying this parameter here will
+override the log
+level parameter in the smb.conf(5) file. File name for log/debug files. The extension
+ The default configuration file name is
- determined at compile time. The file specified contains the
- configuration details required by the server. See smb.conf(5) for more information. Reset DOS archive bit mode to
+ indicate file has been archived. COMPLETE LIST OF SERVICE PARAMETERS
EXPLANATION OF EACH PARAMETER
WARNINGS
VERSION
SEE ALSO
AUTHOR
smbcacls {//server/share} {filename} [-U username] [-A acls] [-M acls] [-D acls] [-S acls] [-C name] [-G name] [-n] [-h] {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]DESCRIPTION
OPTIONS
".client"
will be appended. The log file is
+never removed by the client.ACL FORMAT
EXIT STATUS
VERSION
AUTHOR
GUEST
- is used. username = <value>
-password = <value>
-domain = <value>
".client"
will be appended. The log file is
+never removed by the client.username = <value>
+password = <value>
+domain = <value>
GUEST
is used. OPERATIONS
NOTES
ENVIRONMENT VARIABLES
INSTALLATION
DIAGNOSTICS
VERSION
AUTHOR
smbcontrol [-i] [-i] [-s]DESCRIPTION
OPTIONS
close-share
,
- debug
,
- force-election
, ping
-
, Type of message to send. See
+ the section
profile
, debuglevel
, profilelevel
,
- or printnotify
.close-share
message-type sends a
- message to smbd which will then close the client connections to
- the named share. Note that this doesn't affect client connections
- to any other shares. This message-type takes an argument of the
- share name for which client connections will be closed, or the
- "*" character which will close all currently open shares.
- This may be useful if you made changes to the access controls on the share.
- This message can only be sent to any parameters required for the message-type
MESSAGE-TYPES
smbd
.debug
message-type allows
- the debug level to be set to the value specified by the
- parameter. This can be sent to any of the destinations.force-election
message-type can only be
- sent to the nmbd
destination. This message
- causes the This message causes the nmbd daemon to force a new browse
- master election.ping
message-type sends the
- number of "ping" messages specified by the parameter and waits
- for the same number of reply "pong" messages. This can be sent to
- any of the destinations.profile
message-type sends a
- message to an smbd to change the profile settings based on the
- parameter. The parameter can be "on" to turn on profile stats
- collection, "off" to turn off profile stats collection, "count"
- to enable only collection of count stats (time stats are
- disabled), and "flush" to zero the current profile stats. This can
- be sent to any smbd or nmbd destinations.debuglevel
message-type sends
- a "request debug level" message. The current debug level setting
- is returned by a "debuglevel" message. This can be
- sent to any of the destinations.profilelevel
message-type sends
- a "request profile level" message. The current profile level
- setting is returned by a "profilelevel" message. This can be sent
- to any smbd or nmbd destinations.printnotify
message-type sends a
- message to smbd which in turn sends a printer notify message to
- any Windows NT clients connected to a printer. This message-type
- takes the following arguments:
-
- smbd
.
- smbd
. smbd
. Should not be used manually.VERSION
SEE ALSO
AUTHOR
".client"
will be appended. The log file is
+never removed by the client.FILES
LIMITATIONS
ENVIRONMENT VARIABLES
PAM INTERACTION
VERSION
DIAGNOSTICS
SIGNALS
SEE ALSO
AUTHOR
smbmnt {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]AUTHOR
ENVIRONMENT VARIABLES
BUGS
SEE ALSO
AUTHOR
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) for details)
- then any name type matches for lookup.
-
EXAMPLES
VERSION
BUGS
SEE ALSO
AUTHOR
smbspool [job] [user] [title] [copies] [options] [filename] {job} {user} {title} {copies} {options} [filename]VERSION
".client"
will be appended. The log file is
+never removed by the client.VERSION
SEE ALSO
AUTHOR
smbtar {-s server} [-p password] [-x services] [-X] [-d directory] [-u user] [-t tape] [-t tape] [-b blocksize] [-N filename] [-i] [-r] [-l loglevel] [-v] {filenames} [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}
The Samba server uses TCP to talk to the client. Thus if you are @@ -111,8 +111,8 @@ CLASS="SECT1" >
There are a number of socket options that can greatly affect the @@ -139,8 +139,8 @@ CLASS="SECT1" >
The option "read size" affects the overlap of disk reads/writes with @@ -165,8 +165,8 @@ CLASS="SECT1" >
At startup the client and server negotiate a "maximum transmit" size, @@ -188,8 +188,8 @@ CLASS="SECT1" >
If you set the log level (also known as "debug level") higher than 2 @@ -202,8 +202,8 @@ CLASS="SECT1" >
The "read raw" operation is designed to be an optimised, low-latency @@ -224,8 +224,8 @@ CLASS="SECT1" >
The "write raw" operation is designed to be an optimised, low-latency @@ -241,8 +241,8 @@ CLASS="SECT1" >
One person has reported that setting the protocol to COREPLUS rather @@ -258,8 +258,8 @@ CLASS="SECT1" >
Slow logins are almost always due to the password checking time. Using @@ -271,8 +271,8 @@ CLASS="SECT1" >
Often a speed problem can be traced to the client. The client (for @@ -389,7 +389,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevAppendixesMigration from NT4 PDC to Samba-3 PDC
Prints the version number for +smbd.
The file specified contains the +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 smb.conf(5) for more information. +The default configuration file name is determined at +compile time.
debuglevel is an integer +from 0 to 10. The default value if this parameter is +not specified is zero.
The higher this value, the more detail will be +logged to the log files about the activities of the +server. At level 0, only critical errors and serious +warnings will be logged. Level 1 is a reasonable level for +day to day running - it generates a small amount of +information about operations carried out.
Levels above 1 will generate considerable +amounts of log data, and should only be used when +investigating a problem. Levels above 3 are designed for +use only by developers and generate HUGE amounts of log +data, most of which is extremely cryptic.
Note that specifying this parameter here will +override the log +level parameter in the smb.conf(5) file.
File name for log/debug files. The extension
+".client"
will be appended. The log file is
+never removed by the client.
Print a summary of command line options.
Swat is included as binary package with most distributions. The + package manager in this case takes care of the installation and + configuration. This section is only for those who have compiled + swat from scratch. +
After you compile SWAT you need to run make install @@ -185,7 +277,7 @@ CLASS="COMMAND" >
To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/".
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.
This man page is correct for version 2.2 of the Samba suite.
This man page is correct for version 3.0 of the Samba suite.Print usage message
Print a summary of command line options.Prints the version number for +smbd.
This man page is correct for version 2.2 of +>This man page is correct for version 3.0 of the Samba suite.
All access to Unix/Linux system file via Samba is controlled at + the operating system file access control level. When trying to + figure out file access problems it is vitally important to identify + the identity of the Windows user as it is presented by Samba at + the point of file access. This can best be determined from the + Samba log files. + |
From an NT4/2000/XP client, single-click with the right @@ -167,8 +199,8 @@ CLASS="SECT1" >
Clicking on the 11.4. Viewing file or directory permissions10.4. Viewing file or directory permissions
The third button is the 11.4.1. File Permissions10.4.1. File Permissions
The standard UNIX user/group/world triple and @@ -369,8 +401,8 @@ CLASS="SECT2" >
Directories on an NT NTFS file system have two @@ -401,8 +433,8 @@ CLASS="SECT1" >
Modifying file and directory permissions is as simple @@ -497,8 +529,8 @@ CLASS="SECT1" >
PrevSystem PoliciesAdvanced Configuration
Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. @@ -121,16 +121,16 @@ CLASS="SECT1" >
A simple module to audit file access to the syslog @@ -167,8 +167,30 @@ CLASS="SECT2" >
This module is identical with the audit module above except +that it sends audit logs to both syslog as well as the smbd log file/s. The +loglevel for this module is set in the smb.conf file. At loglevel = 0, only file +and directory deletions and directory and file creations are logged. At loglevel = 1 +file opens are renames and permission changes are logged , while at loglevel = 2 file +open and close calls are logged also.
A recycle-bin like modules. When used any unlink call @@ -238,8 +260,8 @@ CLASS="SECT2" >
A netatalk module, that will ease co-existence of samba and @@ -271,8 +293,8 @@ CLASS="SECT1" >
This section contains a listing of various other VFS modules that @@ -287,8 +309,8 @@ CLASS="SECT2" >
URL: 20.3.2. vscan19.3.2. vscan
URL: PrevNextHosting a Microsoft Distributed File System tree on SambaPAM Configuration for Centrally Managed Authentication
Print a summary of command line options.
File name for log/debug files. The extension
+ '.client'
will be appended. The log file is never removed
+ by the client.
+
Prints the version number for +smbd.
The file specified contains the +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 smb.conf(5) for more information. +The default configuration file name is determined at +compile time.
file.
Print a summary of command line options.
File name for log/debug files. The extension
- '.client'
will be appended. The log file is never removed
- by the client.
-
Show sequence numbers of + all known domains
Print username and password used by winbindd + during session setup to a domain controller. Username + and password can be set using '-A'. Only available for + root.
Check whether winbindd is still alive. + Prints out either 'succeeded' or 'failed'. +
Prints the version number for +smbd.
Print a summary of command line options.
Integration of UNIX and Microsoft Windows NT through @@ -107,8 +107,8 @@ CLASS="SECT1" >
It is well known that UNIX and Microsoft Windows NT have @@ -161,8 +161,8 @@ CLASS="SECT1" >
Winbind unifies UNIX and Windows NT account management by @@ -203,8 +203,8 @@ CLASS="SECT2" >
Winbind is targeted at organizations that have an @@ -227,8 +227,8 @@ CLASS="SECT1" >
The winbind system is designed around a client/server @@ -247,8 +247,8 @@ CLASS="SECT2" >
Over the last few years, efforts have been underway @@ -273,8 +273,8 @@ CLASS="SECT2" >
Since late 2001, Samba has gained the ability to @@ -292,8 +292,8 @@ CLASS="SECT2" >
The Name Service Switch, or NSS, is a feature that is @@ -372,8 +372,8 @@ CLASS="SECT2" >
Pluggable Authentication Modules, also known as PAM, @@ -421,8 +421,8 @@ CLASS="SECT2" >
When a user or group is created under Windows NT @@ -447,8 +447,8 @@ CLASS="SECT2" >
An active system can generate a lot of user and group @@ -470,8 +470,8 @@ CLASS="SECT1" >
Many thanks to John Trostel 16.5.1. Introduction14.5.1. Introduction
This HOWTO describes the procedures used to get winbind up and @@ -548,8 +548,8 @@ CLASS="SECT2" >
If you have a samba configuration file that you are currently @@ -618,8 +618,8 @@ CLASS="SECT2" >
Before starting, it is probably best to kill off all the SAMBA @@ -663,8 +663,8 @@ CLASS="SECT3" >
The configuration and compilation of SAMBA is pretty straightforward. @@ -729,8 +729,8 @@ CLASS="SECT3" >
Several parameters are needed in the smb.conf file to control @@ -909,8 +909,8 @@ CLASS="SECT3" >
Enter the following command to make the SAMBA server join the @@ -947,8 +947,8 @@ CLASS="SECT3" >
Eventually, you will want to modify your smb startup script to @@ -1083,16 +1083,16 @@ CLASS="SECT3" >
The 16.5.3.6.2. Solaris14.5.3.6.2. Solaris
On solaris, you need to modify the @@ -1285,8 +1285,8 @@ CLASS="SECT4" >
If you restart the 16.5.3.7. Configure Winbind and PAM14.5.3.7. Configure Winbind and PAM
If you have made it this far, you know that winbindd and samba are working @@ -1367,8 +1367,8 @@ CLASS="SECT4" >
The 16.5.3.7.2. Solaris-specific configuration14.5.3.7.2. Solaris-specific configuration
The /etc/pam.conf needs to be changed. I changed this file so that my Domain @@ -1583,8 +1583,8 @@ CLASS="SECT1" >
Winbind has a number of limitations in its current @@ -1625,8 +1625,8 @@ CLASS="SECT1" >
The winbind system, through the use of the Name Service @@ -1671,7 +1671,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextIntegrating MS Windows networks with SambaAdvanced Network Manangement
Sets the debuglevel to an integer between - 0 and 100. 0 is for no debugging and 100 is for reams and - reams. To submit a bug report to the Samba Team, use debug - level 100 (see BUGS.txt).
Prints the version number for +smbd.The file specified contains the +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 smb.conf(5) for more information. +The default configuration file name is determined at +compile time.
debuglevel is an integer +from 0 to 10. The default value if this parameter is +not specified is zero.
The higher this value, the more detail will be +logged to the log files about the activities of the +server. At level 0, only critical errors and serious +warnings will be logged. Level 1 is a reasonable level for +day to day running - it generates a small amount of +information about operations carried out.
Levels above 1 will generate considerable +amounts of log data, and should only be used when +investigating a problem. Levels above 3 are designed for +use only by developers and generate HUGE amounts of log +data, most of which is extremely cryptic.
Note that specifying this parameter here will +override the log +level parameter in the smb.conf(5) file.
File name for log/debug files. The extension
+".client"
will be appended. The log file is
+never removed by the client.
Print a summary of command line options.
Specifies the location of the all-important - smb.conf(5) file.
Client processes resolving names through the winbindd
- nsswitch module read an environment variable named $WINBINDD_DOMAIN. If this variable contains a comma separated
- list of Windows NT domain names, then winbindd will only resolve users
- and groups within those Windows NT domains. PAM is really easy to misconfigure. Make sure you know what
you are doing when modifying PAM configuration files. It is possible
to set up PAM such that you can no longer log into your system. The UNIX pipe over which 'privilaged' clients
+ communicate with the winbindd program. For security
+ reasons, access to some winbindd functions - like those needed by
+ the ntlm_auth utility - is restricted. By default,
+ only users in the 'root' group will get this access, however the administrator
+ may change the group permissions on $LOCKDIR/winbindd_privilaged to allow
+ programs like 'squid' to use ntlm_auth.
+ Note that the winbind client will only attempt to connect to the winbindd daemon
+ if both the $LOCKDIR/winbindd_privilaged directory
+ and $LOCKDIR/winbindd_privilaged/pipe file are owned by
+ root. NOTES
to become aware of new trust relationships between
servers, it must be sent a SIGHUP signal. SIGNALS
FILES