F5 - Remote Desktop with Gateway

Question

We are deploying the Deploying F5 with Microsoft Remote Desktop Services and noticed that the client connect using the RPC over HTTP transport as opposed to the HTTP / UDP transport&nbsp;
Is there a way to force to the F5 to use the UDP transport, at present on the remote desktop gateway we only see one session as opposed to three. There should be one for the http and two for the UDP session&nbsp;
We were following the F5 Guide for the setup " f5-microsoft-remote-desktop-services-dg " and using a using a combined virtual server for Remote Desktop Gateway and Remote Desktop Web Access&nbsp;
We also had to remove the Irule for the gateway virtual server and turn of the Http profile as the connections would fail and we would see the following error in the logs&nbsp;
"http_process_state_prepend - Invalid action EV_INGRESS_DATA during ST_HTTP_PREPEND_HEADERS"&nbsp;

mikeshimkus_111 · Answer

Hi, do you have UDP virtual servers set up for RD Gateway?  The client should automatically connect over UDP if the service is available.  &nbsp;
I think that deployment guide is deprecated, replaced by &nbsp;
http://www.f5.com/pdf/deployment-guides/microsoft-remote-desktop-gateway-dg.pdf&nbsp;
and &nbsp;
http://www.f5.com/pdf/deployment-guides/microsoft-rds-session-host-dg.pdf&nbsp;

cedian_139209 · Answer

We are currently running version 10.2.1 on the LTM&nbsp;
By UDP virtual Servers for the gateway are your referring to UDP/3391 for the remote FX&nbsp;

cedian_139209 · Answer

We are currently running version 10.2.1 on the LTM

By UDP virtual Servers for the gateway are your referring to UDP/3391 for the remote FX

mikeshimkus_111 · Answer

Yes.

cedian_139209 · Answer

when I look at the statistics we do not see any hits for that virtual server
the system is configured with three virtual servers
One of the connection broker - separate ip - listening on 3389
One for the gateway - separate ip - listening on 443 - Protocol is TCP
One for the Remote FX - Same ip as the gateway - listening on 3391 - protocol is 3391

We only see hits on the first two virtual servers

Forum Discussion

F5 - Remote Desktop with Gateway

7 Replies

Recent Discussions

import live updates from version x to version y

Tenant image upgrade

iRule editor partition button does not work

F5Access | MacOS Sonoma

Overwriting or adding LTM SSL Traffic cert and key using iControlREST

Related Content

Two-Factor Authentication – Remote Desktop Gateway

API Gateway Mapping - Gartner - F5

Remote Desktop Web Access and Remote Desktop Gateway SSO Through APM

Remote Desktop Protocol (RDP) using an SSL VPN

Microsoft Remote Desktop Gateway servers iApp