I have capured the Launch.ica file. Do you have any difficultly going to other HTTPS sites through the proxy? In the end pay close attention to what address the SSL certificate is issued to. Make sure all servers can resolve each other and if your NATing that appropriate altaddr's and host/DNS are setup properly.Jeff 1336-51395-223526 Back to top S Whorrall Members #3 S Whorrall 10 check over here
If you configure XML Service via XenApp for example port 8080 it should show up in the CtxHttp folder. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. Thank you for the reply. I have changed a file called icafile.xslt to contain the ProxyType=Auto line, on the MSAM server - But it still does not show up in the Launch.ica files I capture.
I am getting error saying "The Citrix SSL Relay name could not be resolved (SSL error 40)". Upgraded client to fix feature parity issues with new version of XenApp and now clients behind a proxy farm will no longer connect. Jeff 1336-51395-223734 Back to top S Whorrall Members #5 S Whorrall 10 posts Posted 26 May 2004 - 02:47 PM Thanks for the input again Jeff.Checked - all internal servers are Until then, I am trying to be my own CA and issue a cert for my SG FQDN 0 LVL 1 Overall: Level 1 Message Author Comment by:Quadeeb20032006-07-05 I will
Covered by US Patent. I have the following setting currently under manage secure client access and am changing them around to see if anything works. create an "A Record" so that secure.billsmoonko.com = 70.169.x.x (assuming this is your external ip address and this address is NAT'd on your firewall to the internal IP Address of your Citrix Receiver Linux Command Line The Citrix SSL Relay name could not be resolved (SSL error 40) Started by S Whorrall , 25 May 2004 - 06:42 PM Login to Reply 12 replies to this topic
Currently, I uninstalled my digicert and am trying to make my own. That is why I was getting the errors. Today, we did some testing in a few other PCs and got "SSL Error 61: You have not chosen to trust "Root CA", the issuer of the server's security certificate(Screenshot attached). http://discussions.citrix.com/topic/51395-the-citrix-ssl-relay-name-could-not-be-resolved-ssl-error-40/ Regards Karthik 1331-340063-1780826 Back to top Report abuse Back to Secure Gateway 3.x Reply to quoted posts Clear Citrix ©1999-2016 Citrix Systems, Inc.
Citrix SSL Relay Name Could not be resolved(SSL Error 40) Started by Sathya T , 09 April 2010 - 04:22 AM Login to Reply 9 replies to this topic Sathya T Citrix Receiver Linux Window Mode Resolution Create a DNS record that resolves the FQDN of the Secure Gateway server or create an entry in the host file on the client devices. The time now is 05:13 AM. Several functions may not work.
In that case, you will need to buy 2 separate certificates, use 2 separate external IP addresses, and have different FQDNs specified in the DMZ settings on each WI server. 1331-281804-1531086 I have been lucky enough to work with a number of talented people though... Citrix Ssl Error 40 Fix Several functions may not work. Citrix Receiver Linux Certificate Error Users access the CSG WI using the name server.FQDN address.However I've now been asked to allow external users access via the internet.
TcpPort will specify on what port the XML services are running. check my blog Adv Reply February 12th, 2012 #4 latinlightning View Profile View Forum Posts Private Message Just Give Me the Beans! On the MSAM site I have the Website Viewer installed. We do not have a wildcard certificate. Citrix Receiver Linux You Have Not Chosen To Trust
I don't know MSAM but if it's like WI, then you need to make sure that it is setup properly with the correct CSG FQDN. A 1331-348363-1799248 Back to top KEN ZYGMUNT Members #2 KEN ZYGMUNT 1,544 posts Posted 20 February 2014 - 08:23 PM Hi Alex, More and more proxy servers nowadays But the same problem continues. this content Attached Files DMZ FQDN.png 30.25K 495 downloads 1331-281804-1530775 Helpful Answer Back to top John Rehill Members #3 John Rehill 13 posts Posted 08 February 2011 - 11:26 PM I've marked the
The SSL Relay name could not be resolved (SSL Error 40) Started by Karthikeyan Mohan , 10 November 2013 - 09:35 PM Login to Reply 8 replies to this topic Best Reason A DNS record was not made to resolve the FQDN name of the gateway — or — The FQDN of the Secure Gateway server entered in Web Interface/NFuseAdmin/server-side firewall/Secure Gateway So a quick rundown on our configuration.CSG Version: 3.1WI Version: 5.1.1Users access the WI page by going to "https://insight.domain.com.auCSG is running on "servername.domain.com.au"Both WI and CSG have correct SSL certificates installed Citrix Receiver Linux Mint Contact your help desk with the following information: Cannot connect to the Citrix XenApp Server.SSL Error 59: The server sent a security certificate identifying "
local direct connection - no problem, only CG. 0 LVL 1 Overall: Level 1 Citrix 1 Message Expert Comment by:oneyp2006-06-30 I've also seen personal firewalls cause the same problem. The FQDN of my SG server and the Common Name for the server certificate are different. If anyone has an idea I'd appreciate it. have a peek at these guys A wildcard certificate?What is the common name of the certificate? *.company.com ? 1331-340063-1777682 Helpful Answer Back to top Karthikeyan Mohan Members #3 Karthikeyan Mohan 7 posts Posted 11 November 2013 -
Another potential pitfall occurs when the user is not using their default browser. Several functions may not work. thanks for pointing me in the right direction. When attempting to connect to our servers via WI/CSG anyone with the latest client receives "The Citrix SSL Relay Name Could not be Resolved (SSL Error 40)"I've gone through a lot
I'm on Ubuntu 11.04 and running Firefox 10.0. Contact your help desk with the following information: You have not chosen to trust the "AddTrust External CA Root" the issuer of the server's security certificate (SSL error 61). After checking the certificates in FF that particular CA (AddTrust) IS in there so I'm out of ideas here . . . . I am not sure what error I was getting probably SSL Error 40.Check if the Citrix XML is running or not in the services.