XCLN: RPC Ping Utility and Exchange 2000 Server (272218)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

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 protocol_sequence]

where protocol_sequence is the supported transport mechanism of RPC.

You can specify the protocol sequences in the following table.

Protocol SequenceTransport Mechanism
ncacn_npNamed Pipes
ncacn_ip_tcpTransmission Control Protocol/Internet Protocol (TCP/IP)
ncacn_nb_nbNetwork basic input/output system (NetBIOS) over NetBIOS Enhanced User Interface (NetBEUI)
ncacn_spxSequenced Packet Exchange (SPX)
ncacn_vns_sppBanyan VINES
ncadg_ip_udpUser Datagram Protocol (UDP) datagram TCP/IP
ncadg_ipxInternetwork Packet Exchange (IPX) datagram IPX
ncalrpc Local procedure call

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

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.

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

    Verifies that authenticated RPCs function correctly

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 protocol_sequence] -n network_address [-e end_point] [-c xxx] [-s]

where protocol_sequence is the supported transport mechanism of RPC, network_address is the name of the server (this option is required), end_point is the end point that you want to find (the default is rping), and xxx 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.

Protocol SequenceTransport Mechanism
ncacn_npNamed Pipes
ncacn_ip_tcpTCP/IP
ncacn_nb_nb NetBIOS over NetBEUI
ncacn_spxSPX
ncacn_vns_spp Banyan VINES
ncadg_ip_udpUDP datagram TCP/IP
ncadg_ipxIPX datagram IPX

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.

Modification Type:MinorLast Reviewed:4/28/2005
Keywords:kbinfo KB272218