Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
sze
New Contributor

VPN SSL Web and Remote application published throught RDWeb access

Hello,

 

We want that external users (VPN SSL web) to connect to the remoteapps through RDwebaccess (RDP through https). 

The bookmarker is defined to the rdweb URL [link]https://localrdweb/RDWeb[/link] and we opens port 443 and 3389 to RD broker, RD web access and RDS Host.

Users can access to the RDweb portal but when they launch the remote application (which is published on the RDweb portal) they got errors (the remote server is unreacheable)

 

help please ?

 

best regards

5 REPLIES 5
bunger
New Contributor

Curious whether you ever found a fix for this?

Heaven_Knows
New Contributor III

sze wrote:

Hello,

 

We want that external users (VPN SSL web) to connect to the remoteapps through RDwebaccess (RDP through https). 

The bookmarker is defined to the rdweb URL https://localrdweb/RDWeb and we opens port 443 and 3389 to RD broker, RD web access and RDS Host.

Users can access to the RDweb portal but when they launch the remote application (which is published on the RDweb portal) they got errors (the remote server is unreacheable)

 

help please ?

 

best regards

i got same problem with you, fortigate and rds web, when click the bookmark an tcp/ip connection from local computer to web rdp port (443) of internal network machine sync sent, they wont be able to reach each other, so never connected.

No way to use thsi via vpn portal, i think that we have to publish it directly.

pmit
New Contributor III

This is because the new HTML version of RDWeb uses web sockets which the Fortigate proxy does not support. The web sockets attempt to connect directly which of course does not work when someone is connected via VPN.  I am trying to get a feature request for this going as many newer apps use web sockets. There are other proxy solutions that do support this even though Fortinet has not yet implemented it. I have not had enough time to test them, but NGINX supports web socket proxy and Kazzing https://kaazing.com/kwg supposedly supports it as well. I will post more if I get a feature request going. 

 

Please vote up

TAG

SSL VPN

web socket

wss:

 

GVTC_HELP
New Contributor

Thanks for this.  Been fighting it all morning.  Is there a feature request I can put a me too on?

 

Christian_89
Contributor III

Based on the information you have provided, it seems that there may be an issue with the Remote Desktop Gateway (RD Gateway) configuration or the Remote Desktop Session Host (RDSH) configuration.

Here are a few troubleshooting steps you can try:

1. Check the RD Gateway configuration to ensure that it is properly configured and that the SSL certificate is valid and trusted by the connecting clients.

2. Verify that the Remote Desktop Services (RDS) roles are installed and configured correctly on the servers hosting the RD Web Access and RDSH.

3. Ensure that the RD Gateway is properly configured to allow external clients to connect to the internal network. This includes ensuring that the appropriate ports (TCP 443 and TCP 3389) are open and properly forwarded to the RD Gateway server.

4. Check the RemoteApp and Desktop Connection settings on the client device to ensure that the correct settings are configured and that the client is using the RD Gateway to connect to the RDSH.

5. Verify that the DNS resolution is correctly configured for the internal resources and that the clients can resolve the correct IP addresses for the RD Web Access and RDSH servers.

6. Check the logs on the RD Gateway and RDSH servers for any error messages or warnings related to the RemoteApp and Desktop Connection.

7. Finally, try connecting to the RD Web Access and RemoteApp from a client machine on the internal network to verify that the internal connections are working correctly. If the internal connections work, this can help narrow down the issue to the RD Gateway configuration or the external connectivity.

By performing these steps, you should be able to isolate the issue and identify the root cause. If you are still unable to resolve the issue, you may need to engage the support teams for the RD Gateway and RDSH to assist with further troubleshooting and resolution.

Labels
Top Kudoed Authors