SUMMARY RPC PING utilities can be used to confirm that the network is running Microsoft Exchange Server and the RPC connection between any supported Microsoft Exchange Client workstations. This utility can be used to check if the Microsoft Exchange Server service is in response to the RPC request of the customer workstation over the network.
More information The RPC ping utility has two components: server-side components and client components.
The executable of each component is listed below:
Server components: rpings.exe (for Microsoft Exchange Windows NT
Server)
Customer component: rpingc32.exe (for Microsoft Windows NT and Windows 95)
RPINGC16.EXE (for Microsoft Windows 3.1x client)
RPINGDOS.EXE (for Microsoft DOS Customer)
RPings.exe
RPings.exe is the server-side RPC PING utility.
RPings contains two RPC functions Echo and Stats, which are called by client RPC PING utilities RPINGC16, RPINGC32 or RPINGDOS.
To use all available protocol sequences, do not run RPings any option.
RPings.exe
Command line syntax:
Rpings [-P protocol sequence]
Protocol Sequences Can Be Set Using There Friendly Names
-p namedpipes
-p TCPIP
-p ipx / spx
-P NetBIOS
-p Vines
ENTER '@Q' to exit rpings.
among them,
Protocol sequence - is a supported RPC transport mechanism, such as: NETBIOS NCA connection through TCP / IP (ncacn_nb_nb) through NetBEUI (ncacn_nb_nb) by NetBEUI (ncacn_nb_nb) TCPIOS NETBIOS NCA connection via NetBEUI (ncacn_nb_nb) by NetBEUI (ncacn_nb_nb) IPX / SPX NCA connection via Banyan Vines (NCACN_VNS_SPP) VINES NCA connection
RPINGC32.EXE, RPINGC16.EXE and RPINGDOS.EXE
RPINGC32 is a 32-bit client RPC ping utility. RPINGC16 and RPINGDOS.exe are 16-bit versions of client tools. They are connected and bind to the specified target RPC server and display status, which can be used with protocol sequences of endpoints and RPC connection quality.
RPINGC32.EXE and RPINGC16.EXE utilities are set to run in a Windows environment. RPINGDOS.EXE utilities are running in the MS-DOS environment.
RPINGC32.EXE and RPINGC16.EXE
Option:
Exchange Server: Name of Exchange Server to Ping
Protocol sequence: The following options can be used:
ANY (Default)
Named pipes
IPX / SPX
TCP / IP
NetBIOS
Vines
Endpoint: The following endpoints on Exchange Server
Available:
RPING (Default, All)
Store (The Exchange Store)
Admin (The Exchange Admin "
PING Number: ContinuousStop AT ___
Mode: Ping Only (RPings responded characters)
End Point Search (enumerate all available endpoints)
Safe operation: Verify authorized RPC operation
RPINGDOS.EXE
grammar:
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
The protocol sequence can be set using the following friendly name
-p namedpipes
-p TCPIP
-p ipx / spx
-P NetBIOS
-p Vines
RPCPING utilities and files in the support / rpcping directory of the Exchange Server CD.
Test communication process
Determine the identity of two Exchange Server computers that you will take trouble. The Exchange Server computer that initiates communication is called the "Call" server, and the Exchange Server computer that receives the call is called the "response" server.
Important: At the same time, log in to the computer running Windows NT Server on the Call and Answer Server. If you are unable to determine what the Exchange service account is, find the Site Configuration object in the Service Account Password tab in Properties. At the same time, RPings.exe and RPINGC32.exe are run on the call and the answer server. This process will test RPC communication in both directions; thus need to run rPings.exe and rPINGC32.exe simultaneously on both computers. In the call server, configure RPINGC32.EXE to connect (ping) answering servers:
Enter the name of the answering server in the Exchange Server field. Select TCPIP as "Protocol Order". If you do not use TCP / IP as a network protocol between servers, select the appropriate protocol. Select RPING as the end point. Enter the number of pinges 3. (This is a number of casually, there is no special meaning.) Set Mode as ping only. Important: Enabling Run with security Click Start Running If the test is successful, you should receive information similar to the following: Successful RPC Binding Using these Parameters:
Network address = server
Endpoint = 2256
UUID =
Protocol sequence = ncacn_ip_tcp
Ping # 1 succeeded
Ping # 2 succeeded
Ping # 3 succeeded
Server Statistics:
#Calls received AT Server = 4
#Calls initiated by server = 0
#Calls received AT Server = 4
#Packets initiated by server = 4 Important: From another direction, ie, from the answering server to the call server, repeat the above process. Explain the results
If the RPC ping connection (PING) remote server is two-way successful, you can assume that the network and RPC configuration is correct. If all tests are done when logged in with an Exchange service account, then the configuration of Windows NT permissions is also correct. In this case, the most likely problematic is the configuration error in Exchange Server. Check the MTA name, password, rewrite account information, and more. If this is all correct, please check the consistency and integrity of the directory between the two servers.
If RPC Ping is unable to connect (ping) remote server, it can be determined that there is a network problem. Use ping to connect to the remote server with a name. If you cannot connect by name, press the IP address. If the connection is successfully connected according to the IP address, the problem is very likely that the host name resolution problem. If you are successful in the name connection, you can search in Windows NT Knowledge Base in Windows NT Knowledge Base in the error message received in the RPC PING. Make sure the RPC positioning program and RPC services are started normally. You can reach the "Services" in the Control Panel and the "Event Viewer". For further troublesome answers to RPC configuration issues, please consult Windows NT technical support to get help.
RPC communication in Exchange Server
When Exchange Server MTA needs to open the RPC link with the remote Exchange Server MTA, you need to do the following:
Establish a reliable connection with the remote server. Use TCP / IP as a network protocol, which will involve host resolution, TCP handshake, and any firewall or router existing between the two servers. Establish a link between the process between the process (IPC) of the remote server. This involves the exchange of Windows NT credentials (Windows NT domain, Windows NT username, and password) and verify login. Establish an RPC connection between Exchange Server MTA. This is a binding and back binding process, where call MTA first confirms that it is communicating with the target MTA (check the remote MTA name and password), then answer the MTA confirmation call MTA is a call party (the name of the call MTA is returned and the password is returned and Check it). As you know, you cannot establish a connection, which may be due to host name resolution issues, firewall issues, Windows NT security issues, or Exchange Server configuration issues.
source:
http://support.microsoft.com/default.aspx?scid=kb;zh-cn;175496
