This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 98%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAE%3C/text%3E%3C/svg%3E)
Hi Team,
I have encountering an issue with devices while updating their records.
This issue occurs after installing FortiClient ZTNA.
I monitored the traffic by Wireshark and I observed that the connection refused as shown:
I opened a request with Fortinet support but I also appreciate your support to investigate why the dynamic update refused.
Thanks,
Alaa Elrayes
Could anyone help me ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 4%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESY%3C/text%3E%3C/svg%3E)
I think I have the same issue. I also have a ticket open. What version of FCT did you install? After upgrading from 7.0.8 to 7.2.2 my clients get a refused from our Windows DNS server. I'm going to try an install of 7.2.2 without the ZTNA components to see if that fixes it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 53%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAE%3C/text%3E%3C/svg%3E)
@Shane Yoder
Our FortiClient is 7.2.1 and I have tried also 7.2.2 but the same issue.
The FortiClient uses unsecure connection with the DNS server and if you change the DNS security to allow unsecure, machines will update records but it is not a secure workarround.
I forced the machine to use "secure only" using GPO but the result is a query without dynamic update.
Finally, my opened ticket to FortiClient support marked as a bug.
@Alaa Elrayes Can you share a bug ID or your ticket number?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
@Shane Yoder Bug ID 0964456