Troubleshooting Reconnecting to Disconnected Sessions

A common topic of discussion on the user forums is having the ability (or not having the ability) to reconnect to disconnected sessions.

A common topic of discussion on the user forums is having the ability (or not having the ability) to reconnect to disconnected sessions.  In addition to searching Citrix’s site for known issues and hotfixes, there are a few items to consider in the troubleshooting process.  This article offers a few simple suggestions to accelerate that process. 

Were users able to reconnect to disconnected sessions before?

If Yes:

The zone data collector (ZDC) is responsible for keeping track of which users have disconnected sessions on which servers. If your users were able to reconnect to disconnected sessions before, there could be a problem with your ZDC.  To confirm that a disconnected session exists for a specific user, either check the Citrix Management Console (CMC) for disconnected sessions or run the queryds command-line tool.  

The queryds tool is a free tool from Citrix that lets you view the contents of a ZDC’s dynamic store—an in-memory set of tables where the ZDC tracks dynamic information. QueryDS can be found on your Presentation Server CD in the \Support\debug directory or it can be downloaded from as part of the CTXDataXP utility.  Copy QueryDS.exe to one of your Presentation Servers and run the following command from a command prompt to determine if you have any disconnected session listed in the table: 

queryds /table:Disc_Sessions

If a disconnected session is not listed for the user in question then either (a) the entry wasn’t communicated properly to the ZDC or (b) the ZDC isn’t working right and didn’t properly write the entry to its dynamic store. In either case, you can try stopping and starting the IMA service on your ZDC and/or specifying another server to be the ZDC.

If No:

If your users have never been able to reconnect to disconnected sessions then you need to configure your environment to allow this capability.  There are two ways to do this--using Workspace Control or editing the ICA connection properties via the Citrix Connection Configuration (CCC) tool. 

Workspace Control

If you’re using Presentation Server 3 or newer, using Workspace Control is the most efficient method of reconnecting to disconnected sessions. It also provides centralized administration and more functionality than if you edited the CCC on each individual Citrix server.  With Workspace Control the user reconnects to a disconnected session and the reconnected session will take on the local settings of the active client device.  For example, if a user moves from one client device to another, the local printer settings will follow the user.  With Workspace Control the user also has the luxury of disconnecting and reconnecting to multiple sessions with one click.  

To use Workspace Control your clients must access their Citrix sessions through the Web Interface (WI) or the Program Neighborhood Agent (PNA).  To enable Workspace Control on the server side simply launch the Web Interface admin tool (either the admin web site or the Access Suite Console MMC snap-in, depending in which version of Web Interface you’re using). For details on configuring Workspace Control refer to your Presentation Server Administrator’s Guide.  

Citrix Connection Configuration

If using Workspace Control is not an option it is still possible to reconnect to disconnected sessions by editing the ICA connection in the Citrix Connection Configuration (CCC) utility.  This option, however, is limited and does not provide the full functionality of Workspace Control.  For example, local client device settings will not follow a user if they log in on a new client device and reconnect to a disconnected session.  The reconnected session in this scenario would have the printer settings of the original session.  Further, by editing the CCC to reconnect to disconnect sessions you cannot reconnect to all of your disconnected applications in one click.  You must launch each application individually to pick up the reconnected session. 

To edit the connection to allow reconnecting to disconnected sessions, launch the CCC and go into the advanced properties of the ica-tcp connection.  Uncheck “Inherit User Disconnection Timeout” and “No Disconnection Timeout” and assign a Disconnection Timeout value (for example 60 minutes).  Note that if a disconnected session times out from exceeding the value you set, naturally, you will not be able to reconnect as your original session will be terminated. Uncheck inherit user config to the right of, “On broken or timed-out connection” and select disconnect from the drop down menu.  Uncheck inherit user config to the right of, “Reconnect sessions disconnected” and select from any client or from this client only, whichever option you choose.

Join the conversation


Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

I am getting big problem here , I have an ICA file that connect to the Citrix server and open an application. But when i run the script created in LoadRunner it will not open up Multiple Remote session and it will just open one session and when it will try to open other session it kills the other session. would you pls tell me why is it happening .
Email me at :
Use different user accounts for the load runner sessions.  And quit cross posting in several different threads...that's really annoying.

What a very great article this is! Very, very impressive. I read it and it changed my way of working completely.
Keep on the good work and have fun in the BM company!
Your fans from Holland! (Marcel & Bjorn)
This is a dumb questions, but typically why do clients become disconnected?  Improper shut down, PNA issues, network issue?
I have small problem could you help me any one....
in 'citrix connection configuration'i am trying to edit the configure in 'Edit connection ' advanced connection settings i cannot enable the 'Disconnection Timeout settings(in minutes) showing disable.

This is likely to be caused by a GPO or registry tweak - Andrew Bonehill - Vistorm



hi there...

I am trying to create a session pool for all users

so i made them connect with the same user

and so i've got many disconnected sessions available for them, the problem is that instead of getting automatically a session they get the message

"You have already accessed remote desktop connections on this computer. Please select one of the following:"

and i don't need them to see it... how could i get rid of it ?

btw - i've noticed that after two minutes the ts chooses a session by itself so maybe there is a timeout configured somewhere.

thanks ahead =]