I have an issue with Forticleint that has just popped up in the last
week or so, without any configuration or version changes to either the
FortiGate unit or the FortiClient agents. FortiClient is licensed, FWIW.
Fortigate 5.2.0, FortiClient 5.2.x (d...
I am having a problem with the DHCP server on a 60C running 5.2
firmware. Basically, when I try to reserve an IP for certain devices, as
soon as the then-existing IP reservation expires, the device gets the
DNS server address assigned as its gateway ...
I am running 5.2 on a 60C, with FortiClient 5.2.1 on all clients, all of
which are " on-net" . However, on the 60C, all of the clients show up as
" off-net" . Is there something that I need to do in order to make them
register properly?
Ah thank you. I had searched the forums but missed this post. Guess I'
ll deal with the workarounds until this is corrected. This issue was
also reported in this post. It appears to be related to the known issue
mentioned in the release notes:
I do have discovery enabled, and yes here is another L3 device between
the FGT and the clients (though I have no VLANs configured). Is that the
issue / is it resolvable?
