- Timestamp:
- Mar 1, 2010, 3:05:48 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/manpages/smbclient.1.html
r368 r411 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbclient</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.7 5.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="smbclient"><a name="smbclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbclient — ftp-like client to access SMB/CIFS resources2 on servers</p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbclient</code> [-b <buffer size>] [-d debuglevel] [-e] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]</p></div><div class="cmdsynopsis"><p><code class="literal">smbclient</code> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-l log-basename] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]</p></div></div><div class="refsect1" title="DESCRIPTION"><a name="id2489739"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbclient</code> is a client that can1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbclient</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbclient — ftp-like client to access SMB/CIFS resources 2 on servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbclient</code> [-b <buffer size>] [-d debuglevel] [-e] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]</p></div><div class="cmdsynopsis"><p><code class="literal">smbclient</code> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-l log-basename] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]</p></div></div><div class="refsect1" lang="en"><a name="id2483756"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbclient</code> is a client that can 3 3 'talk' to an SMB/CIFS server. It offers an interface 4 4 similar to that of the ftp program (see <a class="citerefentry" href="ftp.1.html"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a>). … … 6 6 to the local machine, putting files from the local machine to 7 7 the server, retrieving directory information from the server 8 and so on. </p></div><div class="refsect1" title="OPTIONS"><a name="id2489779"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service8 and so on. </p></div><div class="refsect1" lang="en"><a name="id2483795"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service 9 9 you want to use on the server. A service name takes the form 10 10 <code class="filename">//server/service</code> where <em class="parameter"><code>server … … 41 41 host names to IP addresses. The option takes a space-separated 42 42 string of different name resolution options.</p><p>The options are :"lmhosts", "host", "wins" and "bcast". They 43 cause names to be resolved as follows:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="constant">lmhosts</code>: Lookup an IP43 cause names to be resolved as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="constant">lmhosts</code>: Lookup an IP 44 44 address in the Samba lmhosts file. If the line in lmhosts has 45 45 no name type attached to the NetBIOS name (see 46 46 the <a class="citerefentry" href="lmhosts.5.html"><span class="citerefentry"><span class="refentrytitle">lmhosts</span>(5)</span></a> for details) then 47 any name type matches for lookup.</p></li><li class="listitem"><p><code class="constant">host</code>: Do a standard host47 any name type matches for lookup.</p></li><li><p><code class="constant">host</code>: Do a standard host 48 48 name to IP address resolution, using the system <code class="filename">/etc/hosts 49 49 </code>, NIS, or DNS lookups. This method of name resolution … … 52 52 file). Note that this method is only used if the NetBIOS name 53 53 type being queried is the 0x20 (server) name type, otherwise 54 it is ignored.</p></li><li class="listitem"><p><code class="constant">wins</code>: Query a name with54 it is ignored.</p></li><li><p><code class="constant">wins</code>: Query a name with 55 55 the IP address listed in the <em class="parameter"><code>wins server</code></em> 56 56 parameter. If no WINS server has 57 been specified this method will be ignored.</p></li><li class="listitem"><p><code class="constant">bcast</code>: Do a broadcast on57 been specified this method will be ignored.</p></li><li><p><code class="constant">bcast</code>: Do a broadcast on 58 58 each of the known local interfaces listed in the 59 59 <em class="parameter"><code>interfaces</code></em> … … 162 162 Try to authenticate with kerberos. Only useful in 163 163 an Active Directory environment. 164 </p></dd><dt><span class="term">-C|--use-ccache</span></dt><dd><p> 165 Try to use the credentials cached by winbind. 164 166 </p></dd><dt><span class="term">-A|--authentication-file=filename</span></dt><dd><p>This option allows 165 167 you to specify a file from which to read the username and … … 205 207 </code> compatible backups of all the files on an SMB/CIFS 206 208 share. The secondary tar flags that can be given to this option 207 are : </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><em class="parameter"><code>c</code></em> - Create a tar file on UNIX.209 are : </p><div class="itemizedlist"><ul type="disc"><li><p><em class="parameter"><code>c</code></em> - Create a tar file on UNIX. 208 210 Must be followed by the name of a tar file, tape device 209 211 or "-" for standard output. If using standard output you must 210 212 turn the log level to its lowest value -d0 to avoid corrupting 211 213 your tar file. This flag is mutually exclusive with the 212 <em class="parameter"><code>x</code></em> flag. </p></li><li class="listitem"><p><em class="parameter"><code>x</code></em> - Extract (restore) a local214 <em class="parameter"><code>x</code></em> flag. </p></li><li><p><em class="parameter"><code>x</code></em> - Extract (restore) a local 213 215 tar file back to a share. Unless the -D option is given, the tar 214 216 files will be restored from the top level of the share. Must be … … 217 219 Restored files have their creation times (mtime) set to the 218 220 date saved in the tar file. Directories currently do not get 219 their creation dates restored properly. </p></li><li class="listitem"><p><em class="parameter"><code>I</code></em> - Include files and directories.221 their creation dates restored properly. </p></li><li><p><em class="parameter"><code>I</code></em> - Include files and directories. 220 222 Is the default behavior when filenames are specified above. Causes 221 223 files to be included in an extract or create (and therefore 222 224 everything else to be excluded). See example below. Filename globbing 223 works in one of two ways. See <em class="parameter"><code>r</code></em> below. </p></li><li class="listitem"><p><em class="parameter"><code>X</code></em> - Exclude files and directories.225 works in one of two ways. See <em class="parameter"><code>r</code></em> below. </p></li><li><p><em class="parameter"><code>X</code></em> - Exclude files and directories. 224 226 Causes files to be excluded from an extract or create. See 225 227 example below. Filename globbing works in one of two ways now. 226 See <em class="parameter"><code>r</code></em> below. </p></li><li class="listitem"><p><em class="parameter"><code>F</code></em> - File containing a list of files and directories.228 See <em class="parameter"><code>r</code></em> below. </p></li><li><p><em class="parameter"><code>F</code></em> - File containing a list of files and directories. 227 229 The <em class="parameter"><code>F</code></em> causes the name following the tarfile to 228 230 create to be read as a filename that contains a list of files and directories to … … 230 232 See example below. Filename globbing works in one of two ways. 231 233 See <em class="parameter"><code>r</code></em> below. 232 </p></li><li class="listitem"><p><em class="parameter"><code>b</code></em> - Blocksize. Must be followed234 </p></li><li><p><em class="parameter"><code>b</code></em> - Blocksize. Must be followed 233 235 by a valid (greater than zero) blocksize. Causes tar file to be 234 236 written out in blocksize*TBLOCK (usually 512 byte) blocks. 235 </p></li><li class="listitem"><p><em class="parameter"><code>g</code></em> - Incremental. Only back up237 </p></li><li><p><em class="parameter"><code>g</code></em> - Incremental. Only back up 236 238 files that have the archive bit set. Useful only with the 237 <em class="parameter"><code>c</code></em> flag. </p></li><li class="listitem"><p><em class="parameter"><code>q</code></em> - Quiet. Keeps tar from printing239 <em class="parameter"><code>c</code></em> flag. </p></li><li><p><em class="parameter"><code>q</code></em> - Quiet. Keeps tar from printing 238 240 diagnostics as it works. This is the same as tarmode quiet. 239 </p></li><li class="listitem"><p><em class="parameter"><code>r</code></em> - Regular expression include241 </p></li><li><p><em class="parameter"><code>r</code></em> - Regular expression include 240 242 or exclude. Uses regular expression matching for 241 243 excluding or excluding files if compiled with HAVE_REGEX_H. 242 244 However this mode can be very slow. If not compiled with 243 245 HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. 244 </p></li><li class="listitem"><p><em class="parameter"><code>N</code></em> - Newer than. Must be followed246 </p></li><li><p><em class="parameter"><code>N</code></em> - Newer than. Must be followed 245 247 by the name of a file whose date is compared against files found 246 248 on the share during a create. Only files newer than the file 247 249 specified are backed up to the tar file. Useful only with the 248 <em class="parameter"><code>c</code></em> flag. </p></li><li class="listitem"><p><em class="parameter"><code>a</code></em> - Set archive bit. Causes the250 <em class="parameter"><code>c</code></em> flag. </p></li><li><p><em class="parameter"><code>a</code></em> - Set archive bit. Causes the 249 251 archive bit to be reset when a file is backed up. Useful with the 250 252 <em class="parameter"><code>g</code></em> and <em class="parameter"><code>c</code></em> flags. … … 271 273 commands to be executed instead of prompting from stdin. <em class="parameter"><code> 272 274 -N</code></em> is implied by <em class="parameter"><code>-c</code></em>.</p><p>This is particularly useful in scripts and for printing stdin 273 to the server, e.g. <code class="literal">-c 'print -'</code>. </p></dd></dl></div></div><div class="refsect1" title="OPERATIONS"><a name="id2539288"></a><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with275 to the server, e.g. <code class="literal">-c 'print -'</code>. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2533317"></a><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with 274 276 a prompt : </p><p><code class="prompt">smb:\> </code></p><p>The backslash ("\\") indicates the current working directory 275 277 on the server, and will change if the current working directory … … 469 471 the given arbitrary number. Without an argument prints out the current 470 472 vuid being used. Used for internal Samba testing purposes. 471 </p></dd></dl></div></div><div class="refsect1" title="NOTES"><a name="id2487394"></a><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames,473 </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2534408"></a><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames, 472 474 passwords, share names (AKA service names) and machine names. 473 475 If you fail to connect try giving all parameters in uppercase. … … 476 478 on a valid NetBIOS name being used, so you need to supply a valid 477 479 name that would be known to the server.</p><p>smbclient supports long file names where the server 478 supports the LANMAN2 protocol or above. </p></div><div class="refsect1" title="ENVIRONMENT VARIABLES"><a name="id2487420"></a><h2>ENVIRONMENT VARIABLES</h2><p>The variable <code class="envar">USER</code> may contain the480 supports the LANMAN2 protocol or above. </p></div><div class="refsect1" lang="en"><a name="id2534433"></a><h2>ENVIRONMENT VARIABLES</h2><p>The variable <code class="envar">USER</code> may contain the 479 481 username of the person using the client. This information is 480 482 used only if the protocol level is high enough to support … … 486 488 to instead of connecting to a server. This functionality is primarily 487 489 intended as a development aid, and works best when using a LMHOSTS 488 file</p></div><div class="refsect1" title="INSTALLATION"><a name="id2540580"></a><h2>INSTALLATION</h2><p>The location of the client program is a matter for490 file</p></div><div class="refsect1" lang="en"><a name="id2534469"></a><h2>INSTALLATION</h2><p>The location of the client program is a matter for 489 491 individual system administrators. The following are thus 490 492 suggestions only. </p><p>It is recommended that the smbclient software be installed … … 497 499 running SMB/CIFS server. It is possible to run <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> as an ordinary user - running that server as a daemon 498 500 on a user-accessible port (typically any port number over 1024) 499 would provide a suitable test server. </p></div><div class="refsect1" title="DIAGNOSTICS"><a name="id2540633"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a501 would provide a suitable test server. </p></div><div class="refsect1" lang="en"><a name="id2534522"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a 500 502 specified log file. The log file name is specified at compile time, 501 503 but may be overridden on the command line. </p><p>The number and nature of diagnostics available depends 502 504 on the debug level used by the client. If you have problems, 503 set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" title="VERSION"><a name="id2540652"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.</p></div><div class="refsect1" title="AUTHOR"><a name="id2540663"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities505 set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" lang="en"><a name="id2534540"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2534551"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 504 506 were created by Andrew Tridgell. Samba is now developed 505 507 by the Samba Team as an Open Source project similar
Note:
See TracChangeset
for help on using the changeset viewer.
