Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Issue with RDP Connection Failures
#1
We are using ASG Remote Desktop 2017 (version 10.1.5713.0)

It is quite common that we will double-click an RDP connection, and the tab opens, but it is stuck at a colored screen with a “Reconnect” button.

However if I connect using the built-in Windows RDP client, it works just fine.  Only ASG RD has any issue.

The problem seems to be more frequent when I am connecting to remote systems with a higher latency.

This affects multiple users on multiple computers. All Windows 10.

Any ideas?
Reply
#2
Please deactivate the "Retry connecting if connection fails" in Settings=>Connections - then you should see the error code - and that's what we need for analyzing the problem
Regards/Gruss
Oliver
Reply
#3
We are having the same problem. Doing the above suggestion to see the error code gives this message:
RDP protocol error (Return code:50331671) , Your computer can't connect to the remote computer because a security package error occurred in the transport layer.

Remark: For most of our connection we have configured a RD gateaway. Upon starting ASG first connection always fails on a connection that uses the gateaway. Going directly to the gateaway works fine. After we get the error when we retry, then it connects.
Reply
#4
Perhaps you can try to disable some RDP functionalities in the properties of the connection - I have this error if I try to open more than 1 connection simultaneously using RD-Gateway - it works only of one RD-gateway connection is established successfully
Regards/Gruss
Oliver
Reply
#5
(11-01-2018, 09:12 AM)DevOma Wrote: Please deactivate the "Retry connecting if connection fails" in Settings=>Connections - then you should see the error code - and that's what we need for analyzing the problem

Thanks, sorry it took me so long to reply.  I swear I subscribed to e-mail notifications for replies but must have missed it when it came in.

This did seem to help; I always get an RDP error of some kind now when it happens, giving me something to troubleshoot.  I am yet to reproduce the problem where it works with the standalone mstsc.exe but not in ASG.
Reply




Users browsing this thread: 1 Guest(s)