Forum Discussion

alex_4_236440's avatar
alex_4_236440
Icon for Altostratus rankAltostratus
May 09, 2017

APM Remote Desktop - Could not connect

Hi all,

 

I'm trying to configure a full webtop that can be accessed externally that contains RDP links to various servers (not RDSH). I've followed the instructions in the following video, which seems to be the only thing I can find remotely close to what I'm trying to achieve:

 

https://www.youtube.com/watch?v=XBr4rl_GnKc

 

When I access the links, it simply states "could not connect to server" after a minute or two. This happens when using the java client too.

 

I've checked the APM logs, and everything looks good; however, nothing is logged when I actually click the RDP link, and I can't find another log with details of this aspect (???).

 

I'm sure I'm missing something very simple, but I can't find anything at all. In terms of set up, this is part of an SSL-VPN deployment that was created using the wizard. I've simply created an additional full webtop that is assigned to a specific AD group that also contains links for various remote desktops / rdp.

 

Any help appreciated!

 

application delivery
BIG-IP Access Policy Manager (APM)
ssl-vpn
  • alex_4_236440's avatar
    alex_4_236440
    May 10, 2017

    This was caused by a wildcard forwarding IP virtual server and AFM. The solution in the end was to add an AFM rule to the wildcard server for port 3389 with a destination of the SSL-VPN VIP and the IP of any Windows server that an APM remote desktop object had been created for.

     

  • Jad_Tabbara__J1's avatar
    Jad_Tabbara__J1
    Icon for Cirrostratus rankCirrostratus
    May 09, 2017

    Hello,

     

    Have you verified that the remote server is accessible from F5. You can connect via ssh to the BIG-IP then make a telnet x.x.x.x 3389...

     

    Could you share your VS configuration (at least the "Content Rewrite" and "Access Policy" parts) ? Is the "Auto Map" settings set for the "Source Address Translation" ?

     

    Note: If your are testing from a Windows machine, it is better to use the MS RDP client instead of using java RDP client.

     

    Depending on the BIG IP version you are running you can also check the "APM Compatibility matrix" to view if it supported.

     

    Matrix for 12.0 version : https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-clientcompatmatrix-12-0-0.html

     

    Regards

     

  • alex_4_236440's avatar
    alex_4_236440
    Icon for Altostratus rankAltostratus
    May 10, 2017

    This was caused by a wildcard forwarding IP virtual server and AFM. The solution in the end was to add an AFM rule to the wildcard server for port 3389 with a destination of the SSL-VPN VIP and the IP of any Windows server that an APM remote desktop object had been created for.

     

    • The-messenger's avatar
      The-messenger
      Icon for Cirrostratus rankCirrostratus
      Sep 17, 2017

      Thanks for posting your find! I had the same issue and the wildcard forwarding IP server was disabled.