Hi All,We have followed this article to set FQDN access using Split
tunnel:https://community.fortinet.com/t5/FortiGate/Technical-Tip-Access-to-Specific-FQDN-using-Split-Tunnel-SSL-VPN/ta-p/190062
The users are able to access the FQDN thought the spli...
Hi All,We have an old FortiGate 100D (v6.0.5 build0268 (GA)) which we
access by browser with the IP address of it.I have installed self-signed
SSL on it and added it to the administration setting to start accessing
it by FQDN, however the interface p...
Hi I thought so also, however even though that the group does not exist
in any policy, the VPN connection keep working.I believe this is a
difference in the behavior between static to dynamic portals. I have
upgraded the FortiClient on both Windows a...
Hi AEK,First thank you for all your help.Just fyi, I went even further
and removed the "Dynamic_Test_Group" from all policy rules,yet I'm still
getting the extra route once the FortiClient connected, meaning that it
is coming from the Portal mapping:
hi AEK,I have removed all FQDN from the rule and kept only 8.8.8.8 as
IP, not name:* the test group "Dynamic_Test_Group" isnt in any other
rule, only this onehowever the extra route still showing after the
ForitClient gets connected:
Hi hbac, thank you for your reply.I can show my policy without the FQDN
entries, I have checked them all and all resolve to specific IP
addresses: Forti version 7.2.3FortiClient version 7.0.9.0493
