2X Client Gateway service will not start

  • Thread starter Thread starter basspro
  • Start date Start date
B

basspro

Am evaluating product. Loaded on W2K server, running TS (application mode) with Citrix Metaframe 1.8 already on server.

Went through all steps. Changed our IIS to port 81.
The 2X client gateway service will not start. Gives error "Could not start 2X Client gateway service on local computer. The service did not return an error..."

Any help greatly appreciated. Am being pushed to look at Citrix alternatives immediately.
 
Are you sure you managed to move the port of IIS from port 80 to port 81 ?

Do a "netstat -an" to verify if port 80 is still in use.
 
Have you tried to use another port for the 2X Client Gateway port? Try to use port 90 instead and re-check. (Perhaps port 80 is still in use)

If you do not manage to start the service, you should check that 2X client gateway service is installed properly. Open the Windows Services Console and check the status of the service. Make sure that "2XProxyGateway.exe" is in place. If not I would suggest to uninstall and reinstall everything.

When installing using Multiple Servers; one should not forget to choose the 2X Client Gateway if needed.

If you do not manage to start the 2X client gateway check the event log for more information.
 
Hi there,

Similar to the port conflict that may occur on port 80, you might have an other port conflict with the citrix port.

You need to change the citrix listening port, from the citrix console to say to port 5000.

Then from the 2X application server console, under the terminal servers, edit the terminal server that has citrix, make sure that the type is set to Citrix server or both, and in the ICA port set it to port 5000.

Nixu
 
Hey, thanks for all of the help.
The end result is that I changed the gateway port to 90 and the Citrix port to 5000 as suggested and the service started.

As info, I had tested whether port 80 was in use via netstat and Sysinternals tools. Port 80 was not in use. I had run IISRESET /stop, IISRESET/start several times. Nothing worked. I did not reboot the server because this is a production server and cannot be rebooted until Sunday.

Again, thanks for all of the help. Greatly appreciated.
 
You must log in or register to reply here.
Back
Top