📄 rpcclient.1
字号:
.TPqueryusergroupsQuery user groups.TPquerygroupmemQuery group membership.TPqueryaliasmemQuery alias membership.TPquerydispinfoQuery display info.TPquerydominfoQuery domain info.TPenumdomusersEnumerate domain users.TPenumdomgroupsEnumerate domain groups.TPenumalsgroupsEnumerate alias groups.TPcreatedomuserCreate domain user.TPsamlookupnamesLook up names.TPsamlookupridsLook up names.TPdeletedomuserDelete domain user.TPsamquerysecobjQuery SAMR security object.TPgetdompwinfoRetrieve domain password info.TPlookupdomainLook up domain.SS "SPOOLSS".TPadddriver <arch> <config> [<version>]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\fBgetdriverdir\fR\&. Possible values for\fIarch\fR are the same as those for the \fBgetdriverdir\fR command\&. The \fIconfig\fR parameter is defined as follows:.nfLong 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.fiAny 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 \fIversion\fR 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\&..TPaddprinter <printername> <sharename> <drivername> <port>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 \fBadddriver\fR) and the \fIport\fRmust be a valid port name (see\fBenumports\fR\&..TPdeldriverDelete 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\&..TPdeldriverex <driver> [architecture] [version]Delete the specified printer driver including driver files\&. You can limit this action to a specific architecture and a specific version\&. If no architecure is given, all driver files of that driver will be deleted\&..TPenumdataEnumerate 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)\&..TPenumdataexEnumerate printer data for a key.TPenumjobs <printer>List the jobs and status of a given printer\&. This command corresponds to the MS Platform SDK EnumJobs() function.TPenumkeyEnumerate printer keys.TPenumports [level]Executes an EnumPorts() call using the specified info level\&. Currently only info levels 1 and 2 are supported\&..TPenumdrivers [level]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\&..TPenumprinters [level]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 1, 2 and 5\&..TPgetdata <printername> <valuename;>Retrieve the data for a given printer setting\&. See the \fBenumdata\fR command for more information\&. This command corresponds to the GetPrinterData() MS Platform SDK function\&..TPgetdataexGet printer driver data with keyname.TPgetdriver <printername>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\&..TPgetdriverdir <arch>Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture\&. Possible values for \fIarch\fR are "Windows 4\&.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000"\&..TPgetprinter <printername>Retrieve the current printer information\&. This command corresponds to the GetPrinter() MS Platform SDK function\&..TPgetprintprocdirGet print processor directory.TPopenprinter <printername>Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer\&..TPsetdriver <printername> <drivername>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 \fBenumprinters\fR and\fBenumdrivers\fR commands for obtaining a list of of installed printers and drivers\&..TPaddformAdd form.TPsetformSet form.TPgetformGet form.TPdeleteformDelete form.TPenumformsEnumerate form.TPsetprinterSet printer comment.TPsetprinterdataSet REG_SZ printer data.TPsetprintername <printername> <newprintername>Set printer name.TPrffpcnexRffpcnex test.SS "NETLOGON".TPlogonctrl2Logon Control 2.TPlogonctrlLogon Control.TPsamsyncSam Synchronisation.TPsamdeltasQuery Sam Deltas.TPsamlogonSam Logon.SS "GENERAL COMMANDS".TPdebuglevelSet the current debug level used to log information\&..TPhelp (?)Print a listing of all known commands or extended help on a particular command\&..TPquit (exit)Exit \fBrpcclient \fR\&..SH "BUGS".PP\fBrpcclient\fR 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\&..PPFrom Luke Leighton's original rpcclient man page:.PP\fBWARNING!\fR 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\&..PPThe 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 \fBsmbd\fR(8) and \fBrpcclient\fR(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\&..SH "VERSION".PPThis man page is correct for version 3\&.0 of the Samba suite\&..SH "AUTHOR".PPThe 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\&..PPThe 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\&.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -