Can access apps in 2X Client window, but not from Web Portal

Hi all, I need some help. I have 2X ApplicationServer newest version installed on a clean install of Server 2003 Enterprise, Terminal Services installed, and have the Web Portal installed as well. in IIS the "default website" is Stopped, and the 2X web site is running on port 81. in the ApplicationServer console under Gateway, it is running on port 80, and I created a new SSL cert under the SSL tab, port 443.

On my firewall, I have port 443 and 80 forwarded to my ApplicationServer.

On the Internet, I can log into the Web Portal, install the 2X client, see the published apps, but when I go to launch them, the 2X client pops up with "connecting, please wait..." and about 10 second later I get a popup error "The client could not establish a connection to the remote computer". I have tried everything i can come up with in the Web Portal Farm settings page: My public IP of my firewall, the hostname of the server, and the IP of the server, and every combination of SSL, regular, gateway, and direct mode, to no avail.

The thing that gets me is, if I double-click on the 2X system tray icon, it shows all my published applications as well, and if i launch one from there, ut launches the apps just fine! I have tried this on multiple computers with the same results.

 

Kindly make sure that in web-portal-->Farm Settings-->advanced Settings you override 2x client gateway as shown in the attached screen shot.

 

I verified it is set up as your screen shot indicates, and I am still getting the same results. I did yet another complete clean install, with the same results: I can connect to any published application when launched directly from the installed 2X Client, but from the web page, it will not launch.

 

FIXED!

If anyone else is having this problem, I hope they find this info useful. The problem turned out to be internal name resolution. When I set the farm name to the fully qualified name (server.domain.com), the actual local 2X server did not have proper resolution for that FQDN. I added a static entry in the c:\windows\system32\drivers\etc\hosts file to resolve this full name, then everything started working.

The reason others probably do not come up against this very often is, I was running this in my DMZ, where I do not have an actual DNS server with forward lookup zones. If this is running in your LAN, and talking to your AD and DNS, then more than likely that FQDN is already resolved accurately.

Hope this helps someone else along the way.

 

for someone first time read this post, Make sure you login as administrator, otherwise you not see the top setting
From the 2xa file that is downloaded after you click on an icon has NT in the Primary server part of the file. Please do the following:

Log on the Web Portal as the Administrator.
Click on the Farms hyperlink to access the Farm settings.
Selet the Farm to edit.
In the Advance Client Settings make sure you check the Overrided Client settings for the following:
Primay Connect should be the external ip address for the client gateway.
Mode should be the same as you have it setup on the Application server (gateway, direct or ssl).
Port Number should be what you have it setup on the Application server to be.

This should correct the issue.