Forum Discussion
APM Remote Desktop - Could not connect
- 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.
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
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com