Hacked By AnonymousFox

Current Path : C:/Windows/SysWOW64/en-US/
Upload File :
Current File : C:/Windows/SysWOW64/en-US/rpcping.exe.mui

MZ@	!L!This program cannot be run in DOS mode.

$<ߵRRRЫRЫPRRichRPEL!


@ ܞ8.rdata@@.rsrc @@
T88$8.rdata8x.rdata$zzzdbg .rsrc$01 .rsrc$02 
琖o|ر@G۽|(i(@Xp			 !TMUIIg֭&L,'OAMUIen-US''@%'&'0T('7'Tt''8['?(kUsage: 

rpcping [-t <protseq>] [-s <server_addr>] [-e <endpoint>            

        |-f <interface UUID>[,MajorVer]] [-O <Interface Object UUID]

        [-i <#_iterations>] [-u <security_package_id>] [-a <authn_level>]                             

        [-N <server_princ_name>] [-I <auth_identity>] [-C <capabilities>]

        [-T <identity_tracking>] [-M <impersonation_type>]

        [-S <server_sid>] [-P <proxy_auth_identity>] [-F <RPCHTTP_flags>]

        [-H <RPC/HTTP_authn_schemes>] [-o <binding_options>]

        [-B <server_certificate_subject>] [-b] [-E] [-q] [-c]

        [-A <http_proxy_auth_identity>] [-U <HTTP_proxy_authn_schemes>]

        [-r <report_results_interval>] [-v <verbose_level>] 



Pings a server using RPC. Options are:



-t <protseq> - 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 <server_addr> - the server address. If not specified, the local

    machine will be pinged. E.g. server, server.com, 157.59.244.141

        

-e <endpoint> - 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 <binding_options> - the binding options for the RPC ping. See the

    MSDN for more details (RpcStringBindingCompose and RPC over HTTP).

    

-f <interface UUID>[,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 <Object UUID> - Object Uuid if the interface registerd one.



-i <#_iterations> - number of calls to make. The default is 1. This

    option is useful for measuring connection latency if multiple

    iterations are specified.

    

-u <security_package_id> - the security package (security provider) RPC

    will use to make the call. The security package is identified as a

    number or a name. If a number is used it is the same number as in the

    RpcBindingSetAuthInfoEx API. The table below gives the names and

    numbers. Names are not case sensitive:

        Negotiate - 9 or one of nego, snego or negotiate

        NTLM - 10 or NTLM

        SChannel - 14 or SChannel

        Kerberos - 16 or Kerberos

        Kernel - 20 or Kernel

    If you specify this option you must specify authentication level other

    than none. There is no default for this option. If it is not specified,

    RPC will not use security for the ping.

    

-a <authn_level> - the authentication level to use. Possible values are

    connect, call, pkt, integrity and privacy. If this option is

    specified, the security package id (-u) must also be specified. There

    is no default for this option. If this option is not specified, RPC

    will not use security for the ping.



-N <server_princ_name> - 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 <auth_identity> - 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 <capabilities> - 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 <identity_tracking> - 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 <impersonation_type> - can be anonymous, identify, impersonate or

    delegate. Default is impersonate. This field can be used only when

    authentication level and security package are selected.  



-S <server_sid> - 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 <effectiveonly> - 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 <serversecuritydescriptor> - 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 <proxy_auth_identity> - 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 <RPCHTTP_flags> - 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 <RPC/HTTP_authn_schemes> - 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 <server_certificate_subject> - 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.



-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 <http_proxy_auth_identity> - 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 <HTTP_proxy_authn_schemes> - 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 <report_results_interval> - 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 <verbose_level> - 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.

$Out of memory

@Cannot allocate %1!d! bytes

4Invalid switch: %1!s!

lInvalid option %1!c!, missing required parameter

RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006

%1!s!

%1!s!

If you specify auth identity, you must specify authentication level and security package

If you specify identity tracking, you must specify authentication level and security package

If you specify impersonation type, you must specify authentication level and security package

If you specify a SID, you must specify authentication level and security package

To prompt for credentials, you must specify authentication level and security package

LCannot parse security package id

LCannot parse authentication level

<Cannot parse flags string

HCannot parse auth schemes array

PCannot parse identity tracking mode

HCannot parse impersonation type

 Error %1!d! : %2!s! returned in the WinHttpQueryAuthSchemes. possibably anonymous requests or requests on unsecure channel are not allowed

lError %1!d! : %2!s! returned in WinHttpSetOption

tError %1!d! : %2!s! returned in WinhttpSetOption (3)

lError %1!d! : %2!s! returned in WinHttpSetOption

|Status %1!d! returned in the RpcCertGeneratePrincipalName

|Error %1!d! : %2!s! returned in CredIsMarshaledCredential

xError %1!d! : %2!s! returned in CredUnMarshalCredential

pError %1!d! : %2!s! returned in CertOpenSystemStore

Error %1!d! : %2!s! returned in CertFindCertificateInStore

pError %1!d! : %2!s! returned in CryptAcquireContext

pError %1!d! : %2!s! returned in CryptSetProvParam 

tError %1!d! : %2!s! returned in WinHttpSetOption (1)

xError %1!d! : %2!s! returned in WinHttpSetOption (cert)

pError %1!d! : %2!s! returned in MultiByteToWideChar

lError %1!d! : %2!s! returned in RtlStringCbPrintf

tError %1!d! : %2!s! returned in WinHttpSetCredentials

pError %1!d! : %2!s! returned in WinHttpSendRequest

xError %1!d! : %2!s! returned in WinHttpReceivedResponse

|Error %1!d! : %2!s! returned in WinHttpQueryHeadersFailed

Error %1!d! : %2!s! returned in WinHttpSetCredentials for RPC Proxy

tError %1!d! : %2!s! returned in WinHttpSetOption - 4

Error %1!d! : %2!s! returned in WinHttpSetCredentials for Http Proxy

xError %1!d! : %2!s! returned in WinHttpQueryHeaders - 2

lError %1!d! : %2!s! returned in RtlStringCchCopy

`Error %1!d! : %2!s! returned in WinHttpOpen

hError %1!d! : %2!s! returned in WinHttpConnect

pError %1!d! : %2!s! returned in WinHttpOpenRequest

hError %1!d! : %2!s! returned in GetModuleHandle

lError %1!d! : %2!s! returned in GetProcessAddress

H%1!s! failed - %2!d! (%3!08x!)

Error %1!d! : %2!s! returned in CertGetCertificateContextProperty

Error %1!d! : %2!s! returned in WinHttpSendRequest - probably server is not configured to accept smart cards

@Error retrieving user input

XUse Server Preffered Auth Scheme: %1!d!

XUse Proxy Preffered Auth Scheme: %1!d!

`Client failed to authenticate to RPC proxy

To use BASIC authentication scheme for RPC Proxy, you must specify the user/domain/password (-P)

To use BASIC authentication scheme for HTTP Proxy, you must specify the user/domain/password (-A)

HSetting autologon policy to low

To use implicit logon credentials with NTLM, you must use SSL with server certificate subject or disable lanman hash

LSetting autologon policy to high

Authentication scheme %1!d! is not supported. Currently only NTLM and BASIC are supported

tCannot convert server certificate subject to Unicode

The server certificate subject from the RPC proxy (%1!s!, %2!s!) does not match the one (%3!s!) specified

CredIsMarshaledCredential failed with NULL certCredentialInfo

CredIsMarshaledCredential failed with wrong CredType: %1!d!

lCryptAcquireContextW failed with NULL cspProvider

`Smart card auth has no implicit credentials

You must specify at least one authentication scheme if you specify the RPC_C_HTTP_FLAG_USE_FIRST_AUTH_SCHEME

hWinHttpSetCredentials for target server called

8Sending ping to server

Server requires a certificate and client did not specify one. Exiting ...

dClient certificate is required by the server

Smart card specified but not accepted by server (ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED returned). Exiting ...

TNo smart card specified. Exiting ...

TResponse from server received: %1!d!

Smart card used and error 401 returned from server - probably server is not configured to accept smart cards

`Client is not authorized to ping RPC proxy

LAccess denied pinging HTTP proxy

pFirst WinHttpQueryHeaders should not have succeeded

@You mush specify Rpc Proxy

TError when checking IE settings %1!d!

XError %1!d! : %2!s! port # is too long

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

Either an interface or an endpoint can be given, but not both

lCannot find protocol sequence: %1!s!. Exiting...

hSChannel requires a certificate to be supplied

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

8Wrong access type %1!u!

xRPCPinging proxy server %1!s! with Echo Request Packet

`Pinging successfully completed in %1!d! ms

 Ping failed

DException %1!lu! (0x%2!08lX!)

@Couldn't get EEInfo: %1!d!

@Number of records is: %1!d!

PCouldn't finish enumeration: %1!d!

4ComputerName is %1!s!

0ProcessID is %1!d!

|System Time is: %1!d!/%2!d!/%3!d! %4!d!:%5!d!:%6!d!:%7!d!

DGenerating component is %1!d!

<Status is 0x%1!X!, %2!d!

@Detection location is %1!d!

(Flags is %1!d!

@NumberOfParameters is %1!d!

0Ansi string: %1!S!

4Unicode string: %1!s!

,Long val: 0x%1!x!

,Short val: %1!d!

4Pointer val: 0x%1!x!

Truncated

0Invalid type: %1!d!

If you specify auth identity in the form <user,domain,password>, a domain must be specified: %1!s!

If you specify auth identity in the form <user,domain,password>, a password must be specified: %1!s!,%2!s!

@Enter password for %1!s!: 

DCannot parse bitflags: %1!s!

(You must specify authentication level, security package and ncacn_http protocol sequence if you want to use RPC/HTTP front end security (%1!s!)

You must specify the binding option if you want to Ping the RPC proxy. (-E)

Invalid BindingOption (%1!s!). You must specify the RpcProxy

`Cannot retrieve computer name %1!d! : %2!s!

tCannot retrieve smart card credentials %1!d! : %2!s!

PCannot parse interface UUID: %1!s!

If you specify authentication level other than 1, you must specify a security provider

If you specify a security package, you must specify authentication level other than none

8Cannot parse SID: %1!s!

You must specify one or more proxy authentication schemes if you want to authenticate to the HTTP Proxy

You must use SSL if you want to verify the server certificate subject

You must use SSL if you want to retrieve the server certificate subject

You can retrieve the server subject certificate only if you do Proxy Echo only

If you use a smart card for proxy auth, you cannot specify explicit proxy credentials

If you use certificate for authentication, you must use SSL

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)

HTTP Proxy authentication cannot be done with a smart card

You need to specify the HTTP proxy only when -E is enabled

XSince 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

$%1!s! [Y/N]:

$%1!s! : %2!s!

\Server Certificate Subject: (%1!s!;%2!s!)

Completed %1!d! calls in %2!d! ms

%3!d! T/S or %4!3d!.%5!03d! ms/T



`Maximum of seven -n switchs, extra ignored

You must specify one or more authentication schemes if you want to authenticate to the RPC/HTTP Proxy



@Time %1!s!:   %2!d!.%3!03d!

`Couldn't run RPC Network Diagnostics: %1!d!

Error %1!d! : %2!s! returned in CertSetCertificateContextProperty 

If you use a smart card for rpc auth, you cannot specify explicit credentials

If you specify the certificate authentication scheme then you must use a smart card

lBinary val: Length %1!d! %2!X! %3!X! %4!X! %5!X! 

LRPCPing set Activity ID:  {%1!s!}

Using basic authentication without SSL can expose your credentials. Do you want to continue? [%1!s!/%2!s!] %0

Y%0

y%0

N%0

n%0

Error %1!d! : %2!s! returned in ConvertStringSecurityDescriptorToSecurityDescriptor

LCannot parse EffectiveOnly: %1!s!

TEffectiveOnly must be either 0 or 1.

4VS_VERSION_INFO
cE
cE?StringFileInfo040904B0LCompanyNameMicrosoft CorporationJFileDescriptionRPC Ping Utilityh$FileVersion10.0.17763.1 (WinBuild.160101.0800)8InternalNameRpcPing.exe.LegalCopyright Microsoft Corporation. All rights reserved.HOriginalFilenameRpcPing.exe.muij%ProductNameMicrosoft Windows Operating System>
ProductVersion10.0.17763.1DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD

Hacked By AnonymousFox1.0, Coded By AnonymousFox