Hi David, thanks a lot for your answer, it was very useful.
Well I finally get my WebPortal and my AppPortal working properly through internet. It seem like my Secure-IT configuration was not right plus that this scenario had a particular limitations like using an IP instead a domain name and the fact that the web portal and the secure gateway were working under a Windows 2008 enviroment and that had two network interfaces, one for local, and other facing internet.
The corrections I made were the following:
Mount the web portal and the secure gateway on a Windows 2003
Create a self certificate and installed on clients as discribed on this post
Secure-IT Configuration:
RDP Proxy enabled using WebAcces Server´s external IP on port 443
Web Proxy enabled using WebAcces Server´s external IP on port 443, destination WebAcces Server´s internal IP on port 80. Enabled SSL using the self certificate
Broker Proxy enabled using WebAcces Server´s external IP on port 9443, destination Broker Server´s internal IP on port 8080. Enebled SSL using the self certificate
Restart Quest SSL Service.
Modify Firewall/SSL settings on administrator´s web portal:
I have read through the notes above and have some suggestions for you that will help to identify the cause of the problem.
There is no problem using a self-signed certificate, you just have to ensure that all the client devices have this certificate installed and trusted. Have you done this?
For the certificate itself, have you created it in such a way that the IssuedTo name and the FriendlyName are exactly the same, as this is required?
The certificate should use the fully qualified domain name format, remote.vworkspace.co.uk, and not a short NetBIOS name, such as remote.
Your configuration for Secure-IT looks to be correct so long as Secure-IT is also installed on the WebAccess server. You will need to check the Enable SSL check box and select the certifcate for each proxy that you are using. If you make any changes to the Secure-IT settings you must restart the Secure-IT service for these to take effect.
On the WebAccess Server configuration your external and Internal URL’s are not correct, these should be as follows:
Where you substitue remote.vworkspace.co.uk for your certificate name or the URL that is set in your external DNS. You do not need to add the /provision/web-it/default.aspx part.
Are your client devices using Internet Explorer 8, or later?
javi1
2 Posts
1
December 2nd, 2011 19:00
Hi David, thanks a lot for your answer, it was very useful.
Well I finally get my WebPortal and my AppPortal working properly through internet. It seem like my Secure-IT configuration was not right plus that this scenario had a particular limitations like using an IP instead a domain name and the fact that the web portal and the secure gateway were working under a Windows 2008 enviroment and that had two network interfaces, one for local, and other facing internet.
The corrections I made were the following:
Trying again I successfully connect and launch my aplications an desktops.
I want to thank you again for the advice.
Saludos.
DELL-David Y
228 Posts
1
November 30th, 2011 10:00
Hello Javier,
I have read through the notes above and have some suggestions for you that will help to identify the cause of the problem.
There is no problem using a self-signed certificate, you just have to ensure that all the client devices have this certificate installed and trusted. Have you done this?
For the certificate itself, have you created it in such a way that the IssuedTo name and the FriendlyName are exactly the same, as this is required?
The certificate should use the fully qualified domain name format, remote.vworkspace.co.uk, and not a short NetBIOS name, such as remote.
Your configuration for Secure-IT looks to be correct so long as Secure-IT is also installed on the WebAccess server. You will need to check the Enable SSL check box and select the certifcate for each proxy that you are using. If you make any changes to the Secure-IT settings you must restart the Secure-IT service for these to take effect.
On the WebAccess Server configuration your external and Internal URL’s are not correct, these should be as follows:
External: https://remote.vworkspace.co.uk/ (note https for external)
Internal: http://remote.vworkspace.co.uk
Where you substitue remote.vworkspace.co.uk for your certificate name or the URL that is set in your external DNS. You do not need to add the /provision/web-it/default.aspx part.
Are your client devices using Internet Explorer 8, or later?
If so you will need to edit the Internet Explorer options since you will not have published a certificate revocation list. We have published this solution in the knowledgebase for this issue, https://support.quest.com/Search/SolutionDetail.aspx?id=SOL58145&category=Solutions&SKB=1
Please let me know if you need further assistance
Regards
David