Export (0) Print
Expand All
Expand Minimize

Ping test not performed

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2006-08-09

The Microsoft® Exchange Server Analyzer Tool tries to query the Win32_PingStatus Microsoft Windows® Management Instrumentation (WMI) class to analyze the response object for various mail-flow-specific configuration settings.

Win32_PingStatus typically returns an object that has 24 properties that supply extensive details about the ping packets that the class sends.

If the Exchange Server Analyzer does not receive the expected object in response to its query after six consecutive attempts, the Exchange Server Analyzer displays a warning.

This warning indicates that the Win32_PingStatus could not be performed.

The most likely cause of this failure is that the computer that tries to execute the Win32_PingStatus command is running on the Microsoft Windows® 2000 Server operating system. Windows 2000 Server does not support the Win32_PingStatus WMI class.

If the computer that tries to execute the Win32_PingStatus command is not running on the Windows 2000 Server operating system, the issue could be the result of general networking issues or a permissions problem.

To correct this error
  1. Make sure that the Exchange Server computer has been started and is connected to the network.

  2. Use the PING command from the computer that is running the Exchange Server Analyzer to see whether the target Exchange Server computer is reachable.

  3. Use the PING command from a server that is on the same subnet with the target Exchange server to see whether the target Exchange Server computer is reachable.

  4. If there is a firewall, check to see whether remote procedure call (RPC) ports are blocked.

  5. Examine the permissions for the account under which the Exchange Server Analyzer is running. The account under which the Exchange Server Analyzer is running must have local Administrator permissions on each Exchange server that it scans.

For more information about network connectivity problems, see the Microsoft Knowledge Base article 325487, "How to troubleshoot network connectivity problems" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325487).

For more information about Exchange Server Best Practices Analyzer connectivity problems, see "Microsoft Exchange Server Best Practices Analyzer Tool Troubleshooting Connectivity Problems" (http://go.microsoft.com/fwlink/?LinkId=56285).

For more information about the Win32_PingStatus WMI class, see the MSDN® article, "Win32_PingStatus" (http://go.microsoft.com/fwlink/?linkid=33549).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft