I've added several computers in my LAN domain to the Windows>Clients device group (all with the same settings), however only 2 (out of the 10 or so) have found all their sensors, the others only show the Ping and RDP sensors. I've tried running Auto-Discovery and Sensor Recommendation on all of them (and made sure they were all turned on) but no change... Any idea what could be blocking PRTG from detecting sensors on the others?

Article Comments

Dear LanguidLegend,

Thank you very much for your KB-posting.

  • Please check the Windows and SNMP credentials in the device settings in PRTG an ensure that you are using a user with sufficient access rights
  • Please check if WMI and SNMP is running on the target-hosts

In case that the issue persists afterwards, kindly open a new support ticket (using the Ticket No PAE851499) and send us a support bundle including the log files.

Best regards,
Sven


Apr, 2017 - Permalink

How do I check whether WMI and SNMP is running on the target-hosts?


Apr, 2017 - Permalink

Dear LanguidLegend,

  • For WMI:
    • Please use our WMI Tester (https://www.paessler.com/tools/wmitester), run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, usually the "OS-Query" from the "Advanced" Tab of the Tool works best, please send us the Results.

Best regards,
Sven


Apr, 2017 - Permalink

For computer 192.168.1.11 (on which I received all sensors): 

BootDevice;BuildNumber;BuildType;Caption;CodeSet;CountryCode;CreationClassName;CSCreationClassName;CSDVersion;CSName;CurrentTimeZone;DataExecutionPrevention_32BitApplications;DataExecutionPrevention_Available;DataExecutionPrevention_Drivers;DataExecutionPrevention_SupportPolicy;Debug;Description;Distributed;EncryptionLevel;ForegroundApplicationBoost;FreePhysicalMemory;FreeSpaceInPagingFiles;FreeVirtualMemory;InstallDate;LargeSystemCache;LastBootUpTime;LocalDateTime;Locale;Manufacturer;MaxNumberOfProcesses;MaxProcessMemorySize;MUILanguages;Name;NumberOfLicensedUsers;NumberOfProcesses;NumberOfUsers;OperatingSystemSKU;Organization;OSArchitecture;OSLanguage;OSProductSuite;OSType;OtherTypeDescription;PAEEnabled;PlusProductID;PlusVersionNumber;Primary;ProductType;RegisteredUser;SerialNumber;ServicePackMajorVersion;ServicePackMinorVersion;SizeStoredInPagingFiles;Status;SuiteMask;SystemDevice;SystemDirectory;SystemDrive;TotalSwapSpaceSize;TotalVirtualMemorySize;TotalVisibleMemorySize;Version;WindowsDirectory
\Device\HarddiskVolume2;7601;Multiprocessor Free;Microsoft Windows 7 Professional ;1252;1;Win32_OperatingSystem;Win32_ComputerSystem;Service Pack 1;SHFB-RAQUEL;-420;True;True;True;2;False;"";False;256;2;1102376;2931932;4187716;20110523122605.000000-420;"";20170410073409.375199-420;20170410074913.842000-420;0409;Microsoft Corporation;-1;2097024;{en-US};Microsoft Windows 7 Professional |C:\Windows|\Device\Harddisk0\Partition3;0;80;2;48;Microsoft;32-bit;1033;256;18;"";True;"";"";True;1;shfb1;00371-OEM-8992671-00524;1;0;3143320;OK;272;\Device\HarddiskVolume3;C:\Windows\system32;C:;"";6284924;3143320;6.1.7601;C:\Windows

For computer 192.168.1.24 (which is also online):

Error: 800706BA: The RPC server is unavailable

Apr, 2017 - Permalink

Please make sure that the requirements for WMI are all met on 192.168.1.24. This could either be a firewall/av issue or permissions not configured correctly.


Apr, 2017 - Permalink