Microsoft KB Archive/272218

= XCLN: RPC Ping Utility and Exchange 2000 Server =

Article ID: 272218

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q272218



SUMMARY
This document provides instructions for using the RPC Ping utility for Exchange 2000 Server. You can use the RPC Ping utility to confirm the remote procedure call (RPC) connectivity between the Exchange 2000 server and any of the supported Messaging Application Programming Interface (MAPI) clients on the network. You can also use the RPC Ping utility to verify that Exchange 2000 services are responding to RPC requests from clients across the network.



MORE INFORMATION
To use the RPC Ping utility, you must run Rpings.exe on the Exchange Server computer and Rpingc.exe on the MAPI client computer.

Server Component
Depending on the platform, run one of the following components on the Exchange Server computer:  Intel:

Winnt\I386\Rpings.exe

 Alpha:

Winnt\Alpha\Rpings.exe



Options
Rpings.exe contains two RPC functions (Echo and Stats) that are called by Rpingc.exe on the client. By default, Rpings.exe uses all available protocol sequences. To specify a particular protocol sequence, type the following command in the folder that contains Rpings.exe

RPINGS [-p ]

where  is the supported transport mechanism of RPC.

You can specify the protocol sequences in the following table.

Client Component
Rpingc.exe connects and binds to the specified destination RPC server and displays the status, available protocol sequences with end points, and quality of the RPC connection.

Depending on the platform, run one of the following components on the MAPI client computer:  Microsoft Windows NT, Microsoft Windows 2000, Microsoft Windows 95, and Microsoft Windows 98 running on Intel:

Winnt\I386\Rpingc.exe

 Windows NT and Windows 2000 running on Alpha:

Winnt\Alpha\Rpingc.exe

 Microsoft Windows 3.1x clients:

Win16\Rpingc.exe

 Microsoft DOS clients:

Dos\Rpingc.exe

</li></ul>

Options for Windows Clients
Rpingc.exe is available with a graphical user interface on Windows clients. You can customize your Rpingc.exe configuration on Windows clients by using the following options:  Exchange Server:

The name of the Exchange Server computer that you want to ping.

</li> Protocol Sequence:  Any (default)</li> Named Pipes</li> IPX/SPX</li> TCP/IP</li> NetBIOS</li> VINES</li></ul> </li> End Point:  Rping (default, all)</li> Store (the Exchange Information Store service)</li> Admin (the Exchange Administrator service)</li></ul> </li> <li>Number of pings: <ul> <li>Continuous</li> <li>Stop at x</li></ul> </li> <li>Mode: <ul> <li>Ping Only (character echoed by Rpings)</li> <li>End Point Search (enumerates all end points that are available)</li></ul> </li> <li>Run with Security:

Verifies that authenticated RPCs function correctly

</li></ul>

Options for DOS Clients
Rpingc.exe is not available with a graphical user interface on DOS clients. To customize your Rpingc.exe configuration on DOS clients, type the following command in the folder that contains Rpingc.exe

RPINGC [-p ] -n   [-e  ] [-c  ] [-s]

where  is the supported transport mechanism of RPC,   is the name of the server (this option is required),   is the end point that you want to find (the default is rping), and   is the number of pings (the default is 1).

The default protocol sequence is named pipes. You can specify the protocol sequences in the following table.

You can also specify the protocol sequences by the following friendly names:
 * Namedpipes
 * tcpip
 * ipx/spx
 * netbios
 * vines

The -s option runs an endpoint search.

Additional query words: XCCC

Keywords: kbinfo KB272218

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.