Troubleshooting Tip: Why ZTNA Destinations May Not Reflect in FortiClient: Causes and Fixes

Description

This article describes why ZTNA (Zero Trust Network Access) destinations may not reflect or appear correctly in FortiClient.

Scope

FortiClient.

Solution

For TCP forwarding, configuring a ZTNA destination profile in EMS is required to ensure the ZTNA destination appears on FortiClient.

However, even after the ZTNA destination profile is correctly configured and applied to the appropriate endpoint, the ZTNA destination may still not appear on FortiClient.

In the FortiClient, the ZTNA destination does not reflect even though it is configured on the EMS

EMS config:

Expand the Rules section and see if the gateway is enabled. If it is disabled, enable it and see if the ZTNA destination is visible in the FortiClient:

Enable it:

The ZTNA destination is now, appearing on the endpoint: