Description This article describes that in Meraki AP integration,
FortiNAC sometimes may not update the Host state to offline when it
receives the Syslog message 'events type=disassociation'. Since FortiNAC
is not able to read live sessions from Mera...
Description This article describes the cases when the network
administrators want to be notified when a host is identified as an 'At
Risk' state. In some environments where connectivity is important, the
Scan remediation action can be configured to D...
Description This article describes how to upgrade a FortiNAC-F setup
running NAC-OS using an interim build image. The procedure is used to
upgrade the firmware to a version suggested and offered by the TAC
support team, mainly for testing new feature...
Description This article describe how to use events and audit logs in
cases when a new issue arises on an existing setup that was previously
working normally. This also applies for an intermittent issue that
appear at specific time only. Scope FortiN...
Description This article describes that in authentications that include
MSCHAPv2, the Winbind tool needs to be configured and FortiNAC must be
joined to the domain for the authentications to succeed. Scope FortiNAC,
Windows Server AD. Solution In lat...
The concept of "not in the database" is valid for the whole domain only,
not for the subdomains. As long as the domain is present in the database
every request for it's subdomains will not be forwarded. If the entry is
not found locally it will respo...
As I know this is a limit for the standard DNS server not only a
limitation of FGT. If the network has a private DNS server configured
with all this private domains you can choose to forward all the request
without specifying domains in the local dat...
I think this is a DNS server behavior, if the domain exist locally all
the subdomains for that domain will be searched locally, the requests
will not be forwarded to the external DNS server. As a workaround you
can create another/similar domain for t...
It may be an emulator issue (GNS3) while bridging to an external
interface. Try connecting another virtual host from within GNS3 to the
FGT (or a VPC) to verify the communication.