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

[RobertB1]

Hi all, 

We have a few issues with our WinRM/JEA discovery, I must say, I'm not a fan, seems very fragile. One of the issue we are working with Microsoft to fix. The other we have no lead on yet. 

We have also followed all the steps to confirm the mid servers are configured correctly. However, we still getting this error 'Can't connect to target host via WinRM service, and this MID server is set to connect via WinRM.'. 

But! Only from mid server within a certain location cluster. 

I've included the disco log, and error from the mid server

Thanks as always for any help

[AJ-TechTrek]

Hi @RobertB1 ,

Good Day !!!

You must need to check from Mid Server to Target host connect to Port 5985, 5986

You can run the Telnet TaregtHostIP Port (5985,5986) from Cammands Prompt if you are using windows server.

https://learn.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/configure...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

[RobertB1]

Thanks for the suggestion AJ, I should have made my original post clearer. This issue is only present from a single mid server cluster. Servers are discovered without issue from other cluster. 

Also, the error is presenting itself at the classify phase, we’ve already got a successful result from the probe on 5985. 

cheers 

Rob 

[AJ-TechTrek]

Hi @RobertB1 ,

Your attached screenshot if not clear showing about the Port details, Also below articles will help you in this.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116898

https://www.servicenow.com/community/itom-forum/windows-discovery-and-winrm/m-p/987431

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535181

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

[MattSN]

My check list for WinRM

• Must have WinRM serivce enabled -  Use GPO to automaticaly start service named - WinRM
• Must have MID Server or wildcard * in list of trusted hosts - See GPO option Allow remote server management through WinRM
• Reverse DNS must be functional from the MID Server - KB0747683

Testing reverse dns from the MID server in PowerShell/CMD

#where target is 192.168.1.33 and DNS Server is 192.168.1.1
nslookup -type=ptr 192.168.1.33 192.168.1.1