Page 1 of 1

Unable to probe ESX host

Posted: Mon Oct 04, 2021 2:10 am
by epicit
Hi guys,

We are adding a server as a esx host within automate and receive an error 'no connection could be made because the target machine actively refused it. I've attached screenshots of the error as well? Looks like python can't check the request.

Thanks

Re: Unable to probe ESX host

Posted: Mon Oct 11, 2021 3:48 pm
by Cubert
Please have a look at the following post and make sure this is not a factor.

viewtopic.php?f=31&t=5228&sid=389ab88e6 ... 003a6050a2

Next the error for Actively refused connection is that CIM services are not running on the port being queried so the port on the ESX host is "actively refusing" connections on that port. This means CIM service has died (see this alot) try rebooting ESX host or CIM is disabled in which the above post should help you get it enabled and functional for querying.


So try those 2 pills first and see if either lead to a resolution.

If it was a password or some error parsing the CIM DATA you would not get this refused error. This only comes from port denial. So could be a firewall on ESX host aswell, again the above post should help get you sorted.

Re: Unable to probe ESX host

Posted: Fri Oct 07, 2022 4:40 pm
by rspaulding
epicit wrote: Mon Oct 04, 2021 2:10 am Hi guys,

We are adding a server as a esx host within automate and receive an error 'no connection could be made because the target machine actively refused it. I've attached screenshots of the error as well? Looks like python can't check the request.

Thanks
We are having the same issue with 7.0 Update 3. I followed your instructions and verified all services are running, but getting the Python errors mentioned above. Any further ideas to try?

Re: Unable to probe ESX host

Posted: Sat Oct 08, 2022 3:12 pm
by Cubert
Here is how to test manually for data.

viewtopic.php?p=9697#p9697

If you are getting a rejection then you either have no service running on CIM port or a firewall up on ESX that is not allowing outside access to the port.

Otherwise we would be getting a different error. A user / password bad or a SSL error to some effect but to get a connection refused which is strictly a I knock but no one answers error.