S10 disconnecting sessions

Viewing 15 posts - 31 through 45 (of 102 total)
1 2 3 4 5 6 7
  • Author
    Posts
  • December 19, 2008 at 10:13 am #14709
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    I am going to disable Session Reliability for now and see if that improves things any more.

    I will contact WYSE for the new firmware.

    December 19, 2008 at 3:15 pm #14711
    aLiE
    Participant
    • Total Post: 310
    • Jacked into The Matrix
    • ★★★★★★

    @ConfGen wrote:

    Wyse is going to release a new version of firmware tomorrow or early next week. It should be 6.2.026.
    Don’t know if it will help but worth a try.

    Ok ConfigGen, i have to say you really do have a lot inside info.

    December 22, 2008 at 11:48 am #14724
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    Just got 6.2.022 but that has not made a difference.

    Apparently 6.2.0.028 is still under development, and that the 6.2.0.24 is the next release but that is still unavailable for customer use.

    Does any one have any other suggestions, this is driving me and my users nuts.

    January 9, 2009 at 9:45 am #14823
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    Hi Guys,

    I am still having the issues, does any one have any more suggestions?

    January 9, 2009 at 10:12 am #14824
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    6.2.0_027 and 6.3.0_012 are released by Wyse.
    These are their major release version and you should with these ones.

    CG

    January 9, 2009 at 10:30 am #14828
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    I am chasing WYSE for the firmware but this is really getting my head scratching.

    Nothing on the Citrix Server Event logs indicate anything, I have disabled session reliability but the problems still occur.

    I never had any problems withe 1200LE, or the last batch of S10’s, it just seems to be these new batches…

    January 9, 2009 at 11:18 am #14829
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Can you clarify on “old batches” and “new batches”?
    Which firmware, which manufacturing date, where manufactured, ….

    CG

    January 9, 2009 at 11:29 am #14830
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    These are new batch details:

    Prod : SX0
    Part NO: 902110-02L
    Sub-Assy P/N: 849150-02L
    Manufacture Date: July 2008
    Made in China.

    Old Batch Details:

    Prod Id: SX0
    Part NO: 902110-02L
    Manufacture Date: January 2007
    Made in Mexico

    Firmware on Devices is: 6.2.0_22

    The chasis does look slightly different, but I suppose that is just a cosmetic thing…

    January 9, 2009 at 11:50 am #14831
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    So you are using the same firmware on both units and only the newer fail?

    CG

    January 9, 2009 at 11:54 am #14832
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    That is correct only the newer units seems to be affected.

    January 9, 2009 at 11:55 am #14834
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    That sounds like very valuable information for Wyse. Have you comunicated this?

    CG

    January 9, 2009 at 11:57 am #14835
    andyl
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    I have Version 6.3.0_12 if you want it …

    January 9, 2009 at 11:59 am #14836
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    Hi Andy,

    That would be great? Shall PM you my email?

    January 9, 2009 at 1:22 pm #14839
    andyl
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    Yep – that would be fine

    January 9, 2009 at 2:22 pm #14840
    hatrick
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    Thanks Andy, email in PM.

  • Author
    Posts
Viewing 15 posts - 31 through 45 (of 102 total)
1 2 3 4 5 6 7
  • You must be logged in to reply to this topic.