1 mailto(samba-bugs@samba.anu.edu.au)
3 manpage(smbclient)(1)(23 Oct 1998)(Samba)(SAMBA)
6 manpagename(smbclient)(ftp-like client to access SMB/CIFS resources on servers)
11 bf(smbclient) service [password] [-s smb.conf] [-B IP addr] [-O socket_options][-R name resolve order] [-M NetBIOS name] [-i scope] [-N] [-n NetBIOS name] [-d debuglevel] [-P] [-p port] [-l log basename] [-h] [-I dest IP] [-E] [-U username] [-L NetBIOS name] [-t terminal code] [-m max protocol] [-W workgroup] [-T<c|x>IXFqgbNan] [-D directory] [-c command string]
16 This program is part of the bf(Samba) suite.
18 bf(smbclient) is a client that can 'talk' to an SMB/CIFS server. It
19 offers an interface similar to that of the ftp program (see bf(ftp
20 (1))). Operations include things like getting files from the server
21 to the local machine, putting files from the local machine to the
22 server, retrieving directory information from the server and so on.
29 dit(bf(servicename)) servicename is the name of the service you want
30 to use on the server. A service name takes the form
31 tt(//server/service) where em(server) is the NetBIOS name of the SMB/CIFS
32 server offering the desired service and em(service) is the name
33 of the service offered. Thus to connect to the service em(printer) on
34 the SMB/CIFS server em(smbserver), you would use the servicename
36 tt(//smbserver/printer)
38 Note that the server name required is NOT necessarily the IP (DNS)
39 host name of the server ! The name required is a NetBIOS server name,
40 which may or may not be the same as the IP hostname of the machine
43 The server name is looked up according to the url(bf(name resolve
44 order))(smbclient.1.html#name_resolve_order) parameter in the smb.conf
45 file, allowing an administrator to change the order and methods by
46 which server names are looked up.
48 dit(bf(password)) password is the password required to access the
49 specified service on the specified server. If this parameter is
50 supplied, the bf(-N) option (suppress password prompt) is assumed.
52 There is no default password. If no password is supplied on the
53 command line (either by using this parameter or adding a password to
54 the bf(-U) option (see below)) and the bf(-N) option is not specified,
55 the client will prompt for a password, even if the desired service
56 does not require one. (If no password is required, simply press ENTER
57 to provide a null password.)
59 Note: Some servers (including OS/2 and Windows for Workgroups) insist
60 on an uppercase password. Lowercase or mixed case passwords may be
61 rejected by these servers.
63 Be cautious about including passwords in scripts.
65 dit(bf(-s smb.conf)) This parameter specifies the pathname to the
66 Samba configuration file, smb.conf. This file controls all aspects of
67 the Samba setup on the machine and smbclient also needs to read this
70 dit(bf(-B IP addr)) The IP address to use when sending a broadcast packet.
72 dit(bf(-O socket_options)) TCP socket options to set on the client
73 socket. See the url(socket options)(smb.conf.5.html#socket options)
74 parameter in the url(bf(smb.conf (5)))(smb.conf.5.html) manpage for
75 the list of valid options.
77 label(name_resolve_order)
78 dit(bf(-R name resolve order)) This option allows the user of
79 smbclient to determine what name resolution services to use when
80 looking up the NetBIOS name of the host being connected to.
82 The options are :"lmhosts", "host", "wins" and "bcast". They cause
83 names to be resolved as follows :
87 it() bf(lmhosts) : Lookup an IP address in the Samba lmhosts file.
89 it() bf(host) : Do a standard host name to IP address resolution,
90 using the system /etc/hosts, NIS, or DNS lookups. This method of name
91 resolution is operating system depended for instance on IRIX or
92 Solaris this may be controlled by the em(/etc/nsswitch.conf) file).
94 it() bf(wins) : Query a name with the IP address listed in the bf(wins
95 server) parameter in the smb.conf file. If no WINS server has been
96 specified this method will be ignored.
98 it() bf(bcast) : Do a broadcast on each of the known local interfaces
99 listed in the bf(interfaces) parameter in the smb.conf file. This is
100 the least reliable of the name resolution methods as it depends on the
101 target host being on a locally connected subnet. To specify a
102 particular broadcast address the bf(-B) option may be used.
106 The default order is lmhosts, host, wins, bcast and without this
107 parameter the name resolution methods will be attempted in this order.
109 dit(bf(-M NetBIOS name)) This options allows you to send messages,
110 using the "WinPopup" protocol, to another computer. Once a connection
111 is established you then type your message, pressing ^D (control-D) to
114 If the receiving computer is running WinPopup the user will receive
115 the message and probably a beep. If they are not running WinPopup the
116 message will be lost, and no error message will occur.
118 The message is also automatically truncated if the message is over
119 1600 bytes, as this is the limit of the protocol.
121 One useful trick is to cat the message through bf(smbclient).
124 tt(cat mymessage.txt | smbclient -M FRED)
126 will send the message in the file em(mymessage.txt) to the machine FRED.
128 You may also find the bf(-U) and bf(-I) options useful, as they allow
129 you to control the FROM and TO parts of the message.
131 See the message command section of bf(smb.conf (5)) for a description
132 of how to handle incoming WinPopup messages in Samba.
134 Note: Copy WinPopup into the startup group on your WfWg PCs if you
135 want them to always be able to receive messages.
137 dit(bf(-i scope)) This specifies a NetBIOS scope that smbclient will use
138 to communicate with when generating NetBIOS names. For details on the
139 use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes
140 are em(very) rarely used, only set this parameter if you are the
141 system administrator in charge of all the NetBIOS systems you
144 dit(bf(-N)) If specified, this parameter suppresses the normal
145 password prompt from the client to the user. This is useful when
146 accessing a service that does not require a password.
148 Unless a password is specified on the command line or this parameter
149 is specified, the client will request a password.
151 dit(bf(-n NetBIOS name)) By default, the client will use the local
152 machine's hostname (in uppercase) as its NetBIOS name. This parameter
153 allows you to override the host name and use whatever NetBIOS name you
157 dit(bf(-d debuglevel)) debuglevel is an integer from 0 to 10, or the
160 The default value if this parameter is not specified is zero.
162 The higher this value, the more detail will be logged to the log files
163 about the activities of the client. At level 0, only critical errors
164 and serious warnings will be logged. Level 1 is a reasonable level for
165 day to day running - it generates a small amount of information about
166 operations carried out.
168 Levels above 1 will generate considerable amounts of log data, and
169 should only be used when investigating a problem. Levels above 3 are
170 designed for use only by developers and generate HUGE amounts of log
171 data, most of which is extremely cryptic. If debuglevel is set to the
172 letter 'A', then em(all) debug messages will be printed. This setting
173 is for developers only (and people who em(really) want to know how the
174 code works internally).
176 dit(bf(-P)) If this option is specified, the service requested will be
177 connected to as a printer service rather than as a normal filespace
178 service. Operations such as put and get will not be applicable for
181 By default, services will be connected to as NON-printer services.
183 dit(bf(-p port)) This number is the TCP port number that will be used
184 when making connections to the server. The standard (well-known) TCP
185 port number for an SMB/CIFS server is 139, which is the default.
187 dit(bf(-l logfilename)) If specified, logfilename specifies a base
188 filename into which operational data from the running client will be
191 The default base name is specified at compile time.
193 The base name is used to generate actual log file names. For example,
194 if the name specified was "log", the debug file would be
197 The log file generated is never removed by the client.
199 dit(bf(-h)) Print the usage message for the client.
201 dit(bf(-I IP address)) IP address is the address of the server to
202 connect to. It should be specified in standard "a.b.c.d" notation.
204 Normally the client would attempt to locate a named SMB/CIFS server by
205 looking it up via the NetBIOS name resolution mechanism described
206 above in the url(bf(name resolve order))(smbclient.1.html#name_resolve_order) parameter
207 above. Using this parameter will force the client to assume that the
208 server is on the machine with the specified IP address and the NetBIOS
209 name component of the resource being connected to will be ignored.
211 There is no default for this parameter. If not supplied, it will be
212 determined automatically by the client as described above.
214 dit(bf(-E)) This parameter causes the client to write messages to the
215 standard error stream (stderr) rather than to the standard output
218 By default, the client writes messages to standard output - typically
221 dit(bf(-U username)) This specifies the user name that will be used by
222 the client to make a connection, assuming your server is not a downlevel
223 server that is running a protocol level that uses passwords on shares,
226 Some servers are fussy about the case of this name, and some insist
227 that it must be a valid NetBIOS name.
229 If no username is supplied, it will default to an uppercase version of
230 the environment variable tt(USER) or tt(LOGNAME) in that order. If no
231 username is supplied and neither environment variable exists the
232 username "GUEST" will be used.
234 If the tt(USER) environment variable containts a '%' character,
235 everything after that will be treated as a password. This allows you
236 to set the environment variable to be tt(USER=username%password) so
237 that a password is not passed on the command line (where it may be
238 seen by the ps command).
240 If the service you are connecting to requires a password, it can be
241 supplied using the bf(-U) option, by appending a percent symbol ("%")
242 then the password to username. For example, to attach to a service as
243 user tt("fred") with password tt("secret"), you would specify. nl()
245 tt(-U fred%secret) nl()
247 on the command line. Note that there are no spaces around the percent
250 If you specify the password as part of username then the bf(-N) option
251 (suppress password prompt) is assumed.
253 If you specify the password as a parameter em(AND) as part of username
254 then the password as part of username will take precedence. Putting
255 nothing before or nothing after the percent symbol will cause an empty
256 username or an empty password to be used, respectively.
258 The password may also be specified by setting up an environment
259 variable called tt(PASSWORD) that contains the users password. Note
260 that this may be very insecure on some systems but on others allows
261 users to script smbclient commands without having a password appear in
262 the command line of a process listing.
264 Note: Some servers (including OS/2 and Windows for Workgroups) insist
265 on an uppercase password. Lowercase or mixed case passwords may be
266 rejected by these servers.
268 Be cautious about including passwords in scripts or in the
269 tt(PASSWORD) environment variable. Also, on many systems the command
270 line of a running process may be seen via the tt(ps) command to be
271 safe always allow smbclient to prompt for a password and type it in
274 dit(bf(-L)) This option allows you to look at what services are
275 available on a server. You use it as tt("smbclient -L host") and a
276 list should appear. The bf(-I) option may be useful if your NetBIOS
277 names don't match your tcp/ip dns host names or if you are trying to
278 reach a host on another network.
280 dit(bf(-t terminal code)) This option tells smbclient how to interpret
281 filenames coming from the remote server. Usually Asian language
282 multibyte UNIX implementations use different character sets than
283 SMB/CIFS servers (em(EUC) instead of em(SJIS) for example). Setting
284 this parameter will let smbclient convert between the UNIX filenames
285 and the SMB filenames correctly. This option has not been seriously
286 tested and may have some problems.
288 The terminal codes include tt(sjis), tt(euc), tt(jis7), tt(jis8),
289 tt(junet), tt(hex), tt(cap). This is not a complete list, check the
290 Samba source code for the complete list.
292 dit(bf(-m max protocol level)) Normally, smbclient will negotiate with
293 the server to use the most advanced version of the SMB/CIFS protocol
294 that the server supports. Occasionaly it may be desirable to tell
295 smbclient to negotiate a lower level of the protocol, hence this
296 parameter. Valid options for the em(max protocol level) are :
312 dit(bf(-W WORKGROUP)) Override the default workgroup specified in
313 smb.conf for this connection. This may be needed to connect to some
316 label(minus_T) dit(bf(-T tar options)) smbclient may be used to create
317 bf(tar (1)) compatible backups of all the files on an SMB/CIFS
318 share. The secondary tar flags that can be given to this option are :
322 dit(bf(c)) Create a tar file on UNIX. Must be followed by the
323 name of a tar file, tape device or tt("-") for standard output. If
324 using standard output you must turn the log level to its lowest value
325 tt(-d0) to avoid corrupting your tar file. This flag is
326 mutually exclusive with the bf(x) flag.
328 dit(bf(x)) Extract (restore) a local tar file back to a
329 share. Unless the bf(-D) option is given, the tar files will be
330 restored from the top level of the share. Must be followed by the name
331 of the tar file, device or tt("-") for standard input. Mutually exclusive
332 with the bf(c) flag. Restored files have theuir creation times (mtime)
333 set to the date saved in the tar file. Directories currently do not
334 get their creation dates restored properly.
336 dit(bf(I)) Include files and directories. Is the default
337 behaviour when filenames are specified above. Causes tar files to
338 be included in an extract or create (and therefore everything else to
339 be excluded). See example below. Filename globbing does not work for
340 included files for extractions (yet).
342 dit(bf(X)) Exclude files and directories. Causes tar files to
343 be excluded from an extract or create. See example below. Filename
344 globbing does not work for excluded files (yet).
346 dit(bf(b)) Blocksize. Must be followed by a valid (greater than
347 zero) blocksize. Causes tar file to be written out in
348 blocksize*TBLOCK (usually 512 byte) blocks.
350 dit(bf(g)) Incremental. Only back up files that have the
351 archive bit set. Useful only with the bf(c) flag.
353 dit(bf(q)) Quiet. Keeps tar from printing diagnostics as it
354 works. This is the same as tarmode quiet.
356 dit(bf(N)) Newer than. Must be followed by the name of a file
357 whose date is compared against files found on the share during a
358 create. Only files newer than the file specified are backed up to the
359 tar file. Useful only with the bf(c) flag.
361 dit(bf(a)) Set archive bit. Causes the archive bit to be reset
362 when a file is backed up. Useful with the bf(g) and bf(c) flags.
366 em(Tar Long File Names)
368 smbclient's tar option now supports long file names both on backup and
369 restore. However, the full path name of the file must be less than
370 1024 bytes. Also, when a tar archive is created, smbclient's tar
371 option places all files in the archive with relative names, not
376 All file names can be given as DOS path names (with tt(\) as the
377 component separator) or as UNIX path names (with tt(/) as the
378 component separator).
384 it() Restore from tar file backup.tar into myshare on mypc (no password on share).
386 tt(smbclient //mypc/myshare "" -N -Tx backup.tar)
388 it() Restore everything except users/docs
390 tt(smbclient //mypc/myshare "" -N -TXx backup.tar users/docs)
392 it() Create a tar file of the files beneath users/docs.
394 tt(smbclient //mypc/myshare "" -N -Tc backup.tar users/docs)
396 it() Create the same tar file as above, but now use a DOS path name.
398 tt(smbclient //mypc/myshare "" -N -tc backup.tar users\edocs)
400 it() Create a tar file of all the files and directories in the share.
402 tt(smbclient //mypc/myshare "" -N -Tc backup.tar *)
406 dit(bf(-D initial directory)) Change to initial directory before
407 starting. Probably only of any use with the tar bf(-T) option.
409 dit(bf(-c command string)) command string is a semicolon separated
410 list of commands to be executed instead of prompting from stdin.
411 bf(-N) is implied by bf(-c).
413 This is particularly useful in scripts and for printing stdin to the
414 server, e.g. tt(-c 'print -').
419 manpagesection(OPERATIONS)
421 Once the client is running, the user is presented with a prompt :
425 The backslash ("\") indicates the current working directory on the
426 server, and will change if the current working directory is changed.
428 The prompt indicates that the client is ready and waiting to carry out
429 a user command. Each command is a single word, optionally followed by
430 parameters specific to that command. Command and parameters are
431 space-delimited unless these notes specifically state otherwise. All
432 commands are case-insensitive. Parameters to commands may or may not
433 be case sensitive, depending on the command.
435 You can specify file names which have spaces in them by quoting the
436 name with double quotes, for example "a long file name".
438 Parameters shown in square brackets (eg., "[parameter]") are
439 optional. If not given, the command will use suitable
440 defaults. Parameters shown in angle brackets (eg., "<parameter>") are
443 Note that all commands operating on the server are actually performed
444 by issuing a request to the server. Thus the behaviour may vary from
445 server to server, depending on how the server was implemented.
447 The commands available are given here in alphabetical order.
451 label(questionmark) dit(bf(? [command])) If "command" is specified,
452 the bf(?) command will display a brief informative message about the
453 specified command. If no command is specified, a list of available
454 commands will be displayed.
456 label(exclaimationmark) dit(bf(! [shell command])) If "shell command"
457 is specified, the bf(!) command will execute a shell locally and run
458 the specified shell command. If no command is specified, a local shell
461 label(cd) dit(bf(cd [directory name])) If "directory name" is
462 specified, the current working directory on the server will be changed
463 to the directory specified. This operation will fail if for any reason
464 the specified directory is inaccessible.
466 If no directory name is specified, the current working directory on
467 the server will be reported.
469 label(del) dit(bf(del <mask>)) The client will request that the server
470 attempt to delete all files matching "mask" from the current working
471 directory on the server.
473 label(dir) dit(bf(dir <mask>)) A list of the files matching "mask" in
474 the current working directory on the server will be retrieved from the
475 server and displayed.
477 label(exit) dit(bf(exit)) Terminate the connection with the server and
478 exit from the program.
480 label(get) dit(bf(get <remote file name> [local file name])) Copy the
481 file called "remote file name" from the server to the machine running
482 the client. If specified, name the local copy "local file name". Note
483 that all transfers in smbclient are binary. See also the
484 link(bf(lowercase))(lowercase) command.
486 label(help) dit(bf(help [command])) See the link(bf(?))(questionmark)
489 label(lcd) dit(bf(lcd [directory name])) If "directory name" is
490 specified, the current working directory on the local machine will
491 be changed to the directory specified. This operation will fail if for
492 any reason the specified directory is inaccessible.
494 If no directory name is specified, the name of the current working
495 directory on the local machine will be reported.
497 label(lowercase) dit(bf(lowercase)) Toggle lowercasing of filenames
498 for the link(bf(get))(get) and link(bf(mget))(mget) commands.
500 When lowercasing is toggled ON, local filenames are converted to
501 lowercase when using the link(bf(get))(get) and link(bf(mget))(mget)
502 commands. This is often useful when copying (say) MSDOS files from a
503 server, because lowercase filenames are the norm on UNIX systems.
505 label(ls) dit(bf(ls <mask>)) See the link(bf(dir))(dir) command above.
507 label(mask) dit(bf(mask <mask>)) This command allows the user to set
508 up a mask which will be used during recursive operation of the
509 link(bf(mget))(mget) and link(bf(mput))(mput) commands.
511 The masks specified to the link(bf(mget))(mget) and
512 link(bf(mput))(mput) commands act as filters for directories rather
513 than files when recursion is toggled ON.
515 The mask specified with the .B mask command is necessary to filter
516 files within those directories. For example, if the mask specified in
517 an link(bf(mget))(mget) command is "source*" and the mask specified
518 with the mask command is "*.c" and recursion is toggled ON, the
519 link(bf(mget))(mget) command will retrieve all files matching "*.c" in
520 all directories below and including all directories matching "source*"
521 in the current working directory.
523 Note that the value for mask defaults to blank (equivalent to "*") and
524 remains so until the mask command is used to change it. It retains the
525 most recently specified value indefinitely. To avoid unexpected
526 results it would be wise to change the value of .I mask back to "*"
527 after using the link(bf(mget))(mget) or link(bf(mput))(mput) commands.
529 label(md) dit(bf(md <directory name>)) See the link(bf(mkdir))(mkdir)
532 label(mget) dit(bf(mget <mask>)) Copy all files matching mask from the
533 server to the machine running the client.
535 Note that mask is interpreted differently during recursive operation
536 and non-recursive operation - refer to the link(bf(recurse))(recurse)
537 and link(bf(mask))(mask) commands for more information. Note that all
538 transfers in .B smbclient are binary. See also the
539 link(bf(lowercase))(lowercase) command.
541 label(mkdir) dit(bf(mkdir <directory name>)) Create a new directory on
542 the server (user access privileges permitting) with the specified
545 label(mput) dit(bf(mput <mask>)) Copy all files matching mask in
546 the current working directory on the local machine to the current
547 working directory on the server.
549 Note that mask is interpreted differently during recursive operation
550 and non-recursive operation - refer to the link(bf(recurse))(recurse)
551 and link(bf(mask))(mask) commands for more information. Note that all
552 transfers in .B smbclient are binary.
554 label(print) dit(bf(print <file name>)) Print the specified file
555 from the local machine through a printable service on the server.
557 See also the link(bf(printmode))(printmode) command.
559 label(printmode) dit(bf(printmode <graphics or text>)) Set the print
560 mode to suit either binary data (such as graphical information) or
561 text. Subsequent print commands will use the currently set print
564 label(prompt) dir(bf(prompt)) Toggle prompting for filenames during
565 operation of the link(bf(mget))(mget) and link(bf(mput))(mput)
568 When toggled ON, the user will be prompted to confirm the transfer of
569 each file during these commands. When toggled OFF, all specified files
570 will be transferred without prompting.
572 label(put) dit(bf(put <local file name> [remote file name])) Copy the
573 file called "local file name" from the machine running the client to
574 the server. If specified, name the remote copy "remote file name".
575 Note that all transfers in smbclient are binary. See also the
576 link(bf(lowercase))(lowercase) command.
578 label(queue) dir(bf(queue)) Displays the print queue, showing the job
579 id, name, size and current status.
581 label(quit) dit(bf(quit)) See the link(bf(exit))(exit) command.
583 label(rd) dir(bf(rd <directory name>)) See the link(bf(rmdir))(rmdir)
586 label(recurse) dir(bf(recurse)) Toggle directory recursion for the
587 commands link(bf(mget))(mget) and link(bf(mput))(mput).
589 When toggled ON, these commands will process all directories in the
590 source directory (i.e., the directory they are copying .IR from ) and
591 will recurse into any that match the mask specified to the
592 command. Only files that match the mask specified using the
593 link(bf(mask))(mask) command will be retrieved. See also the
594 link(bf(mask))(mask) command.
596 When recursion is toggled OFF, only files from the current working
597 directory on the source machine that match the mask specified to the
598 link(bf(mget))(mget) or link(bf(mput))(mput) commands will be copied,
599 and any mask specified using the link(bf(mask))(mask) command will be
602 label(rm) dir(bf(rm <mask>)) Remove all files matching mask from
603 the current working directory on the server.
605 label(rmdir) dit(bf(rmdir <directory name>)) Remove the specified
606 directory (user access privileges permitting) from the server.
608 label(tar) dit(bf(tar <c|x>[IXbgNa])) Performs a tar operation - see
609 the url(bf(-T))(smbclient.1.html#minus_T) command line option
610 above. Behaviour may be affected by the link(bf(tarmode))(tarmode)
611 command (see below). Using g (incremental) and N (newer) will affect
612 tarmode settings. Note that using the "-" option with tar x may not
613 work - use the command line option instead.
615 label(blocksize) dit(bf(blocksize <blocksize>)) Blocksize. Must be
616 followed by a valid (greater than zero) blocksize. Causes tar file to
617 be written out in blocksize*TBLOCK (usually 512 byte) blocks.
619 label(tarmode) dir(bf(tarmode <full|inc|reset|noreset>)) Changes tar's
620 behaviour with regard to archive bits. In full mode, tar will back up
621 everything regardless of the archive bit setting (this is the default
622 mode). In incremental mode, tar will only back up files with the
623 archive bit set. In reset mode, tar will reset the archive bit on all
624 files it backs up (implies read/write share).
626 label(setmode) dit(bf(setmode <filename> <perm=[+|\-]rsha>)) A version
627 of the DOS attrib command to set file permissions. For example:
629 tt(setmode myfile +r)
631 would make myfile read only.
636 manpagesection(NOTES)
638 Some servers are fussy about the case of supplied usernames,
639 passwords, share names (aka service names) and machine names. If you
640 fail to connect try giving all parameters in uppercase.
642 It is often necessary to use the -n option when connecting to some
643 types of servers. For example OS/2 LanManager insists on a valid
644 NetBIOS name being used, so you need to supply a valid name that would
645 be known to the server.
647 smbclient supports long file names where the server supports the
648 LANMAN2 protocol or above.
650 label(ENVIRONMENT VARIABLES)
651 manpagesection(ENVIRONMENT VARIABLES)
653 The variable bf(USER) may contain the username of the person using the
654 client. This information is used only if the protocol level is high
655 enough to support session-level passwords.
657 The variable bf(PASSWORD) may contain the password of the person using
658 the client. This information is used only if the protocol level is
659 high enough to support session-level passwords.
662 manpagesection(INSTALLATION)
664 The location of the client program is a matter for individual system
665 administrators. The following are thus suggestions only.
667 It is recommended that the smbclient software be installed in the
668 /usr/local/samba/bin or /usr/samba/bin directory, this directory
669 readable by all, writeable only by root. The client program itself
670 should be executable by all. The client should em(NOT) be setuid or
673 The client log files should be put in a directory readable and
674 writable only by the user.
676 To test the client, you will need to know the name of a running
677 SMB/CIFS server. It is possible to run url(bf(smbd (8)))(smbd.8.html)
678 an ordinary user - running that server as a daemon on a
679 user-accessible port (typically any port number over 1024) would
680 provide a suitable test server.
683 manpagesection(DIAGNOSTICS)
685 Most diagnostics issued by the client are logged in a specified log
686 file. The log file name is specified at compile time, but may be
687 overridden on the command line.
689 The number and nature of diagnostics available depends on the debug
690 level used by the client. If you have problems, set the debug level to
691 3 and peruse the log files.
694 manpagesection(VERSION)
696 This man page is correct for version 2.0 of the Samba suite.
701 The original Samba software and related utilities were created by
702 Andrew Tridgell email(samba-bugs@samba.anu.edu.au). Samba is now developed
703 by the Samba Team as an Open Source project similar to the way the
704 Linux kernel is developed.
706 The original Samba man pages were written by Karl Auer. The man page
707 sources were converted to YODL format (another excellent piece of Open
708 Source software) and updated for the Samba2.0 release by Jeremy
709 Allison, email(samba-bugs@samba.anu.edu.au).
711 See url(bf(samba (7)))(samba.7.html) to find out how to get a full
712 list of contributors and details on how to submit bug reports,