Let's see if you can help me, I have several computers using the Forticlient to access the company's VPN, the connection is established correctly, but as soon as you try to download the messages from Microsoft Outlook through Exchange it does so for a few minutes, then the Outlook itself puts me, after retrying it, disconnected, and does not let me work with the Outlook ...
any ideas ??
The connection is simple, mail server (VM) -switch-fortigate-(ISP)Internet
Thank you in advance.
It is SSLVPN. We have held off of 6.0.9 due to the RDP bug in SSLVPN. We were on 6.0.5 and experienced a logging delay issue. Logs were getting dropped or buffered for an excessive amount of time. Moving to 6.0.7 fixed that, but now we have this issue. Frustrating. You think they would QC something as critical as SSLVPN more rigorously. Release notes don't mention this type of issue so maybe we are the lucky winners of the unique bug.
It is odd. Everything else works fine, it just seems to be munging Outlook 16 connectivity to our on-Prem Exchange 2016 server. All DNS and layer 3/Pings check out just fine. Can still log into OWA just fine. But the minute I connect via FortiClient VPN it starts logging connectivity issues when Outlook tries to sync.
They recognise there is an issue with RDP sessions being removed from the Fortigate whilst the RDP session is still active but have said they are not aware of Outlook connections dropping also when on SSL Vpn.
They want me to run debug when client is connected and provide them with the times when Outlook disconnects.
We upgraded from 5.6.10 to 6.0.9 and have 100's of SSL Vpn users.
Had no choice but to roll back our Vpn gateway Fortigates as many complaints from users.
Hopefully, this is fixed in 6.0.10 or at least they give me the special fixed firmware.
Just tell them you want to try build 8661 and see if that works, or perhaps better yet wait a few more weeks for 6.0.10 and monitor these forums to see if that helps. I remember when we moved from 5.6 to 6 it took lots of conversion work with some of our policies.
I explained to Fortinet that others with exactly the same problem have been given an interim firmware which appears to resolve the problem.
They said they will give me the same interim firmware to try and to let them know if this fixes my issue, however it comes with the caveat that you cannot roll-back the firmware and with no guarantees that it may introduce other issues.
If you have hardware that stores previous firmware on alternative partition, you can roll back by booting to the alternative partition, otherwise you have to format and TFTP previous firmware back to the Fortigate.
As this is a production Fortigate i'm not so keen now to apply an interim firmware which Fortigate probably will not offer full support on.
Running FortiClient 220.127.116.110 and our users can create a VPN connection. Which seems to stay stable.
VPN stays connected, Networkshares stay connected and accessible, Outlook is working.
But after several minutes Outlook is disconnected. All other connections are still working and accessible (networkshares for example). Closing Outlook and reopening does not solve it. Let Outlook reconnect does not solve the issue.
Our FortiGate is running firmware 6.4.6. (Firmware 6.4.7 is available not yet installed).
Is there a solution for this issue?
I have some kind of a solution, that is connect to the client by teamviewer and give the client a ipconfig /flushdns
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.