RPCCLIENT(1) | User Commands | RPCCLIENT(1) |
NAME¶
rpcclient - tool for executing client side MS-RPC functions
SYNOPSIS¶
rpcclient [-A authfile] [-c <command string>] [-d debuglevel] [-l logdir] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-I destinationIP] {server}
DESCRIPTION¶
This tool is part of the samba(7) suite.
rpcclient 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.
OPTIONS¶
server
-c|--command=<command string>
-I|--dest-ip IP-address
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.
-p|--port port
-d|--debuglevel=level
The higher this value, the more detail will be logged to the log files about the activities of the server. 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.
Note that specifying this parameter here will override the log level parameter in the smb.conf file.
-V|--version
-s|--configfile=<configuration file>
-l|--log-basename=logdirectory
--option=<name>=<value>
-N|--no-pass
Unless a password is specified on the command line or this parameter is specified, the client will request a password.
If a password is specified on the command line and this option is also defined the password on the command line will be silently ingnored and no password will be used.
-k|--kerberos
-C|--use-ccache
-A|--authentication-file=filename
username = <value> password = <value> domain = <value>
Make certain that the permissions on the file restrict access from unwanted users.
-U|--user=username[%password]
If %password is not specified, the user will be prompted. The client will first check the USER environment variable, then the LOGNAME 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 does not wish 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 ps command. To be safe always allow rpcclient to prompt for a password and type it in directly.
-S|--signing on|off|required
-P|--machine-pass
-e|--encrypt
--pw-nt-hash
-n|--netbiosname <primary NetBIOS name>
-i|--scope <scope>
-W|--workgroup=domain
-O|--socket-options socket options
-?|--help
--usage
COMMANDS¶
LSARPC¶
lsaquery
lookupsids
lookupnames
enumtrust
enumprivs
getdispname
lsaenumsid
lsaenumprivsaccount
lsaenumacctrights
lsaenumacctwithright
lsaaddacctrights
lsaremoveacctrights
lsalookupprivvalue
lsaquerysecobj
LSARPC-DS¶
dsroledominfo
DFS
dfsexist
dfsadd
dfsremove
dfsgetinfo
dfsenum
REG¶
shutdown
abortshutdown
SRVSVC¶
srvinfo
netshareenum
netfileenum
netremotetod
SAMR¶
queryuser
querygroup
queryusergroups
querygroupmem
queryaliasmem
querydispinfo
querydominfo
enumdomusers
enumdomgroups
enumalsgroups
createdomuser
samlookupnames
samlookuprids
deletedomuser
samquerysecobj
getdompwinfo
lookupdomain
SPOOLSS¶
adddriver <arch> <config> [<version>]
Long Driver 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.
The version parameter lets you specify the printer driver version number. If omitted, the default driver version for the specified architecture will be used. This option can be used to upload Windows 2000 (version 3) printer drivers.
addprinter <printername> <sharename> <drivername> <port>
deldriver <driver>
deldriverex <driver> [architecture] [version] [flags]
enumdata
enumdataex
enumjobs <printer>
enumkey
enumports [level]
enumdrivers [level]
enumprinters [level]
getdata <printername> <valuename;>
getdataex
getdriver <printername>
getdriverdir <arch>
getprinter <printername>
getprintprocdir
openprinter <printername>
setdriver <printername> <drivername>
See also the enumprinters and enumdrivers commands for obtaining a list of of installed printers and drivers.
addform
setform
getform
deleteform
enumforms
setprinter
setprinterdata
setprintername <printername> <newprintername>
rffpcnex
NETLOGON¶
logonctrl2
logonctrl
samsync
samdeltas
samlogon
FSRVP¶
fss_is_path_sup <share>
fss_get_sup_version
fss_create_expose <context> <[ro|rw]> <share1> [share2] ... [shareN]
fss_delete <base_share> <shadow_copy_set_id> <shadow_copy_id>
fss_has_shadow_copy <base_share>
fss_get_mapping <base_share> <shadow_copy_set_id> <shadow_copy_id>
fss_recovery_complete <shadow_copy_set_id>
GENERAL COMMANDS¶
debuglevel
help (?)
quit (exit)
BUGS¶
rpcclient 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:
WARNING! 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 smbd(8) and rpcclient(1) that are incompatible for some commands or services. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may result in incompatibilities.
VERSION¶
This man page is correct for version 3 of the Samba suite.
AUTHOR¶
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. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
06/20/2018 | Samba 4.2 |