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.
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-messengerSep 17, 2017Cirrostratus
Thanks for posting your find! I had the same issue and the wildcard forwarding IP server was disabled.
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