Description This article describes an issue that may affect setups that
are upgraded from firmware v9.x running in CentOS to firmware v7.x
running in FortiNAC-OS. The captive portal is not reachable, the reason
(error 503): 'Service Unavailable. The ...
Description This article describes an example of how to set up VPN
session management for a FortiGate in FortiNAC using the Dissolvable
Agent on the end host, along with key troubleshooting steps. Scope
FortiNAC, Dissolvable Agent and FortiGate. Solu...
Description This article describes an example of how to set up FortiNAC
and Persistent Agent communication in a simplified network. Scope
FortiNAC and Persistent Agent. Solution Network design and IP planning.
Below is an example of a network diagram...
Description This article describes how to extract and utilize the
FortiNAC MIB file in a Network Monitoring System. This helps monitor the
FortiNAC setup itself, like its hardware components, license usage, and
the details of clients and managed devi...
Description This article explains a behavior that may occur when
attempting to uninstall or install a Persistent Agent package on a
Windows host where the software was originally installed via Group
Policy. Scope FortiNAC and Persistent Agent. Soluti...
I think the tag that is used is not the right one, this integration is
not related to FortiNAC (as a product) but related to FortiGate and
FortiAuthenticator.
The OS version seems standard, can you tell the agent version that is
installed in the end host and can FNAC be upgraded to 7.4.1? If the
System updates are not configured, the definitions may be old, some
details are shown in this article.
This limitation is explained on these articles: Technical Tip: IKEv2
tunnel fails when LDAP based usergroup is used for EAP Troubleshooting
Tip: Using IKEv2 for a dial-up IPsec tunnel with a RADIUS server and
Local user