XCLN: How to Use RPCPing to Test RPC Communication
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
The RPC Ping Utility can be used to confirm the RPC connectivity betweenthe computer running Microsoft Exchange Server and any of the supportedMicrosoft Exchange Client workstations on the network. This utility can beused to check if the Microsoft Exchange Server services are responding toRPC requests from the client workstations via the network.
There are two components in the RPC Ping Utility: a server-side componentand a client-side component.
The executable file of each component is listed below:
Server Component: Rpings.exe (for the Microsoft Exchange Windows NT Server) Client Component: Rpingc32.exe (for Microsoft Windows NT and Windows95) Rpingc16.exe (for Microsoft Windows 3.1x clients) Rpingdos.exe (for Microsoft DOS clients)
Rpings.exe is the server-side RPC ping utility.
Rpings contains two RPC functions Echo and Stats called by the client-sideRPC ping utilities Rpingc16, Rpingc32 or Rpingdos.
Run Rpings without any options to use all available protocol sequences.
Command Line Syntax:
RPINGS [-p Protocol Sequence] Protocol sequences can be set using these friendly names -p namedpipes -p tcpip -p ipx/spx -p netbios -p vines enter '@q' to exit rpings.
Protocol Sequence - Is the supported transport mechanisms of RPC such as:
namedpipes NCA connection over Named Pipes (ncacn_np)
tcpip NCA connection over TCP/IP (ncacn_ip_tcp) netbios NCA connection over Netbios on Netbeui (ncacn_nb_nb) ipx/spx NCA connection over SPX (ncacn_spx) vines NCA connection over Banyan Vines (ncacn_vns_spp)
Rpingc32.exe, Rpingc16.exe, and Rpingdos.exe
Rpingc32 is the 32-bit version of the client-side of the RPC Ping Utility.Rpingc16 and Rpingdos.exe are the 16-bit versions of the clientside. They will connect and bind to the specified destination RPC serverand display the status, available protocol sequences with end points andquality of the RPC connection.
Both the Rpingc32.exe and Rpingc16.exe utilities are set up to run in theWindows environment. Rpingdos.exe utility runs in the MS-DOS environment.
Rpingc32.exe and Rpingc16.exe
Exchange Server: The name of the Exchange Server to ping Protocol Sequence: The following options are available: Any (default) Named Pipes IPX/SPX TCP/IP Netbios Vines End Point: The following End Points on the Exchange Server are available: Rping (default, all) Store (the Exchange Store) Admin (the Exchange Admin) Number of Pings: Continuous Stop at ___ Mode: Ping Only (character echoed by RPINGS) End Point Search (enumerates all endpoints available) Run with Security: verifies that authenticated RPCs work
RPINGDOS [-p Protocol Sequence] -n Network Address [-e End Point] [-c xxx] [-s] -p [protocol_sequence] defaults to named pipes -n [network_address] is required -e [endpoint] endpoint to find, defaults to rping -c [xxx] number of pings, defaults to 1. -s run an endpoint search Protocol sequences can be set using these friendly names -p namedpipes -p tcpip -p ipx/spx -p netbios -p vines
The RPCPING utility and files can be found on the Exchange Server CD in theSupport\Rpcping directory.
Article ID: 167260 - Last Review: 06/22/2014 18:18:00 - Revision: 4.0