rpcping.exe

Associated Error Codes

Below lists error codes and symbolic names found for this module.

Code	Found in	Description
0x2711	8.11011	Usage: rpcping [-t ] [-s ] [-e \|-f [,MajorVer]] [-O ] [-u ] [-a ] [-N ] [-I ] [-C ] [-T ] [-M ] [-S ] [-P ] [-F ] [-H ] [-o ] [-B ] [-b] [-E] [-q] [-c] [-A ] [-U ] [-r ] [-v ]
0x2712	78.11011	Pings a server using RPC. Options are: -t - protocol sequence to use. Can be one of the standard RPC protocol sequences - ncacn_ip_tcp, ncacn_np, ncacn_http, etc. If not specified, default is ncacn_ip_tcp. -s - the server address. If not specified, the local machine will be pinged. E.g. server, server.com, 157.59.244.141 -e - the endpoint to ping. If none is specified, the endpoint mapper on the target machine will be pinged. This option is mutually exclusive with the interface (-f) option. -o - the binding options for the RPC ping. See the MSDN for more details (RpcStringBindingCompose and RPC over HTTP). -f [,MajorVer] - the interface to ping. This option is mutually exclusive with the endpoint option. The interface is specified as a UUID. If the MajorVer is not specified, version 1 of the interface will be sought. When interface is specified, rpcping will query the endpoint mapper on the target machine to retrieve the endpoint for the specified interface. The endpoint mapper will be queried using the options specified in the command line. -O
0x2713	78.11011	-N - specifies a server principal name. Same semantics as the ServerPrincName argument to RpcBindingSetAuthInfoEx. See the MSDN for more information on RpcBidningSetAuthInfoEx. This field can be used only when authentication level and security package are selected. -I - allows you to specify alternative identity to connect to the server. The identity is in the form user,domain,password where the three fields have the obvious meaning. If the user name, domain or password have special characters that can be interpreted by the shell be sure to enclose the identity in double quotes. You can specify * instead of the password and RPC will prompt you to enter the password without echoing it on the screen. If this field is not specified, the identity of the logged on user will be used. This field can be used only when authentication level and security package are selected. -C - a hex bitmask of flags. It has the same meaning as the Capabilities field in the RPC_SECURITY_QOS structure described in the MSDN. This field can be used only when authentication level and security package are selected. -T - can be static or dynamic. If not specified, dynamic is the default. This field can be used only when authentication level and security package are selected. -M - can be anonymous, identify, impersonate or delegate. Default is impersonate. This field can be used only when authentication level and security package are selected.
0x2714	1011	-S - the expected SID of the server. For more information see the Sid field in the RPC_SECURITY_QOS structure in the MSDN. Using this option requires Windows .NET Server 2003 or higher. This field can be used only when authentication level and security package are selected. -Z - the EffectiveOnly setting to use. For more information see the EffectiveOnly field in the RPC_SECURITY_QOS structure in MSDN. Using this option requires Windows Vista or higher. This field can be used only when authentication level and security package are selected. -D - the security descriptor (in string format) of the server when using mutual authentication. For more information see the ServerSecurityDescriptor field in the RPC_SECURITY_QOS structure in MSDN. Using this option requires Windows 8 or higher. This field can be used only when authentication level and security package are selected. -P - specifies the identity to authenticate with to the RPC/HTTP proxy. Has the same format as for the -I option. Also, you must specify security package (-u), authentication level (-a), and authentication schemes (-H) in order to use this option. -F - the flags to pass for RPC/HTTP front end authentication. The flags may be specified as numbers or names The currently recognized flags are: Use SSL - 1 or ssl or use_ssl Use first auth scheme - 2 or first or use_first See the Flags field in RPC_HTTP_TRANSPORT_CREDENTIALS for more information. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -H - the authentication schemes to use for RPC/HTTP front end authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM Certificate - 65536 or Cert Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -B - the server certificate subject. For more information, see the ServerCertificateSubject field in the RPC_HTTP_TRANSPORT_CREDENTIALS structure in the MSDN. You must use SSL for this option to work. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -b - retrieves the server certificate subject from the certificate sent by the server and prints it to a screen or a log file. Valid only when the Proxy Echo only option (-E) and the use SSL options are specified. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -R - specifies the HTTP proxy. if it's 'none', we will not use HTTP proxy but directly attempt the RPC proxy. the value 'default' means to use the IE settings in your client machine. any other value will be treated as the explicit HTTP proxy. if you don't specify this flag, the default value is assumed, that is, the IE settings are checked. this flag is valid only when the -E (Echo Only) flag is enabled.
0x2715	8.11011	-E - restricts the ping to the RPC/HTTP proxy only. The ping does not reach the server. Useful when trying to establish whether the RPC/HTTP proxy is reachable. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. To specify an HTTP proxy, use the -R flag. If an HTTP proxy is specified in the -o flag, this option will be ignored. -q - quiet mode. Does not issue any prompts except for passwords. Assumes 'Y' response to all queries. Use this option with care. -c - use smart card certificate. RPCPing will prompt user to choose smart card. -A - specifies the identity to authenticate with to the HTTP proxy. Has the same format as for the -I option. Also, you must specify authentication schemes (-U), security package (-u) and authentication level (-a) in order to use this option. -U - the authentication schemes to use for HTTP proxy authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM You must specify security package (-u) and authentication level (-a) in order to use this option. -r - if multiple iterations are specified, this option will make rpcping display current execution statistics periodically instead after the last call. The report interval is given in seconds. Default is 15. -v - tells rpcping how verbose to make the output. Default value is 1. 2 and 3 provide more output from rpcping. Example: Find out if your Exchange server that you connect through RPC/HTTP is accessible: rpcping -t ncacn_http -s exchange_server -o RpcProxy=front_end_proxy -P "username,domain,*" -H Basic -u NTLM -a connect -F 3 When prompted for the password, enter it. exchange_server is the name of your exchange server, front_end_proxy is the name of your proxy, username and domain are your user name and domain as you would enter them in the Outlook prompt. The other parameters will ask rpcping to ping your Exchange server in exactly the same way as Outlook will connect to it for the typical profile. -p - Prompt for credentials if authentication fails.
0x2725	78.11011	Out of memory
0x2726	78.11011	Cannot allocate %1!d! bytes
0x2728	78.11011	Invalid switch: %1!s!
0x2729	78.11011	Invalid option %1!c!, missing required parameter
0x272a	78.11011	RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006
0x272b	78.11011	%1!s!
0x272c	78.11011	%1!s!
0x272d	8.11011	If you specify auth identity, you must specify authentication level and security package
0x272e	8.11011	If you specify identity tracking, you must specify authentication level and security package
0x272f	8.11011	If you specify impersonation type, you must specify authentication level and security package
0x2730	8.11011	If you specify a SID, you must specify authentication level and security package
0x2731	8.11011	To prompt for credentials, you must specify authentication level and security package
0x2732	8.11011	Cannot parse security package id
0x2733	8.11011	Cannot parse authentication level
0x2734	8.11011	Cannot parse flags string
0x2735	8.11011	Cannot parse auth schemes array
0x2736	8.11011	Cannot parse identity tracking mode
0x2737	8.11011	Cannot parse impersonation type
0x2774	78.11011	Error %1!d! : %2!s! returned in the WinHttpQueryAuthSchemes. possibably anonymous requests or requests on unsecure channel are not allowed
0x2775	78.11011	Error %1!d! : %2!s! returned in WinHttpSetOption
0x2776	78.11011	Error %1!d! : %2!s! returned in WinhttpSetOption (3)
0x2777	78.11011	Error %1!d! : %2!s! returned in WinHttpSetOption
0x2778	78.11011	Status %1!d! returned in the RpcCertGeneratePrincipalName
0x2779	78.11011	Error %1!d! : %2!s! returned in CredIsMarshaledCredential
0x277a	78.11011	Error %1!d! : %2!s! returned in CredUnMarshalCredential
0x277b	78.11011	Error %1!d! : %2!s! returned in CertOpenSystemStore
0x277c	78.11011	Error %1!d! : %2!s! returned in CertFindCertificateInStore
0x277d	78.11011	Error %1!d! : %2!s! returned in CryptAcquireContext
0x277e	78.11011	Error %1!d! : %2!s! returned in CryptSetProvParam
0x277f	78.11011	Error %1!d! : %2!s! returned in WinHttpSetOption (1)
0x2780	78.11011	Error %1!d! : %2!s! returned in WinHttpSetOption (cert)
0x2781	78.11011	Error %1!d! : %2!s! returned in MultiByteToWideChar
0x2782	78.11011	Error %1!d! : %2!s! returned in RtlStringCbPrintf
0x2783	78.11011	Error %1!d! : %2!s! returned in WinHttpSetCredentials
0x2784	78.11011	Error %1!d! : %2!s! returned in WinHttpSendRequest
0x2785	78.11011	Error %1!d! : %2!s! returned in WinHttpReceivedResponse
0x2786	78.11011	Error %1!d! : %2!s! returned in WinHttpQueryHeadersFailed
0x2787	78.11011	Error %1!d! : %2!s! returned in WinHttpSetCredentials for RPC Proxy
0x2788	78.11011	Error %1!d! : %2!s! returned in WinHttpSetOption - 4
0x2789	78.11011	Error %1!d! : %2!s! returned in WinHttpSetCredentials for Http Proxy
0x278a	78.11011	Error %1!d! : %2!s! returned in WinHttpQueryHeaders - 2
0x278b	78.11011	Error %1!d! : %2!s! returned in RtlStringCchCopy
0x278c	78.11011	Error %1!d! : %2!s! returned in WinHttpOpen
0x278d	78.11011	Error %1!d! : %2!s! returned in WinHttpConnect
0x278e	78.11011	Error %1!d! : %2!s! returned in WinHttpOpenRequest
0x278f	78.11011	Error %1!d! : %2!s! returned in GetModuleHandle
0x2790	78.11011	Error %1!d! : %2!s! returned in GetProcessAddress
0x2791	78.11011	%1!s! failed - %2!d! (%3!08x!)
0x2792	78.11011	Error %1!d! : %2!s! returned in CertGetCertificateContextProperty
0x2793	78.11011	Error %1!d! : %2!s! returned in WinHttpSendRequest - probably server is not configured to accept smart cards
0x2794	8.11011	Error retrieving user input
0x27d9	78.11011	Use Server Preffered Auth Scheme: %1!d!
0x27da	78.11011	Use Proxy Preffered Auth Scheme: %1!d!
0x27db	78.11011	Client failed to authenticate to RPC proxy
0x27dc	78.11011	To use BASIC authentication scheme for RPC Proxy, you must specify the user/domain/password (-P)
0x27dd	78.11011	To use BASIC authentication scheme for HTTP Proxy, you must specify the user/domain/password (-A)
0x27de	78.11011	Setting autologon policy to low
0x27df	78.11011	To use implicit logon credentials with NTLM, you must use SSL with server certificate subject or disable lanman hash
0x27e0	78.11011	Setting autologon policy to high
0x27e1	78.11011	Authentication scheme %1!d! is not supported. Currently only NTLM and BASIC are supported
0x27e2	78.11011	Cannot convert server certificate subject to Unicode
0x27e3	78.11011	The server certificate subject from the RPC proxy (%1!s!, %2!s!) does not match the one (%3!s!) specified
0x27e4	78.11011	CredIsMarshaledCredential failed with NULL certCredentialInfo
0x27e5	78.11011	CredIsMarshaledCredential failed with wrong CredType: %1!d!
0x27e6	78.11011	CryptAcquireContextW failed with NULL cspProvider
0x27e7	78.11011	Smart card auth has no implicit credentials
0x27e8	78.11011	You must specify at least one authentication scheme if you specify the RPC_C_HTTP_FLAG_USE_FIRST_AUTH_SCHEME
0x27e9	78.11011	WinHttpSetCredentials for target server called
0x27ea	78.11011	Sending ping to server
0x27eb	78.11011	Server requires a certificate and client did not specify one. Exiting ...
0x27ec	78.11011	Client certificate is required by the server
0x27ed	78.11011	Smart card specified but not accepted by server (ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED returned). Exiting ...
0x27ee	78.11011	No smart card specified. Exiting ...
0x27ef	78.11011	Response from server received: %1!d!
0x27f0	78.11011	Smart card used and error 401 returned from server - probably server is not configured to accept smart cards
0x27f1	78.11011	Client is not authorized to ping RPC proxy
0x27f2	78.11011	Access denied pinging HTTP proxy
0x27f3	78.11011	First WinHttpQueryHeaders should not have succeeded
0x27f4	78.11011	You mush specify Rpc Proxy
0x27f5	78.11011	Error when checking IE settings %1!d!
0x27f6	78.11011	Error %1!d! : %2!s! port # is too long
0x27f7	78.11011	The IE settings are ambiguous. We don't know whether we should directly access RPC proxy or use HTTP proxy. You can use -R to clarify it
0x27f8	78.11011	Either an interface or an endpoint can be given, but not both
0x27f9	78.11011	Cannot find protocol sequence: %1!s!. Exiting...
0x27fa	78.11011	SChannel requires a certificate to be supplied
0x27fb	78.11011	Trying to resolve interface %1!X!-%2!X!-%3!X!-%4!X!%5!X!%6!X!%7!X!%8!X!%9!X!%10!X!%11!X!, Version: %12!d!.0
0x27fc	78.11011	Wrong access type %1!u!
0x27fd	78.11011	RPCPinging proxy server %1!s! with Echo Request Packet
0x27fe	78.11011	Pinging successfully completed in %1!d! ms
0x27ff	78.11011	Ping failed
0x2800	78.11011	Exception %1!lu! (0x%2!08lX!)
0x2801	78.11011	Couldn't get EEInfo: %1!d!
0x2802	78.11011	Number of records is: %1!d!
0x2803	78.11011	Couldn't finish enumeration: %1!d!
0x2804	78.11011	ComputerName is %1!s!
0x2805	78.11011	ProcessID is %1!d!
0x2806	78.11011	System Time is: %1!d!/%2!d!/%3!d! %4!d!:%5!d!:%6!d!:%7!d!
0x2807	78.11011	Generating component is %1!d!
0x2808	78.11011	Status is 0x%1!X!, %2!d!
0x2809	78.11011	Detection location is %1!d!
0x280a	78.11011	Flags is %1!d!
0x280b	78.11011	NumberOfParameters is %1!d!
0x280c	78.11011	Ansi string: %1!S!
0x280d	78.11011	Unicode string: %1!s!
0x280e	78.11011	Long val: 0x%1!x!
0x280f	78.11011	Short val: %1!d!
0x2810	78.11011	Pointer val: 0x%1!x!
0x2811	78.11011	Truncated
0x2812	78.11011	Invalid type: %1!d!
0x2813	78.11011	If you specify auth identity in the form , a domain must be specified: %1!s!
0x2814	78.11011	If you specify auth identity in the form , a password must be specified: %1!s!,%2!s!
0x2815	78.11011	Enter password for %1!s!:
0x2816	78.11011	Cannot parse bitflags: %1!s!
0x2817	78.11011	You must specify authentication level, security package and ncacn_http protocol sequence if you want to use RPC/HTTP front end security (%1!s!)
0x2818	78.11011	You must specify the binding option if you want to Ping the RPC proxy. (-E)
0x2819	78.11011	Invalid BindingOption (%1!s!). You must specify the RpcProxy
0x281a	78.11011	Cannot retrieve computer name %1!d! : %2!s!
0x281b	78.11011	Cannot retrieve smart card credentials %1!d! : %2!s!
0x281c	78.11011	Cannot parse interface UUID: %1!s!
0x281d	78.11011	If you specify authentication level other than 1, you must specify a security provider
0x281e	78.11011	If you specify a security package, you must specify authentication level other than none
0x281f	78.11011	Cannot parse SID: %1!s!
0x2820	78.11011	You must specify one or more proxy authentication schemes if you want to authenticate to the HTTP Proxy
0x2821	78.11011	You must use SSL if you want to verify the server certificate subject
0x2822	78.11011	You must use SSL if you want to retrieve the server certificate subject
0x2823	78.11011	You can retrieve the server subject certificate only if you do Proxy Echo only
0x2824	78.11011	If you use a smart card for proxy auth, you cannot specify explicit proxy credentials
0x2825	78.11011	If you use certificate for authentication, you must use SSL
0x2826	78.11011	If you use a certificate, you must either use SCHANNEL as the auth package or use FE security and specify exactly one auth scheme (cert)
0x2827	78.11011	HTTP Proxy authentication cannot be done with a smart card
0x2828	78.11011	You need to specify the HTTP proxy only when -E is enabled
0x2829	78.11011	Since you have specified the RPC/HTTP proxy echo only option (-E), the endpoint/interface you have specified will be ignored as no calls will reach the RPC/HTTP server
0x282a	78.11011	%1!s! [Y/N]:
0x282b	78.11011	%1!s! : %2!s!
0x282c	78.11011	Server Certificate Subject: (%1!s!;%2!s!)
0x282d	78.11011	Completed %1!d! calls in %2!d! ms %3!d! T/S or %4!3d!.%5!03d! ms/T
0x282e	78.11011	Maximum of seven -n switchs, extra ignored
0x282f	78.11011	You must specify one or more authentication schemes if you want to authenticate to the RPC/HTTP Proxy
0x2830	78.11011
0x2831	78.11011	Time %1!s!: %2!d!.%3!03d!
0x2832	78.11011	Couldn't run RPC Network Diagnostics: %1!d!
0x2833	78.11011	Error %1!d! : %2!s! returned in CertSetCertificateContextProperty
0x2834	78.11011	If you use a smart card for rpc auth, you cannot specify explicit credentials
0x2835	78.11011	If you specify the certificate authentication scheme then you must use a smart card
0x2836	78.11011	Binary val: Length %1!d! %2!X! %3!X! %4!X! %5!X!
0x2837	78.11011	RPCPing set Activity ID: {%1!s!}
0x2838	8.11011	Using basic authentication without SSL can expose your credentials. Do you want to continue? [%1!s!/%2!s!]
0x2839	8.11011	Y
0x283a	8.11011	y
0x283b	8.11011	N
0x283c	8.11011	n
0x283d	1011	Error %1!d! : %2!s! returned in ConvertStringSecurityDescriptorToSecurityDescriptor
0x283e	1011	Cannot parse EffectiveOnly: %1!s!
0x283f	1011	EffectiveOnly must be either 0 or 1.
0x2711	7	Usage: rpcping [-t ] [-s ] [-e \|-f [,MajorVer]] [-O ] [-u ] [-a ] [-N ] [-I ] [-C ] [-T ] [-M ] [-S ] [-P ] [-F ] [-H ] [-o ] [-B ] [-b] [-E] [-q] [-c] [-A ] [-U ] [-r ] [-v ] [-d]
0x2714	78.1	-S - the expected SID of the server. For more information see the Sid field in the RPC_SECURITY_QOS structure in the MSDN. Using this option requires Windows .NET Server 2003 or higher. This field can be used only when authentication level and security package are selected. -P - specifies the identity to authenticate with to the RPC/HTTP proxy. Has the same format as for the -I option. Also, you must specify security package (-u), authentication level (-a), and authentication schemes (-H) in order to use this option. -F - the flags to pass for RPC/HTTP front end authentication. The flags may be specified as numbers or names The currently recognized flags are: Use SSL - 1 or ssl or use_ssl Use first auth scheme - 2 or first or use_first See the Flags field in RPC_HTTP_TRANSPORT_CREDENTIALS for more information. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -H - the authentication schemes to use for RPC/HTTP front end authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM Certificate - 65536 or Cert Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -B - the server certificate subject. For more information, see the ServerCertificateSubject field in the RPC_HTTP_TRANSPORT_CREDENTIALS structure in the MSDN. You must use SSL for this option to work. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -b - retrieves the server certificate subject from the certificate sent by the server and prints it to a screen or a log file. Valid only when the Proxy Echo only option (-E) and the use SSL options are specified. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -R - specifies the HTTP proxy. if it's 'none', we will not use HTTP proxy but directly attempt the RPC proxy. the value 'default' means to use the IE settings in your client machine. any other value will be treated as the explicit HTTP proxy. if you don't specify this flag, the default value is assumed, that is, the IE settings are checked. this flag is valid only when the -E (Echo Only) flag is enabled.
0x2715	7	-E - restricts the ping to the RPC/HTTP proxy only. The ping does not reach the server. Useful when trying to establish whether the RPC/HTTP proxy is reachable. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. To specify an HTTP proxy, use the -R flag. If an HTTP proxy is specified in the -o flag, this option will be ignored. -q - quiet mode. Does not issue any prompts except for passwords. Assumes 'Y' response to all queries. Use this option with care. -c - use smart card certificate. RPCPing will prompt user to choose smart card. -A - specifies the identity to authenticate with to the HTTP proxy. Has the same format as for the -I option. Also, you must specify authentication schemes (-U), security package (-u) and authentication level (-a) in order to use this option. -U - the authentication schemes to use for HTTP proxy authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM You must specify security package (-u) and authentication level (-a) in order to use this option. -r - if multiple iterations are specified, this option will make rpcping display current execution statistics periodically instead after the last call. The report interval is given in seconds. Default is 15. -v - tells rpcping how verbose to make the output. Default value is 1. 2 and 3 provide more output from rpcping. -d - launch RPC network diagnostic UI Example: Find out if your Exchange server that you connect through RPC/HTTP is accessible: rpcping -t ncacn_http -s exchange_server -o RpcProxy=front_end_proxy -P "username,domain,*" -H Basic -u NTLM -a connect -F 3 When prompted for the password, enter it. exchange_server is the name of your exchange server, front_end_proxy is the name of your proxy, username and domain are your user name and domain as you would enter them in the Outlook prompt. The other parameters will ask rpcping to ping your Exchange server in exactly the same way as Outlook will connect to it for the typical profile. -p - Prompt for credentials if authentication fails.
162 entries