[THIN] Re: Desktop sessions trying to connect to unpublished desktop
- From: "Gascoyne, Jo" <jo.gascoyne@xxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 20 Sep 2005 13:00:41 +0100
Bob - thanks for your reply. I don't think that the issues were caused
by a name resolution issue, and as far as I am aware there was not an
issue with our data collector.
We are running Metaframe XP - FR3.
We are still having this issue occassionally, with different servers
each time.
The problem seems to be that for whatever reason, a server with a
published desktop fails and the IMA service may hang. The server is the
unpublished from the CMC, but published desktop requests are still
getting load balanced to the server that has been unpublished.
A good start would be able to query the datastore - to see the state of
the server and maybe pinpoint why users are still trying to connect to
it - but I am not sure if this is possible.
Any help appreciated,
Thanks
Jo
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Robert K Coffman Jr - Info From Data Corporation
Sent: 26 August 2005 19:33
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Desktop sessions trying to connect to unpublished
desktop
Jo,
Are you sure this wasn't a master browser problem?
In our environment, we have our master browsers aliased in DNS to
something like mb1.domain.com, mb2.domain.com etc.
If we are doing maintenance on a browser, we'll redirect clients to a
browser merely by updating the alias. Recently I forgot to do this, and
when a server came up in a problematic state, clients were trying to
connect to it for published application resolution and getting messages
similar to the ones you posted below.
- Bob Coffman
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Gascoyne, Jo
Sent: Friday, August 26, 2005 11:03 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Desktop sessions trying to connect to
unpublished desktop
We have a citrix farm, with a published desktop. We have approx.
70 servers that desktop is published from. At the weekend, we
unpublished all but 5 servers, so that maintenence could be carried out
on the rest of the farm.
Later we started to find that people were having issues
connecting to the published desktop. People were either
"There is no Citrix Server configured on the specified address"
"The citrix server you have selected is not accepting
connections"
or
the connection hung at the connecting screen.
The issue was that as the clients were connecting, they were
connecting to the Master Browser normally, but were then some
connections (but not all) were being allocated to the server that wasn't
published, and was in an unusable state(server wouldn't accept RDP or
ICA connections). Rebooting the server resolved the issue, and
connections were then handled normally.
I would like to understand why we had this issue, and would
appreciate ideas on the best route of investigation.
Jo Gascoyne
Other related posts:
