Re: RDP sessions disconnected after server rejoins nlb cluster

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.

"An***" 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:

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.
"An***" <An***@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8332F60E-14D9-4935-A88B-4B4CD0FB4E7E@xxxxxxxxxxxxxxxx
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




.