Istvan had provided the commands on Monday:
Enable debug level logging on the Forticlient (if you use tunnel-mode) in File -> Settings -> Logging I think and the same on the Fortigate:
# diagnose debug application sslvpn -1
# diagnose debug enable
than start a new session and when it gets stuck, look at both logs.
If you don' t use tunnel-mode then check the Windows Application and System Event logs instead.
Don' t forget to disable debug-level logging on both after you finished.
# diagnose debug disable
# diagnose debug reset
Maybe show the process you used in the command line to enable these diagnostics, and the fact that the output remained blank for the duration of you test. Otherwise, if either the client or FortiGate provided *some* output, even if it wasn' t immediately relevant, post it here so everyone can have a look.
Fuzz any confidential details as need be, of course.
Regards,
Chris McMullan
Fortinet Ottawa