Hello - I have the 2X Web Portal installed on a gateway server which is located behind a firewall. This gateway computer is configured to point to my 2X Terminal Server farm. I have opened port 80 in the firewall to allow traffic to the Web Portal gateway server. From a PC behind the firewall, I can access the Web Portal application and launch my applications. From the other side of the firewall (the outside world), I can navigate to the web portal site (http://xxxxxxx/2XWebPortal/logon.aspx) and get the logon screen. I can then log on and get the screen showing available applications (http://xxxxxx/2XWebPortal/AppList.aspx?folder=30) but when I attempt to launch an application I receive the message that "The Client could not access the remote application. Terminal Server might be too busy to accept new connections or you may be experiencing network problems." I'm wondering if this might not be a Windows Active Directory permissions issue? Or any other ideas would be welcome. Thank you, Gary Decker
Hi There, It seams that the client is getting the internal IP of the 2X App Server. From the Web settings, you can configure the public ip the client needs. 1) Farm settings -> Click on the farm Name -> Advanced settings 2) Check Override 2X Client Gateway IP/Host 3) Set the Public Primary Hostname / IP Nixu
Followup So...It's been awhile since I visited this problem. I never did get it to work but, at the time, had bigger fish to fry. I'm revisiting it again at the request of several users who would like to have off-campus access to some of our applications. I have now set up the Web Access interface on the same server that is serving out my applications and I have updated to 2x Access Portal v6.2. Other than that, my situation is the same. I have changed the 'Advanced Settings' in the 'Farm Settings' to 'Override 2X Client Gateway IP/Host' and set the Primary IP to 150.131.193.243 (external IP address of my server) and the Secondary IP to 10.8.99.13 (internal IP address of my server). Connection type is set to 'Direct Mode' and the Port is set to '80'. From a PC outside my firewall, I can get a listing of available applications in my browser but when I attempt to launch an application I receive the error mentioned in the 1st post. Just before this error appears, I can see the 2X Application Connector attempting to make the connection and, in the lower right-hand corner, I am seeing the correct IP of the 2X Application server being searched for. It appears to first search for the primary IP and then the secondary IP. I have assigned port 8080 to the Web Portal application and that port is opened in the firewall. From a PC within the firewall I am able to launch applications. Are there additional ports that should be opened? Or any other ideas? Thanks for any help. - Gary Decker
Re: Followup Hi gdecker, You would need to open the following ports: 1) Port 8080 with the iis server: required to view the Wep Portal. 2) Port 80 with the 2X Application Server: required to launch the published application. 3) Port 3389 with the Terminal Server: since you are connecting in direct mode. (If you set it to gateway mode you do not need this port as data will pass through port 80) Nixu
Web Portal Ok. That did it! I'm now able to access my applications thru the Web Portal. I've now enabled SSL on the 2X Client Gateway and generated a new certificate and I've opened port 443 on my firewall. But am not sure that SSL is being used by my remote client. On the remote client, when I'm presented with the "Welcome to the 2X ...." screen, the option for "Secure Login" is grayed out and I cannot check the box. I can go ahead and login at this point and then can select the "Connection Mode" in the "2X Access Portal" screen. But I'm concerned the initial login credentials are being sent unencrypted. Can you shed some light on this process for me? Thanks again. - Gary Decker
Web Portal vs 2X Client Now that I have the 2X Application Web Portal working, I've discovered that I can also access my 2X Application Server applications simply by launching the 2X ApplicationServer and LoadBalancer Client on the remote computer and configuring the Connection Settings by entering my Primary Connection (150.131.193.243), Secondary Connection (10.8.99.13), Connection Mode (SSL), Port (443), and the username and password. The connection refreshes, my available applications show up and I'm able to launch those applications. So my question is: what's the advantage of the Web Portal over the 2X AppServer Client Portal? Thanks, Gary Decker
