WDM 5.7.2 and wnos.ini file

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #45009
    majishun
    Participant
    • Total Post: 4
    • Newbie

    Hi,

    I have WDM installed on a MS 2008 R2 Server.

    I have locally setup a working RDP connection on the WYSE 3040 terminal.

    When I create a wnos.ini to enable VNC connections and RDP connection to my TSPlus Server in the ftproot, then reboot the WYSE terminal, the VNC connections are working, but now I am getting a certificate error every time. “Failed to connect to the Connection Server. The server provided a certificate that is invalid.  – The certificate authority is invalid or incorrect. – The host name in the certificate is invalid or does not match”.

    I want to be able to use the wnos.ini file to setup a RDP connection to my Windows TSPlus Server.

    Please advise?

    #45013
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    MS RDSH server is using SSL by default. Therefore, you have to import the servers or CA certificate (depending on if it is a self-signed certificate by the server or a domain CA certificate) to the client.
    Copy the cert to the wnos\cacerts folder and add
    AddCertificate=name_of_cert.crt
    to your wnos.ini.

    CG

    #45020
    majishun
    Participant
    • Total Post: 4
    • Newbie

    Thanks Thomas, the self-signed certificate currently has the options of being exported as a .pfx or .pem or .cer format, does it need have a .crt extension? If so, is it just a case of just manually changing the extension to .crt?

    #45021
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Export as Cer und rename to crt or import as cer. Both will work.

    CG

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