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...
Mostly the LDAP/AD integration it is used for host/user network
authentication and role based access, typically using PEAP/MSCHAPv2,
some details are shown here: Technical Tip: MSCHAPv2 authentication,
join FortiNAC in domain and checks Portal authen...
You can try to configure a recipient exclusion as an inbound policy, to
bypass the email delivery, something similar to this: Technical Tip: How
to configure exclusion policy for a recipient address
Due to the limitations of this setup, you may also consider limiting at
least the IP assignment for the voice VLAN through DHCP (VCI pattern or
reservation and block unknown). It is not considered secure, but it will
at least reduce unnecessary netwo...
