Can't connect to target host via WinRM service, and this MID server is set to connect via WinRM only

monica12
Mega Contributor

Hello team,

While implementing Server discovery using JEA, i came across an error for one of the server: "Can't connect to target host via WinRM service, and this MID server is set to connect via WinRM only".

Its throwing the same error while validating the credentials and while doing quick discovery.

Please can someone help on this. Thanks in advance !

PFB SS's for the same

find_real_file.png

find_real_file.png

1 ACCEPTED SOLUTION

Any recent reboot was done on this server and after that issue got resolved?

🙂 Many times reboot does the trick

Reagrds

RP

View solution in original post

6 REPLIES 6

Rahul Priyadars
Giga Sage
Giga Sage

It seems that WIN RM service is not enabled on Target Host.

I assume Configuration is done as per Service Now Steps.

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/concept/mic...

 

Use the following MID Server property and System property to troubleshoot issues:

  1. mid.probe.collect_debug_info: This is an optional MID Server property to collect debug information. When this property is set to true, the MID Server collects credential debug info and puts it in the payload of ECC input message. It doesn't affect how JEA works.
  2. glide.discovery.log_debug_info: This is an optional system property to collect debug information. When this property is set to true, the discovery sensor extracts the debug info from ECC input message and writes it to the discovery log table, so the debug information is visible when inspecting discovery status.

Regards

RP

Ashutosh Munot1
Kilo Patron
Kilo Patron

Hi,

Just make sure, have you done this step as well

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/product/mid-server/task/enable-winRM-MID-servers.html

 

Thanks,
Ashutosh

monica12
Mega Contributor

Hi,

I followed all the prerequisites for JEA as per servicenow docs ,it was happening for just this server, now it got resolved, did nothing. Strange. Thanks anyways.

Any recent reboot was done on this server and after that issue got resolved?

🙂 Many times reboot does the trick

Reagrds

RP