October 3, 2023

[SOLVED] SSL: unable to setup connection (ERR=-5902)

Home Forum WTOS/ThinOS [SOLVED] SSL: unable to setup connection (ERR=-5902)

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #6904
    Wyse_Egor
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    Good afternoon everyone.

    I’m having issues connecting to a specific server using c10le with OS 7.0.113 (s10 with older WTOS work just fine). The error message I receive is “SSL: unable to setup connection (ERR=-5902)” it’s 100% reproduce-able (i.e. happens all the time).

    Here’s what I tried already:
    1) Saved SSL certificate as base64 *.cer from windows RDP client and imported it to c10le via ini file (successful import confirmed via event log).
    2) Downloaded root CA of Entrust and imported it to c10le (also successfully)
    3) Confirmed date/time settings on the terminal (accurate for EDT)

    And I’m still getting this error. Since the server is publicly accessible, could someone with c10le/7.0.113 please try to connect – xxxxxxx.com.

    Any suggestions are greatly appreciated, thanks.

    #21249
    ConfGen
    Keymaster
    • Total Post: 10695
    • Jedi Master
    • ★★★★★★★

    Remove the cer certificate, rename it to crt and import again.
    Local time on the client is correct?

    CG

    #21253
    Wyse_Egor
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    Thank you for your reply. The local time is accurate.

    I tried renaming files to *.crt, updating ini to reflect new file extension, then performed g-key reset to wipe saved certificates and confirmed via event log that both certificates (crts) were installed successfully. Still no luck, same error message.

    Perhaps there is a way to ignore SSL and make client behave like version 6 (which works flawlessly with this server)?

    I will also try to request crt from the server admins (as opposed to using the one saved from Windows Xp RDP client).

    #21297
    Wyse_Egor
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    The solution is:

    SessionConfig=RDP EnableNLA=no
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.