If you're having trouble connecting to one of your Windows machines using Remote Desktop (RDP), here's a short guide on how to troubleshoot.

Verify if the connection works with Microsoft Remote Desktop for Mac

First of all, please verify that you can connect to your remote machine using Microsoft Remote Desktop for Mac.
You can get the app here: https://itunes.apple.com/app/microsoft-remote-desktop-10/id1295203466
Please try this on the same machine you're running Royal TSX on.

Import the MSRDP connection into Royal TSX

If you can connect using Microsoft Remote Desktop for Mac, you can try exporting the connection and importing it back into Royal TSX.
To do this, right-click the entry in MSRDP and select "Export". In the save panel, select a location to save the .rdp file to.
Back in Royal TSX select the folder you want to import the connection to.
Then go to "File - Import - RDP files..." and select the exported file. Verify that your credentials are correct after importing the connection, then try to connect to the imported connection.

Check the "Network Level Authentication" (NLA) setting

If the connection still doesn't work in Royal TSX, a common cause is that "Network Level Authentication" (NLA) needs to be either enabled or disabled, depending on how your Windows host is set up. To adjust this setting, open the properties of your RDP connection and navigate to the "Advanced - Authentication" section. If that's the culprit and you need to adjust multiple connections, you can use our bulk-edit feature to do so.

All I see is black

If your connection is actually established but the only thing you see is a black screen, please see this KB article for more information.

Azure Active Directory (AzureAD)

If you're trying to connect to a machine joined to an Azure Active Directory (AzureAD), please ensure that "Network Level Authentication" (NLA) is disabled on the target machine and your connection properties in Royal TSX. Also, it's required to enable "TLS Encryption" in Royal TSX.

Smart Card redirection

While smart card redirection is generally supported by Royal TSX and the FreeRDP plugin, unfortunately it's kind of in an experimental state at the moment. This is reflected in the UI as we marked the checkbox to enable smart card redirection with "Experimental". As the feature very much depends on what kind of hardware (smart card reader and smart card) you have, it might work perfectly or not at all. The FreeRDP continues to make improvements to the implementation so with each new release, smart card support improves too.

If you currently are trying to use smart card redirection but can't get it to work, the first thing you might want to try is to enable "TLS Encryption" in the "Advanced - Authentication" settings of your RDP connection's properties.

Connecting to xrdp servers

Since version 4.1.1 of the FreeRDP plugin it's required to enable "Glyph Caching (Experimental)" in the "Advanced - Connection" properties of your RDP connection to be able to connect to xrdp servers. Please note that this is due to a bug in xrdp, not Royal TSX or FreeRDP. You can read more about the issue on FreeRDP's issue tracker.

Advanced Troubleshooting

If you still can't connect with Royal TSX, please contact us and include at least the following information:
  • The exact error message you're receiving
  • The Royal TSX and FreeRDP plugin version you're using
  • OS and version of the remote machine you're trying to connect to
  • OS and version of your Mac
  • Screenshots of your configuration from both, Royal TSX and Microsoft Remote Desktop for Mac
  • A debug log file (see below)

Creating a debug log file

To create a debug log file for RDP connections, please follow these instructions:

  • Go to "Preferences - Logging - File Logging"
  • Make sure "Enable File Logging" is checked
  • Set the "Logging level" to "Verbose"
  • Note the "Logfile path" since you will need it later on (or open Finder, navigate to the path right away and keep the window open)
  • Switch to the "Connection Types - Remote Desktop" section
  • In the "Plugin Settings" tab, scroll down and make sure "Enable Debug Logging" is checked
  • Apply the changes
  • Reproduce your problem
  • Locate the log file on your file system and include it in your ticket

Since debug logging heavily impacts performance, you should always disable logging (especially the RDP specific setting) after you're done reproducing your problem.