abakkook

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: T50 Won’t connect to cluster after newest firmware #23838
    abakkook
    Member
    • Total Post: 3
    • Newbie

    Hello jmcp,

    Thank you so much for your post. I have been watching the firmware and hoping they will update it, but nothing. Its like they have stopped working on these devices. I believe in the future I am going to go with a different OS. I’ve heard the WyseOS has no problems with this. Thank you so much for the older firmware post! I had been looking for that everywhere. Once I get a few minutes I will try and restore these terminals back to the older version and I will report back if it worked for me. Thanks.

    in reply to: T50 Won’t connect to cluster after newest firmware #23202
    abakkook
    Member
    • Total Post: 3
    • Newbie

    Hi guys,

    I want to apologize that I never responded after your posts. Thank you for continuing to keep us updated. I was able to get the 1.018 version to work with our cluster. Although, now I can’t remember what I did. I believe I followed deej instructions and just made a change on our terminal servers and then it worked and then forgot to reply. It was a crazy time.

    However, we are still having issues with these T50s. I am with allroy1975. I am about to just throw in the towel. Although it looks like you may have got something working. Here are the issues we have at this moment:

    1. T50s will connect to the cluster. However, after you login it will often kick you back to the home screen again. So you login again. It will do this from 2 – 8 times before it actually connect to the terminal servers and loads your desktop. I am not sure why it is doing this, but I see others having similar problems. We are running DNS round robin with a session broker. Allroy1975 were you able to overcome this problem with your copying of the older firmware RDPclient?

    2. Newer Wyse T50s that I bought more recently have problems locking up in the session. Randomly the session just stops allowing for the mouse to work. The keyboard still works. We are currently trying different usb mouse instead of the ps/2 mouse through the keyboard to see if that works. I’m not holding my breath. Looking at some other forum posts it looks like many have been having this issue and were even wondering if it is a bad batch of T50s or something.

    You are right. Page 16 of the specs shows that it should work with the Session Broker.

    Any help I can get would be greatly appreciated! Thanks and I hope each of you got these figured out too.

    Thanks

    in reply to: T50 Won’t connect to cluster after newest firmware #22293
    abakkook
    Member
    • Total Post: 3
    • Newbie

    Hi Allroy1975,

    I believe that we are experiencing the same issue you described here since we upgraded our firmware on our T50 to the 20120203-0_U-1.018 version. I have one T50 that is still on the old firmware and it seems to be working just fine. However, this newly upgraded one wont connect to the terminal server farm. We also have a windows 2008 terminal server farm with a session broker and load balancing enabled. It seems that I can connect directly to the terminal server with the session broker on it, but any others it lets me log in and then it says welcome and then it goes back to the home screen of the T50. Its driving me nuts. Did you ever figure out what was causing this? Did you get any leads? Thanks in advance for any help.

    Isaac

Viewing 3 posts - 1 through 3 (of 3 total)