HELP PLEASE {NO SUCH HOST IS KNOWN} ERROR

  -  

a Windows Update Status Sensor reports "Last Message" as "No such host is known".Is the Message "No such host is known" delivered by the target device where i want khổng lồ know the update Status from?Or does this mean, that the prtg cannot find the host?

Other Sensors on this device work fine.

Bạn đang xem: Help please {no such host is known} error

The file "Result of Sensor .txt" Looks like:

1 No such host is knownin the file "Result of Sensor .Data.txt", the following part looks OK

Data<"environment">.asString := "";Data<"exefile">.asString := "LastWindowsUpdateSensor.exe";Data<"exeparams">.asString := " -host="10.xx.xx.xx" -timeout=43198 -port=5985 -user="xxxxxx.xxxxxserviceprtg" -pass="***" "-debugfile=C:ProgramDatahostingvietnam.vnPRTG Network MonitorLogs (Sensors)Result of Sensor .log"";Data<"fastcount">.asString := "0";Data<"host">.asString := "10.xx.xx.xx";best regards

D.

Xem thêm: Chi Tiết Cách Làm Email Marketing Miễn Phí Tốt Nhất Năm 2021

last-sensor-stateprtgwindows-update-status
Created on Apr 19, 2017 9:29:38 AM by

*
DieterD(0)●1

Last change on Jun 27, 2018 5:17:23 AM by

*
Luciano Lingnau

Permalink


Best Answer


Accepted Answer

Votes:

5

Your Vote:

UpDown
Hi All,

I had this same issue. Multiple devices in the same IP subnet as my local probe all working fine (non-PowerShell sensors và PowerShell sensors). But two devices in a different IP subnet with all "normal" sensors were working just fine, but the PowerShell sensor for Windows Updates failing. It was reporting "No such host is known".

Xem thêm: Sữa Lỗi Không Mở Được Folder Khi Kich Đúp Chuột, Lỗi Không Mở Được My Computer Và Các Thư Mục

After some digging around I could validated the following:

TCP 5985 wasn"t blocked (used telnet from the monitoring probe host)Remote PowerShell was working (from the probe server:

Invoke-Command -ComputerName -ScriptBlock hostname I then tried the above Invoke-Command again, but with just the IP address as I noticed in the logs above và in my logs the IP address was used by the sensor. This failed with the below error message:

Connecting to lớn remote vps aaa.bbb.yyy.zzz failed with the following error message : The WinRM clientcannot process the request. Default authentication may be used with an IP address under the following conditions: thetransport is HTTPS or the destination is in the TrustedHosts list, & explicit credentials are provided. Usewinrm.cmd to configure TrustedHosts. Chú ý that computers in the TrustedHosts danh mục might not be authenticated. For moreinformation on how to set TrustedHosts run the following command: winrm help config. For more information, see theabout_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (aaa.bbb.yyy.zzz:String) <>, PSRemotingTransportException + FullyQualifiedErrorId : CannotUseIPAddress,PSSessionStateBrokenThis led me down lớn figuring out why the Invoke-Command failed with an IP address, but not with a host name. In my case I did not try lớn fix the issue with altering the trusted host list or behavior, because the sensors on same subnet worked just fine by IP address. So I kept digging. I was able to lớn dig out the actual PowerShell command in the "Windows Update Status" sensor and tried that with both IP address và hostname:

> & "C:Program Files (x86)PRTG Network MonitorSensor SystemLastWindowsUpdateSensor.exe" -host="" -user="" -pass=""> & "C:Program Files (x86)PRTG Network MonitorSensor SystemLastWindowsUpdateSensor.exe" -host="" -user="" -pass=""The IP address command failed with "No such host is known", but the same command with the hostname succeeded! I then looked into the device itself and realized I had created all devices based on IP address. I changed the two device with the failing sensor to FQDNs và now it works perfectly. I don"t know why exactly an IP address invoked across a subnet causes this behavior but changing it to hostname fixed my issue.