This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

WMI Ping check from DMZ to external IP's

FormerMember
FormerMember

We are trying to obtain availability from numerous IP addresses beyond from our DMZ using WMI (target server in DMZ) to test using a script from thwack (WMI Win32_PingStatus class).




This is helping us keep the SW server secure and without the need for a poller. The DCOM and WMI element between our SW server and the target are fine as we can use various APM tests confirming this functionality works OK. 

Testing availability to local servers or devices within our DMZ result in a positive response from the script.

The problem is when we extend the IP to devices beyond our externally facing firewall script fails with the following message. 

Failed with "undefined" status, script output did not contain required field "statistic". Actual script output begins "host x.x.x.x could not be contacted ".

I must add at this point these devices are pingable from the target machine command line.

We can however target other devices within our DMZ with this APM template and these all return positive. Debug logging on the server doesn't give us any other clues than the message above.

We have also extracted the VBscript and run this locally on the WMI target machine, the external sites work? This is obviously causing confusion.

Any help appreciated.

  • I'm guessing that it's a problem with credentials that have been assigned to this application component.

    By design, VB scripts are executed locally (on the poller) against remote devices. It uses the assigned credentials to execute it locally and then authenticate to the remote device. Therefore, you need to make sure that the credentials you have assigned to this component are valid on both the poller and the remote device.

    Does this sound like the source of your problem?

  • FormerMember
    0 FormerMember in reply to qle

    Hi qle

    Originally we were looking to use a local user account on the target, this didn't help with the test...

    "Unable to impersonate user localmachine\localaccount". This user must be a valid user on the Orion Server/Polling engine.

    So we reverted to AD and using a domain admin account we still get a negative response

    "Host x.x.x.x could not be contacted"

     After assigning a local account to match the remote local account on Solarwinds we now get the same respnse as the AD credential

     "Host x.x.x.x could not be contacted"message....

    At both locations (Solarwinds and target server the user used is set to local administrator)

    Progression to a degree for local accounts however no cigar just yet

    Thanks in advance for further assistance

  • FormerMember
    0 FormerMember in reply to FormerMember

    When debugging (advanced options within APM) the log file outputs the following.

    ERROR Solarwinds.APM.Probes.WindowsScriptsProbe - Solarwinds.APM.Probes.Script.ScriptNoStatisticException: Script output did not contain required field "Statistic". Actual script output begins "Host x.x.x.x could not be contacted"

    at Solarwinds.APM.Probes.Script.ScriptResult.DoFind(String label) 

    at Solarwinds.APM.Probes.Script.ScriptResult.FindStatistic()

    at Solarwinds.APM.Probes.Script.ScriptResult.get_Statistic()

    at Solarwinds.APM.Probes.Script.WindowsScriptProbe.Probe(ProbeInformation configuration, ProbeResult result)

     

    Its worth pointing out that we are not interested in response times only Availability (at the mo). Although getting this script to work would be ideal going forward as we have numerous customers on the horizon with this type of requirement.

     TIA

  • Can you confirm that if you log into the poller with this account and execute this VB script against the remote device, it is successful?