Windows Devices discovered by a discovery job are being assigned the device class "other", the probe is unable to connect successfully to the device's local WMI repository

Last Modified

Fri Mar 10 15:35 GMT 2023

Description

  • Windows Devices discovered by a discovery job are being assigned the device class "other"
  • The probe performing the discovery job is unable to connect successfully to the device's local WMI repository
    • NAAssetDiscovery.log:
      • ERROR Connect: unable to connect to remote network resource

Environment

  • N-able N-central

Solution

  • First to confirm if the probe is able to connect to the end device by performing the following steps:
    1. Login to the probe device
    2. Click Start > Run > WBEMTEST
    3. Click Connect
    4. Enter \\<Remote Device IP>\root\cimv2
      • For example: \\192.168.1.1\root\cimv2
    5. Enter in the correct credentials
    6. Select Connect
  • If doing the above steps then generates the following error then either there's a restriction in place that blocks DOM, RPC or WMI access, or there's a local WMI repository issue
    • 0x800706ba, the RPC server is unavailable
  • To resolve please do the following:
    1. Please ensure there's no firewall restrictions in place that would stop the probe from querying the host
    2. Re-sync/re-build the local WMI repository on the remote device
  • NOTE: By default, Windows automatically creates an ADMIN$ share, a resource that is used during remote administration of a computer
  • If this share is not accessible, the probe will be unable to correctly identify and install the agent on the remote device