- Download and Install the Remote Desktop Client from the Apple Store on your Mac:
- //itunes.apple.com/us/app/microsoft-remote-desktop/id1295203466?mt=12
For more information on the Microsoft RDP client for mac, go to //docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-mac
- Login and establish a connection with the VPN Tunnel
- Launch the Microsoft Remote Desktop Client
- Click on the Plus sign in the application and select Desktop
- In PC Name, Enter the FQDN of your desktop and click on save
- In Save Desktops you will see the name of your PC, double click on the PC
- Enter your userid and password and click continue
- A popup will come up, “You are connecting to the RDP host, The certificate could be verified back to the root certificate. Your connection may not be secure. Do you want to continue?” Click Continue to proceed
- You will now be logged into your MSHS or MSSM desktop
Q: When I click the RDP Icon after tunneling in I get the error message, “We couldn’t connect to remote PC. Make sure the PC is turned on and connect to the network, and that remote access is enabled.”
A: Verify that the tunnel connection stills says connected. If it is connected, please verify the FQDN that you entered in the the RDP client. If both is correct, please contact the helpdesk to further troubleshoot this issue.
Q: When I click the RDP Icon after tunneling in I get the error message, “We couldn’t connect to the remote PC. You might not have permission to sign in remotely. Contact your network administrator for assistance”
A: Your AD account was not added to your desktop to allow Remote Desktop Connection. Please contact the helpdesk to have them add your account to your workstation for Remote Desktop Connection.
-
I have not used it, but it sounds like it has old cred cached somewhere.
-
what version of MAC RDP are you using. I downloaded the RDP from the APP store and seems to be working fine. You may want to check the username and password being used to connect.
Edit:
Try downloading Microsoft Remote Desktop from the App store, it's free.
-
I believe the RDP client was downloaded from the app store.
I have the following notes so far:
I connected 5 times in a row to the RDS Gateway server [log on and log off] from Windows 7. On the mac, when I successfully connect, it gives me a certificate error but lets me through. Event ID 4625 is thrown up 4 times in the Security section of event viewer. The event type is audit failure. "An account failed to log on". After being able to connect for a maximum of two times, the event ID 4625 is again thrown twice and this time it says Account Lockout.
-
Is your Mac connected to your domain? Can you post a pic of the setting on the RDP?
-
It ended up being solved by installing the latest version of the Microsoft Remote Desktop Client.
Today I was going to share my WiFi internet connection, when I realized I had the Remote Management sharing turned on, on my Mac, giving all privileges to all users including Guests.
I thought it was very strange, since I have never set this sharing myself and I don't think this comes as a default setting in Mountain Lion system.
So, I got a bit paranoid of possible hacking and spying, and I want to discover how I can see if someone logged in, and remotely and monitored/viewed my computer.
Maybe someone know the string match I should type on the system Console to find remote connections? Maybe I can see that in a specific log file? Or maybe someone knows a command in the terminal that shows me the log of all computers that connect to mine? I know the port mainly used to this Remote Management is the 5900.
Please, I am very worried about this, and I want to find out who did this thing.
Modified on: Wed, 19 Jun, 2019 at 12:18 PM
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.
Please try this on the same machine you're running Royal TSX on.
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.
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.
Did you find it helpful? Yes No
Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.