We are having on going issues related to the UTM features. Called
support the other day - no joke - 45 minutes on hold. Once they answered
the call, they opened a ticket for us (we could of done this online
without the 45 minute delay), and said some...
I'm working (albeit very slowly) with FN support on this but wanted to
throw the issue out to a wider audience to see if anyone had any ideas.
I have 2 x FG200D in a active-active HA pair. Was running 5.2.10 with
the below issue. Currently running 5....
Not sure if this is the correct forum.... We are testing out the
explicit proxy. We first tried using Digest auth (between the client and
the FG) with LDAP to authetnicate the client. Doesn't work. Fortinet
sort of acknowledges this is broke. :( BTW ...
Same setup as my last post -- Fortigate running with full SSL/TLS
inspection. How do we limit the cipher suites the Fortigate accepts from
the web servers it connects to? In the current, default configuration,
the Fortigate accepts quite a few undesi...
I've tried to deal with tech support a few times but.....we don't seem
to be on the same page. Setup: Fortiguard peforming full SSL/TLS
inspection of web traffic traffic. Does any sort of OCSP checking
happen? If not, how come? Thanks.Tom
- Has the firmware always been updated using proper firmware upgrade
path?Yes. - Has this particular cluster worked appropriately before? If
so, what Firmware was it running then? To the best of my recollection,
the cluster started life around 5.2.3 ...
We upgraded multiple locations to 5.2.8 in the hopes the SIP ALG issue
was resolved - negative. At some random point in time, the FG will start
natting SIP (port 5060) traffic using the IP address of the outbound
interface. When I say random, I mean ...
