Windows Server Discovery Failing Despite Valid Credentials

[Arjun69]

We're encountering an issue with Windows server discovery in ServiceNow. The discovery is failing with the error:

"Could not find any valid credentials to authenticate the target for type [Windows]"

Here are the details:

• The credentials used for these servers are confirmed to exist in the credential list.
• The same credentials have successfully discovered other servers within the same subnet.
• Port 135 is being used for the discovery.
• Verified that there are no firewall or network restrictions blocking the port.

Has anyone faced a similar issue or have suggestions on what else to check? Any insights would be appreciated.

[Abbas_5]

Hello @Arjun69,

Please refer to the link below:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657528

If this is helpful, please click the thumbs-up button and accept this solution as the correct answer, referring to it in the future. It will be helpful to them.

Thanks & Regards, '
Abbas Shaik

[David77]

We are seeing a similar problem on servers that were previously being consistently discovered for some time. 
We cannot see it's caused by a specific MIDserver, as we have don a Discover now using the same MID where it failed with the credential not found error and had it work. 

We're not sure if its related to our MID version (Xanadu) or to MIDs being updated to WIN11 OS.