Hi everybody, I´ve got a situation here in a lab enviroment that need to be solved before go to production the soon as posible. I know that it´s nothing complicated but I still can´t get it work, so need your advise to detect what am doing wrong.

I succesfully configured Vworkspace with some apps on TS and VDI. I´m also able to use this apps and desktops trough the appPortal and the website on the local network so an axeption on the firewall was made to publish the webportal on the internet. After that, the portal is accesible by going to http://x.x.x.x(public ip)/provision/web-it/default.aspx

and I´m still able to connect to my apps and desktops but only on the local network. When I´m trying to connect since other place trough the webportal I´ve got this error:

Escritorio remoto no puede conecarse al equipo remoto por una de las siguientes razones:

1)No esta habilitado el acceso remoto al servidor

2)El equipo remoto esta apagado

3)El equipo remoto noesta disponible en la red

Asegurese de que el equipo remoto esta encendido y conectado a la red, el acceso remoto esta habilitado.

This is caused because the broker IP can´t be routing properly (as shown on thread 2282) So, on my WebAcces Server, where the webportal and the Secure Gateway were installed, went to Control Panel and open Quest Secure-IT to configure it as recomend on thread 11872 but unfortunately the Video Tutorial on SOL58849 doesn´t exist any more so I tried to figured out how, and here is whereI  probably mess up.

Trying to recreate the scenario described on PDF´s SOL76217 page 3, I did the folowing on Proxies tab on Quesst Secure-IT Properties:

1. 1. Enabled RDP Proxy using the WebAcces Server´s local IP on port 443. Use a self signed certificate.
   2. Enabled Web Interface Proxy using the WebAcces Server´s local IP on port 443, and destination used the same WebAcces Server´s local IP on port 80.
      1. I tried with and with out Enable SSL and using the same certificate with the same results.
   3. Enabled Connection Broker Proxy using the WebAcces Server´s local IP on port 9443, and destination used the Broker Server´s local IP on port 8080
      1. I tried with and with out Enable SSL and using the same certificate with the same results.

Then, on the Admin WebPortal, on the Firewall/SSL VPN section, I did the following:

1. 1. Select SSL Getway.
   2. On SSL Gateway filled:
      1. External SSL Gateway ... Address: x.x.x.x (the public IP that is pointing to the WebAcces Server)
      2. TCP Port: 443
      3. SSL Gateway Local Adrees List: x.x.x.x (the intenal  WebAcces Server´s IP)
      4. NAT support is NOT enabled
      5. Web URL external: http://x.x.x.x(public ip)/provision/web-it/default.aspx
      6. Web URL internal: http://x.x.x.x(public ip)/provision/web-it/default.aspx

Once seted up those configurations, I attempt to connect to my apps/desktops using the web portal but when the .pit file comes out, it immediately show the error:

Archivo de Conexion no valido (c:\......\*.pit) especificado. (Conection file specified invalid)

Is it wrong my Secure-IT configuration?

Do I need a therd party certificate?

Do I need a domain name?

Any help would be highly appreciated.