Known Issues

This page contains all known issues and fixes for the Forticlient application.

Windows known issues

Microsoft has released an update which causes issues with the Fortinet Client connection where it fails while connecting or becomes unstable.

If you system has the KB2693643 update installed, please uninstall it. Once uninstalled, reboot your computer then try connecting to WROAMS using the Fortinet Client again.

Instructions on how to uninstall an update can be found at How to uninstall a Windows update - Microsoft Support
If you are experiencing issues connecting to WROAMS using the Fortinet Client, it is possible that your antivirus or firewall may not be correctly configured or conflicting with the Fortinet Client.

If you are using a third-party antivirus solution (such as Norton or McAfee) you may have to manually whitelist the Fortinet Client, or remove your third-party antivirus solution.

If you are experiencing issues with the Forticlient app disconnecting after a couple seconds check the following:

  1. Ensure your computer is up to date - information on checking for updates can be found at Get the latest Windows update - Microsoft Support
  2. Check for updated network adapter drivers - please check with your device's manufacturer or your local IT support for updated drivers

If the issue persists after following all steps please click here to create a ticket.

MacOS known issues

If you are using MacOS Sequoia (15.0), the Fortinet installer may prompt you for permissions to use a new network extension.

Some users may experience an issue where clicking the 'Open System Settings' while the installer asks for permissions does not bring them to the correct permissions screen.

In order to do so, please go to System Settings > General > Login Items & Extensions > Network Extensions (click the circled 'i') and enable all Fortinet related options (FortiTray / FortiClientNetwork / FortiClientProxy / FortiClientPacketFilter etc).

mac_install_permission1.png

mac_install_permission2.png

mac_install_permission3.png

Linux known issues

1- Open the Terminal, and run the following command:

    sudo resolvectl status

Check and confirm that the response has a line resolv.conf mode: stub is present

2- If the line is present, execute this:

Edit /etc/systemd/resolved.conf file:

Change the following parameters:

    edit line #DNSStubListener=yes
    to be DNSStubListener=no

Save the file.

3- Run the following commands:

    systemctl stop systemd-resolved
    systemctl start system-resolved

4- Run the following command:

    sudo resolvectl status

The mode should now show as 'uplink'.

This may be caused due to the gnome-keyring not being correctly configured.

1- Open the Terminal, and run the following commands:

To install the gnome-keyring:

    sudo apt install gnome-keyring

To initialize and unlock the login keyring:

    killall gnome-keyring-daemon

To configure the keyring:

    echo -n “your-login-password" | gnome-keyring-daemon --unlock

Users may experience issues enrolling the Forticlient application to the EMS server if they have installed the 7.4 version.

If you have version 7.4 installed, please uninstall / purge the application, then install version 7.2.

More information on installing Fortinet for Linux can be found at Fortinet Linux Product Downloads Information

Published on  and maintained in Cascade.