7 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.57"></HEAD
27 >nmbd
--
NetBIOS name server to provide NetBIOS
28 over IP naming services to clients
</DIV
30 CLASS=
"REFSYNOPSISDIV"
40 > [-D] [-a] [-o] [-P] [-h] [-V] [-d
<debug level
>] [-H
<lmhosts file
>] [-l
<log file
>] [-n
<primary netbios name
>] [-p
<port number
>] [-s
<configuration file
>]
</P
50 >This program is part of the Samba suite.
</P
55 > is a server that understands
56 and can reply to NetBIOS over IP name service requests, like
57 those produced by SMB/CIFS clients such as Windows
95/
98/ME,
58 Windows NT, Windows
2000, and LanManager clients. It also
59 participates in the browsing protocols which make up the
60 Windows
"Network Neighborhood" view.
</P
62 >SMB/CIFS clients, when they start up, may wish to
63 locate an SMB/CIFS server. That is, they wish to know what
64 IP number a specified host is using.
</P
66 >Amongst other services,
<B
70 listen for such requests, and if its own NetBIOS name is
71 specified it will respond with the IP number of the host it
72 is running on. Its
"own NetBIOS name" is by
73 default the primary DNS name of the host it is running on,
74 but this can be overridden with the
<EM
77 option (see OPTIONS below). Thus
<B
81 reply to broadcast queries for its own name(s). Additional
85 > to respond on can be set
86 via parameters in the
<A
87 HREF=
"smb.conf.5.html"
93 > configuration file.
</P
98 > can also be used as a WINS
99 (Windows Internet Name Server) server. What this basically means
100 is that it will act as a WINS database server, creating a
101 database from name registration requests that it receives and
102 replying to queries from clients for these names.
</P
108 proxy, relaying broadcast queries from clients that do
109 not understand how to talk the WINS protocol to a WIN
128 >If specified, this parameter causes
132 > to operate as a daemon. That is,
133 it detaches itself and runs in the background, fielding
134 requests on the appropriate port. By default,
<B
138 will operate as a daemon if launched from a command shell.
139 nmbd can also be operated from the
<B
143 meta-daemon, although this is not recommended.
150 >If this parameter is specified, each new
151 connection will append log messages to the log file.
152 This is the default.
</P
158 >If this parameter is specified, the
159 log files will be overwritten when opened. By default,
163 > will append entries to the log
170 >Prints the help information (usage)
177 >-H
<filename
></DT
180 >NetBIOS lmhosts file. The lmhosts
181 file is a list of NetBIOS names to IP addresses that
182 is loaded by the nmbd server and used via the name
183 resolution mechanism
<A
184 HREF=
"smb.conf.5.html#nameresolveorder"
186 > name resolve order
</A
188 HREF=
"smb.conf.5.html"
195 to resolve any NetBIOS name queries needed by the server. Note
196 that the contents of this file are
<EM
202 > to answer any name queries.
203 Adding a line to this file affects name NetBIOS resolution
208 >The default path to this file is compiled into
209 Samba as part of the build process. Common defaults
212 >/usr/local/samba/lib/lmhosts
</TT
216 >/usr/samba/lib/lmhosts
</TT
222 HREF=
"lmhosts.5.html"
228 > man page for details on the
229 contents of this file.
</P
235 >Prints the version number for
242 >-d
<debug level
></DT
245 >debuglevel is an integer
246 from
0 to
10. The default value if this parameter is
247 not specified is zero.
</P
249 >The higher this value, the more detail will
250 be logged to the log files about the activities of the
251 server. At level
0, only critical errors and serious
252 warnings will be logged. Level
1 is a reasonable level for
253 day to day running - it generates a small amount of
254 information about operations carried out.
</P
256 >Levels above
1 will generate considerable amounts
257 of log data, and should only be used when investigating
258 a problem. Levels above
3 are designed for use only by developers
259 and generate HUGE amounts of log data, most of which is extremely
262 >Note that specifying this parameter here will override
264 HREF=
"smb.conf.5.html#loglevel"
269 HREF=
"smb.conf.5.html"
278 >-l
<log file
></DT
281 >The -l parameter specifies a path
282 and base filename into which operational data from
287 be logged. The actual log file name is generated by
288 appending the extension
".nmb" to the specified base
289 name. For example, if the name specified was
"log"
290 then the file log.nmb would contain the debugging data.
</P
292 >The default log file path is compiled into Samba as
293 part of the build process. Common defaults are
<TT
295 > /usr/local/samba/var/log.nmb
</TT
298 > /usr/samba/var/log.nmb
</TT
302 >/var/log/log.nmb
</TT
306 >-n
<primary NetBIOS name
></DT
309 >This option allows you to override
310 the NetBIOS name that Samba uses for itself. This is identical
312 HREF=
"smb.conf.5.html#netbiosname"
315 > parameter in the
<A
316 HREF=
"smb.conf.5.html"
323 > file. However, a command
324 line setting will take precedence over settings in
331 >-p
<UDP port number
></DT
334 >UDP port number is a positive integer value.
335 This option changes the default UDP port number (normally
137)
339 > responds to name queries on. Don't
340 use this option unless you are an expert, in which case you
344 >-s
<configuration file
></DT
347 >The default configuration file name
348 is set at build time, typically as
<TT
350 > /usr/local/samba/lib/smb.conf
</TT
352 this may be changed when Samba is autoconfigured.
</P
354 >The file specified contains the configuration details
355 required by the server. See
<A
356 HREF=
"smb.conf.5.html"
363 > for more information.
388 >If the server is to be run by the
392 > meta-daemon, this file
393 must contain suitable startup information for the
394 meta-daemon. See the section INSTALLATION below.
404 >or whatever initialization script your
407 >If running the server as a daemon at startup,
408 this file will need to contain an appropriate startup
409 sequence for the server. See the section INSTALLATION
419 >If running the server via the
424 must contain a mapping of service name (e.g., netbios-ssn)
425 to service port (e.g.,
139) and protocol type (e.g., tcp).
426 See the section INSTALLATION below.
</P
431 >/usr/local/samba/lib/smb.conf
</TT
435 >This is the default location of the
437 HREF=
"smb.conf.5.html"
444 server configuration file. Other common places that systems
445 install this file are
<TT
447 >/usr/samba/lib/smb.conf
</TT
454 >When run as a WINS server (see the
456 HREF=
"smb.conf.5.html#winssupport"
461 HREF=
"smb.conf.5.html"
471 will store the WINS database in the file
<TT
478 > directory configured under
479 wherever Samba was configured to install itself.
</P
487 HREF=
"smb.conf.5.html#localmaster"
492 HREF=
"smb.conf.5.html"
502 will store the browsing database in the file
<TT
510 configured under wherever Samba was configured to install itself.
527 > process it is recommended
528 that SIGKILL (-
9)
<EM
530 > be used, except as a last
531 resort, as this may leave the name database in an inconsistent state.
532 The correct way to terminate
<B
536 a SIGTERM (-
15) signal and wait for it to die on its own.
</P
541 > will accept SIGHUP, which will cause
542 it to dump out it's namelists into the file
<TT
548 >/usr/local/samba/var/locks
</TT
550 directory (or the
<TT
553 > directory configured
554 under wherever Samba was configured to install itself). This will also
558 > to dump out it's server database in
562 > file. In addition, the debug log level
563 of nmbd may be raised by sending it a SIGUSR1 (
<B
566 <nmbd-pid
></B
567 >) and lowered by sending it a
570 >kill -USR2
<nmbd-pid
></B
572 allow transient problems to be diagnosed, whilst still running at a
573 normally low log level.
</P
583 >This man page is correct for version
2.2 of
606 HREF=
"smb.conf.5.html"
614 HREF=
"smbclient.1.html"
622 HREF=
"testparm.1.html"
629 HREF=
"testprns.1.html"
635 >, and the Internet RFC's
643 In addition the CIFS (formerly SMB) specification is available
644 as a link from the Web page
<A
645 HREF=
"http://samba.org/cifs/"
648 http://samba.org/cifs/
</A
659 >The original Samba software and related utilities
660 were created by Andrew Tridgell. Samba is now developed
661 by the Samba Team as an Open Source project similar
662 to the way the Linux kernel is developed.
</P
664 >The original Samba man pages were written by Karl Auer.
665 The man page sources were converted to YODL format (another
666 excellent piece of Open Source software, available at
668 HREF=
"ftp://ftp.icce.rug.nl/pub/unix/"
670 > ftp://ftp.icce.rug.nl/pub/unix/
</A
671 >) and updated for the Samba
2.0
672 release by Jeremy Allison. The conversion to DocBook for
673 Samba
2.2 was done by Gerald Carter
</P