[THIN] Re: Connecting to disconnected session
- From: "Scott R" <sreichardt@xxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Wed, 24 Dec 2003 12:10:00 -0600
MessageThat was for the WYSE 1200LE model?
Scott
----- Original Message -----
From: Foote, Eric
To: thin@xxxxxxxxxxxxx
Sent: Wednesday, December 24, 2003 11:14 AM
Subject: [THIN] Re: Connecting to disconnected session
Yes we had the same problem, I have a private fix from Wyse, don't know if
they have made it available on their general release yet.
My terminal rev is - 4.3.039i
Eric
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Scott
Sent: Wednesday, December 24, 2003 12:11 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Connecting to disconnected session
Does this never happen to anyone else or is this normal Citrix operation?
-----Original Message-----
From: Scott [mailto:sreichardt@xxxxxxx]
Sent: Monday, December 22, 2003 2:46 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: Connecting to disconnected session
Setup:
Using two MFXP FR3 on Win2k sp3 servers load balanced in one farm. Clients
connect with WYSE 1200LE winterms on internal LAN. Only the Desktop is
published. Disconnect timeout is set to 30 min, Idle timeout is set to 60 min.
On broken or timeout setting is set to disconnect. Users can reconnect from
any client.
Problem:
Why is it sometimes when a user hits their idle timeout and gets
disconnected, when they log in, they might happen to get that session back, but
they might get on the other server and not reconnect to the session. This
leaves their other session in a disconnected state. I've looked around the faq
and citrix kb and found some similar problems with the session getting
disconnected but staying in an active state, but my users sessions are in a
disconnected state which I thought they should be able to reconnect. It
doesn't matter how long they are disconnected either.
Thanks,
Scott
Other related posts:
