Discovery on windows server fails, credential test fails, but remote PowerShell from MID server works

[Bob D]

I have several windows servers on a subnet.   All but one are Discovered properly.  One fails.

from Discovery logs:

Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

also

{"credential_type":"Windows","credential_name":"Windows","credential_order":"100","credential_success":false,"credential_id":"9e.....................b0ee"},

And finally - A credential test on this server fails to connect.

Has to be a credential issue, right?  Or possibly network connectivity?

However - 

Windows admins are able to establish remote PowerShell connection from the MID server using the Windows credential in question and run simple commands such as  >dir c:\       

I don't believe I have any options from the ServiceNow side to change any configuration or setting to address this. Suggestions on what could be the issue on the server side if the remote PowerShell from MID server is working?   

thank you

[Bob D]

Yes.  That's what makes this frustrating.  Several other windows servers on the same subnet are discovered OK with this same credential.  I don't want to change anything with my ServiceNow or network config because it's working.  To me - all evidence points to something on the server itself that is preventing a successful Discovery.

thank you, as always, Doug for your willingness to jump in

[Shekhar Deshin1]

This error occurs if the server administrator does not have permissions to the local security policy on Microsoft Windows 2008 server.
1.You can verify the Local Security Policy on failing server.
2.The user does not have remote access to the computer through DCOM.
Typically, DCOM errors occur when connecting to a remote computer with a different operating system version.

Thanks

[Brian Nielsen]

Hi Bob D

It could very well be caused by WMI/RPC/firewall rules. The best source I could come up with in snap is this article from HI

"Resolving issue of RPC Server unavailable during Windows Server discovery in Service Mapping"
https://hi.service-now.com/kb_view.do?sysparm_article=KB0564282

Best regards Brian