Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
On-net/off-net detection requires:
-5.2.3
-the FortiGate to act as DHCP server for your clients; otherwise, define option 224 on your DHCP scope (on whichever server you use) to be the S/N of the FortiGate in regular text (Windows Server 2012) or hex (2008).
If you define a non-default profile for a specific (batch of) FortiClient(s), it needs to match based on device or device group primarily. "Detect and Identify Devices" needs to be enabled on the interface facing clients. Be aware, iOS devices can be differentiated from Windows or Mac devices, but not among themselves (i.e., iPhone vs. iPad). The limitation here is in the MAC address and OS identifying information not being clear enough what product it is.
Regards, Chris McMullan Fortinet Ottawa
I would run the NAC daemon debug when the FortiClient registers to the FortiGate, and see what profile is chosen there.
diag debug reset
diag debug enable
diag debug application fcnacd -1
<initiate a registration, then...>
diag debug reset
diag debug disable
I'd suggest opening a ticket with TAC to help interpret the output.
Regards, Chris McMullan Fortinet Ottawa
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1713 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.