anonymous1204
Technical User
We are running a Citrix farm (Metaframe xpe using web interface pn agent) with a pair of servers one of which is the domain controller on a windows 2003 platform.
These are load balancing.
Access to Citrix is through a firewall with users authenticating with client authn
A number of users are experiencing intermittent problems when running up applications.
i. A user will successfully log in and then when the go to launch an application it doesn’t execute and nothing happens. (The use is not shown as being logged on to the server). If you wait a couple of minutes it works!!!
ii. A user will log in and try to execute a processor hungry application once again this will time out.
a. The work around for this is to run up a less processor intensive application and then retry the original application.
The servers used are not showing a significant amount of cpu utilisation or memory useage.
I originally believed that the problem existed with the 2nd server and did some testing (removing server 2 from the properties of the published app) the problem appeared to go away but reappeared again.
I am reluctant to prioritise applications in case this causes further problems.
Has anyone experienced this sort of behaviour and if so what is the fix for it?
These are load balancing.
Access to Citrix is through a firewall with users authenticating with client authn
A number of users are experiencing intermittent problems when running up applications.
i. A user will successfully log in and then when the go to launch an application it doesn’t execute and nothing happens. (The use is not shown as being logged on to the server). If you wait a couple of minutes it works!!!
ii. A user will log in and try to execute a processor hungry application once again this will time out.
a. The work around for this is to run up a less processor intensive application and then retry the original application.
The servers used are not showing a significant amount of cpu utilisation or memory useage.
I originally believed that the problem existed with the 2nd server and did some testing (removing server 2 from the properties of the published app) the problem appeared to go away but reappeared again.
I am reluctant to prioritise applications in case this causes further problems.
Has anyone experienced this sort of behaviour and if so what is the fix for it?