Getting error while doing window discovery

Gaurav49
Tera Contributor

‎04-05-2021 02:06 PM

HI all,

I am getting below different set of errors for different IP addresses while discovery windows server. Could someone please suggest how to fix those.

1) Request not sent to uri= https://x.x.x.x./api/cluster : java.net.SocketException: Socket Closed

2) The result file \\x.x.x.x\admin$\temp\psscript_output_9b87a3b7-c378-4b40-a019-e362b05bf1f8.txt can't be fetched because it doesn't existHRESULT: [-2146233087]

3)Authentication failure with the local MID server service credential.

4)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))

Labels:
0 Helpfuls
  • 1,844 Views
2 REPLIES 2

Rahul Priyadars
Giga Sage
Giga Sage

‎04-05-2021 05:48 PM

1) Request not sent to uri= https://x.x.x.x./api/cluster : java.net.SocketException: Socket Closed---> Seems PORT Issue.

2) The result file \\x.x.x.x\admin$\temp\psscript_output_9b87a3b7-c378-4b40-a019-e362b05bf1f8.txt can't be fetched because it doesn't existHRESULT: [-2146233087]---> 

3)Authentication failure with the local MID server service credential.---> Windows CREDS not working.

4)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))--> Is your Destination Device is Reachable from MID Server?

Please check connectivity and Credentials .

You can refer below KB for reference-

https://hi.service-now.com/kb_view.do?sysparm_article=KB0657528

Regards

RP

 

Venky VA
ServiceNow Employee
ServiceNow Employee

‎04-05-2021 06:31 PM

hi gaurav,

  • Check windows credentials are active.
  • Test windows credentials using machine IP your are trying to discover.
  • Check windows machine reachable from mid server[try ping from mid server to windows].
  • The credential that you configure must have the following:
    • Access to the WMI service to the current namespace and sub-namespaces.
    • Access to the Powershell service.
    • Membership in the Distributed COM Users local security group.