--- title: "Communicating through a RelayServer" slug: "communicating-through-a-relayserver" tags: ["Agent", "Product Usage"] updated: 2026-08-26T12:54:08Z published: 2026-08-26T19:15:28Z canonical: "docs.trellix.com/communicating-through-a-relayserver" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Communicating through a RelayServer Enabling relay capability in your network converts a Trellix Agent to a **RelayServer**. A Trellix Agent with relay capability can access ePO - On-prem, Agent Handler, or the distributed repository listed in **`Sitelist.xml`**. A Trellix Agent discovers each **RelayServer** in the network at every agent-server communication, and caches details for the first five unique servers to respond. If the connection fails or the required content update isn't available, Trellix Agent connects to the first **RelayServer** in its cached list. Relay capability can be enabled on Trellix Agent that does not have direct connectivity to ePO - On-prem or **Agent Handler** to bridge communication between the client systems and ePO - On-prem. You can configure more than one Trellix Agent as a **RelayServer** to maintain network load balance. ### Note **Agent Handler** is not available on McAfee ePO Cloud. When a Trellix Agent uses relay to communicate with ePO server (Saas or On-prem), the connections are established in two parts; first between Trellix Agent and the **RelayServer**, and second between the **RelayServer** and ePO server. These connections are maintained during the communication. ### Note For ePO - SaaS: Relay Server/Client functionality is supported but disabled by default. To use this feature, you must manually enable and configure it within your Trellix Agent policies in the ePO - SaaS console. :