Description | This article describes when FortiClient does not send ZTNA traffic when using the wrong FQDN syntax. |
Scope | FortiClient endpoint v7.2.2. |
Solution |
FortiClient does not send traffic if the ZTNA rule for FQDN does not have the specific syntax.
For example: This setting will work when setting FQDN destination host like 'test01.test.local:8000' and will be converted by ZTNA traffic and be received at FortiGate.
Result: FortiClient will send ZTNA traffic to the destination.
The FQDN 'test02' is not complete and Forticlient will not send ZTNA traffic to the destination.
A solution can be to modify it as 'test02.local:80' for example and FortiClient will accept FQDN and then send ZTNA traffic to the destination. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.