Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RDP sessions disconnected after server rejoins nlb cluster

92 views
Skip to first unread message

AndiK

unread,
Jun 9, 2008, 6:31:01 AM6/9/08
to
Each time a node joins (after reboot or new node) our nlb cluster, some
(about 10 or twenty out of 200-300 in total) active rdp sessions to other
cluster members are disconnected.

The nlb cluster consists of 8 servers serving 300 rdp clients, most of them
wyse thin clients. Balanced traffic is only TCP 3389. All servers are Windows
Server 2003 Entrise Edition with SP2. Session redirection is achieved via
windows session directory.

Did anyone else notice this effect or is there a known solution?

Best regards

Andi


Munindra Das [MSFT]

unread,
Jun 12, 2008, 12:46:32 PM6/12/08
to
Can you check if there is any error recorded in the event log on the client
that got disconnect and/or the server from which session was disconnected?
In the mean time I will try to investigate if I can find the cause for it
and will reply back if I find anything.

You can also try posting this to one of the Clusterning/NLB newsgroup since
this seems to be related to NLB registering the new node with DNS -
microsoft.public.windows.server.clustering,
microsoft.public.windows.server.dns.

Thanks!

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"AndiK" <An...@discussions.microsoft.com> wrote in message
news:8332F60E-14D9-4935...@microsoft.com...

AndiK

unread,
Jun 13, 2008, 6:51:00 AM6/13/08
to
There are no related log entries on the servers as far as i remember. Nearly
all clients are Wyse ThinOS based Thin Clients, and i missed to check the log
of one of these machines last time.
I will try to reproduce the error to check again for log entries on both
sides. Thank you for the hint with the clustering newsgroup. I will do this
immediately.
Best regards

Andi

AndiK

unread,
Jun 19, 2008, 7:20:01 AM6/19/08
to
I have check the logs on our clients (Wyse Thin OS based) and on the affected
servers after the last incedent (server 12 rejoins cluster, rdp sessions on
server 11 and others are lost), no relevant information to find.

bertusmatthee

unread,
Oct 24, 2008, 5:19:05 AM10/24/08
to
We are experiencing the same issue. We have a Wyse thin OS install base connecting to Windows2003Enterprise SP2 Terminal Servers in a NLB cluster with Session Directory. When the problem occurs the users are also unable to log off from their session , because they autoatically get re-logged on their session when they try to log off.
The other symptom is that their session intermittently and they need to switch off the wyse term and reconnect to the existing session.

Ramasamy Pullappan [MSFT]

unread,
Oct 29, 2008, 4:08:06 PM10/29/08
to
Not sure if I understand your scenario right. Your mail seems to be a
continuation of a previous conversation but I have no context.

If the problem is that logging off results in automatic logging back in,
then it might be because of ForceAutoLogon being set. Check for the
autologon related keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon

Ram.

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

"Bertus Matthee" wrote in message
news:20081024519...@vodamail.co.za...

James M

unread,
Sep 15, 2010, 12:28:24 PM9/15/10
to
Andi, did you find the cause of this issue?
We have been experiencing it for some time and are now afraid to join nodes during business hours.

THanks!!


>> On Thursday, June 12, 2008 12:46 PM Munindra Das [MSFT] wrote:

>> Can you check if there is any error recorded in the event log on the client
>> that got disconnect and/or the server from which session was disconnected?
>> In the mean time I will try to investigate if I can find the cause for it
>> and will reply back if I find anything.
>>
>> You can also try posting this to one of the Clusterning/NLB newsgroup since
>> this seems to be related to NLB registering the new node with DNS -
>> microsoft.public.windows.server.clustering,
>> microsoft.public.windows.server.dns.
>>
>> Thanks!
>>

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

>> "AndiK" <An...@discussions.microsoft.com> wrote in message
>> news:8332F60E-14D9-4935...@microsoft.com...


>>> On Friday, June 13, 2008 6:51 AM Andi wrote:

>>> There are no related log entries on the servers as far as i remember. Nearly
>>> all clients are Wyse ThinOS based Thin Clients, and i missed to check the log
>>> of one of these machines last time.
>>> I will try to reproduce the error to check again for log entries on both
>>> sides. Thank you for the hint with the clustering newsgroup. I will do this
>>> immediately.
>>> Best regards
>>>
>>> Andi
>>>
>>> "Munindra Das [MSFT]" wrote:


>>>> On Thursday, June 19, 2008 7:20 AM Andi wrote:

>>>> I have check the logs on our clients (Wyse Thin OS based) and on the affected
>>>> servers after the last incedent (server 12 rejoins cluster, rdp sessions on
>>>> server 11 and others are lost), no relevant information to find.
>>>>
>>>> "AndiK" wrote:


>>>>> On Friday, October 24, 2008 5:19 AM Bertus Matthee wrote:

>>>>> We are experiencing the same issue. We have a Wyse thin OS install base connecting to Windows2003Enterprise SP2 Terminal Servers in a NLB cluster with Session Directory. When the problem occurs the users are also unable to log off from their session , because they autoatically get re-logged on their session when they try to log off.
>>>>>
>>>>> The other symptom is that their session intermittently and they need to switch off the wyse term and reconnect to the existing session.


>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>> ComponentOne Studio for ASP.NET AJAX - Free License Giveaway
>>>>> http://www.eggheadcafe.com/tutorials/aspnet/ce98ce1f-2b5d-4ec8-b6d5-a1049651514e/componentone-studio-for-aspnet-ajax--free-license-giveaway.aspx

0 new messages