The citrix ssl relay name could not be resolved (SSL error 40)

some more helpful info here:

http://support.citrix.com/forums/thread.jspa?messageID=375495&fromSearchPage=true&#375495

Thanks mgcIT for the prompt response really much appreciated, I will take a look ASAP.

Unfortunatly other things have taken a priority ! ... who'd of thought it !
Thanks
Nick

Yes it does match . . . I have tried disabling the virus/firewall software on the PC but no avail.

Version = 3.0.1

Computer NetBIOS Name: lalala
Configuration captured on: 23/03/2007 14:55:20
----------------------------------------------

Secure Gateway Global Settings
------------------------------
  Version = 3.0.1
  Product secured = MetaFrame Presentation Server only
  Logging level =  3 (All events including information)
  Client connection timeout =  100 seconds
  Maximum concurrent connections =  250
  Certificate FQDN = lalala.domain.local

Interfaces
----------

  All interfaces (0.0.0.0 : 444)
  ------------------------------
    Protocol = SSL, TLS
    Cipher suites = ALL
    Secured = Yes
    HTTP = No
    ICA = Yes
    SOCKS = Yes
    Gateway Client = No
    LoadBalancerIPs = None defined

Web Interface
-------------
  FQDN = localhost
  Port = 80
  Secured = No
  Protocol = SSL, TLS
  Cipher suites = ALL
  Access mode = Indirect
  Tested OK

Authority Servers
-----------------

  ID = STA96C8FA226374
  --------------------
    FQDN = blahblahblah.domain.local
    Port = 80
    Path = /Scripts/ctxsta.dll
    Type = STA
    Secured = No
    Protocol = SSL, TLS
    Cipher suites = ALL
    Tested OK

Certificate Check
-----------------
  FQDN = lalala.domain.local
  This certificate is currently valid.

EOF

>> All interfaces (0.0.0.0 : 444)


444 is not the default ssl port (it is 443) so have you tried accessing your site from the outside by also specifying the port?

for example

https://mydomain.citrix.com:444/


also, in the Access Suite Console, what do you have set as your default connection under Manage Secure Client Access > Edit DMZ Settings?

Yes, sorry I should of said.

I am aware of this, it is because we use a third party plugin for a one time passwords authentication which uses 443.  (securenvoy.com) and it can't share ports.

It is set to secure gateway direct.

I have tried connecting on 444 but i get a timeout as it is configured to listen on 443.

I really appreciate your help so far
Thanks
Nick

>> it is configured to listen on 443.

why would you have it configured to listen on 443 if securenvoy is using that and cannot share ports?

do you have port 444 open on your firewall pointing to your SG?

I'm no pro at this, i'm trying to give you detail but it was setup by a third party. Is there a way I can get the config off the servers for you to take a look at ?

I have three servers IIS/WI and CSG server - Securenvoy server and a STA server.

The firewall port forwards 443 requests to the iis / CSG / WI box which authenticates with the DC and the securenvoy box given a sta to allow resource on the presentation server.

The secure gateway port is set to 444.

Thanks again.
Nick

your setup seems fine but I think the problem you get is when you say "the firewall port forwards 443 requests to the iis / CSG / WI box"

If your CSG is configured to use port 444, you aren't doing any good by opening port 443 to it from the firewall.  In your firewall config open 444 to your CSG instead of 443 and see if you can access your site by specifying the port:

https://mydomain.citrix.com:444/

the csg is listening on port 443.
  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1045           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1046           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:14940        0.0.0.0:0              LISTENING
  TCP    172.16.10.30:139       0.0.0.0:0              LISTENING
  TCP    172.16.10.30:444       0.0.0.0:0              LISTENING
  TCP    172.16.10.30:1044      172.16.10.95:389       CLOSE_WAIT
  TCP    172.16.10.30:5900      172.16.1.12:4992       ESTABLISHED
  TCP    172.16.10.30:32188     172.16.10.95:389       CLOSE_WAIT
  TCP    172.16.10.30:32880     172.16.10.95:135       TIME_WAIT
  TCP    172.16.10.30:32881     172.16.10.95:1026      TIME_WAIT
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1025           *:*
  UDP    0.0.0.0:1026           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1027         *:*
  UDP    127.0.0.1:1034         *:*
  UDP    127.0.0.1:1049         *:*
  UDP    172.16.10.30:123       *:*
  UDP    172.16.10.30:137       *:*
  UDP    172.16.10.30:138       *:*

the secure gateway port is set to 444 for comms after the initial connection is made.

Ok, I fixed it.

The problem was the certificate, I changed ti to reflect the name of the website (not the name of the internal server) and although I got another error this was fixed by using an earlier version of the client.

Thanks for your help with this, I understand how frustrating it must be.
Cheers
Nick