This site includes topics specific to Healthcare but much applies to Information Technology in other industries. MAAADIT is a personal blog documenting problem/fix situations, IT solutions and system analysis encountered in a typical IT work day. Once the server reboots check that not all 4 Load Evaluator percentages are either at 100% or 0%. If not, it may be necessary to run the command prompt with elevated privileges. You should receive a Successful message after entering the command.
#Cannot connect to citrix xenapp server windows
To resolve corrupt performance counters on Windows Server 2008 running Citrix XenApp, it is necessary to do the following: Citrix Load Evaluator Memory/CPU Utilization at 100% Fix If All 4 of the Load Evaluator percentages are either 100% or 0% then you know that your performance counters are corrupt.
On the right column select the Load Manager Monitor tab. In the Citrix XenApp Advanced Configuration window, under the Server Farm, we expand the Servers tab and select the problem XenApp server on the left column. Rebooting the server will not resolve the issue.įrom the Server 2008 Start Menu > Citrix > Administration Tools, if we open the XenApp Advanced Configuration utility in XenApp 5, we can tell if the problem is due to Windows Server 2008 corrupt performance counters. The server may be unavailable or you may have entered the server name incorrectly.” Unable to locate the requested Citrix XenApp name. Users call the Helpdesk explaining that they cannot connect to Citrix Xenapp and the following message occurs: “Cannot connect to the Citrix XenApp server. a cert with something like " *." and use that on both interfaces, and users can connect to "" from the outside, and "vpn-inside," on the inside.Īlternatively, you can indeed just use 2 different certificates.įor #3, sorry I don't know of any detailed configuration guides for citrix over webvpn.A common problem I’ve experienced working on Citrix XenApp 5.0 running on Windows Server 2008 is corrupt performance counters. inside users resolve to the internal ip of the ASA, outside users resolve the same name to the outside ip of the ASA) then you can use the same cert on both interfaces.Īlternatively you can purchase a "wildcard" cert, i.e. So if you can have your DNS point the same name to different ip addresses depending on the location (i.e.
The name or ip address in the cert must match what the user connects to though.
For #1 : step d should not even be needed.Īs for the self-signed cert: if you don't create one explicitly, the ASA will create one for you, but it will create a new one every time the ASA reboots - so better create one manually.įor #2: the cert will typically contain the hostname (FQDN), not the IP address (although that is also possible).
0 kommentar(er)
