Port conflicts with ePolicy Orchestrator services when netstat only displays listening process as belonging to System
Last Modified: 2023-07-13 06:59:59 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Port conflicts with ePolicy Orchestrator services when netstat only displays listening process as belonging to System
Technical Articles ID:
KB79533
Last Modified: 2023-07-13 06:59:59 Etc/GMT EnvironmentePolicy Orchestrator (ePO) 5.x
ProblemePO services are unable to start.
Typically, using the But, some processes are listed only as System when you run
CausePort conflict issue. Some processes, both Windows and third-party, only report as listening through the System process.
SolutionThis behavior is expected.
When a port conflict occurs, there are three primary ways to resolve it:
Workaround 1Change the port that the other service is using
Follow the steps to allow ePO services to bind to their preconfigured port if there's a port conflict:
Workaround 2Change the port that ePO is using
See the following articles for detailed information about changing ePO ports:
Affected ProductsLanguages:This article is available in the following languages: |
|