Description This article describes a behavior that affects setups using
RADIUS authentication with PEAP/MSCHAPv2 and that have a partially
functioning Winbind configuration. Scope FortiNAC. Solution When Winbind
is not working properly, for example, ...
Description This article describes a behavior that affects setups that
are recently upgraded to firmware version 7.6.5. Scope FortiNAC 7.6.5.
Solution When the setup is updated to this firmware version, the
'TelnetServer' debug will be automatically ...
Description This article describes a simple method to quickly verify
database synchronization between two nodes in a High Availability (HA)
cluster. Scope FortiNAC. Solution When the primary node is in control
and the cluster is healthy, database syn...
Description This article describes the changes to the firmware update
procedure in newer versions of FortiNAC. Scope FortiNAC v7.6.3 and later
versions. Solution In newer versions of FortiNAC, the firmware file will
no longer be downloaded directly f...
Description This article describes the configuration steps required to
quickly isolate hosts that initially had the Persistent Agent
communicating, but are no longer doing so. The host's compliance status
may have changed during this time, and it may...
Since the source and destination IPs are hidden, have you verified that
in both the working and non‑working cases the IPs of FNAC and the FSW
are the same, and that there is no NAT between them?
From the FNAC perspective, the CoA/DM content and attributes appear the
same on both cases. Since it is accepted previously but ignored by the
switch when the host is disabled, I assume this is because the host is
not seen as authenticated on the swi...
