I have one Web Gateway server published to the internet with an external IP and publicly resolvable hostname apps2.external.domain. This server sits behind an ISA2004 server with NO packet inspection running. There are three TS servers with the 2x agent installed sitting behind it. I can connect to the gateway server and run published apps from the three TS servers from inside the network, but when connecting from an internet host, i can login to the web portal, see the published apps, but when i click to run them I get an error stating i cannot connect. I am trying to understand if this an issue with the external client trying to resolve the internal hostname or whether it is a firewall rule. If its a case of the external/internet client trying to resolve the internal hostname what can i do to fix this? What setting can I change so the web gateway will successfully pass the apps back to the internet client? I should note that from the internet client i have tried using direct, gateway and ssl modes all with the same results. I have reviewed all documentation and do not see where I am going wrong. Any help would be greatly appreciated.
It looks like I managed to get this worked out. I had to use the advanced settings and enter the external (public) fqdn name and choose gateway mode. I think some of it also had to do with the ports i chose to use initially to avoid conflicts.
I have the same problem, however after trying everything, I am still stuck. The part that is really making me scratch my head is, if I manually open up the 2X Client on the remote workstation (Across the internet) and display the published applications in there (rather than in a browser), I can launch them just fine. If I do it from the browser, they will not launch, and give me an error "The client could not establish a connection to the remote computer." I have blown out the installation and reinstalled using exactly what the install guide calls for, and still get the same results.