Mac: You have not chosen to trust 'DigiCert SHA2 Secure Server CA', the issuer of the servers security certificate. 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. Cannot connect to the Citrix XenApp server SSL Error 61: You have not chosen to trust 'DigiCert SHA2 Secure Server CA', the issuer of the servers security certificate. You can test this with either your own 798046 account or if they are on a different Citrix Farm like Office 2007 or H&R Block use one of the firms logins. So all I had to do was add an exception for the IP range of the XenApp servers in my wpad.dat/ global.pac files to go DIRECT rather than via proxy. 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. This also could be a problem on our end with a VO Citrix server not accepting inbound connections. ISA also expects the traffic in the original connection to be one that it understands (like HTTP) and if it does not know what the traffic is, the traffic is dropped which is the.
So if you can have your DNS point the same name to different ip addresses depending on the location (i.e. Citrix Receiver can sometimes display the following error: unable to connect to the server, SSL error 47 or SSL Error 47 / sslv3 alert handshake failure. If requests are redirected as SSL requests, the ISA server terminates the SSL connection and encrypts the packets again before passing them on to Access Gateway. SSL Error 61: You have not chosen to trust Certificate, the issuer of the server’s security certificate.
CANNOT CONNECT TO CITRIX XENAPP SERVER SSL ERROR 61 UPGRADE
After some thorough testing, I concluded that Citrix Receiver 4.7 was indeed the problem, and the fix is to either downgrade to 4.6 or upgrade Citrix Netscaler to the. SSL Error 61: You have not chosen to trust ‘Certificate Authority’, the issuer to the server’s security certificate. The name or ip address in the cert must match what the user connects to though. Contact your help desk with the following information: Cannot connect to the Citrix XenApp server. Found this article from Citrix that discusses a know bug with the new Citrix Receiver 4.7, but in our case this shouldn’t be the issue as we are using a VPX and not MPX or SDX. Cannot connect to the Citrix XenApp Server. Note that on the TMG server the TCP port 1494 (ICA) is allowed for the specified servers, in addition to HTTPS & ICA Session/Session reliability enabled protocols.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). Workspace app for Linux is available in English, German, Spanish, French, Japanese, Dutch, Portuguese (Brazil), Simplified Chinese, Russian and Italian. When entering the credentials it opens the ” Launching … “ window and it keeps hanging. Citrix Workspace on Linux enables users to access virtual desktops and hosted applications delivered by XenDesktop and XenApp from devices running the Linux operating system.
My choice was to integrate a Citrix Access Gateway (CAG) mainly because we are using other product. SSL Error 61: You have not chosen to trust Verisign Class 3 Secure Server CA G2, the issuer of the server’s security certificate. I was able to login in the CAG and the Web Interface as well, but not able to launch application. As you might know, Citrix has issued some virtual appliance and I had to chose between, Citrix Access Gateway 4.6.2 VPX and Netscaller VPX Express. Here is the error message I got when I wanted to launch published application (XenApp).
During the next stage, the Citrix receiver will send the STA ticket to NetScaler Gateway, and it will try to resolve the STA ticket. My company (Activlan) had to renew our certificate installed on our Citrix Secure Gateway 3.1.3. The current state is connected: There is an SSL connection from Client to NetScaler Gateway. SSL Error 4: the proxy denied access to 10 STA00237D35D7AA C2FC9547C8B26FB0E61F6B096D30B4B0 port 1494 So we successfully connected to Citrix NetScaler Gateway. After installing a new Microsoft TMG Server 2010 firewall, the XenApp Application couldn't connect, having the following errors.Įrror#1: SSL Error 4: the proxy denied access to 10 STA00237D35D7AA 213E518DB75AA083405B7BD0E3CC9814 port 1494Įrror#2: Unable to launch you ntact your helpdesk with the following information: Cannot connect to the Citrix XenApp server.
0 kommentar(er)
