Hi
We have a segmented network in which (for example) all "voice" related devices have a separate network.
For example:
- All servers (inlcuding PRTG) and stuff have 10.10.10.x
- All "voice" servers and stuff have 10.10.11.x
The probe in 10.10.10.x seems to monitore everything like a charm from servers and devices in the "voice" network, except of the "Windows Updates Status" (Powershell) sensor. This sensor responds with "no such host is known". The same sensors work on the normal network.
Any ideas why this is happening? I have searched the docs, but could not find a solution to this :(
Regards,
Alex
Article Comments
Hello Alex,
Thank you for your message.
To use the Windows Update sensor on devices on a different network, I invite you to check the following:
You might also check if you use the IP address of the devices and if so, change them to their FQDN and trying to add the sensor again. Here is a kb article which correspond to your situation: https://www.paessler.com/manuals/prtg/windows_update_info_sensor
You could also install a remote probe within the other network and try to add the Windows Update sensor on it. This way, you can make sure that the devices configuration is correct and only have to open the port TCP 23560 through the firewall.
Regards.
May, 2022 - Permalink
Hello Alex,
Thank you for your message.
To use the Windows Update sensor on devices on a different network, I invite you to check the following:
You might also check if you use the IP address of the devices and if so, change them to their FQDN and trying to add the sensor again. Here is a kb article which correspond to your situation: https://www.paessler.com/manuals/prtg/windows_update_info_sensor
You could also install a remote probe within the other network and try to add the Windows Update sensor on it. This way, you can make sure that the devices configuration is correct and only have to open the port TCP 23560 through the firewall.
Regards.
May, 2022 - Permalink