Jump to content

Computer Alert Can't connect to ESET Inspect


Recommended Posts

I have deployed a brand new Server for Eset Inspect. The Server connect witch my EP (Eset Protect). I can connect into the Inspect console from my computer. I can manage it and saw all my endpoint into It. I have deployed the Eset Inspect Connector via Eset Protect on my computer. The Eset Inspect Connector got installed. But I got this alert "Can't connect to ESET Inspect". In Eset protect console or Eset Inspect console, if i go into computer and search my computer i got this warning.

If i go on my computer and check logs at C:\ProgramData\ESET\Inspect Connector\Logs. I got 

2022-11-08 00:10:25 0260c Error: Error while sending request to server at "localhost:8093".Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée (google translate from french) "No connection could be established because the target computer expressly refused it "

I was worried about "request to server at "localhost:8093"" Maybe localhost are'nt correct"

 

Can somebody help me ? 

Thanks

 

 

 

Link to comment
Share on other sites

  • Administrators

How did you install the EI connector? Does it work if you install it manually using an msi installer and enter the EI server's hostname?

 

Link to comment
Share on other sites

Alternatively, assign a EI Connector policy with the correct hostname / ip adres configured to the  device(s) via ESET PROTECT. (assuming you don't already have a policy based on your description) 

Link to comment
Share on other sites

I have not add somes Policy for the EI connector. I only gone into Eset Protect and made a task for deploy the connector on my endpoint. Where can i found the right informations/configuration for my policies if i need one?

Link to comment
Share on other sites

You can create a new policy in ESET PROTECT:

image.png.e7c39df32b5f703540cca7cca7f6435a.png

Select the product ESET Inspect Connector (1) & define the correct hostname/IP of the server where you installed ESET Inspect Server component (2) & select the correct Certificate Authority. 
image.thumb.png.1e71592b952710e8424e1b5717b741ff.png

Assign the policy to the all group (or a different group if you prefer):
image.png.7aeb72bdc0487138110957f7a4e9ba40.png

 

 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...