diff options
| author | Luke Leighton <lkcl@samba.org> | 1999-11-19 23:26:42 +0000 |
|---|---|---|
| committer | Luke Leighton <lkcl@samba.org> | 1999-11-19 23:26:42 +0000 |
| commit | 69fb70bea547434753cd969c7134fa3ca7522bf2 (patch) | |
| tree | 45433600d0e829ec82d3a63e590bfe15cd1dacbe /docs | |
| parent | 01072b78e61a7d752410ae868d9c156cae6ff357 (diff) | |
| download | samba-69fb70bea547434753cd969c7134fa3ca7522bf2.tar.gz samba-69fb70bea547434753cd969c7134fa3ca7522bf2.tar.bz2 samba-69fb70bea547434753cd969c7134fa3ca7522bf2.zip | |
yodl update - rpcclient
(This used to be commit 9eef1817f8f29c2d69832806b394658cf2cce5e9)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/htmldocs/rpcclient.1.html | 592 | ||||
| -rw-r--r-- | docs/htmldocs/samba.7.html | 8 | ||||
| -rw-r--r-- | docs/htmldocs/smb.conf.5.html | 6 | ||||
| -rw-r--r-- | docs/htmldocs/smbd.8.html | 15 | ||||
| -rw-r--r-- | docs/manpages/rpcclient.1 | 742 | ||||
| -rw-r--r-- | docs/manpages/samba.7 | 12 | ||||
| -rw-r--r-- | docs/manpages/smb.conf.5 | 6 | ||||
| -rw-r--r-- | docs/manpages/smbd.8 | 15 | ||||
| -rw-r--r-- | docs/textdocs/rpcclient.1.txt | 685 |
9 files changed, 2065 insertions, 16 deletions
diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html new file mode 100644 index 0000000000..5af27f2088 --- /dev/null +++ b/docs/htmldocs/rpcclient.1.html @@ -0,0 +1,592 @@ + + + + + +<html><head><title>rpcclient (1)</title> + +<link rev="made" href="mailto:samba-bugs@samba.org"> +</head> +<body> + +<hr> + +<h1>rpcclient (1)</h1> +<h2>Samba</h2> +<h2>23 Oct 1998</h2> + + + + +<p><br><a name="NAME"></a> +<h2>NAME</h2> + rpcclient - utility to manage MSRPC resources on servers +<p><br><a name="SYNOPSIS"></a> +<h2>SYNOPSIS</h2> + +<p><br><strong>rpcclient</strong> +[<a href="rpcclient.1.html#password">password</a>] +<a href="rpcclient.1.html#servername">-S servername</a> +[<a href="rpcclient.1.html#minusU">-U [username][%][password]</a>] +[<a href="rpcclient.1.html#minusW">-W domain</a>] +[<a href="rpcclient.1.html#minusl">-l log basename</a>] +[<a href="rpcclient.1.html#minusd">-d debuglevel</a>] +[<a href="rpcclient.1.html#minusO">-O socket options</a>] +[<a href="rpcclient.1.html#minusi">-i scope</a>] +[<a href="rpcclient.1.html#minusN">-N</a>] +[<a href="rpcclient.1.html#minusn">-n NetBIOS name</a>] +[<a href="rpcclient.1.html#minush">-h</a>] +[<a href="rpcclient.1.html#minusI">-I dest IP</a>] +[<a href="rpcclient.1.html#minusE">-E</a>] +[<a href="rpcclient.1.html#minust">-t terminal code</a>] +[<a href="rpcclient.1.html#minusc">-c command string</a>] +[<a href="rpcclient.1.html#minusB">-B IP addr</a>] +[<a href="rpcclient.1.html#minuss">-s smb.conf</a>] +[<a href="rpcclient.1.html#minusm">-m max protocol</a>] +<p><br><a name="DESCRIPTION"></a> +<h2>DESCRIPTION</h2> + +<p><br>This program is part of the <strong>Samba</strong> suite. +<p><br><strong>rpcclient</strong> is a client that can 'talk' to an SMB/CIFS MSRPC server. +Operations include things like managing a SAM Database (users, groups +and aliases) in the same way as the Windows NT programs +<strong>User Manager for Domains</strong> and <strong>Server Manager for Domains</strong>; +managing a remote registry in the same way as the Windows NT programs +<strong>REGEDT32.EXE</strong> and <strong>REGEDIT.EXE</strong>; viewing a remote event log (same +as <strong>EVENTVWR.EXE</strong>) etc. +<p><br>Typical usage is like this: <br> +<code>rpcclient -I 192.168.32.1 -S "*SMBSERVER" -U fred%secret -l log</code> +<br> +<p><br><a name="OPTIONS"></a> +<h2>OPTIONS</h2> + +<p><br><ul> +<p><br><a name="servername"></a> +<li><strong><strong>servername</strong></strong> servername is the name of the server you want +to use on the server. This should be the NetBIOS name of the SMB/CIFS +server, which can be <strong>*SMBSERVER</strong> on Windows NT 4.0 or Samba Servers. +<p><br>Note that the server name required is NOT necessarily the IP (DNS) +host name of the server! The name required is a NetBIOS server name, +which may or may not be the same as the IP hostname of the machine +running the server. Also, remember that having a period in a NetBIOS +name (such as an IP hostname) may cause connectivity problems on your +network: NT tends to strip NetBIOS names from the leading period +onwards. +<p><br>The server name is looked up according to either the +<a href="rpcclient.1.html#minusR"><strong>-R</strong></a> parameter to <strong>rpcclient</strong> or using the +<a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> +parameter in the smb.conf file, allowing an administrator to change +the order and methods by which server names are looked up. +<p><br><a name="password"></a> +<li><strong><strong>password</strong></strong> password is the password required to access the +specified service on the specified server. If this parameter is +supplied, the <a href="rpcclient.1.html#minusN"><strong>-N</strong></a> option (suppress password prompt) is assumed. +<p><br>There is no default password. If no password is supplied on the +command line (either by using this parameter or adding a password to +the <a href="rpcclient.1.html#minusU"><strong>-U</strong></a> option (see below)) and the <a href="rpcclient.1.html#minusN"><strong>-N</strong></a> option is not specified, +the client will prompt for a password, even if the desired service +does not require one. (If no password is required, simply press ENTER +to provide a null password.) +<p><br>Note: Some servers (including OS/2 and Windows for Workgroups) insist +on an uppercase password. Lowercase or mixed case passwords may be +rejected by these servers. +<p><br>Be cautious about including passwords in scripts. +<p><br><a name="minuss"></a> +<li><strong><strong>-s smb.conf</strong></strong> This parameter specifies the pathname to the +Samba configuration file, smb.conf. This file controls all aspects of +the Samba setup on the machine and rpcclient also needs to read this +file. +<p><br><a name="minusB"></a> +<li><strong><strong>-B IP addr</strong></strong> The IP address to use when sending a broadcast packet. +<p><br><a name="minusO"></a> +<li><strong><strong>-O socket options</strong></strong> TCP socket options to set on the client +socket. See the <a href="smb.conf.5.html#socketoptions">socket options</a> +parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> manpage for +the list of valid options. +<p><br><a name="minusR"></a> +<li><strong><strong>-R name resolve order</strong></strong> This option allows the user of +rpcclient to determine what name resolution services to use when +looking up the NetBIOS name of the host being connected to. +<p><br>The options are :"lmhosts", "host", "wins" and "bcast". They cause +names to be resolved as follows : +<p><br><ul> +<p><br><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file. +The lmhosts file is stored in the same directory as the +<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. +<p><br><li > <strong>host</strong> : 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 depended for instance on IRIX or +Solaris this may be controlled by the <em>/etc/nsswitch.conf</em> file). +<p><br><li > <strong>wins</strong> : Query a name with the IP address listed in the <a href="smb.conf.5.html#winsserver"><strong>wins +server</strong></a> parameter in the smb.conf file. If +no WINS server has been specified this method will be ignored. +<p><br><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces +listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter +in the smb.conf file. This is the least reliable of the name resolution +methods as it depends on the target host being on a locally connected +subnet. To specify a particular broadcast address the <a href="rpcclient.1.html#minusB"><strong>-B</strong></a> option +may be used. +<p><br></ul> +<p><br>If this parameter is not set then the name resolve order defined +in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file parameter +<a href="smb.conf.5.html#nameresolveorder">(<strong>name resolve order</strong>)</a> +will be used. +<p><br>The default order is lmhosts, host, wins, bcast and without this +parameter or any entry in the <a href="smb.conf.5.html#nameresolveorder"><strong>"name resolve +order"</strong></a> parameter of the +<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file the name resolution methods +will be attempted in this order. +<p><br><a name="minusi"></a> +<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that rpcclient 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 <em>very</em> rarely used, only set this parameter if you are the +system administrator in charge of all the NetBIOS systems you +communicate with. +<p><br><a name="minusN"></a> +<li><strong><strong>-N</strong></strong> 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. +<p><br>Unless a password is specified on the command line or this parameter +is specified, the client will request a password. +<p><br><a name="minusn"></a> +<li><strong><strong>-n NetBIOS name</strong></strong> 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. +<p><br><a name="minusd"></a> +<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10, or the +letter 'A'. +<p><br>The default value if this parameter is not specified is zero. +<p><br>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. +<p><br>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 <em>all</em> debug messages will be printed. This setting +is for developers only (and people who <em>really</em> want to know how the +code works internally). +<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log +level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf +(5)</strong></a> file. +<p><br><a name="minusp"></a> +<li><strong><strong>-p port</strong></strong> This number is the TCP port number that will be used +when making connections to the server. The standard (well-known) TCP +port number for an SMB/CIFS server is 139, which is the default. +<p><br><a name="minusl"></a> +<li><strong><strong>-l logfilename</strong></strong> If specified, logfilename specifies a base +filename into which operational data from the running client will be +logged. +<p><br>The default base name is specified at compile time. +<p><br>The base name is used to generate actual log file names. For example, +if the name specified was "log", the debug file would be +<code>log.client</code>. +<p><br>The log file generated is never removed by the client. +<p><br><a name="minush"></a> +<li><strong><strong>-h</strong></strong> Print the usage message for the client. +<p><br><a name="minusI"></a> +<li><strong><strong>-I IP address</strong></strong> IP address is the address of the server to +connect to. It should be specified in standard "a.b.c.d" notation. +<p><br>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 <a href="rpcclient.1.html#minusR"><strong>name resolve order</strong></a> 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. +<p><br>There is no default for this parameter. If not supplied, it will be +determined automatically by the client as described above. +<p><br><a name="minusE"></a> +<li><strong><strong>-E</strong></strong> This parameter causes the client to write messages to the +standard error stream (stderr) rather than to the standard output +stream. +<p><br>By default, the client writes messages to standard output - typically +the user's tty. +<p><br>Note that by default, debug information is always sent to stderr. +Debug information can instead be sent to a file, using the +<a href="rpcclient.1.html#minusl">-l log basename</a> option. +<p><br><a name="minusU"></a> +<li><strong><strong>-U username</strong></strong> This specifies the user name that will be used by +the client to make a connection, assuming your server is not a downlevel +server that is running a protocol level that uses passwords on shares, +not on usernames. +<p><br>Some servers are fussy about the case of this name, and some insist +that it must be a valid NetBIOS name. +<p><br>If no username is supplied, it will default to an uppercase version of +the environment variable <code>USER</code> or <code>LOGNAME</code> in that order. If no +username is supplied and neither environment variable exists the +username "GUEST" will be used. +<p><br>If the <code>USER</code> environment variable contains a '%' character, +everything after that will be treated as a password. This allows you +to set the environment variable to be <code>USER=username%password</code> so +that a password is not passed on the command line (where it may be +seen by the ps command). +<p><br>If the service you are connecting to requires a password, it can be +supplied using the <a href="rpcclient.1.html#minusU"><strong>-U</strong></a> option, by appending a percent symbol ("%") +then the password to username. For example, to attach to a service as +user <code>"fred"</code> with password <code>"secret"</code>, you would specify. <br> +<p><br><code>-U fred%secret</code> <br> +<p><br>on the command line. Note that there are no spaces around the percent +symbol. +<p><br>If you specify the password as part of username then the <a href="rpcclient.1.html#minusN"><strong>-N</strong></a> option +(suppress password prompt) is assumed. +<p><br>If you specify the password as a parameter <em>AND</em> as part of username +then the password as part of username will take precedence. Putting +nothing before or nothing after the percent symbol will cause an empty +username or an empty password to be used, respectively. +<p><br>The password may also be specified by setting up an environment +variable called <code>PASSWORD</code> that contains the users password. Note +that this may be very insecure on some systems but on others allows +users to script rpcclient commands without having a password appear in +the command line of a process listing. +<p><br>Note: Some servers (including OS/2 and Windows for Workgroups) insist +on an uppercase password. Lowercase or mixed case passwords may be +rejected by these servers. +<p><br>Be cautious about including passwords in scripts or in the +<code>PASSWORD</code> environment variable. Also, on many systems the command +line of a running process may be seen via the <code>ps</code> command to be +safe always allow rpcclient to prompt for a password and type it in +directly. +<p><br><a name="minust"></a> +<li><strong><strong>-t terminal code</strong></strong> This option tells rpcclient how to interpret +filenames coming from the remote server. Usually Asian language +multibyte UNIX implementations use different character sets than +SMB/CIFS servers (<em>EUC</em> instead of <em>SJIS</em> for example). Setting +this parameter will let rpcclient convert between the UNIX filenames +and the SMB filenames correctly. This option has not been seriously +tested and may have some problems. +<p><br>The terminal codes include <code>sjis</code>, <code>euc</code>, <code>jis7</code>, <code>jis8</code>, +<code>junet</code>, <code>hex</code>, <code>cap</code>. This is not a complete list, check the +Samba source code for the complete list. +<p><br><a name="minusm"></a> +<li><strong><strong>-m max protocol level</strong></strong> With the new code in Samba2.0, +<strong>rpcclient</strong> always attempts to connect at the maximum +protocols level the server supports. This parameter is +preserved for backwards compatibility, but any string +following the <strong>-m</strong> will be ignored. +<p><br><a name="minusW"></a> +<li><strong><strong>-W Domain</strong></strong> Override the default Domain, which is the remote server's +Domain. This option may be needed to connect to some servers. It is also +possible to specify the remote server name as the Domain, which will +force the username and password to be authenticated against the remote +server's local SAM instead of the Domain SAM. +<p><br><a name="minusc"></a> +<li><strong><strong>-c command string</strong></strong> command string is a semicolon separated +list of commands to be executed instead of prompting from stdin. +<a href="rpcclient.1.html#minusN"><strong>-N</strong></a> is implied by <strong>-c</strong>. +<p><br>This is particularly useful in scripts, e.g. <code>-c 'lsaquery; enumusers -u'</code>. +<p><br></ul> +<p><br><a name="OPERATIONS"></a> +<h2>OPERATIONS</h2> + +<p><br>Once the client is running, the user is presented with a prompt : +<p><br><code>smb:\></code> +<p><br>The prompt indicates that the client is ready and waiting to carry out +a user command. Each command is a single word, optionally followed by +parameters specific to that command. Command and parameters are +space-delimited unless these notes specifically state otherwise. All +commands are case-insensitive. Parameters to commands may or may not +be case sensitive, depending on the command. +<p><br>You can specify names (e.g registry keys; user or group names; +service names) which have spaces in them by quoting the +name with double quotes, for example "dRMON SmartAgent". +<p><br>Parameters shown in square brackets (e.g., "[parameter]") are +optional. If not given, the command will use suitable +defaults. Parameters shown in angle brackets (e.g., "<parameter>") are +required. +<p><br>Note that all commands operating on the server are actually performed +by issuing a request to the server. Thus the behavior may vary from +server to server, depending on how the server was implemented. +<p><br>The commands available are listed in groups relating to different services: +<p><br><ul> +<p><br><li><strong>Misccellaneous</strong> +<p><br><ul> +<p><br><a name="questionmark"></a> <li><strong><strong>? [command]</strong></strong> If "command" is specified, + the <strong>?</strong> command will display a brief informative message about the + specified command. If no command is specified, a list of available + commands will be displayed. +<p><br><a name="exclaimationmark"></a> <li><strong><strong>! [shell command]</strong></strong> If "shell command" + is specified, the <strong>!</strong> command will execute a shell locally and run + the specified shell command. If no command is specified, a local shell + will be run. +<p><br><a name="exit"></a> <li><strong><strong>exit</strong></strong> Terminate the connection with the server and + exit from the program. +<p><br><a name="help"></a> <li><strong><strong>help [command]</strong></strong> See the <a href="rpcclient.1.html#questionmark"><strong>?</strong></a> + command above. +<p><br><a name="quit"></a> <li><strong><strong>quit</strong></strong> See the <a href="rpcclient.1.html#exit"><strong>exit</strong></a> command. +<p><br></ul> +<p><br><li><strong>Event Log</strong> +<p><br><ul> +<p><br><a name="eventlog"></a> <li><strong><strong>eventlog</strong></strong> + list the events +<p><br></ul> +<p><br><li><strong>Service Control</strong> +<p><br>It is possible to use command-line completion (if you have + the GNU readline library) for Service names, by pressing the + tab key. +<p><br><ul> +<p><br><a name="svcenum"></a> <li><strong><strong>svcenum</strong></strong> + [-i] Lists Services Manager +<p><br><a name="svcinfo"></a> <li><strong><strong>svcinfo</strong></strong> + <service> Service Information +<p><br><a name="svcstart"></a> <li><strong><strong>svcstart</strong></strong> + <service> [arg 0] [arg 1] ... Start Service +<p><br><a name="svcstop"></a> <li><strong><strong>svcstop</strong></strong> + <service> Stop Service +<p><br></ul> +<p><br><li><strong>Scheduler</strong> +<p><br><ul> +<p><br><a name="at"></a> <li><strong><strong>at</strong></strong> + Scheduler control (at /? for syntax) +<p><br></ul> +<p><br><li><strong>Registry</strong> +<p><br>It is possible to use command-line completion (if you have + the GNU readline library) for registry key and value names, + by pressing the tab key. +<p><br><ul> +<p><br><a name="regenum"></a> <li><strong><strong>regenum</strong></strong> + <keyname> Registry Enumeration (keys, values) +<p><br><a name="regdeletekey"></a> <li><strong><strong>regdeletekey</strong></strong> + <keyname> Registry Key Delete +<p><br><a name="regcreatekey"></a> <li><strong><strong>regcreatekey</strong></strong> + <keyname> [keyclass] Registry Key Create +<p><br><a name="shutdown"></a> <li><strong><strong>shutdown</strong></strong> + [-m message] [-t timeout] [-r or --reboot] Server Shutdown +<p><br><a name="regqueryval"></a> <li><strong><strong>regqueryval</strong></strong> + <valname> Registry Value Query +<p><br><a name="regquerykey"></a> <li><strong><strong>regquerykey</strong></strong> + <keyname> Registry Key Query +<p><br><a name="regdeleteval"></a> <li><strong><strong>regdeleteval</strong></strong> + <valname> Registry Value Delete +<p><br><a name="regcreateval"></a> <li><strong><strong>regcreateval</strong></strong> + <valname> <valtype> <value> Registry Key Create +<p><br><a name="reggetsec"></a> <li><strong><strong>reggetsec</strong></strong> + <keyname> Registry Key Security +<p><br><a name="regtestsec"></a> <li><strong><strong>regtestsec</strong></strong> + <keyname> Test Registry Key Security +<p><br></ul> +<p><br><li><strong>Printing</strong> +<p><br>It is possible to use command-line completion (if you have + the GNU readline library) for Printer and job names, by + pressing the tab key. +<p><br><ul> +<p><br><a name="spoolenum"></a> <li><strong><strong>spoolenum</strong></strong> + Enumerate Printers +<p><br><a name="spooljobs"></a> <li><strong><strong>spooljobs</strong></strong> + <printer name> Enumerate Printer Jobs +<p><br><a name="spoolopen"></a> <li><strong><strong>spoolopen</strong></strong> + <printer name> Spool Printer Open Test +<p><br></ul> +<p><br><li><strong>Server</strong> +<p><br><ul> +<p><br><a name="time"></a> <li><strong><strong>time</strong></strong> + Display remote time +<p><br><a name="brsinfo"></a> <li><strong><strong>brsinfo</strong></strong> + Browser Query Info +<p><br><a name="wksinfo"></a> <li><strong><strong>wksinfo</strong></strong> + Workstation Query Info +<p><br><a name="srvinfo"></a> <li><strong><strong>srvinfo</strong></strong> + Server Query Info +<p><br><a name="srvsessions"></a> <li><strong><strong>srvsessions</strong></strong> + List sessions on a server +<p><br><a name="srvshares"></a> <li><strong><strong>srvshares</strong></strong> + List shares on a server +<p><br><a name="srvtransports"></a> <li><strong><strong>srvtransports</strong></strong> + List transports on a server +<p><br><a name="srvconnections"></a> <li><strong><strong>srvconnections</strong></strong> + List connections on a server +<p><br><a name="srvfiles"></a> <li><strong><strong>srvfiles</strong></strong> + List files on a server +<p><br></ul> +<p><br><li><strong>Local Security Authority</strong> +<p><br><ul> +<p><br><a name="lsaquery"></a> <li><strong><strong>lsaquery</strong></strong> + Query Info Policy (domain member or server) +<p><br><a name="lsaenumdomains"></a> <li><strong><strong>lsaenumdomains</strong></strong> + Enumerate Trusted Domains +<p><br><a name="lookupsids"></a> <li><strong><strong>lookupsids</strong></strong> + Resolve names from SIDs +<p><br><a name="lookupnames"></a> <li><strong><strong>lookupnames</strong></strong> + Resolve SIDs from names +<p><br><a name="querysecret"></a> <li><strong><strong>querysecret</strong></strong> + LSA Query Secret (developer use) +<p><br></ul> +<p><br><li><strong>NETLOGON</strong> +<p><br><ul> +<p><br><a name="ntlogin"></a> <li><strong><strong>ntlogin</strong></strong> + [username] [password] NT Domain login test +<p><br><a name="domtrust"></a> <li><strong><strong>domtrust</strong></strong> + <domain> NT Inter-Domain test +<p><br><a name="samsync"></a> <li><strong><strong>samsync</strong></strong> + SAM Synchronization Test (experimental) +<p><br></ul> +<p><br><li><strong>SAM Database</strong> +<p><br>It is possible to use command-line completion (if you have + the GNU readline library) for user, group, alias and domain + names, by pressing the tab key. +<p><br><ul> +<p><br><a name="lookupdomain"></a> <li><strong><strong>lookupdomain</strong></strong> + Obtain SID for a local domain +<p><br><a name="enumusers"></a> <li><strong><strong>enumusers</strong></strong> + SAM User Database Query (experimental!) +<p><br><a name="addgroupmem"></a> <li><strong><strong>addgroupmem</strong></strong> + <group rid> [user] [user] ... SAM Add Domain Group Member +<p><br><a name="addaliasmem"></a> <li><strong><strong>addaliasmem</strong></strong> + <alias rid> [member sid1] [member sid2] ... SAM Add Domain Alias Member +<p><br><a name="delgroupmem"></a> <li><strong><strong>delgroupmem</strong></strong> + <group rid> [user] [user] ... SAM Delete Domain Group Member +<p><br><a name="delaliasmem"></a> <li><strong><strong>delaliasmem</strong></strong> + <alias rid> [member sid1] [member sid2] ... SAM Delete Domain Alias Member +<p><br><a name="creategroup"></a> <li><strong><strong>creategroup</strong></strong> + SAM Create Domain Group +<p><br><a name="createalias"></a> <li><strong><strong>createalias</strong></strong> + SAM Create Domain Alias +<p><br><a name="createuser"></a> <li><strong><strong>createuser</strong></strong> + <username> SAM Create Domain User +<p><br><a name="delgroup"></a> <li><strong><strong>delgroup</strong></strong> + SAM Delete Domain Group +<p><br><a name="delalias"></a> <li><strong><strong>delalias</strong></strong> + SAM Delete Domain Alias +<p><br><a name="ntpass"></a> <li><strong><strong>ntpass</strong></strong> + NT SAM Password Change +<p><br><a name="samuserset2"></a> <li><strong><strong>samuserset2</strong></strong> + <username> [-s acb_bits] SAM User Set Info 2 (experimental!) +<p><br><a name="samuserset"></a> <li><strong><strong>samuserset</strong></strong> + <username> [-p password] SAM User Set Info (experimental!) +<p><br><a name="samuser"></a> <li><strong><strong>samuser</strong></strong> + <username> SAM User Query (experimental!) +<p><br><a name="samgroup"></a> <li><strong><strong>samgroup</strong></strong> + <groupname> SAM Group Query (experimental!) +<p><br><a name="samalias"></a> <li><strong><strong>samalias</strong></strong> + <aliasname> SAM Alias Query +<p><br><a name="samaliasmem"></a> <li><strong><strong>samaliasmem</strong></strong> + <aliasname> SAM Alias Members +<p><br><a name="samgroupmem"></a> <li><strong><strong>samgroupmem</strong></strong> + SAM Group Members +<p><br><a name="samtest"></a> <li><strong><strong>samtest</strong></strong> + SAM User Encrypted RPC test (experimental!) +<p><br><a name="enumaliases"></a> <li><strong><strong>enumaliases</strong></strong> + SAM Aliases Database Query (experimental!) +<p><br><a name="enumdomains"></a> <li><strong><strong>enumdomains</strong></strong> + SAM Domains Database Query (experimental!) +<p><br><a name="enumgroups"></a> <li><strong><strong>enumgroups</strong></strong> + SAM Group Database Query (experimental!) +<p><br><a name="dominfo"></a> <li><strong><strong>dominfo</strong></strong> + SAM Query Domain Info +<p><br><a name="dispinfo"></a> <li><strong><strong>dispinfo</strong></strong> + SAM Query Display Info +<p><br></ul> +<p><br></ul> +<p><br><a name="NOTES"></a> +<h2>NOTES</h2> + +<p><br>Some servers are fussy about the case of supplied usernames, +passwords, share names (AKA service names) and machine names. If you +fail to connect try giving all parameters in uppercase. +<p><br>It is often necessary to use the <a href="rpcclient.1.html#minusn"><strong>-n</strong></a> option when connecting +to some types of servers. For example OS/2 LanManager insists on a valid +NetBIOS name being used, so you need to supply a valid name that would +be known to the server. +<p><br>rpcclient only works on servers that support MSRPC over SMB. This includes +all versions of Windows NT, including the ports to Unix such as AS/U and +AFPS. Support for MSRPC over SMB in other servers is currently rare and +patchy, for example Samba 2.0 only supports a limited set of MSRPC commands, +and some of those are not supported very well. +<p><br><a name="ENVIRONMENTVARIABLES"></a> +<h2>ENVIRONMENT VARIABLES</h2> + +<p><br>The variable <strong>USER</strong> may contain the username of the person using the +client. This information is used only if the protocol level is high +enough to support session-level passwords. +<p><br>The variable <strong>PASSWORD</strong> may contain the password of the person using +the client. This information is used only if the protocol level is +high enough to support session-level passwords. +<p><br><a name="INSTALLATION"></a> +<h2>INSTALLATION</h2> + +<p><br>The location of the client program is a matter for individual system +administrators. The following are thus suggestions only. +<p><br>It is recommended that the rpcclient software be installed in the +/usr/local/samba/bin or /usr/samba/bin directory, this directory +readable by all, writeable only by root. The client program itself +should be executable by all. The client should <em>NOT</em> be setuid or +setgid! +<p><br>The client log files should be put in a directory readable and +writeable only by the user. +<p><br>To test the client, you will need to know the name of a running +SMB/CIFS server. It is possible to run <a href="smbd.8.html"><strong>smbd (8)</strong></a> +an ordinary user - running that server as a daemon on a +user-accessible port (typically any port number over 1024) would +provide a suitable test server. +<p><br><a name="DIAGNOSTICS"></a> +<h2>DIAGNOSTICS</h2> + +<p><br>Most diagnostics issued by the client are logged in a specified log +file. The log file name is specified at compile time, but may be +overridden on the command line. +<p><br>The number and nature of diagnostics available depends on the debug +level used by the client. If you have problems, set the debug level to +3 and peruse the log files. +<p><br><a name="VERSION"></a> +<h2>VERSION</h2> + +<p><br>This man page is correct for version 2.0 of the Samba suite. +<p><br><a name="BUGS"></a> +<h2>BUGS</h2> + +<p><br><ul> +<li><strong>WARNING!</strong> +The MSPRC over SMB code has been developed from examining Network traces. +No documentation is available from the original creators (Microsoft) on +how MSRPC over SMB works, or how the individual MSRPC services work. +Microsoft's implementation of these services has been demonstrated (and +reported) to be... a bit flakey in places. +<p><br>The development of Samba's implementation of these services is <em>also</em> +a bit rough, and as more of the services are understood, it can even result +in versions of <a href="smbd.8.html"><strong>smbd (8)</strong></a> and rpcclient that are +incompatible for some commands or services. Additionally, the developers +are sending reports to Microsoft, and problems found by or reported to +Microsoft are fixed in Service Packs, which may also result in +incompatibilities. +<p><br>It is therefore not guaranteed that the execution of an rpcclient command will +work. It is also not guaranteed that the target server will continue to +operate, i.e the execution of an MSRPC command may cause a remote service to +fail, or even cause the remote server to fail. Usual rules apply, of course: +the developers bear absolutely no responsibility for the use, misuse, or +lack of use of rpcclient, by any person or persons, whether legal, +illegal, accidental, deliberate, intentional, malicious, curious, etc. +<p><br><li><strong>Command Completion</strong> +Command-completion (available if you have the GNU readline library) used on +certain commands may not operate correctly if the word being completed (such as a registry key) contains a space. Typically, the name will be completed, but +you will have to go back and put quotes round it, yourself. +<p><br><li><strong>SAM Database command-completion</strong> +Command-completion (available if you have the GNU readline library) of user, +group and alias names does not work on remote Domains, which would normally +be specified like this: <br> +<code>DOMAIN_name\\user_name</code>. <br> +The only names that can be completed in this fashion are the local names +in the SAM database of the target server. +<p><br></ul> +<p><br><a name="AUTHOR"></a> +<h2>AUTHOR</h2> + +<p><br>The original Samba software and related utilities were created by +Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed +by the Samba Team as an Open Source project similar to the way the +Linux kernel is developed. +<p><br>The original Samba man pages were written by Karl Auer. The man page +sources were converted to YODL format (another excellent piece of Open +Source software, available at +<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>) +and updated for the Samba2.0 release by Jeremy Allison. This man page +was developed cut-and-paste style from the smbclient man page, by +Luke Kenneth Casson Leighton. +<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. +<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full +list of contributors and details on how to submit bug reports, +comments etc. +<p><br></body> +</html> diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index f197ccfa32..2fc86fd65a 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -56,6 +56,14 @@ client. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to any SMB server (such as a PC running Windows NT). +<p><br><li><strong><a href="rpcclient.1.html"><strong>rpcclient</strong></a></strong> <br> <br> The <a href="rpcclient.1.html"><strong>rpcclient</strong> +(1)</a> program is a client that can 'talk' to an +SMB/CIFS MSRPC server. Operations include things like managing a SAM +Database (users, groups and aliases) in the same way as the Windows NT +programs <strong>User Manager for Domains</strong> and <strong>Server Manager for Domains</strong>; +managing a remote registry in the same way as the Windows NT programs +<strong>REGEDT32.EXE</strong> and <strong>REGEDIT.EXE</strong>; viewing a remote event log (same +as <strong>EVENTVWR.EXE</strong>). <p><br><li><strong><a href="testparm.1.html"><strong>testparm</strong></a></strong> <br> <br> The <a href="testparm.1.html"><strong>testparm (1)</strong></a> utility allows you to test your <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> configuration file. diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 433c7ce5bb..bba323c40a 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -840,10 +840,10 @@ shares in a net view and in the browse list. <p><br><strong>Example:</strong> <code> browseable = No</code> <p><br><a name="casesensitive"></a> -<li><strong><strong>case sensitive (G)</strong></strong> +<li><strong><strong>case sensitive (S)</strong></strong> <p><br>See the discussion in the section <a href="smb.conf.5.html#NAMEMANGLING"><strong>NAME MANGLING</strong></a>. <p><br><a name="casesignames"></a> -<li><strong><strong>casesignames (G)</strong></strong> +<li><strong><strong>casesignames (S)</strong></strong> <p><br>Synonym for <a href="smb.conf.5.html#casesensitive"><strong>"case sensitive"</strong></a>. <p><br><a name="changenotifytimeout"></a> <li><strong><strong>change notify timeout (G)</strong></strong> @@ -3732,7 +3732,7 @@ smb_shm_alloc : alloc of XX bytes failed"</code>. <p><br><strong>Example:</strong> <code> shared mem size = 5242880 ; Set to 5mb for a large number of files.</code> <p><br><a name="shortpreservecase"></a> -<li><strong><strong>short preserve case (G)</strong></strong> +<li><strong><strong>short preserve case (S)</strong></strong> <p><br>This boolean parameter controls if new files which conform to 8.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the <code>"default"</code> case. This diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 78d8c3587a..790c406394 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -357,11 +357,16 @@ performance. <p><br><a name="SEEALSO"></a> <h2>SEE ALSO</h2> -<p><br><strong>hosts_access (5)</strong>, <strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, -<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbclient.1.html"><strong>smbclient -(1)</strong></a>, <a href="testparm.1.html"><strong>testparm (1)</strong></a>, -<a href="testprns.1.html"><strong>testprns (1)</strong></a>, and the Internet RFC's -<strong>rfc1001.txt</strong>, <strong>rfc1002.txt</strong>. In addition the CIFS (formerly SMB) +<p><br><strong>hosts_access (5)</strong>, +<strong>inetd (8)</strong>, +<a href="nmbd.8.html"><strong>nmbd (8)</strong></a>, +<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, +<a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, +<a href="testparm.1.html"><strong>testparm (1)</strong></a>, +<a href="testprns.1.html"><strong>testprns (1)</strong></a>, +<a href="rpcclient.1.html"><strong>rpcclient (1)</strong></a>, +and the Internet RFC's <strong>rfc1001.txt</strong>, <strong>rfc1002.txt</strong>. +In addition the CIFS (formerly SMB) specification is available as a link from the Web page : <a href="http://samba.org/cifs/">http://samba.org/cifs/</a>. <p><br><a name="AUTHOR"></a> diff --git a/docs/manpages/rpcclient.1 b/docs/manpages/rpcclient.1 new file mode 100644 index 0000000000..f077587fb8 --- /dev/null +++ b/docs/manpages/rpcclient.1 @@ -0,0 +1,742 @@ +.TH "rpcclient " "1" "23 Oct 1998" "Samba" "SAMBA" +.PP +.SH "NAME" +rpcclient \- utility to manage MSRPC resources on servers +.PP +.SH "SYNOPSIS" +.PP +\fBrpcclient\fP +[password] +-S servername +[-U [username][%][password]] +[-W domain] +[-l log basename] +[-d debuglevel] +[-O socket options] +[-i scope] +[-N] +[-n NetBIOS name] +[-h] +[-I dest IP] +[-E] +[-t terminal code] +[-c command string] +[-B IP addr] +[-s smb\&.conf] +[-m max protocol] +.PP +.SH "DESCRIPTION" +.PP +This program is part of the \fBSamba\fP suite\&. +.PP +\fBrpcclient\fP is a client that can \'talk\' to an SMB/CIFS MSRPC server\&. +Operations include things like managing a SAM Database (users, groups +and aliases) in the same way as the Windows NT programs +\fBUser Manager for Domains\fP and \fBServer Manager for Domains\fP; +managing a remote registry in the same way as the Windows NT programs +\fBREGEDT32\&.EXE\fP and \fBREGEDIT\&.EXE\fP; viewing a remote event log (same +as \fBEVENTVWR\&.EXE\fP) etc\&. +.PP +Typical usage is like this: +.br +\f(CWrpcclient -I 192\&.168\&.32\&.1 -S "*SMBSERVER" -U fred%secret -l log\fP +.br +.PP +.SH "OPTIONS" +.PP +.IP +.IP "\fBservername\fP" +servername is the name of the server you want +to use on the server\&. This should be the NetBIOS name of the SMB/CIFS +server, which can be \fB*SMBSERVER\fP on Windows NT 4\&.0 or Samba Servers\&. +.IP +Note that the server name required is NOT necessarily the IP (DNS) +host name of the server! The name required is a NetBIOS server name, +which may or may not be the same as the IP hostname of the machine +running the server\&. Also, remember that having a period in a NetBIOS +name (such as an IP hostname) may cause connectivity problems on your +network: NT tends to strip NetBIOS names from the leading period +onwards\&. +.IP +The server name is looked up according to either the +\fB-R\fP parameter to \fBrpcclient\fP or using the +\fBname resolve order\fP +parameter in the smb\&.conf file, allowing an administrator to change +the order and methods by which server names are looked up\&. +.IP +.IP "\fBpassword\fP" +password is the password required to access the +specified service on the specified server\&. If this parameter is +supplied, the \fB-N\fP option (suppress password prompt) is assumed\&. +.IP +There is no default password\&. If no password is supplied on the +command line (either by using this parameter or adding a password to +the \fB-U\fP option (see below)) and the \fB-N\fP option is not specified, +the client will prompt for a password, even if the desired service +does not require one\&. (If no password is required, simply press ENTER +to provide a null password\&.) +.IP +Note: Some servers (including OS/2 and Windows for Workgroups) insist +on an uppercase password\&. Lowercase or mixed case passwords may be +rejected by these servers\&. +.IP +Be cautious about including passwords in scripts\&. +.IP +.IP "\fB-s smb\&.conf\fP" +This parameter specifies the pathname to the +Samba configuration file, smb\&.conf\&. This file controls all aspects of +the Samba setup on the machine and rpcclient also needs to read this +file\&. +.IP +.IP "\fB-B IP addr\fP" +The IP address to use when sending a broadcast packet\&. +.IP +.IP "\fB-O socket options\fP" +TCP socket options to set on the client +socket\&. See the socket options +parameter in the \fBsmb\&.conf (5)\fP manpage for +the list of valid options\&. +.IP +.IP "\fB-R name resolve order\fP" +This option allows the user of +rpcclient to determine what name resolution services to use when +looking up the NetBIOS name of the host being connected to\&. +.IP +The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause +names to be resolved as follows : +.IP +.IP +.IP o +\fBlmhosts\fP : Lookup an IP address in the Samba lmhosts file\&. +The lmhosts file is stored in the same directory as the +\fBsmb\&.conf\fP file\&. +.IP +.IP o +\fBhost\fP : 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 depended for instance on IRIX or +Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fP file)\&. +.IP +.IP o +\fBwins\fP : Query a name with the IP address listed in the \fBwins +server\fP parameter in the smb\&.conf file\&. If +no WINS server has been specified this method will be ignored\&. +.IP +.IP o +\fBbcast\fP : Do a broadcast on each of the known local interfaces +listed in the \fBinterfaces\fP parameter +in the smb\&.conf file\&. This is the least reliable of the name resolution +methods as it depends on the target host being on a locally connected +subnet\&. To specify a particular broadcast address the \fB-B\fP option +may be used\&. +.IP +.IP +If this parameter is not set then the name resolve order defined +in the \fBsmb\&.conf\fP file parameter +(\fBname resolve order\fP) +will be used\&. +.IP +The default order is lmhosts, host, wins, bcast and without this +parameter or any entry in the \fB"name resolve +order"\fP parameter of the +\fBsmb\&.conf\fP file the name resolution methods +will be attempted in this order\&. +.IP +.IP "\fB-i scope\fP" +This specifies a NetBIOS scope that rpcclient 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 \fIvery\fP rarely used, only set this parameter if you are the +system administrator in charge of all the NetBIOS systems you +communicate with\&. +.IP +.IP "\fB-N\fP" +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\&. +.IP +Unless a password is specified on the command line or this parameter +is specified, the client will request a password\&. +.IP +.IP "\fB-n NetBIOS name\fP" +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\&. +.IP +.IP "\fB-d debuglevel\fP" +debuglevel is an integer from 0 to 10, or the +letter \'A\'\&. +.IP +The default value if this parameter is not specified is zero\&. +.IP +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\&. +.IP +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 \fIall\fP debug messages will be printed\&. This setting +is for developers only (and people who \fIreally\fP want to know how the +code works internally)\&. +.IP +Note that specifying this parameter here will override the \fBlog +level\fP parameter in the \fBsmb\&.conf +(5)\fP file\&. +.IP +.IP "\fB-p port\fP" +This number is the TCP port number that will be used +when making connections to the server\&. The standard (well-known) TCP +port number for an SMB/CIFS server is 139, which is the default\&. +.IP +.IP "\fB-l logfilename\fP" +If specified, logfilename specifies a base +filename into which operational data from the running client will be +logged\&. +.IP +The default base name is specified at compile time\&. +.IP +The base name is used to generate actual log file names\&. For example, +if the name specified was "log", the debug file would be +\f(CWlog\&.client\fP\&. +.IP +The log file generated is never removed by the client\&. +.IP +.IP "\fB-h\fP" +Print the usage message for the client\&. +.IP +.IP "\fB-I IP address\fP" +IP address is the address of the server to +connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&. +.IP +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 \fBname resolve order\fP 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\&. +.IP +There is no default for this parameter\&. If not supplied, it will be +determined automatically by the client as described above\&. +.IP +.IP "\fB-E\fP" +This parameter causes the client to write messages to the +standard error stream (stderr) rather than to the standard output +stream\&. +.IP +By default, the client writes messages to standard output - typically +the user\'s tty\&. +.IP +Note that by default, debug information is always sent to stderr\&. +Debug information can instead be sent to a file, using the +-l log basename option\&. +.IP +.IP "\fB-U username\fP" +This specifies the user name that will be used by +the client to make a connection, assuming your server is not a downlevel +server that is running a protocol level that uses passwords on shares, +not on usernames\&. +.IP +Some servers are fussy about the case of this name, and some insist +that it must be a valid NetBIOS name\&. +.IP +If no username is supplied, it will default to an uppercase version of +the environment variable \f(CWUSER\fP or \f(CWLOGNAME\fP in that order\&. If no +username is supplied and neither environment variable exists the +username "GUEST" will be used\&. +.IP +If the \f(CWUSER\fP environment variable contains a \'%\' character, +everything after that will be treated as a password\&. This allows you +to set the environment variable to be \f(CWUSER=username%password\fP so +that a password is not passed on the command line (where it may be +seen by the ps command)\&. +.IP +If the service you are connecting to requires a password, it can be +supplied using the \fB-U\fP option, by appending a percent symbol ("%") +then the password to username\&. For example, to attach to a service as +user \f(CW"fred"\fP with password \f(CW"secret"\fP, you would specify\&. +.br +.IP +\f(CW-U fred%secret\fP +.br +.IP +on the command line\&. Note that there are no spaces around the percent +symbol\&. +.IP +If you specify the password as part of username then the \fB-N\fP option +(suppress password prompt) is assumed\&. +.IP +If you specify the password as a parameter \fIAND\fP as part of username +then the password as part of username will take precedence\&. Putting +nothing before or nothing after the percent symbol will cause an empty +username or an empty password to be used, respectively\&. +.IP +The password may also be specified by setting up an environment +variable called \f(CWPASSWORD\fP that contains the users password\&. Note +that this may be very insecure on some systems but on others allows +users to script rpcclient commands without having a password appear in +the command line of a process listing\&. +.IP +Note: Some servers (including OS/2 and Windows for Workgroups) insist +on an uppercase password\&. Lowercase or mixed case passwords may be +rejected by these servers\&. +.IP +Be cautious about including passwords in scripts or in the +\f(CWPASSWORD\fP environment variable\&. Also, on many systems the command +line of a running process may be seen via the \f(CWps\fP command to be +safe always allow rpcclient to prompt for a password and type it in +directly\&. +.IP +.IP "\fB-t terminal code\fP" +This option tells rpcclient how to interpret +filenames coming from the remote server\&. Usually Asian language +multibyte UNIX implementations use different character sets than +SMB/CIFS servers (\fIEUC\fP instead of \fISJIS\fP for example)\&. Setting +this parameter will let rpcclient convert between the UNIX filenames +and the SMB filenames correctly\&. This option has not been seriously +tested and may have some problems\&. +.IP +The terminal codes include \f(CWsjis\fP, \f(CWeuc\fP, \f(CWjis7\fP, \f(CWjis8\fP, +\f(CWjunet\fP, \f(CWhex\fP, \f(CWcap\fP\&. This is not a complete list, check the +Samba source code for the complete list\&. +.IP +.IP "\fB-m max protocol level\fP" +With the new code in Samba2\&.0, +\fBrpcclient\fP always attempts to connect at the maximum +protocols level the server supports\&. This parameter is +preserved for backwards compatibility, but any string +following the \fB-m\fP will be ignored\&. +.IP +.IP "\fB-W Domain\fP" +Override the default Domain, which is the remote server\'s +Domain\&. This option may be needed to connect to some servers\&. It is also +possible to specify the remote server name as the Domain, which will +force the username and password to be authenticated against the remote +server\'s local SAM instead of the Domain SAM\&. +.IP +.IP "\fB-c command string\fP" +command string is a semicolon separated +list of commands to be executed instead of prompting from stdin\&. +\fB-N\fP is implied by \fB-c\fP\&. +.IP +This is particularly useful in scripts, e\&.g\&. \f(CW-c \'lsaquery; enumusers -u\'\fP\&. +.IP +.PP +.SH "OPERATIONS" +.PP +Once the client is running, the user is presented with a prompt : +.PP +\f(CWsmb:\e>\fP +.PP +The prompt indicates that the client is ready and waiting to carry out +a user command\&. Each command is a single word, optionally followed by +parameters specific to that command\&. Command and parameters are +space-delimited unless these notes specifically state otherwise\&. All +commands are case-insensitive\&. Parameters to commands may or may not +be case sensitive, depending on the command\&. +.PP +You can specify names (e\&.g registry keys; user or group names; +service names) which have spaces in them by quoting the +name with double quotes, for example "dRMON SmartAgent"\&. +.PP +Parameters shown in square brackets (e\&.g\&., "[parameter]") are +optional\&. If not given, the command will use suitable +defaults\&. Parameters shown in angle brackets (e\&.g\&., "<parameter>") are +required\&. +.PP +Note that all commands operating on the server are actually performed +by issuing a request to the server\&. Thus the behavior may vary from +server to server, depending on how the server was implemented\&. +.PP +The commands available are listed in groups relating to different services: +.PP +.IP +.IP "Misccellaneous" +.IP +.IP +.IP "\fB? [command]\fP" +If "command" is specified, +the \fB?\fP command will display a brief informative message about the +specified command\&. If no command is specified, a list of available +commands will be displayed\&. +.IP +.IP "\fB! [shell command]\fP" +If "shell command" +is specified, the \fB!\fP command will execute a shell locally and run +the specified shell command\&. If no command is specified, a local shell +will be run\&. +.IP +.IP "\fBexit\fP" +Terminate the connection with the server and +exit from the program\&. +.IP +.IP "\fBhelp [command]\fP" +See the \fB?\fP +command above\&. +.IP +.IP "\fBquit\fP" +See the \fBexit\fP command\&. +.IP +.IP +.IP "Event Log" +.IP +.IP +.IP "\fBeventlog\fP" +list the events +.IP +.IP +.IP "Service Control" +.IP +It is possible to use command-line completion (if you have +the GNU readline library) for Service names, by pressing the +tab key\&. +.IP +.IP +.IP "\fBsvcenum\fP" +[-i] Lists Services Manager +.IP +.IP "\fBsvcinfo\fP" +<service> Service Information +.IP +.IP "\fBsvcstart\fP" +<service> [arg 0] [arg 1] \&.\&.\&. Start Service +.IP +.IP "\fBsvcstop\fP" +<service> Stop Service +.IP +.IP +.IP "Scheduler" +.IP +.IP +.IP "\fBat\fP" +Scheduler control (at /? for syntax) +.IP +.IP +.IP "Registry" +.IP +It is possible to use command-line completion (if you have +the GNU readline library) for registry key and value names, +by pressing the tab key\&. +.IP +.IP +.IP "\fBregenum\fP" +<keyname> Registry Enumeration (keys, values) +.IP +.IP "\fBregdeletekey\fP" +<keyname> Registry Key Delete +.IP +.IP "\fBregcreatekey\fP" +<keyname> [keyclass] Registry Key Create +.IP +.IP "\fBshutdown\fP" +[-m message] [-t timeout] [-r or --reboot] Server Shutdown +.IP +.IP "\fBregqueryval\fP" +<valname> Registry Value Query +.IP +.IP "\fBregquerykey\fP" +<keyname> Registry Key Query +.IP +.IP "\fBregdeleteval\fP" +<valname> Registry Value Delete +.IP +.IP "\fBregcreateval\fP" +<valname> <valtype> <value> Registry Key Create +.IP +.IP "\fBreggetsec\fP" +<keyname> Registry Key Security +.IP +.IP "\fBregtestsec\fP" +<keyname> Test Registry Key Security +.IP +.IP +.IP "Printing" +.IP +It is possible to use command-line completion (if you have +the GNU readline library) for Printer and job names, by +pressing the tab key\&. +.IP +.IP +.IP "\fBspoolenum\fP" +Enumerate Printers +.IP +.IP "\fBspooljobs\fP" +<printer name> Enumerate Printer Jobs +.IP +.IP "\fBspoolopen\fP" +<printer name> Spool Printer Open Test +.IP +.IP +.IP "Server" +.IP +.IP +.IP "\fBtime\fP" +Display remote time +.IP +.IP "\fBbrsinfo\fP" +Browser Query Info +.IP +.IP "\fBwksinfo\fP" +Workstation Query Info +.IP +.IP "\fBsrvinfo\fP" +Server Query Info +.IP +.IP "\fBsrvsessions\fP" +List sessions on a server +.IP +.IP "\fBsrvshares\fP" +List shares on a server +.IP +.IP "\fBsrvtransports\fP" +List transports on a server +.IP +.IP "\fBsrvconnections\fP" +List connections on a server +.IP +.IP "\fBsrvfiles\fP" +List files on a server +.IP +.IP +.IP "Local Security Authority" +.IP +.IP +.IP "\fBlsaquery\fP" +Query Info Policy (domain member or server) +.IP +.IP "\fBlsaenumdomains\fP" +Enumerate Trusted Domains +.IP +.IP "\fBlookupsids\fP" +Resolve names from SIDs +.IP +.IP "\fBlookupnames\fP" +Resolve SIDs from names +.IP +.IP "\fBquerysecret\fP" +LSA Query Secret (developer use) +.IP +.IP +.IP "NETLOGON" +.IP +.IP +.IP "\fBntlogin\fP" +[username] [password] NT Domain login test +.IP +.IP "\fBdomtrust\fP" +<domain> NT Inter-Domain test +.IP +.IP "\fBsamsync\fP" +SAM Synchronization Test (experimental) +.IP +.IP +.IP "SAM Database" +.IP +It is possible to use command-line completion (if you have +the GNU readline library) for user, group, alias and domain +names, by pressing the tab key\&. +.IP +.IP +.IP "\fBlookupdomain\fP" +Obtain SID for a local domain +.IP +.IP "\fBenumusers\fP" +SAM User Database Query (experimental!) +.IP +.IP "\fBaddgroupmem\fP" +<group rid> [user] [user] \&.\&.\&. SAM Add Domain Group Member +.IP +.IP "\fBaddaliasmem\fP" +<alias rid> [member sid1] [member sid2] \&.\&.\&. SAM Add Domain Alias Member +.IP +.IP "\fBdelgroupmem\fP" +<group rid> [user] [user] \&.\&.\&. SAM Delete Domain Group Member +.IP +.IP "\fBdelaliasmem\fP" +<alias rid> [member sid1] [member sid2] \&.\&.\&. SAM Delete Domain Alias Member +.IP +.IP "\fBcreategroup\fP" +SAM Create Domain Group +.IP +.IP "\fBcreatealias\fP" +SAM Create Domain Alias +.IP +.IP "\fBcreateuser\fP" +<username> SAM Create Domain User +.IP +.IP "\fBdelgroup\fP" +SAM Delete Domain Group +.IP +.IP "\fBdelalias\fP" +SAM Delete Domain Alias +.IP +.IP "\fBntpass\fP" +NT SAM Password Change +.IP +.IP "\fBsamuserset2\fP" +<username> [-s acb_bits] SAM User Set Info 2 (experimental!) +.IP +.IP "\fBsamuserset\fP" +<username> [-p password] SAM User Set Info (experimental!) +.IP +.IP "\fBsamuser\fP" +<username> SAM User Query (experimental!) +.IP +.IP "\fBsamgroup\fP" +<groupname> SAM Group Query (experimental!) +.IP +.IP "\fBsamalias\fP" +<aliasname> SAM Alias Query +.IP +.IP "\fBsamaliasmem\fP" +<aliasname> SAM Alias Members +.IP +.IP "\fBsamgroupmem\fP" +SAM Group Members +.IP +.IP "\fBsamtest\fP" +SAM User Encrypted RPC test (experimental!) +.IP +.IP "\fBenumaliases\fP" +SAM Aliases Database Query (experimental!) +.IP +.IP "\fBenumdomains\fP" +SAM Domains Database Query (experimental!) +.IP +.IP "\fBenumgroups\fP" +SAM Group Database Query (experimental!) +.IP +.IP "\fBdominfo\fP" +SAM Query Domain Info +.IP +.IP "\fBdispinfo\fP" +SAM Query Display Info +.IP +.IP +.PP +.SH "NOTES" +.PP +Some servers are fussy about the case of supplied usernames, +passwords, share names (AKA service names) and machine names\&. If you +fail to connect try giving all parameters in uppercase\&. +.PP +It is often necessary to use the \fB-n\fP option when connecting +to some types of servers\&. For example OS/2 LanManager insists on a valid +NetBIOS name being used, so you need to supply a valid name that would +be known to the server\&. +.PP +rpcclient only works on servers that support MSRPC over SMB\&. This includes +all versions of Windows NT, including the ports to Unix such as AS/U and +AFPS\&. Support for MSRPC over SMB in other servers is currently rare and +patchy, for example Samba 2\&.0 only supports a limited set of MSRPC commands, +and some of those are not supported very well\&. +.PP +.SH "ENVIRONMENT VARIABLES" +.PP +The variable \fBUSER\fP may contain the username of the person using the +client\&. This information is used only if the protocol level is high +enough to support session-level passwords\&. +.PP +The variable \fBPASSWORD\fP may contain the password of the person using +the client\&. This information is used only if the protocol level is +high enough to support session-level passwords\&. +.PP +.SH "INSTALLATION" +.PP +The location of the client program is a matter for individual system +administrators\&. The following are thus suggestions only\&. +.PP +It is recommended that the rpcclient software be installed in the +/usr/local/samba/bin or /usr/samba/bin directory, this directory +readable by all, writeable only by root\&. The client program itself +should be executable by all\&. The client should \fINOT\fP be setuid or +setgid! +.PP +The client log files should be put in a directory readable and +writeable only by the user\&. +.PP +To test the client, you will need to know the name of a running +SMB/CIFS server\&. It is possible to run \fBsmbd (8)\fP +an ordinary user - running that server as a daemon on a +user-accessible port (typically any port number over 1024) would +provide a suitable test server\&. +.PP +.SH "DIAGNOSTICS" +.PP +Most diagnostics issued by the client are logged in a specified log +file\&. The log file name is specified at compile time, but may be +overridden on the command line\&. +.PP +The number and nature of diagnostics available depends on the debug +level used by the client\&. If you have problems, set the debug level to +3 and peruse the log files\&. +.PP +.SH "VERSION" +.PP +This man page is correct for version 2\&.0 of the Samba suite\&. +.PP +.SH "BUGS" +.PP +.IP "WARNING!" +The MSPRC over SMB code has been developed from examining Network traces\&. +No documentation is available from the original creators (Microsoft) on +how MSRPC over SMB works, or how the individual MSRPC services work\&. +Microsoft\'s implementation of these services has been demonstrated (and +reported) to be\&.\&.\&. a bit flakey in places\&. +.IP +The development of Samba\'s implementation of these services is \fIalso\fP +a bit rough, and as more of the services are understood, it can even result +in versions of \fBsmbd (8)\fP and rpcclient that are +incompatible for some commands or services\&. Additionally, the developers +are sending reports to Microsoft, and problems found by or reported to +Microsoft are fixed in Service Packs, which may also result in +incompatibilities\&. +.IP +It is therefore not guaranteed that the execution of an rpcclient command will +work\&. It is also not guaranteed that the target server will continue to +operate, i\&.e the execution of an MSRPC command may cause a remote service to +fail, or even cause the remote server to fail\&. Usual rules apply, of course: +the developers bear absolutely no responsibility for the use, misuse, or +lack of use of rpcclient, by any person or persons, whether legal, +illegal, accidental, deliberate, intentional, malicious, curious, etc\&. +.IP +.IP "Command Completion" +Command-completion (available if you have the GNU readline library) used on +certain commands may not operate correctly if the word being completed (such as a registry key) contains a space\&. Typically, the name will be completed, but +you will have to go back and put quotes round it, yourself\&. +.IP +.IP "SAM Database command-completion" +Command-completion (available if you have the GNU readline library) of user, +group and alias names does not work on remote Domains, which would normally +be specified like this: +.br +\f(CWDOMAIN_name\e\euser_name\fP\&. +.br +The only names that can be completed in this fashion are the local names +in the SAM database of the target server\&. +.IP +.PP +.SH "AUTHOR" +.PP +The original Samba software and related utilities were created by +Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed +by the Samba Team as an Open Source project similar to the way the +Linux kernel is developed\&. +.PP +The original Samba man pages were written by Karl Auer\&. The man page +sources were converted to YODL format (another excellent piece of Open +Source software, available at +\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) +and updated for the Samba2\&.0 release by Jeremy Allison\&. This man page +was developed cut-and-paste style from the smbclient man page, by +Luke Kenneth Casson Leighton\&. +\fIsamba-bugs@samba\&.org\fP\&. +.PP +See \fBsamba (7)\fP to find out how to get a full +list of contributors and details on how to submit bug reports, +comments etc\&. +.PP diff --git a/docs/manpages/samba.7 b/docs/manpages/samba.7 index 96975f34c2..03ab086340 100644 --- a/docs/manpages/samba.7 +++ b/docs/manpages/samba.7 @@ -50,6 +50,18 @@ servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to any SMB server (such as a PC running Windows NT)\&. .IP +.IP "\fBrpcclient\fP" +.br +.br +The \fBrpcclient\fP +(1) program is a client that can \'talk\' to an +SMB/CIFS MSRPC server\&. Operations include things like managing a SAM +Database (users, groups and aliases) in the same way as the Windows NT +programs \fBUser Manager for Domains\fP and \fBServer Manager for Domains\fP; +managing a remote registry in the same way as the Windows NT programs +\fBREGEDT32\&.EXE\fP and \fBREGEDIT\&.EXE\fP; viewing a remote event log (same +as \fBEVENTVWR\&.EXE\fP)\&. +.IP .IP "\fBtestparm\fP" .br .br diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5 index cbe364a1b8..b99dd66bad 100644 --- a/docs/manpages/smb.conf.5 +++ b/docs/manpages/smb.conf.5 @@ -1463,11 +1463,11 @@ shares in a net view and in the browse list\&. \fBExample:\fP \f(CW browseable = No\fP .IP -.IP "\fBcase sensitive (G)\fP" +.IP "\fBcase sensitive (S)\fP" .IP See the discussion in the section \fBNAME MANGLING\fP\&. .IP -.IP "\fBcasesignames (G)\fP" +.IP "\fBcasesignames (S)\fP" .IP Synonym for \fB"case sensitive"\fP\&. .IP @@ -5301,7 +5301,7 @@ smb_shm_alloc : alloc of XX bytes failed"\fP\&. \fBExample:\fP \f(CW shared mem size = 5242880 ; Set to 5mb for a large number of files\&.\fP .IP -.IP "\fBshort preserve case (G)\fP" +.IP "\fBshort preserve case (S)\fP" .IP This boolean parameter controls if new files which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8 index 7088cfd557..7e6c03b5ff 100644 --- a/docs/manpages/smbd.8 +++ b/docs/manpages/smbd.8 @@ -409,11 +409,16 @@ performance\&. .PP .SH "SEE ALSO" .PP -\fBhosts_access (5)\fP, \fBinetd (8)\fP, \fBnmbd (8)\fP, -\fBsmb\&.conf (5)\fP, \fBsmbclient -(1)\fP, \fBtestparm (1)\fP, -\fBtestprns (1)\fP, and the Internet RFC\'s -\fBrfc1001\&.txt\fP, \fBrfc1002\&.txt\fP\&. In addition the CIFS (formerly SMB) +\fBhosts_access (5)\fP, +\fBinetd (8)\fP, +\fBnmbd (8)\fP, +\fBsmb\&.conf (5)\fP, +\fBsmbclient (1)\fP, +\fBtestparm (1)\fP, +\fBtestprns (1)\fP, +\fBrpcclient (1)\fP, +and the Internet RFC\'s \fBrfc1001\&.txt\fP, \fBrfc1002\&.txt\fP\&. +In addition the CIFS (formerly SMB) specification is available as a link from the Web page : http://samba\&.org/cifs/\&. .PP diff --git a/docs/textdocs/rpcclient.1.txt b/docs/textdocs/rpcclient.1.txt new file mode 100644 index 0000000000..78aaca02bc --- /dev/null +++ b/docs/textdocs/rpcclient.1.txt @@ -0,0 +1,685 @@ + +TITLE INFORMATION: rpcclient (1) +AUTHOR INFORMATION: Samba SAMBA +DATE INFORMATION: 23 Oct 1998 + +NAME +rpcclient - utility to manage MSRPC resources on servers + +SYNOPSIS + +rpcclient +[password] +-S servername +[-U [username][%][password]] +[-W domain] +[-l log basename] +[-d debuglevel] +[-O socket options] +[-i scope] +[-N] +[-n NetBIOS name] +[-h] +[-I dest IP] +[-E] +[-t terminal code] +[-c command string] +[-B IP addr] +[-s smb.conf] +[-m max protocol] + +DESCRIPTION + +This program is part of the Samba suite. + +rpcclient is a client that can 'talk' to an SMB/CIFS MSRPC server. +Operations include things like managing a SAM Database (users, groups +and aliases) in the same way as the Windows NT programs +User Manager for Domains and Server Manager for Domains; +managing a remote registry in the same way as the Windows NT programs +REGEDT32.EXE and REGEDIT.EXE; viewing a remote event log (same +as EVENTVWR.EXE) etc. + +Typical usage is like this: + +rpcclient -I 192.168.32.1 -S "*SMBSERVER" -U fred%secret -l log + +OPTIONS + +o servername servername is the name of the server you want +to use on the server. This should be the NetBIOS name of the SMB/CIFS +server, which can be *SMBSERVER on Windows NT 4.0 or Samba Servers. + +Note that the server name required is NOT necessarily the IP (DNS) +host name of the server! The name required is a NetBIOS server name, +which may or may not be the same as the IP hostname of the machine +running the server. Also, remember that having a period in a NetBIOS +name (such as an IP hostname) may cause connectivity problems on your +network: NT tends to strip NetBIOS names from the leading period +onwards. + +The server name is looked up according to either the +-R parameter to rpcclient or using the +name resolve order +parameter in the smb.conf file, allowing an administrator to change +the order and methods by which server names are looked up. + +o password password is the password required to access the +specified service on the specified server. If this parameter is +supplied, the -N option (suppress password prompt) is assumed. + +There is no default password. If no password is supplied on the +command line (either by using this parameter or adding a password to +the -U option (see below)) and the -N option is not specified, +the client will prompt for a password, even if the desired service +does not require one. (If no password is required, simply press ENTER +to provide a null password.) + +Note: Some servers (including OS/2 and Windows for Workgroups) insist +on an uppercase password. Lowercase or mixed case passwords may be +rejected by these servers. + +Be cautious about including passwords in scripts. + +o -s smb.conf This parameter specifies the pathname to the +Samba configuration file, smb.conf. This file controls all aspects of +the Samba setup on the machine and rpcclient also needs to read this +file. + +o -B IP addr The IP address to use when sending a broadcast packet. + +o -O socket options TCP socket options to set on the client +socket. See the socket options +parameter in the smb.conf (5) manpage for +the list of valid options. + +o -R name resolve order This option allows the user of +rpcclient to determine what name resolution services to use when +looking up the NetBIOS name of the host being connected to. + +The options are :"lmhosts", "host", "wins" and "bcast". They cause +names to be resolved as follows : + +o lmhosts : Lookup an IP address in the Samba lmhosts file. +The lmhosts file is stored in the same directory as the +smb.conf file. + +o 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 depended for instance on IRIX or +Solaris this may be controlled by the /etc/nsswitch.conf file). + +o wins : Query a name with the IP address listed in the wins +server parameter in the smb.conf file. If +no WINS server has been specified this method will be ignored. + +o bcast : Do a broadcast on each of the known local interfaces +listed in the interfaces parameter +in the smb.conf file. This is the least reliable of the name resolution +methods as it depends on the target host being on a locally connected +subnet. To specify a particular broadcast address the -B option +may be used. + +If this parameter is not set then the name resolve order defined +in the smb.conf file parameter +(name resolve order) +will be used. + +The default order is lmhosts, host, wins, bcast and without this +parameter or any entry in the "name resolve +order" parameter of the +smb.conf file the name resolution methods +will be attempted in this order. + +o -i scope This specifies a NetBIOS scope that rpcclient 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. + +o -N 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. + +o -n NetBIOS name 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. + +o -d debuglevel 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. + +o -p port This number is the TCP port number that will be used +when making connections to the server. The standard (well-known) TCP +port number for an SMB/CIFS server is 139, which is the default. + +o -l logfilename If specified, logfilename specifies a base +filename into which operational data from the running client will be +logged. + +The default base name is specified at compile time. + +The base name is used to generate actual log file names. For example, +if the name specified was "log", the debug file would be +log.client. + +The log file generated is never removed by the client. + +o -h Print the usage message for the client. + +o -I IP address 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. + +o -E This parameter causes the client to write messages to the +standard error stream (stderr) rather than to the standard output +stream. + +By default, the client writes messages to standard output - typically +the user's tty. + +Note that by default, debug information is always sent to stderr. +Debug information can instead be sent to a file, using the +-l log basename option. + +o -U username This specifies the user name that will be used by +the client to make a connection, assuming your server is not a downlevel +server that is running a protocol level that uses passwords on shares, +not on usernames. + +Some servers are fussy about the case of this name, and some insist +that it must be a valid NetBIOS name. + +If no username is supplied, it will default to an uppercase version of +the environment variable USER or LOGNAME in that order. If no +username is supplied and neither environment variable exists the +username "GUEST" will be used. + +If the USER environment variable contains a '%' character, +everything after that will be treated as a password. This allows you +to set the environment variable to be USER=username%password so +that a password is not passed on the command line (where it may be +seen by the ps command). + +If the service you are connecting to requires a password, it can be +supplied using the -U option, by appending a percent symbol ("%") +then the password to username. For example, to attach to a service as +user "fred" with password "secret", you would specify. + +-U fred%secret + +on the command line. Note that there are no spaces around the percent +symbol. + +If you specify the password as part of username then the -N option +(suppress password prompt) is assumed. + +If you specify the password as a parameter AND as part of username +then the password as part of username will take precedence. Putting +nothing before or nothing after the percent symbol will cause an empty +username or an empty password to be used, respectively. + +The password may also be specified by setting up an environment +variable called PASSWORD that contains the users password. Note +that this may be very insecure on some systems but on others allows +users to script rpcclient commands without having a password appear in +the command line of a process listing. + +Note: Some servers (including OS/2 and Windows for Workgroups) insist +on an uppercase password. Lowercase or mixed case passwords may be +rejected by these servers. + +Be cautious about including passwords in scripts or in the +PASSWORD 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 rpcclient to prompt for a password and type it in +directly. + +o -t terminal code This option tells rpcclient how to interpret +filenames coming from the remote server. Usually Asian language +multibyte UNIX implementations use different character sets than +SMB/CIFS servers (EUC instead of SJIS for example). Setting +this parameter will let rpcclient convert between the UNIX filenames +and the SMB filenames correctly. This option has not been seriously +tested and may have some problems. + +The terminal codes include sjis, euc, jis7, jis8, +junet, hex, cap. This is not a complete list, check the +Samba source code for the complete list. + +o -m max protocol level With the new code in Samba2.0, +rpcclient always attempts to connect at the maximum +protocols level the server supports. This parameter is +preserved for backwards compatibility, but any string +following the -m will be ignored. + +o -W Domain Override the default Domain, which is the remote server's +Domain. This option may be needed to connect to some servers. It is also +possible to specify the remote server name as the Domain, which will +force the username and password to be authenticated against the remote +server's local SAM instead of the Domain SAM. + +o -c command string command string is a semicolon separated +list of commands to be executed instead of prompting from stdin. +-N is implied by -c. + +This is particularly useful in scripts, e.g. -c 'lsaquery; enumusers -u'. + +OPERATIONS + +Once the client is running, the user is presented with a prompt : + +smb:\> + +The prompt indicates that the client is ready and waiting to carry out +a user command. Each command is a single word, optionally followed by +parameters specific to that command. Command and parameters are +space-delimited unless these notes specifically state otherwise. All +commands are case-insensitive. Parameters to commands may or may not +be case sensitive, depending on the command. + +You can specify names (e.g registry keys; user or group names; +service names) which have spaces in them by quoting the +name with double quotes, for example "dRMON SmartAgent". + +Parameters shown in square brackets (e.g., "[parameter]") are +optional. If not given, the command will use suitable +defaults. Parameters shown in angle brackets (e.g., "<parameter>") are +required. + +Note that all commands operating on the server are actually performed +by issuing a request to the server. Thus the behavior may vary from +server to server, depending on how the server was implemented. + +The commands available are listed in groups relating to different services: + +o Misccellaneous + + o ? [command] If "command" is specified, + the ? command will display a brief informative message about the + specified command. If no command is specified, a list of available + commands will be displayed. + + o ! [shell command] If "shell command" + is specified, the ! command will execute a shell locally and run + the specified shell command. If no command is specified, a local shell + will be run. + + o exit Terminate the connection with the server and + exit from the program. + + o help [command] See the ? + command above. + + o quit See the exit command. + +o Event Log + + o eventlog + list the events + +o Service Control + + It is possible to use command-line completion (if you have + the GNU readline library) for Service names, by pressing the + tab key. + + o svcenum + [-i] Lists Services Manager + + o svcinfo + <service> Service Information + + o svcstart + <service> [arg 0] [arg 1] ... Start Service + + o svcstop + <service> Stop Service + +o Scheduler + + o at + Scheduler control (at /? for syntax) + +o Registry + + It is possible to use command-line completion (if you have + the GNU readline library) for registry key and value names, + by pressing the tab key. + + o regenum + <keyname> Registry Enumeration (keys, values) + + o regdeletekey + <keyname> Registry Key Delete + + o regcreatekey + <keyname> [keyclass] Registry Key Create + + o shutdown + [-m message] [-t timeout] [-r or --reboot] Server Shutdown + + o regqueryval + <valname> Registry Value Query + + o regquerykey + <keyname> Registry Key Query + + o regdeleteval + <valname> Registry Value Delete + + o regcreateval + <valname> <valtype> <value> Registry Key Create + + o reggetsec + <keyname> Registry Key Security + + o regtestsec + <keyname> Test Registry Key Security + +o Printing + + It is possible to use command-line completion (if you have + the GNU readline library) for Printer and job names, by + pressing the tab key. + + o spoolenum + Enumerate Printers + + o spooljobs + <printer name> Enumerate Printer Jobs + + o spoolopen + <printer name> Spool Printer Open Test + +o Server + + o time + Display remote time + + o brsinfo + Browser Query Info + + o wksinfo + Workstation Query Info + + o srvinfo + Server Query Info + + o srvsessions + List sessions on a server + + o srvshares + List shares on a server + + o srvtransports + List transports on a server + + o srvconnections + List connections on a server + + o srvfiles + List files on a server + +o Local Security Authority + + o lsaquery + Query Info Policy (domain member or server) + + o lsaenumdomains + Enumerate Trusted Domains + + o lookupsids + Resolve names from SIDs + + o lookupnames + Resolve SIDs from names + + o querysecret + LSA Query Secret (developer use) + +o NETLOGON + + o ntlogin + [username] [password] NT Domain login test + + o domtrust + <domain> NT Inter-Domain test + + o samsync + SAM Synchronization Test (experimental) + +o SAM Database + + It is possible to use command-line completion (if you have + the GNU readline library) for user, group, alias and domain + names, by pressing the tab key. + + o lookupdomain + Obtain SID for a local domain + + o enumusers + SAM User Database Query (experimental!) + + o addgroupmem + <group rid> [user] [user] ... SAM Add Domain Group Member + + o addaliasmem + <alias rid> [member sid1] [member sid2] ... SAM Add Domain Alias Member + + o delgroupmem + <group rid> [user] [user] ... SAM Delete Domain Group Member + + o delaliasmem + <alias rid> [member sid1] [member sid2] ... SAM Delete Domain Alias Member + + o creategroup + SAM Create Domain Group + + o createalias + SAM Create Domain Alias + + o createuser + <username> SAM Create Domain User + + o delgroup + SAM Delete Domain Group + + o delalias + SAM Delete Domain Alias + + o ntpass + NT SAM Password Change + + o samuserset2 + <username> [-s acb_bits] SAM User Set Info 2 (experimental!) + + o samuserset + <username> [-p password] SAM User Set Info (experimental!) + + o samuser + <username> SAM User Query (experimental!) + + o samgroup + <groupname> SAM Group Query (experimental!) + + o samalias + <aliasname> SAM Alias Query + + o samaliasmem + <aliasname> SAM Alias Members + + o samgroupmem + SAM Group Members + + o samtest + SAM User Encrypted RPC test (experimental!) + + o enumaliases + SAM Aliases Database Query (experimental!) + + o enumdomains + SAM Domains Database Query (experimental!) + + o enumgroups + SAM Group Database Query (experimental!) + + o dominfo + SAM Query Domain Info + + o dispinfo + SAM Query Display Info + +NOTES + +Some servers are fussy about the case of supplied usernames, +passwords, share names (AKA service names) and machine names. If you +fail to connect try giving all parameters in uppercase. + +It is often necessary to use the -n option when connecting +to some types of servers. For example OS/2 LanManager insists on a valid +NetBIOS name being used, so you need to supply a valid name that would +be known to the server. + +rpcclient only works on servers that support MSRPC over SMB. This includes +all versions of Windows NT, including the ports to Unix such as AS/U and +AFPS. Support for MSRPC over SMB in other servers is currently rare and +patchy, for example Samba 2.0 only supports a limited set of MSRPC commands, +and some of those are not supported very well. + +ENVIRONMENT VARIABLES + +The variable USER may contain the username of the person using the +client. This information is used only if the protocol level is high +enough to support session-level passwords. + +The variable PASSWORD may contain the password of the person using +the client. This information is used only if the protocol level is +high enough to support session-level passwords. + +INSTALLATION + +The location of the client program is a matter for individual system +administrators. The following are thus suggestions only. + +It is recommended that the rpcclient software be installed in the +/usr/local/samba/bin or /usr/samba/bin directory, this directory +readable by all, writeable only by root. The client program itself +should be executable by all. The client should NOT be setuid or +setgid! + +The client log files should be put in a directory readable and +writeable only by the user. + +To test the client, you will need to know the name of a running +SMB/CIFS server. It is possible to run smbd (8) +an ordinary user - running that server as a daemon on a +user-accessible port (typically any port number over 1024) would +provide a suitable test server. + +DIAGNOSTICS + +Most diagnostics issued by the client are logged in a specified log +file. The log file name is specified at compile time, but may be +overridden on the command line. + +The number and nature of diagnostics available depends on the debug +level used by the client. If you have problems, set the debug level to +3 and peruse the log files. + +VERSION + +This man page is correct for version 2.0 of the Samba suite. + +BUGS + +o WARNING! +The MSPRC over SMB code has been developed from examining Network traces. +No documentation is available from the original creators (Microsoft) on +how MSRPC over SMB works, or how the individual MSRPC services work. +Microsoft's implementation of these services has been demonstrated (and +reported) to be... a bit flakey in places. + +The development of Samba's implementation of these services is also +a bit rough, and as more of the services are understood, it can even result +in versions of smbd (8) and rpcclient that are +incompatible for some commands or services. Additionally, the developers +are sending reports to Microsoft, and problems found by or reported to +Microsoft are fixed in Service Packs, which may also result in +incompatibilities. + +It is therefore not guaranteed that the execution of an rpcclient command will +work. It is also not guaranteed that the target server will continue to +operate, i.e the execution of an MSRPC command may cause a remote service to +fail, or even cause the remote server to fail. Usual rules apply, of course: +the developers bear absolutely no responsibility for the use, misuse, or +lack of use of rpcclient, by any person or persons, whether legal, +illegal, accidental, deliberate, intentional, malicious, curious, etc. + +o Command Completion +Command-completion (available if you have the GNU readline library) used on +certain commands may not operate correctly if the word being completed (such as a registry key) contains a space. Typically, the name will be completed, but +you will have to go back and put quotes round it, yourself. + +o SAM Database command-completion +Command-completion (available if you have the GNU readline library) of user, +group and alias names does not work on remote Domains, which would normally +be specified like this: + +DOMAIN_name\\user_name. + +The only names that can be completed in this fashion are the local names +in the SAM database of the target server. + +AUTHOR + +The original Samba software and related utilities were created by +Andrew Tridgell samba-bugs@samba.org. Samba is now developed +by the Samba Team as an Open Source project similar to the way the +Linux kernel is developed. + +The original Samba man pages were written by Karl Auer. The man page +sources were converted to YODL format (another excellent piece of Open +Source software, available at +ftp://ftp.icce.rug.nl/pub/unix/) +and updated for the Samba2.0 release by Jeremy Allison. This man page +was developed cut-and-paste style from the smbclient man page, by +Luke Kenneth Casson Leighton. +samba-bugs@samba.org. + +See samba (7) to find out how to get a full +list of contributors and details on how to submit bug reports, +comments etc. |