Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > Unable to poll server through WMI due to DNS records

Unable to poll server through WMI due to DNS records

Created by Matthew Lamb, last modified by MindTouch on Jun 23, 2016

Views: 954 Votes: 0 Revisions: 3

Overview

This article goes over the information pertaining to polling servers via WMI and nothing being returned due to missing or incorrect DNS records for that server or the incorrect information is being provided.

 

When attempting to poll the device, you would see the following error in the DataProcessor.logs:

 

2016-04-06 14:44:17,856 [50] ERROR SolarWinds.Net.WMI.WmiConnectionBuilder - WMI - Management scope’s IP address of target computer (x.x.x.x) and reverse looked up IP address (y.y.y.y) don't match. WMI library is trying to connect to y.y.y.y instead of x.x.x.x. Check reverse DNS record for x.x.x.x to fix it.
2016-04-06 14:44:17,856 [50] ERROR SolarWinds.Orion.Pollers.Framework.WMI.WmiHelper - ValidateWmiNode encountered a WmiException while validating Wmi node
SolarWinds.Net.WMI.WmiHostNotRespondingException: The RPC server is unavailable Scope: x.x.x.x\root\CIMV2[\context\administrator] ErrorCode: 0x800706BA ---> System.Runtime.InteropServices.COMException: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Environment

NPM 10 and later

Cause 

The reason the poll and test fail is because the connection through WMI is also verifying the connection information through reverse lookup on the hostname\IP to insure it is correct. If there is no reverse or PTR records or the records exist but they are incorrect, then the WMI connection will resolve to the incorrect IP or will not resolve to an IP connection at all.

Resolution

This is an environment issue and must be confirmed in your network. SolarWinds recommends verifying that the records for that hostname and IP are correct and working properly. Once they are added or corrected, then the WMI connection will be able to resolve through WMI correctly.

 

Last modified
23:52, 22 Jun 2016

Tags

Classifications

Public