Skip to main content
Debbie_FTNT
Staff & Editor
Staff & Editor
Mar 15, 2021 6:32 AM UTC

Technical Tip: Interpreting WSAGetLastError() in FortiClient Debug log

  • Apr 16, 2026 11:50 AM UTC
  • 0 replies
  • 35099 views
  • Translate All
Description
This article describes how to interpret 'WSAGetLastError()' messages sometimes observed.

Solution
FortiClients can sometimes have connection issues with SSLVPN.

This sometimes includes error messages as follows:
Error    VPN    FortiSslvpn: 2148: error: poll_send_ssl -> WSAGetLastError():2745, try:1
Error    VPN    FortiSslvpn: 10908: error: poll_recv_ssl -> WSAGetLastError():2746
These errors are Windows Socket event errors, expressed in hexadeximal format.
WSAGetLastError():2745, for example, is the equivalent of error code 10053.

A list of error codes can be found here:
https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2

The above FortiClient error 2745 translates to decimal value 10053, meaning:

WSAECONNABORTED – Software caused connection abort.
An established connection was aborted by the software in the host computer, possibly due to a data transmission time-put or protocol error.

Notes:
Codes can be converted from hexadecimal to decimal values here:
https://www.rapidtables.com/convert/number/hex-to-decimal.html

Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024