Issue
Solution
When installing ESET Inspect Connector, problems can arise from blocked communication or other configuration issues. Verifying firewall settings ensures that components can communicate properly, while collecting logs and enabling detailed logging provides the necessary information to identify and resolve installation problems effectively.
Verify firewall configuration
Incorrect firewall settings can cause installation failures or prevent ESET Inspect On-Prem components from communicating properly. To verify that communication works properly, check the firewall settings on both the ESET Inspect Server and the computer where the Connector is being installed.
- If Windows Firewall is enabled, the installer automatically creates the necessary communication rules.
- If Windows Firewall is disabled or you are using a third-party firewall, manually allow the following ports: 80, 443, 8093, and 2223.
Collect default logs
You can collect the default ESET Inspect Server and ESET Inspect Connector logs in the following locations:
- ESET Inspect Server:
C:\ProgramData\ESET\Inspect Server\Logs\ - ESET Inspect Connector:
- Windows:
C:\ProgramData\ESET\Inspect Connector\logs - macOS:
/Library/Application Support/ESET/eset_eia/logs - Linux:
/var/log/eset/eei/
- Windows:
By default, the ESET Inspect Server or ESET Inspect Connector installer does not record detailed installation steps; only runtime errors are recorded after the installation is complete. If the installation fails or you need to analyze the process, enable detailed logging.
Enable detailed logging
To enable detailed logging for ESET Inspect Server or ESET Inspect Connector, run the installer from an administrative command prompt with the attribute: /L*Vx temp_log.txt. The attribute creates an additional log file (temp_log.txt) that records the full installation process.