WildCard Certs and 3040 thin clients

Tagged: ,

Viewing 13 posts - 16 through 28 (of 28 total)
  • Author
    Posts
  • #53418
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    #53419
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    #53420
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    #53423
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Last result….
    – I created cacerts folder under wnos and include our cacrt.crt.
    – after use my domain credential it seems “login locally to wyse”. The “start” button text replaced with my name… and popup an RD Gateway Credentials login window.
    – I try to use my domain credentials again, but nothing…
    – a connection icon shown on the destop, but I can’t understand where this connection parameters come from.

    I’m totally confused…. i just try to centrally set up all our clients and use a simple remote desktop connection to our windows terminal servers…

     

    #53425
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Why is your RD Web Access role shown as “Not configured”?
    What do you see when you log in from a browser?

    CG

    #53426
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    And make sure that the two certificates GlobalSign and AlphaSSL are installed on the clients.
    No other certificate is needed.

    CG

    #53430
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    In cacert.crt there is both cert included.

    Basically i think I’m on wrong way…If I go back to the start and reset the clients and start configure with classic RDP protocol, than I’ve just one problem…

    I’m confused whats the point to configure Broker type to Microsoft or set it to None and configure an RDP protocol connection? What is the difference?
    So what if I set az RDP connection, with connecting to address of our broker address?

    I tried this and connecting. But when I hit the password and shown the login screen on windows server, I get wrong password error. I check many times and I type the password well. If I type the password again on the windows login screen then its ok, I logged in.
    So there is a problem when I gave my credentials on RDP Credentials window…the password somehow is passed wrong…
    I’m not sure if you understand what I mean…

    thnx

    #53458
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    With RDP you can go both routes.
    A direct RDP connection is typically used when the user or admin just needs one connection to a dedicated server.
    A broker connection is used when multiple RDSH apps and desktops are needed.

    CG

    #53475
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    We not use any RDHS apps. Users connect to terminal server via remote desktop (mstsc) and RDP (connection protocoll RDP under remote connection node on Wyse clients).

    i’m try again…i’ll keep infrom u…

    #53534
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Sorry for my late reply…I would like to ask one more thing, maybe you have an idea…

    1.

    – i use the session collection name as connection name for example:server.mycompany.local
    –  i save the user name but non the passowrd

    When i click on the connection icon the windows logon window automatically loaded (as expected) and the user name filled out..i just need to type the password and done.

    2. i try to use the connection broker address as connection name
    server.mycompany.hu
    –  i save the user name but non the passowrd

    When i click on the connection icon i get a wyse logon window prompt with user name filled in. I type the good password (if i type wrong password, then get message the password is wrong..) and try to login. The windows logon window loaded but get password error from window server. I type the password again on the windows logon window and done, its ok.

    Any idea why is different the logon process in this two case? Why my password pass from client to windows (accepted the password) but Windows Server not accept it?

    Thanks

     

     

    #53556
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    No, sorry. No idea.

    CG

    #53571
    holian
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Hello,

    Thank you anyway. I ‘ll will be inform you (if you interest). I just try to google and fix if we can…
    I really appreciate your answers and this forum.

    Regards

    #53587
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Yes, please

    CG

Viewing 13 posts - 16 through 28 (of 28 total)
  • You must be logged in to reply to this topic.