Welcome: Guest
NOTE: This site is no longer maintained. Upgrade to the latest version of ipMonitor ยป

Knowledge Center > FAQs
How can I Verify that a Remote Server is Accessible through a RPC Connection?

To properly monitor a Microsoft® Exchange or SQL Server, the Exchange Server and SQL Server Monitors require:

  • Windows Management Instrumentation (WMI) to be enabled and functioning properly.
  • The remote server to be accessible through a RPC connection in order to run the WMI queries.

This article describes a simple method that can be used to verify that a remote server is accessible through a Remote Procedure Call (RPC) connection.

For information on ensuring that WMI is enabled and functioning correctly, refer to the FAQ titled "How Can I Verify that Windows Management Instrumentation (WMI) is Functioning?"

Test the RPC Connection
  1. Log in to the ipMonitor host computer.
  2. Access the Windows Start menu, click Run, then enter the following command and click OK:

         \\Target_Hostname\C$

                      - or -

         \\Target_Primary_IP_Address\C$
Note: Replace the Target_Hostname or Target_Primary_IP_Address variable in the above example with the actual Hostname or Primary IP Address of the target remote server, as shown below.

If the C$ admin share appears within a new Windows Explorer window, or if you receive a login prompt that requires an account and password to proceed, the remote server is accessible through an RPC connection.

However, if you receive an error message, further troubleshooting may be needed to determine the root cause of the issue.

Troubleshooting the RPC Connection

A number of troubleshooting techniques can be used to determine the cause of a severed RPC connection. If you receive an error message using the above verification procedure, ensure that the following criteria are met in order to isolate the likely cause of the problem:

  • The Remote Procedure Call (RPC) Service is installed and functional. To verify this, open the Control Panel (from the Start Menu), double-click Administrative Tools, and then double-click Services.
  • No device or application is blocking RPC traffic between the two servers. For example, a firewall or a router.

Additional suggestions for troubleshooting Remote Procedure Call performance issues can be found in Article 17746 located in the Microsoft Knowledge Base.

Additional Information

For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:

< Back

Last Updated: September 8, 2006 | What did you think of this topic?

Privacy Statement | Terms of Use | EULA | Contact | Site Map

Prices displayed do not reflect international pricing unless otherwise stated. Please see our international price list for current pricing specific to your location. All prices are subject to change without notice.

© 2003-2008 SolarWinds.net, Inc. All Rights Reserved. SolarWinds®, the SolarWinds logo, ipMonitor®, LANsurveyor®, and Orion® are among the trademarks or registered trademarks of the company in the United States and/or other countries. All other trademarks are property of their respective owners.