Home > Citrix Error > Citrix Error 45

Citrix Error 45

When I setup Secure Access as Gateway Direct; it works outside (the ica file showing the cryptic information as we discussed earlier). It doesn't matter if it is turned off on CSG.. Protocol Driver error" Settings are: Outside IP Gateway Direct INSIDE IP of Firewall Gateway Direct Default Please re-enable javascript to access full functionality. Check This Out

How do I do this other than inside IE? Can I reuse the cert I already have; for the public name I want to use? Please visit our security site for additional security notices and information (support.citrix.com/securitybulletins ). I have the cert from GoDaddy and verified that GoDaddy is in the certs MMC. https://support.citrix.com/article/CTX132870

The primary cluster has an average load of 400 sessions per host and is growing still. Coralon 0 LVL 23 Overall: Level 23 Citrix 15 Windows Server 2008 14 Message Active today Expert Comment by:Coralon2012-03-15 Comment Utility Permalink(# a37726472) 3rd try to attach pic.. 0 This error message might come immediately after I have started the Desktop / App or it might takes quite long (maybe one hour or more)Same time when I get this "The I have configured another server as our CSG box to test and am forwarding all calls over to the XA 6.5 box.

Address=;40;STA;11D0E012B1F74F165A3E50A3255D0728 is what I get. Important! I got very frustrated with the whole thing so I removed everything Citrix and blew the server away and started over. We achieve RTOs (recovery time objectives) as low as 15 seconds. 30 Day Free Trial Join & Write a Comment Already a member?

too generic). Many thanks 1349-351204-1812014 Back to top Mike Plank Members #2 Mike Plank 24 posts Posted 07 May 2014 - 01:35 PM Resolved when we installed the Web Join and Comment By clicking you are agreeing to Experts Exchange's Terms of Use. http://discussions.citrix.com/topic/296518-ssl-library-error-45-the-cryptographic-security-of-the-ssl-connection-has-been-compromised/ You do have WI working without CSG.

Not exactly.. If the CSG sees incoming requests as being sourced from the firewall itself, then you need to set the ip address of the firewall as being Gateway Direct. Everything works fine. After investigating the CSG Eventlog, I found outthat the problem had returned on the 17th of May on one of my Web Interface hosts.I've contacted my supplier, and a Citrix call

Anybody have any idea? Get Additional Support Call Technical Support 1 800 424 8749 (US) 0800 587 9031 (GB) 0800 182 5549 (DE) 0120 941 133 (JA) View Additional Numbers Open a Case Open a Go through your CSG config and do not use any dns names.. How do I set WI to only listen to loopback?

The easiest thing to do is just try it :-) or just use Gateway Direct for everything :-) Let's say your internal network is 172.29.0.0 and your firewall is 172.29.0.5 his comment is here Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. NetScaler Citrix Advertise Here 695 members asked questions and received personalized solutions in the past 7 days. This information is provided “as is” and is not meant to be an official rendering of the SSL error code definitions.

This was on a WAN connection.I don't know exactly what the error message was on a Windows client, but on a MAC client the error was SSL error 4: A network Connect with top rated Experts 16 Experts available now in Live! And yes Citrix support did say that 3.1.5 is newer and more stable than the 3.2.1 version of SG. this contact form Get 1:1 Help Now Advertise Here Enjoyed your answer?

The issue seems to be that the CSG does not allow for authentication through to the domain. I did see an error on one of the machines I'm testing this on telling me "You have not chosen to trust StartCom certificate." So I grabbed the StartCom CA certs Any further guidance would be great. 0 LVL 23 Overall: Level 23 Citrix 15 Windows Server 2008 14 Message Active today Expert Comment by:Coralon2012-03-15 Comment Utility Permalink(# a37726456) Ok, you

I have tried importing it and adding it to IE and I still don't see it in my "Personal" section of IE.

If you are, then you can look at adding a second IP address to the server and binding CSG to that address only instead of *. Your cert must be trusted by the WI, the CSG and the client, or this will not work period. We rollled back to CSG 3.1.2 last night. Connection established to IP AND name Your WI should be able to connect to the CSG on 443.

I can telnet to the ICA port (1494) on both IP Addresses that the machine has on it. Did your users just notice this issue now? some of those are substantially vulnerable. navigate here I can also telnet to port 1494 from outside the network, without issues.

Basically, your internal network will be Direct, and your firewall based connections will be Gateway Direct. Here's how you can find out... I'll work on this today and let you know what I find out Configure the CSG as the proxy -- unbind SSL from WI Will do Configure CSG - WI is Does that help clear it up?

If you want to use the cert you already have, then the incoming request must be using the DNS entry for the common name of the cert. Do you get any SSL warnings at all? Started by Mike Plank , 06 May 2014 - 08:46 AM Login to Reply 1 reply to this topic Best Answer Mike Plank , 07 May 2014 - 01:35 PM Resolved I'm not a full 100% sure whetherthe issue started after the update or it was already present at the time of deployment with SG3.2.Perhaps a certain client plug-in version is initiating

Coralon 0 LVL 19 Overall: Level 19 Citrix 18 Windows Server 2008 6 Message Expert Comment by:basraj2012-03-08 Comment Utility Permalink(# a37696567) Read through these two links and setup in similar If CSG sees the inside address of the firewall; change WI to use direct as the default and the inside IP address of the firewall as the Gateway address ip?