What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Issue with Windows Update check

Votes:

0

Hi all, I have an issue with all my Windows Update sensors: not zable to moniutor with the foillowing error:

Connecting to remote server XXXXXXX failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

I already checked on internet and Paessler support, found some threads (about trusting hosts, etc.): did not solved the issue.

Just a precision: the host PRTG server and the monitored clients are both always on different domain when I see this error !! Of course, I verified the credentials: they are correct and indeed, the rest of the monitoring (using WMI) is working well.

Can you help me for that ? Any idea on a solution ?

Thanks in advance for your help !

domain prtg windows-update

Created on May 10, 2023 8:24:10 AM

Last change on May 15, 2023 6:49:30 AM by Felix Wiesneth [Paessler Support]



1 Reply

Votes:

0

Often Remote Powershell across domains is very tricky. It may be necessary to deploy a Remote Probe into the target domain. And then use the sensor under this new Remote Probe.

In the meantime, try formatting your windows credentials a little differently in the settings for the sensor.

Instead of formatting it with domain\username as you would for most sensors, clear out the domain field, and in the username field format it like: username@domain

Alos, since the devices are not in the domain, try to use "Negotiate authentication" in the sensor. There is also some configuration that needs to be done on the device, for more details please see Step 2.2 of the following article:

"Potential issues with the Windows Updates Status (PowerShell) sensor and how to resolve them"

Created on May 16, 2023 4:38:10 PM by Ivan Escalante [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.