We have experienced an issue with specific in-house built applications
that worked when not behind our Fortigate 7.x firewall but started to
fail when we placed behind it. Turns out the application does not send
keep-alive or heartbeats and so the se...
I'm using a Fortigate 4200 running firmware 7.4. Most of our rules use
FQDNs like www.microsoft.com but this seems very permissive. Ideally
we'd like to examine the actual URLs being used and restrict i.e. allow
things like http://www.microsoft.com/c...
So we have been running Forticlient and EMS cloud for 18 months. We have
had many issues with the following: Split tunnel for Webex and MS teams
not workingZTNA tags not syncing to FortigatesLocal LAN Access not
workingEach and every one of these thi...
We are using Forticlient EMS 7.2.4 and Forticlient 7.2.4 on Windows 10
22 H2 Enterprise. Our web filter rules have a mix of Simple, Wildcard
and RegEx based rules. Reading the documentation here it not clear to me
how the match is performed. It state...
I'm using Forticlient EMS 7.2.4 and Fortigate 42000F 7.0.12 (on-prem).
Currently all our policy rules are the traditional system to system or
area to area type i.e. IP/CIDR/HOSTNAME to IP/CIDR/HOSTNAMEI'm looking
for a modern approach where I can gov...
And also, we now have BSOD in forti web filter in Forticlient 7.2.9.
Logged to support. We are lookign at alterntive products. 3rd BSOD we've
experienced with the product.
Just an update on webex split tunnelling. Basically support say they
cannot actually reliably support it! Since the product works by adding
routes to Windows the number of routes for Webex excceeds whats
supported by Windows.
So we have established with support that this is only possible on IPSEC
and not SSL at leats on Forticlient 7.2.4. We are engaged with our
account manager and support on why the documentation states otherwise.
