Providing secure, identity-based access to private apps and resources without traditional VPNs
Update (November 2026)
Following up on this thread one year later. We have now completed the full migration to Global Secure Access (Private Access). All remote users now connect through GSA.
Unfortunately, the issue is still there:
- Users get random RDP disconnections, with the client showing “Attempting to reconnect” as if there was a short network drop.
- The pattern hasn’t changed: some days nothing happens, other days users get 1 to 4 disconnections, at random times and not synchronized between users.
- We tested RDP both with UDP enabled and with TCP only, without any difference.
- We never had this behavior with our previous FortiGate VPN, using the same remote PCs and the same internal network.
What we tried since:
- We worked with Microsoft support for more than 3 months, without finding a root cause or a fix.
- Adjusting the state timeouts on our firewall (pfSense), where the connectors’ outbound traffic goes through, did help, but disconnections still occur.
This makes us think the issue is related to how long-lived TCP sessions are handled between the connectors and the GSA service (idle timeouts, keepalives or tunnel renewal).
Has anyone found a root cause or a fix? Specifically:
- What keepalive interval do the Private Access connectors use for their tunnels to the service, and is it configurable?
- Are there recommended firewall state/idle timeout values for the connectors’ outbound traffic?
- Could the GSA client token refresh cycle (access token renewal or Conditional Access re-evaluation) cause a brief interruption of existing sessions?
- Has anyone else seen RDP stability issues through Private Access and solved them?
Any feedback would be greatly appreciated. Thanks