For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

cedian_139209's avatar
cedian_139209
Icon for Nimbostratus rankNimbostratus
Jun 23, 2015

F5 - Remote Desktop with Gateway

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

 

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

 

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

 

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

 

"http_process_state_prepend - Invalid action EV_INGRESS_DATA during ST_HTTP_PREPEND_HEADERS"

 

application delivery
deployment
LTM
microsoft

7 Replies

    • cedian_139209's avatar
      cedian_139209
      Icon for Nimbostratus rankNimbostratus
      Jun 25, 2015
      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
  • cedian_139209's avatar
    cedian_139209
    Icon for Nimbostratus rankNimbostratus
    Jun 24, 2015

    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

     

    • cedian_139209's avatar
      cedian_139209
      Icon for Nimbostratus rankNimbostratus
      Jun 25, 2015
      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
    • mikeshimkus_111's avatar
      mikeshimkus_111
      Historic F5 Account
      Jun 26, 2015
      Is your client RemoteFX-compatible? It needs to be RDP 8.0 or higher: http://blogs.msdn.com/b/rds/archive/2013/04/09/get-the-best-rdp-8-0-experience-when-connecting-to-windows-7-what-you-need-to-know.aspx