Wyse S10 Upgraded firmware wont connect

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #2001
    Avataryitty
    Member
    • Total Post: 1
    • Newbie

    My company has always used the 6.2.0_8. We recently received thin clients with the the 6.3.0_12 firmware and our ica configuration off our ftp wont work. The thin client tries to connect to the windows desktop but it keeps looping and restarting the count down. What is it about this firmware upgrade that screws up our configuration?

    #15439
    ConfGenConfGen
    Keymaster
    • Total Post: 11109
    • Jedi Master
    • ★★★★★★★

    Never heard about that.
    What is your configuration?

    CG

    #15445
    AvatarStretch
    Member
    • Total Post: 8
    • Newbie

    I have 3 new S10’s w/ the 6.3.0_12 image that will not connect to a Win2003 SP2 terminal server. It flashes and then comes back to the connect manager.

    Only thing I can see is this newer image has RDP 6.0 on it. All the older images have 5.2.

    I can connect to the same terminal server using a RDP 6.0 client on a XP and Vista machine w/ no issues.

    Could it possibly have something to do w/ the server authentication “feature” in RDP 6.0 (http://support.microsoft.com/kb/925876)

    I don’t see anywhere to select the method…maybe this is where it’s failing?

    **Edit**

    I CAN connect to Windows Server 2008 w/o issue….only 2003 will not let me connect.

    #15446
    ConfGenConfGen
    Keymaster
    • Total Post: 11109
    • Jedi Master
    • ★★★★★★★

    I have no problems connecting to my W2k3 server.
    From what you are describing it looks like you have an issues with TSCALs.
    Try adding this line to your wnos.ini and retry after a reboot:

    FixLicense=clean

    CG

    #15712
    AvatarStretch
    Member
    • Total Post: 8
    • Newbie

    They acknowledged there is an issue w/ the 6.3.0_12 image regarding the TS license. They told me to add this to my WNOS.ini:

    clearlicense=yes

    Think you need to be careful with this because if you leave it in there, the terminal will ask for a new RDP/TS license every reboot–thus leaving you with a bunch of licenses tied up for the 90 days it takes M$ to release them.

    This works for me, I just reboot the terminal with that line in, then take it out right after I see the Windows logon screen.

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