FortiClient SSL VPN disconnects only on one Windows desktop after ~20 minutes, then won’t reconnect for another ~20 minutes
Environment
- FortiClient VPN version: 7.0.14.0585
- Windows desktop PC
- CPU: AMD Ryzen 9 9900X
- Motherboard: X870E AORUS PRO ICE
- RAM: 64 GB
- Windows 11 x64
- FortiClient SSL VPN
Problem
- The VPN disconnects after around 20 minutes of use
- It is not exactly 20 minutes, just approximately
- After it disconnects, I cannot reconnect immediately
- I usually have to wait around another 20 minutes before it will connect again
- The problem happens only on this specific PC
- I installed the same FortiClient / used the same VPN profile on another computer, and it does not disconnect there
What I already tested
- Reinstalled FortiClient
- Tried the newest available FortiClient version
- The issue still happens only on this machine
FortiClient log behavior
The FortiClient logs repeatedly show messages like:
- Broken pipe! Client is exited (3)
- g_hEventExit set
- FortiSslvpnD: PipeServerProc exits
This makes me think the client side is breaking locally rather than the FortiGate cleanly rejecting the session.
Windows events around the disconnect
In Event Viewer I’m seeing:
- Windows Error Reporting
- LiveKernelEvent
- P1: 141
I also see some Service Control Manager 7040 entries related to:
- IPsec Policy Agent
- IKE and AuthIP IPsec Keying Modules
But those look secondary to me.
Important detail
This issue does not follow the user/account.
It follows this PC only.
Question
Has anyone seen FortiClient SSL VPN disconnects caused by:
- GPU / display driver instability
- LiveKernelEvent 141
- local Windows/kernel instability
- network stack / driver conflicts on a single PC
Also, has anyone seen a case where after the disconnect, FortiClient will not reconnect for another ~20 minutes, but the same account works fine on a different machine?
I only have access to the FortiClient side. The company asking for support is the customer, and they have not been willing to verify anything on the FortiGate/server side. We are not part of their organization, so we do not have access to FortiGate settings, policies, or server-side logs.