We have some hyper-v VMs that we upgraded from 7.2.3 to 7.2.5
forticlient. SSL VPN no longer works after upgrading.We can repeat the
problem by downgrading to 7.2.3 and then successfully connecting then
upgrading to 7.2.5 and breaking it again.we nee...
When adding an authentication server in EMS I only ever get 1 domain
even when the tenant has multiple domains registered and synced. These
aren't subdomains but two different unique
domains.example1.comexample2.comThe only information I provide is t...
I have an issue on a 200F, running 7.2.8. I have two EMAC vlans. One
where the ansible host is running (VLAN1818). And another that is shared
across multiple firewalls and vdoms across the network (VLAN0998).I have
an ansible playbook with 20 tasks i...
The upgrade path from 7.2.5 is to first go to 7.2.7 then to 7.2.8.What
is actually happening during the 7.2.7 upgrade that it is required as
part of the process?
fortiAfter upgrading to 7.4.3 my 1100E is doing something wrong when
answering requests for ifoutoctets on ipsec interfaces.Occassionaly
Delta for out octets is way too high which shows an ipsec tunnel on a
40Gig interface at 90+ percent utilization ...
I got hit with that on 7.2.10, but was able to update the
fortiauthenticator to 6.6.2 which supports message authenticator AVP.Duo
just released 6.4.2 yesterday and you can add the message authenticator
to Duo now.
TAC provided me with a 7.2.5.7679 Interim build that corrected
everything. Waiting for the next GA to be released before I deploy
everywhere. But the interim release is enough to at least get the 2019
devs up and running.
I opened a ticket with TAC and sent the full forticlient diagnostics and
fortigate debugs. I will be having a screenshare session with an
engineer later today.
