1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
|
RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
NNNNAAAAMMMMEEEE
rpcclient - tool for executing client side MS-RPC functions
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
rrrrppppcccccccclllliiiieeeennnntttt [ ----AAAA aaaauuuutttthhhhffffiiiilllleeee ] [ ----cccc <<<<ccccoooommmmmmmmaaaannnndddd ssssttttrrrriiiinnnngggg>>>> ] [ ----dddd
ddddeeeebbbbuuuugggglllleeeevvvveeeellll ] [ ----hhhh ] [ ----llll llllooooggggffffiiiilllleeee ] [ ----NNNN ] [ ----ssss <<<<ssssmmmmbbbb
ccccoooonnnnffffiiiigggg ffffiiiilllleeee>>>> ] [ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee[[[[%%%%ppppaaaasssssssswwwwoooorrrrdddd]]]] ] [ ----WWWW wwwwoooorrrrkkkkggggrrrroooouuuupppp ]
[ ----NNNN ] sssseeeerrrrvvvveeeerrrr
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
This tool is part of the Samba suite.
rrrrppppcccccccclllliiiieeeennnntttt is a utility initially developed to test MS-RPC
functionality in Samba itself. It has undergone several
stages of development and stability. Many system
administrators have now written scripts around it to manage
Windows NT clients from their UNIX workstation.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
sssseeeerrrrvvvveeeerrrr
NetBIOS name of Server to which to connect. The server
can be any SMB/CIFS server. The name is resolved using
the _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r line from _s_m_b._c_o_n_f(_5).
----AAAA ffffiiiilllleeeennnnaaaammmmeeee
This option allows you to specify a file from which to
read the username and password used in the connection.
The format of the file is
username = <value>
password = <value>
domain = <value>
Make certain that the permissions on the file restrict
access from unwanted users.
----cccc ''''ccccoooommmmmmmmaaaannnndddd ssssttttrrrriiiinnnngggg''''
execute semicolon separated commands (listed below))
----dddd ddddeeeebbbbuuuugggglllleeeevvvveeeellll
set the debuglevel. Debug level 0 is the lowest and 100
being the highest. This should be set to 100 if you are
planning on submitting a bug report to the Samba team
(see _B_U_G_S._t_x_t).
----hhhh Print a summary of command line options.
----llll llllooooggggbbbbaaaasssseeeennnnaaaammmmeeee
File name for log/debug files. The extension '.client'
Page 1 (printed 1/7/103)
RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
will be appended. The log file is never removed by the
client.
----NNNN instruct rrrrppppcccccccclllliiiieeeennnntttt not to ask for a password. By
default, rrrrppppcccccccclllliiiieeeennnntttt will prompt for a password. See also
the -_U option.
----ssss ssssmmmmbbbb....ccccoooonnnnffff
Specifies the location of the all important _s_m_b._c_o_n_f
file.
----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee[[[[%%%%ppppaaaasssssssswwwwoooorrrrdddd]]]]
Sets the SMB username or username and password.
If %password is not specified, the user will be
prompted. The client will first check the UUUUSSSSEEEERRRR
environment variable, then the LLLLOOOOGGGGNNNNAAAAMMMMEEEE variable and if
either exists, the string is uppercased. If these
environmental variables are not found, the username
GUEST is used.
A third option is to use a credentials file which
contains the plaintext of the username and password.
This option is mainly provided for scripts where the
admin doesn't desire to pass the credentials on the
command line or via environment variables. If this
method is used, make certain that the permissions on
the file restrict access from unwanted users. See the
-_A for more details.
Be cautious about including passwords in scripts. Also,
on many systems the command line of a running process
may be seen via the ppppssss command. To be safe always allow
rrrrppppcccccccclllliiiieeeennnntttt to prompt for a password and type it in
directly.
----WWWW ddddoooommmmaaaaiiiinnnn
Set the SMB domain of the username. This overrides the
default domain which is the domain defined in smb.conf.
If the domain specified is the same as the server's
NetBIOS name, it causes the client to log on using the
server's local SAM (as opposed to the Domain SAM).
CCCCOOOOMMMMMMMMAAAANNNNDDDDSSSS
LLLLSSSSAAAARRRRPPPPCCCC
o+ llllssssaaaaqqqquuuueeeerrrryyyy
o+ llllooooooookkkkuuuuppppssssiiiiddddssss - Resolve a list of SIDs to usernames.
o+ llllooooooookkkkuuuuppppnnnnaaaammmmeeeessss - Resolve s list of usernames to SIDs.
Page 2 (printed 1/7/103)
RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
o+ eeeennnnuuuummmmttttrrrruuuussssttttssss
SSSSAAAAMMMMRRRR
o+ qqqquuuueeeerrrryyyyuuuusssseeeerrrr
o+ qqqquuuueeeerrrryyyyggggrrrroooouuuupppp
o+ qqqquuuueeeerrrryyyyuuuusssseeeerrrrggggrrrroooouuuuppppssss
o+ qqqquuuueeeerrrryyyyggggrrrroooouuuuppppmmmmeeeemmmm
o+ qqqquuuueeeerrrryyyyaaaalllliiiiaaaassssmmmmeeeemmmm
o+ qqqquuuueeeerrrryyyyddddiiiissssppppiiiinnnnffffoooo
o+ qqqquuuueeeerrrryyyyddddoooommmmiiiinnnnffffoooo
o+ eeeennnnuuuummmmddddoooommmmggggrrrroooouuuuppppssss
SSSSPPPPOOOOOOOOLLLLSSSSSSSS
o+ aaaaddddddddddddrrrriiiivvvveeeerrrr <<<<aaaarrrrcccchhhh>>>> <<<<ccccoooonnnnffffiiiigggg>>>> - Execute an AddPrinterDriver()
RPC to install the printer driver information on the
server. Note that the driver files should already exist in
the directory returned by ggggeeeettttddddrrrriiiivvvveeeerrrrddddiiiirrrr. Possible values
for _a_r_c_h are the same as those for the ggggeeeettttddddrrrriiiivvvveeeerrrrddddiiiirrrr
command. The _c_o_n_f_i_g parameter is defined as follows:
Long Printer Name:\
Driver File Name:\
Data File Name:\
Config File Name:\
Help File Name:\
Language Monitor Name:\
Default Data Type:\
Comma Separated list of Files
Any empty fields should be enter as the string "NULL".
Samba does not need to support the concept of Print
Monitors since these only apply to local printers whose
driver can make use of a bi-directional link for
communication. This field should be "NULL". On a remote NT
print server, the Print Monitor for a driver must already
be installed prior to adding the driver or else the RPC
will fail.
o+ aaaaddddddddpppprrrriiiinnnntttteeeerrrr <<<<pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee>>>> <<<<sssshhhhaaaarrrreeeennnnaaaammmmeeee>>>> <<<<ddddrrrriiiivvvveeeerrrrnnnnaaaammmmeeee>>>> <<<<ppppoooorrrrtttt>>>> -
Page 3 (printed 1/7/103)
RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
Add a printer on the remote server. This printer will be
automatically shared. Be aware that the printer driver
must already be installed on the server (see aaaaddddddddddddrrrriiiivvvveeeerrrr)
and the _p_o_r_tmust be a valid port name (see eeeennnnuuuummmmppppoooorrrrttttssss.
o+ ddddeeeellllddddrrrriiiivvvveeeerrrr - Delete the specified printer driver for all
architectures. This does not delete the actual driver
files from the server, only the entry from the server's
list of drivers.
o+ eeeennnnuuuummmmddddaaaattttaaaa - Enumerate all printer setting data stored on
the server. On Windows NT clients, these values are stored
in the registry, while Samba servers store them in the
printers TDB. This command corresponds to the MS Platform
SDK GetPrinterData() function (* This command is currently
unimplemented).
o+ eeeennnnuuuummmmjjjjoooobbbbssss <<<<pppprrrriiiinnnntttteeeerrrr>>>> - List the jobs and status of a given
printer. This command corresponds to the MS Platform SDK
EnumJobs() function (* This command is currently
unimplemented).
o+ eeeennnnuuuummmmppppoooorrrrttttssss [[[[lllleeeevvvveeeellll]]]] - Executes an EnumPorts() call using the
specified info level. Currently only info levels 1 and 2
are supported.
o+ eeeennnnuuuummmmddddrrrriiiivvvveeeerrrrssss [[[[lllleeeevvvveeeellll]]]] - Execute an EnumPrinterDrivers()
call. This lists the various installed printer drivers for
all architectures. Refer to the MS Platform SDK
documentation for more details of the various flags and
calling options. Currently supported info levels are 1, 2,
and 3.
o+ eeeennnnuuuummmmpppprrrriiiinnnntttteeeerrrrssss [[[[lllleeeevvvveeeellll]]]] - Execute an EnumPrinters() call.
This lists the various installed and share printers. Refer
to the MS Platform SDK documentation for more details of
the various flags and calling options. Currently supported
info levels are 0, 1, and 2.
o+ ggggeeeettttddddaaaattttaaaa <<<<pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee>>>> - Retrieve the data for a given
printer setting. See the eeeennnnuuuummmmddddaaaattttaaaa command for more
information. This command corresponds to the
GetPrinterData() MS Platform SDK function (* This command
is currently unimplemented).
o+ ggggeeeettttddddrrrriiiivvvveeeerrrr <<<<pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee>>>> - Retrieve the printer driver
information (such as driver file, config file, dependent
files, etc...) for the given printer. This command
corresponds to the GetPrinterDriver() MS Platform SDK
function. Currently info level 1, 2, and 3 are supported.
o+ ggggeeeettttddddrrrriiiivvvveeeerrrrddddiiiirrrr <<<<aaaarrrrcccchhhh>>>> - Execute a
Page 4 (printed 1/7/103)
RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
GetPrinterDriverDirectory() RPC to retreive the SMB share
name and subdirectory for storing printer driver files for
a given architecture. Possible values for _a_r_c_h are
"Windows 4.0" (for Windows 95/98), "Windows NT x86",
"Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT
R4000".
o+ ggggeeeettttpppprrrriiiinnnntttteeeerrrr <<<<pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee>>>> - Retrieve the current printer
information. This command corresponds to the GetPrinter()
MS Platform SDK function.
o+ ooooppppeeeennnnpppprrrriiiinnnntttteeeerrrr <<<<pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee>>>> - Execute an OpenPrinterEx() and
ClosePrinter() RPC against a given printer.
o+ sssseeeettttddddrrrriiiivvvveeeerrrr <<<<pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee>>>> <<<<ddddrrrriiiivvvveeeerrrrnnnnaaaammmmeeee>>>> - Execute a
SetPrinter() command to update the printer driver
associated with an installed printer. The printer driver
must already be correctly installed on the print server.
See also the eeeennnnuuuummmmpppprrrriiiinnnntttteeeerrrrssss and eeeennnnuuuummmmddddrrrriiiivvvveeeerrrrssss commands for
obtaining a list of of installed printers and drivers.
GGGGEEEENNNNEEEERRRRAAAALLLL OOOOPPPPTTTTIIIIOOOONNNNSSSS
o+ ddddeeeebbbbuuuugggglllleeeevvvveeeellll - Set the current debug level used to log
information.
o+ hhhheeeellllpppp ((((????)))) - Print a listing of all known commands or
extended help on a particular command.
o+ qqqquuuuiiiitttt ((((eeeexxxxiiiitttt)))) - Exit rrrrppppcccccccclllliiiieeeennnntttt .
BBBBUUUUGGGGSSSS
rrrrppppcccccccclllliiiieeeennnntttt is designed as a developer testing tool and may
not be robust in certain areas (such as command line
parsing). It has been known to generate a core dump upon
failures when invalid parameters where passed to the
interpreter.
From Luke Leighton's original rpcclient man page:
""""WWWWAAAARRRRNNNNIIIINNNNGGGG!!!! The MSRPC 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 flaky in places.
The development of Samba's implementation is also a bit
rough, and as more of the services are understood, it can
even result in versions of ssssmmmmbbbbdddd((((8888)))) and rrrrppppcccccccclllliiiieeeennnntttt((((1111)))) that are
incompatible for some commands or services. Additionally,
Page 5 (printed 1/7/103)
RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) RRRRPPPPCCCCCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
the developers are sending reports to Microsoft, and
problems found or reported to Microsoft are fixed in Service
Packs, which may result in incompatibilities."
VVVVEEEERRRRSSSSIIIIOOOONNNN
This man page is correct for version 2.2 of the Samba suite.
AAAAUUUUTTTTHHHHOOOORRRR
The original Samba software and related utilities were
created by Andrew Tridgell. Samba is now developed by the
Samba Team as an Open Source project similar to the way the
Linux kernel is developed.
The original rpcclient man page was written by Matthew
Geddes, Luke Kenneth Casson Leighton, and rewritten by
Gerald Carter. The conversion to DocBook for Samba 2.2 was
done by Gerald Carter.
Page 6 (printed 1/7/103)
|
