Reconnect to disconnected session

[Lolek]

We have a little Terminal-Server-Farm with 3 TS and 1 DC.
We are using load balancing for the 3 TS with a Session
Directory on DC. Our Problem is that users who lost her
session (by network errors etc.) don't reconnect to there
existing disconnected session. They always get a new
session on an other TS. I searched trough the knowledge
base but all hints about possible errors we could made in
our configuration were not the solution of this problem.

Can anyone help us? Thanks Thomas

 

[Ivan Leichtling [MSFT]]

What is the status (from qwinsta) of the sessions that are
disconnected by network errors? Active or Disconnected?

We have a little Terminal-Server-Farm with 3 TS and 1 DC.
We are using load balancing for the 3 TS with a Session
Directory on DC. Our Problem is that users who lost her
session (by network errors etc.) don't reconnect to there
existing disconnected session. They always get a new
session on an other TS. I searched trough the knowledge
base but all hints about possible errors we could made in
our configuration were not the solution of this problem.

Can anyone help us? Thanks Thomas

This posting is provided "AS IS" with no warranties, and confers no rights

 

[Lolek]

The sessions are displayed as disconnected.

-----Original Message-----
What is the status (from qwinsta) of the sessions that are
disconnected by network errors? Active or Disconnected?



This posting is provided "AS IS" with no warranties, and confers no rights
.

 

[Matthew Harris [MVP]]

Try running this script at logon...

terminal.servebeer.com/php/check_logon_and_connect.php

-M

 

[Lolek]

Where can I get this script?

-----Original Message-----
Try running this script at logon...

terminal.servebeer.com/php/check_logon_and_connect.php

-M

.

 

[lolek]

Thanks for your informations, but I couldn't solve my
problem.
On which position must I place the script? We use Active
Directory. I tried all posible places where logon scripts
can started during the login of a user. But it doesn't
work. Then I found a hint, that in the registry key
HKLM\Sofware\Microsoft\Windows
NT\CurrentVersion\WinLogon\AppSetup a value for a cmd-
file can be stored there, which must be saved in the
system32-directory. I created a file with your logon-
script an wrote them in the registry. But this did not
work, too!
It seems that the Session Directory Service first try to
connect the user to a terminal server before some logon-
scripts will be started.
Is the following the problem? Our users are only knowing
the virtual IP of the cluster. In the group policy I
defined that IP address redirection is activated.

 

[Matthew Harris [MVP]]

Well, the script only runs on the local machine, so it can
only connec the user to their session if both their
current and old sessions are on the same machine. If you
are running session directory, then you shouldn't have a
problem, since SD should automatically put the user onto
their original server. In this case, are you having the
problem there the old session isn't transitioning into the
disconnected state?

-M

 

[lolek]

No, the sessions are displayed as "Disconnected" in the
terminal services manager. If the user has the same
source-IP, the session will be found. If the user has a
new source-IP (a new dial in connection) and over the
virtual IP from the cluster they come to the same
terminal server, the session will also be found. But if
they come to an other server, the session will not be
found and the user gets an error (limited count of
sessions for the user (set to 1 per user)).

 

[Matthew Harris [MVP]]

This sounds like a problem with session directory
then...If session directory isn't connecting to the user
to their original server, then there isn't anything the
script is going to do for you. Are you positive that SD
is working correctly?

-M

 

[Huei Wang [MSFT]]

Any event on TS in farm? any event in Session Directory? if setup is
correct, you should see success event from TS/SD that a TS has join the
session directory.

--


This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Lolek]

the event logs seems to be Ok. All TS are joined the session directory with
the correct IP-Adresses.
My last change on the configuration was the correct setting of the used
Network-Card and IP-Adress in the Terminal-Session-Configuration on all
Terminal Servers. Now I'm testing the result of this.

Many thanks for further informations