1 <?xml version="1.0" encoding="iso8859-1"?>
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
5 <!ENTITY % globalentities SYSTEM './../global.ent'> %globalentities;
7 <refentry id="rpcclient.1">
10 <refentrytitle>rpcclient</refentrytitle>
11 <manvolnum>1</manvolnum>
16 <refname>rpcclient</refname>
17 <refpurpose>tool for executing client side
18 MS-RPC functions</refpurpose>
23 <command>rpcclient</command>
24 <arg choice="opt">-A authfile</arg>
25 <arg choice="opt">-c <command string></arg>
26 <arg choice="opt">-d debuglevel</arg>
27 <arg choice="opt">-h</arg>
28 <arg choice="opt">-l logfile</arg>
29 <arg choice="opt">-N</arg>
30 <arg choice="opt">-s <smb config file></arg>
31 <arg choice="opt">-U username[%password]</arg>
32 <arg choice="opt">-W workgroup</arg>
33 <arg choice="opt">-N</arg>
34 <arg choice="opt">-I destinationIP</arg>
35 <arg choice="req">server</arg>
40 <title>DESCRIPTION</title>
42 <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle>
43 <manvolnum>7</manvolnum></citerefentry> suite.</para>
45 <para><command>rpcclient</command> is a utility initially developed
46 to test MS-RPC functionality in Samba itself. It has undergone
47 several stages of development and stability. Many system administrators
48 have now written scripts around it to manage Windows NT clients from
49 their UNIX workstation. </para>
54 <title>OPTIONS</title>
59 <listitem><para>NetBIOS name of Server to which to connect.
60 The server can be any SMB/CIFS server. The name is
61 resolved using the <ulink url="smb.conf.5.html#NAMERESOLVEORDER">
62 <parameter>name resolve order</parameter></ulink> line from <citerefentry><refentrytitle>smb.conf</refentrytitle>
63 <manvolnum>5</manvolnum></citerefentry>.</para></listitem>
68 <term>-c|--command='command string'</term>
69 <listitem><para>execute semicolon separated commands (listed
70 below)) </para></listitem>
75 <term>-I IP-address</term>
76 <listitem><para><replaceable>IP address</replaceable> is the address of the server to connect to.
77 It should be specified in standard "a.b.c.d" notation. </para>
79 <para>Normally the client would attempt to locate a named
80 SMB/CIFS server by looking it up via the NetBIOS name resolution
81 mechanism described above in the <parameter>name resolve order</parameter>
82 parameter above. Using this parameter will force the client
83 to assume that the server is on the machine with the specified IP
84 address and the NetBIOS name component of the resource being
85 connected to will be ignored. </para>
87 <para>There is no default for this parameter. If not supplied,
88 it will be determined automatically by the client as described
89 above. </para></listitem>
93 &popt.common.credentials;
94 &popt.common.connection;
101 <title>COMMANDS</title>
104 <title>LSARPC</title>
107 <varlistentry><term>lsaquery</term><listitem><para>Query info policy</para></listitem></varlistentry>
109 <varlistentry><term>lookupsids</term><listitem><para>Resolve a list
110 of SIDs to usernames.
111 </para></listitem></varlistentry>
113 <varlistentry><term>lookupnames</term><listitem><para>Resolve a list
114 of usernames to SIDs.
115 </para></listitem></varlistentry>
117 <varlistentry><term>enumtrusts</term><listitem><para>Enumerate trusted domains</para></listitem></varlistentry>
119 <varlistentry><term>enumprivs</term><listitem><para>Enumerate privileges</para></listitem></varlistentry>
121 <varlistentry><term>getdispname</term><listitem><para>Get the privilege name</para></listitem></varlistentry>
123 <varlistentry><term>lsaenumsid</term><listitem><para>Enumerate the LSA SIDS</para></listitem></varlistentry>
125 <varlistentry><term>lsaenumprivsaccount</term><listitem><para>Enumerate the privileges of an SID</para></listitem></varlistentry>
127 <varlistentry><term>lsaenumacctrights</term><listitem><para>Enumerate the rights of an SID</para></listitem></varlistentry>
129 <varlistentry><term>lsaenumacctwithright</term><listitem><para>Enumerate accounts with a right</para></listitem></varlistentry>
131 <varlistentry><term>lsaaddacctrights</term><listitem><para>Add rights to an account</para></listitem></varlistentry>
133 <varlistentry><term>lsaremoveacctrights</term><listitem><para>Remove rights from an account</para></listitem></varlistentry>
135 <varlistentry><term>lsalookupprivvalue</term><listitem><para>Get a privilege value given its name</para></listitem></varlistentry>
137 <varlistentry><term>lsaquerysecobj</term><listitem><para>Query LSA security object</para></listitem></varlistentry>
143 <title>LSARPC-DS</title>
146 <varlistentry><term>dsroledominfo</term><listitem><para>Get Primary Domain Information</para></listitem></varlistentry>
151 <para><emphasis>DFS</emphasis></para>
153 <varlistentry><term>dfsexist</term><listitem><para>Query DFS support</para></listitem></varlistentry>
154 <varlistentry><term>dfsadd</term><listitem><para>Add a DFS share</para></listitem></varlistentry>
155 <varlistentry><term>dfsremove</term><listitem><para>Remove a DFS share</para></listitem></varlistentry>
156 <varlistentry><term>dfsgetinfo</term><listitem><para>Query DFS share info</para></listitem></varlistentry>
157 <varlistentry><term>dfsenum</term><listitem><para>Enumerate dfs shares</para></listitem></varlistentry>
165 <varlistentry><term>shutdown</term><listitem><para>Remote Shutdown</para></listitem></varlistentry>
166 <varlistentry><term>abortshutdown</term><listitem><para>Abort Shutdown</para></listitem></varlistentry>
172 <title>SRVSVC</title>
175 <varlistentry><term>srvinfo</term><listitem><para>Server query info</para></listitem></varlistentry>
177 <varlistentry><term>netshareenum</term><listitem><para>Enumerate shares</para></listitem></varlistentry>
179 <varlistentry><term>netfileenum</term><listitem><para>Enumerate open files</para></listitem></varlistentry>
181 <varlistentry><term>netremotetod</term><listitem><para>Fetch remote time of day</para></listitem></varlistentry>
191 <varlistentry><term>queryuser</term><listitem><para>Query user info</para></listitem></varlistentry>
192 <varlistentry><term>querygroup</term><listitem><para>Query group info</para></listitem></varlistentry>
193 <varlistentry><term>queryusergroups</term><listitem><para>Query user groups</para></listitem></varlistentry>
194 <varlistentry><term>querygroupmem</term><listitem><para>Query group membership</para></listitem></varlistentry>
195 <varlistentry><term>queryaliasmem</term><listitem><para>Query alias membership</para></listitem></varlistentry>
196 <varlistentry><term>querydispinfo</term><listitem><para>Query display info</para></listitem></varlistentry>
197 <varlistentry><term>querydominfo</term><listitem><para>Query domain info</para></listitem></varlistentry>
198 <varlistentry><term>enumdomusers</term><listitem><para>Enumerate domain users</para></listitem></varlistentry>
199 <varlistentry><term>enumdomgroups</term><listitem><para>Enumerate domain groups</para></listitem></varlistentry>
200 <varlistentry><term>enumalsgroups</term><listitem><para>Enumerate alias groups</para></listitem></varlistentry>
201 <varlistentry><term>createdomuser</term><listitem><para>Create domain user</para></listitem></varlistentry>
202 <varlistentry><term>samlookupnames</term><listitem><para>Look up names</para></listitem></varlistentry>
203 <varlistentry><term>samlookuprids</term><listitem><para>Look up names</para></listitem></varlistentry>
204 <varlistentry><term>deletedomuser</term><listitem><para>Delete domain user</para></listitem></varlistentry>
205 <varlistentry><term>samquerysecobj</term><listitem><para>Query SAMR security object</para></listitem></varlistentry>
206 <varlistentry><term>getdompwinfo</term><listitem><para>Retrieve domain password info</para></listitem></varlistentry>
207 <varlistentry><term>lookupdomain</term><listitem><para>Look up domain</para></listitem></varlistentry>
213 <title>SPOOLSS</title>
216 <varlistentry><term>adddriver <arch> <config></term>
218 Execute an AddPrinterDriver() RPC to install the printer driver
219 information on the server. Note that the driver files should
220 already exist in the directory returned by
221 <command>getdriverdir</command>. Possible values for
222 <parameter>arch</parameter> are the same as those for
223 the <command>getdriverdir</command> command.
224 The <parameter>config</parameter> parameter is defined as
227 <para><programlisting>
233 Language Monitor Name:\
235 Comma Separated list of Files
236 </programlisting></para>
238 <para>Any empty fields should be enter as the string "NULL". </para>
240 <para>Samba does not need to support the concept of Print Monitors
241 since these only apply to local printers whose driver can make
242 use of a bi-directional link for communication. This field should
243 be "NULL". On a remote NT print server, the Print Monitor for a
244 driver must already be installed prior to adding the driver or
245 else the RPC will fail. </para></listitem></varlistentry>
247 <varlistentry><term>addprinter <printername>
248 <sharename> <drivername> <port></term>
250 Add a printer on the remote server. This printer
251 will be automatically shared. Be aware that the printer driver
252 must already be installed on the server (see <command>adddriver</command>)
253 and the <parameter>port</parameter>must be a valid port name (see
254 <command>enumports</command>.</para>
255 </listitem></varlistentry>
258 <varlistentry><term>deldriver</term><listitem><para>Delete the
259 specified printer driver for all architectures. This
260 does not delete the actual driver files from the server,
261 only the entry from the server's list of drivers.
262 </para></listitem></varlistentry>
264 <varlistentry><term>enumdata</term><listitem><para>Enumerate all
265 printer setting data stored on the server. On Windows NT clients,
266 these values are stored in the registry, while Samba servers
267 store them in the printers TDB. This command corresponds
268 to the MS Platform SDK GetPrinterData() function (* This
269 command is currently unimplemented).</para></listitem></varlistentry>
271 <varlistentry><term>enumdataex</term><listitem><para>Enumerate printer data for a key</para></listitem></varlistentry>
273 <varlistentry><term>enumjobs <printer></term>
274 <listitem><para>List the jobs and status of a given printer.
275 This command corresponds to the MS Platform SDK EnumJobs()
276 function</para></listitem></varlistentry>
278 <varlistentry><term>enumkey</term><listitem><para>Enumerate
279 printer keys</para></listitem></varlistentry>
281 <varlistentry><term>enumports [level]</term>
283 Executes an EnumPorts() call using the specified
284 info level. Currently only info levels 1 and 2 are supported.
285 </para></listitem></varlistentry>
289 <varlistentry><term>enumdrivers [level]</term>
291 Execute an EnumPrinterDrivers() call. This lists the various installed
292 printer drivers for all architectures. Refer to the MS Platform SDK
293 documentation for more details of the various flags and calling
294 options. Currently supported info levels are 1, 2, and 3.</para></listitem></varlistentry>
298 <varlistentry><term>enumprinters [level]</term>
299 <listitem><para>Execute an EnumPrinters() call. This lists the various installed
300 and share printers. Refer to the MS Platform SDK documentation for
301 more details of the various flags and calling options. Currently
302 supported info levels are 0, 1, and 2.</para></listitem></varlistentry>
307 <varlistentry><term>getdata <printername> <valuename;></term>
308 <listitem><para>Retrieve the data for a given printer setting. See
309 the <command>enumdata</command> command for more information.
310 This command corresponds to the GetPrinterData() MS Platform
311 SDK function. </para></listitem></varlistentry>
313 <varlistentry><term>getdataex</term><listitem><para>Get
314 printer driver data with
315 keyname</para></listitem></varlistentry>
318 <varlistentry><term>getdriver <printername></term>
320 Retrieve the printer driver information (such as driver file,
321 config file, dependent files, etc...) for
322 the given printer. This command corresponds to the GetPrinterDriver()
323 MS Platform SDK function. Currently info level 1, 2, and 3 are supported.
324 </para></listitem></varlistentry>
327 <varlistentry><term>getdriverdir <arch></term>
329 Execute a GetPrinterDriverDirectory()
330 RPC to retrieve the SMB share name and subdirectory for
331 storing printer driver files for a given architecture. Possible
332 values for <parameter>arch</parameter> are "Windows 4.0"
333 (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
334 Alpha_AXP", and "Windows NT R4000". </para></listitem></varlistentry>
338 <varlistentry><term>getprinter <printername></term>
339 <listitem><para>Retrieve the current printer information. This command
340 corresponds to the GetPrinter() MS Platform SDK function.
341 </para></listitem></varlistentry>
343 <varlistentry><term>getprintprocdir</term><listitem><para>Get
345 directory</para></listitem></varlistentry>
347 <varlistentry><term>openprinter <printername></term>
348 <listitem><para>Execute an OpenPrinterEx() and ClosePrinter() RPC
349 against a given printer. </para></listitem></varlistentry>
351 <varlistentry><term>setdriver <printername>
352 <drivername></term>
353 <listitem><para>Execute a SetPrinter() command to update the printer driver
354 associated with an installed printer. The printer driver must
355 already be correctly installed on the print server. </para>
357 <para>See also the <command>enumprinters</command> and
358 <command>enumdrivers</command> commands for obtaining a list of
359 of installed printers and drivers.</para></listitem></varlistentry>
361 <varlistentry><term>addform</term><listitem><para>Add form</para></listitem></varlistentry>
362 <varlistentry><term>setform</term><listitem><para>Set form</para></listitem></varlistentry>
363 <varlistentry><term>getform</term><listitem><para>Get form</para></listitem></varlistentry>
364 <varlistentry><term>deleteform</term><listitem><para>Delete form</para></listitem></varlistentry>
365 <varlistentry><term>enumforms</term><listitem><para>Enumerate form</para></listitem></varlistentry>
366 <varlistentry><term>setprinter</term><listitem><para>Set printer comment</para></listitem></varlistentry>
367 <varlistentry><term>setprinterdata</term><listitem><para>Set REG_SZ printer data</para></listitem></varlistentry>
368 <varlistentry><term>rffpcnex</term><listitem><para>Rffpcnex test</para></listitem></varlistentry>
376 <title>NETLOGON</title>
380 <varlistentry><term>logonctrl2</term>
381 <listitem><para>Logon Control 2</para></listitem>
384 <varlistentry><term>logonctrl</term>
385 <listitem><para>Logon Control</para></listitem>
388 <varlistentry><term>samsync</term>
389 <listitem><para>Sam Synchronisation</para></listitem>
392 <varlistentry><term>samdeltas</term>
393 <listitem><para>Query Sam Deltas</para></listitem>
396 <varlistentry><term>samlogon</term>
397 <listitem><para>Sam Logon</para></listitem>
404 <title>GENERAL COMMANDS</title>
407 <varlistentry><term>debuglevel</term><listitem><para>Set the current
408 debug level used to log information.</para></listitem></varlistentry>
410 <varlistentry><term>help (?)</term><listitem><para>Print a listing of all
411 known commands or extended help on a particular command.
412 </para></listitem></varlistentry>
414 <varlistentry><term>quit (exit)</term><listitem><para>Exit <command>rpcclient
415 </command>.</para></listitem></varlistentry>
424 <para><command>rpcclient</command> is designed as a developer testing tool
425 and may not be robust in certain areas (such as command line parsing).
426 It has been known to generate a core dump upon failures when invalid
427 parameters where passed to the interpreter. </para>
429 <para>From Luke Leighton's original rpcclient man page:</para>
431 <para><emphasis>WARNING!</emphasis> The MSRPC over SMB code has
432 been developed from examining Network traces. No documentation is
433 available from the original creators (Microsoft) on how MSRPC over
434 SMB works, or how the individual MSRPC services work. Microsoft's
435 implementation of these services has been demonstrated (and reported)
436 to be... a bit flaky in places. </para>
438 <para>The development of Samba's implementation is also a bit rough,
439 and as more of the services are understood, it can even result in
440 versions of <citerefentry><refentrytitle>smbd</refentrytitle>
441 <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rpcclient</refentrytitle>
442 <manvolnum>1</manvolnum></citerefentry> that are incompatible for some commands or services. Additionally,
443 the developers are sending reports to Microsoft, and problems found
444 or reported to Microsoft are fixed in Service Packs, which may
445 result in incompatibilities.</para>
450 <title>VERSION</title>
452 <para>This man page is correct for version 3.0 of the Samba
457 <title>AUTHOR</title>
459 <para>The original Samba software and related utilities
460 were created by Andrew Tridgell. Samba is now developed
461 by the Samba Team as an Open Source project similar
462 to the way the Linux kernel is developed.</para>
464 <para>The original rpcclient man page was written by Matthew
465 Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter.
466 The conversion to DocBook for Samba 2.2 was done by Gerald
467 Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was
468 done by Alexander Bokovoy.</para>