--- title: "Sending a management request in a NAT deployment" slug: "sending-a-management-request-in-a-nat-deployment-1" updated: 2026-08-27T07:56:47Z published: 2026-09-08T22:58:11Z canonical: "docs.trellix.com/sending-a-management-request-in-a-nat-deployment-1" --- > ## 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. # Sending a management request in a NAT deployment Administrators can send a request to add the appliance to the Central Management System appliance. A rendezvous process enables the appliance to attempt the request and allows the Central Management System administrator to see the list of pending requests. ### Requirements for establishing a successful connection To send a management request and successfully establish and maintain the connection, the following must be in place: - **Automatic rendezvous attempts are enabled** on the requesting File Protect appliance (disabled by default). - **The auto connect feature is enabled** on the requesting File Protect appliance so it automatically tries to connect to the Central Management System appliance after the rendezvous attempt succeeds (enabled by default). ### Note See [Preparing an File Protect appliance to send a management request in a NAT deployment](/docs/preparing-file-protect-appliance-send-management-request-nat-deployment) to verify and enable these settings. - **The File Protect appliance has a unique and permanent hostname**. Pending requests from appliances with the same hostname or IP address will be rejected. If the hostname is changed, the connection will be broken and cannot be reset. If this happens, the appliance must be removed from the Central Management System appliance and then added again using the new hostname. - **The Central Management System appliance and the File Protect appliance have the same rendezvous service name**. The rendezvous process has an identifier (known as *service name*) that is set to "cmc" by default. The Central Management System appliance and the requesting appliance must have the same service name; if you change the service name on one, you must change it on the other as well. The` cmc rendezvous service-name <hostname> `command changes the service name; the` no cmc rendezvous service-name `command restores the default value. For details, see the *CLI Command Reference*. ### Important Appliance-initiated connections are not supported in Central Management System high availability (HA) deployments. Prerequisites - Operator or Admin access - Network address translation (NAT) mapping, as described in [Address mapping](/docs/about-nat-address-mapping-5) - *If the requesting appliance is behind a NAT gateway*: The virtual NAT address and port that map to the requesting appliance internal IP address and SSH port - If the Central Management System appliance is behind a NAT gateway: - The virtual NAT address and port that map to the Central Management System internal IP address and SSH port - One of the following: - The accessible Central Management System IP address and port, described in [Configuring and activating an accessible DTI server address](/docs/configuring-and-activating-an-accessible-dti-server-address-3) - Single-port communication enabled on the appliance, described in [Changing the address type for DTI network service requests](/docs/changing-the-address-type-for-dti-network-service-requests-3) :