- #CANNOT CONNECT TO CITRIX XENAPP SERVER INSTALL#
- #CANNOT CONNECT TO CITRIX XENAPP SERVER SOFTWARE#
- #CANNOT CONNECT TO CITRIX XENAPP SERVER LICENSE#
I have now several open issues with the 5.0 product (see this forum and also the Remote Admin forum) and our 3-year 410-system license ends 1-1-2014.
#CANNOT CONNECT TO CITRIX XENAPP SERVER SOFTWARE#
We buy software with support service exactly to handle situations like this and to know that our problems will be looked at by people with insight in the product and a test environment where they can try things. We don't have a complete testbed where we can experiment with software that is a blackbox to us, and we don't have the resources to do that. I think it is not a good way of supporting customers.
Never an answer to questions about the internal operation of the program or about workarounds for known problems. This goes on until the customer decides that it is no longer worth it to put all the effort in this process and risk the operation of the system by installing tooling from unknown origin on production systems.
#CANNOT CONNECT TO CITRIX XENAPP SERVER INSTALL#
It does not matter how much information is passed with a report (see my original post), the replies from ESET are always "try this, try that, install this, make that log" etc. I make my remark because I have found in the past that this is the standard way at ESET of handling problems that customers encounter. What is happening? Is ESET snooping on SSL traffic even when this is not enabled? Looking in the proxy log it appears that a CONNECT was done and serviced OK.Īfter reverting to ESET 4.2.76 this problem no longer occurs. SSL Error 4: Attempted to connect using the ( TLS V1.0 | SSL V3.0 ) protocols. Plugin starts OK and attempts to make connection, this fails with a popup:Ĭannot connect to the Citrix Xenapp Server.
ICA file is downloaded and will be run by the Citrix plugin locally installed on the system. Users can visit HTTPS pages OK, can visit the login page of a Citrix server and login, get the page with available applications, click on an application. ESET Endpoint Antivirus, almost default config, HTTPS scanning not enabled Proxy server for all internet connections Users of Citrix services that exist on external systems (on the internet) no longer can connect. 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.After installing the following issue occurs: 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)
