Failed to Connect to the Target Machine. Error Showing When Attempting to Launch a Remote Session

The cause of this problem could be that the user's engine server was not properly configured to use the DNS for their environment. The engine may be unable to resolve the DNS name for the selected target.

To fix this problem:

• Check that the correct site was selected in the site selection dialog drop-down menu.
• Check that the target server is up and running
• Ensure that the target server is routable from the engine server (e.g. 192.168.x.x engine server will need routes correctly set up to connect to a 10.10.x.x target server)
• Verify the secret data is correct (URL(Machine), Password, Public Key, Private Key, Private Key Passphrase)
• Check that the proper Secret template was used
• Check that secret "Approval" was granted if necessary and that all security requirements are satisfied.
• Do ensure that the engine for the site you selected is "Online" (the engine may have gone offline close to the time the user selected the site to connect to)

RDP Supported Authentication Methods

PRA currently supports Enhanced RDP Security with TLS Encryption and NTLM authentication (CredSSP). The target machine needs to have NLA enabled and NTLM authentication traffic needs to be enabled. Standard RDP Security is not currently supported. Kerberos authentication is supported, if you are participating in the Private Preview. See Kerberos Authentication to learn more.