ePolicy Orchestrator server can't perform an agent wake-up call to a VPN client
Last Modified: 2023-09-01 04:44: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.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
ePolicy Orchestrator server can't perform an agent wake-up call to a VPN client
Technical Articles ID:
KB58818
Last Modified: 2023-09-01 04:44:59 Etc/GMT EnvironmentePolicy Orchestrator (ePO) 5.x
ProblemThe ePO server can't perform an agent wake-up call to a Virtual Private Network (VPN) client.
You see the following error: CauseAn agent wake-up call doesn't work when the client is connected through a VPN. By design, the Trellix Agent (TA) binds to the first IP address that it receives during startup.
This IP address is the one that's sent to the ePO Server. The address that the client is given during system startup isn't the Network Address Translation address. So, the ePO Server is unable to connect to TA using an agent wake-up call. But, the client-to-ePO server communication works, because the client is aware of the ePO Server IP address. The result indicates that the client receives all updates and policies from the server with every agent-to-server communication. Solution
This behavior is expected.
Affected ProductsLanguages:This article is available in the following languages: |
|