Secure Gateway 2.0 problem

[Coty]

Folks:

After installing Secure Gateway 2.0 (service on one machine, STA on second machine, Web interface version 2.1 on third). I can connect to the Gateway machine on 443 (IIS is disabled on this machine so no 443 conflicts) and it gives me the web interface just fine. I can then login and it shows the published apps...but when you click on one it tries to connect to the farm using 1494 instead of going over SSL? Note the CSG diagnostics say everything is peachy? What am I missing here? Is there some modification I need to do to the web interface? It looks like in version 1.1 you modified the nfuse extensions or something but I can find no info for 2.0? Also note I currently (for testing) have no firewall between the gateway server and the web interface and STA...

Thanks!

Coty

 

[rayzze]

In the administrator web site (

http://yourserver/wiadmin)you

need to tell the web interface to use the Secure Gateway Server by going into server side firewall and telling it to use the Secure Gateway for address translation and then towards the bottom giving it a fully qualified path to the gateway box and STA.

Hope that helps,

Ray

 

[Coty]

Ray:

Thanks for the post...I thought that would be it but it still isn't working <sigh> I go to wiadmin and add change the default address translation to Secure Gateway, then go to Secure Gateway for MetaFrame section and add the FQDN and port for the gateway and below that add the STA info.

What is the &quot;Use alternate address of MetaFrame server&quot; for? Also...do I need to do anything in the MetaFrame server address translation section?? I wish I could find some documentation on this <sigh>

Thanks again!

Coty

 

[Coty]

OK...never mind...I wasn't checking the &quot;Apply Changes&quot; link <rolls eyes>

Thanks
Coty

 

[rayzze]

A couple of things to consider here. Make sure your Web interface can resolve the fully qualified name of the Citrix Secure Gateway and the STA by ping or telneting to the open port (443/444)for CSG and 80 for STA. I use a hosts file to make sure I can resolve these names fully qualified. Then make sure that your Citrix Secure Gateway Server can reach the Citrix Servers internal on 1494 and port 80 you can test this with telnet also. Telneting to 1494 should give you returns of ICA ICA and 80 should just connect, if it doesn't your port isn't open. I have hardcoded the IP addresses into the Citrix Metaframe Servers tab in WIAdmin because my gateway is in the DMZ and cannot easily resolve names... If all of this communication works then you should be working. The &quot;Use alternate address of MetaFrame server&quot; is only if you did an altaddr on the internal metaframe servers.

Hope this helps.