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 w...
application delivery
deployment
LTM
microsoft
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

 

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jun 25, 2015
    Yes.
  • 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
  • cedian_139209's avatar
    cedian_139209
    Icon for Nimbostratus rankNimbostratus
    Jun 26, 2015
    they are, we running tests using windows 8 as well as windows 7 clients with the necessary RDP updates When the clients connect to some test windows RDS servers we see them using the UDP transport