How To Use Microsoft Remote Desktop
Rode Neagle
With Microsoft Remote Desktop clients, you can connect to Remote Desktop Services from Windows Server and remote PCs, and use and control desktops and apps that your admin has made available to you. There are clients available for many different types of devices on different platforms and form factors, such as desktops and laptops, tablets, smartphones, and through a web browser. Using your web browser on desktops and laptops, you can connect without having to download and install any software.
Some features are only available with certain clients, so it's important to check Compare the features of the Remote Desktop clients to understand the differences when connecting to Remote Desktop Services or remote PCs.
You can also use most versions of the Remote Desktop client to also connect to Azure Virtual Desktop, as well as to Remote Desktop Services in Windows Server or to a remote PC. If you want information on Azure Virtual Desktop instead, see Remote Desktop clients for Azure Virtual Desktop.
Here's a list of the Remote Desktop client apps and our documentation for connecting to Remote Desktop Services or remote PCs, where you can find download links, what's new, and learn how to install and use each client.
For the last couple days (since upgrading to macOS 12.4, although I don't know whether this is related) I can no longer copy and paste between my remote computer on Microsoft Remote Desktop and other macOS apps. The remote desktop and my Mac appear to be keeping separate clipboards.
In the version of Remote Desktop Web client (Version 1.0.27.0) used by the organization I remotely connect to, there are no options to enable or disable clipboard transfer. (In fact, there are no useful options for users at all!) PATHETIC
In the last week or so, I have repeatedly had to re-add the workspace URL for Windows 365 (the "subscription URL" collected from windows365.microsoft.com) to Microsoft Remote Desktop for Mac. The issue started with the previous version of the app, but has continued to happen about once-a-day since installing the latest version (10.9.0 build 2140) from the Mac App Store.
Everyday, the Workspace vanishes and we have to re-add it. We can then logout, login, close Remote Desktop, open it, etc all day long with no problem. BUT, the next day, the Workspace will appear for a second or so and then vanish.
Same issue here. It stuck for a few weeks but then has been deleting the workspace URL each day so I have to re-add it into the app. I was even still in the Workspace actively and noticed the link in the Remote Desktop Connection app was gone.
This is even worse for me, sometimes it might just close my session for no apparent reason, maybe because I clicked in another screen ? And then back to the little dance of setting the new workspace and typing credentials and passwords. This is really upsetting, please fix ASAP.
Check Credentials: Double-check your credentials (username and password) for your Windows 365 workspace. Make sure they are correct, as incorrect login information can lead to issues.
Workspace Settings: Review the settings for your Windows 365 workspace within Microsoft Remote Desktop. Ensure that you have saved the workspace with the correct settings, including the server address and login credentials.
Credential Management: On your Mac, open the "Keychain Access" application. Search for any saved credentials related to your Windows 365 workspace and delete them. Then, when you connect again, you will be prompted to save new credentials.
Recreate the Workspace: If the problem persists, try deleting the existing workspace in Microsoft Remote Desktop and create it again from scratch. This can sometimes resolve configuration issues.
Reinstall Microsoft Remote Desktop: As a last resort, if none of the above steps work, you might consider uninstalling and reinstalling Microsoft Remote Desktop for Mac. This can help resolve any underlying software issues.
Contact Support: If the issue continues to persist, it's a good idea to reach out to Microsoft Remote Desktop support or your IT department for further assistance. They may be able to provide specific guidance based on your organization's setup.
Remember to back up any important information or settings before making significant changes to your remote desktop configuration. Additionally, make sure you have permission and authorization to access your Windows 365 workspace.
I have the same problem with a customer of ours. There, the problem occurs on several Macs with different Mac OS versions. On some Macs the workspace disappears almost daily. On others, the problem occurs only every few weeks.
@Christian_Ehret I have two Macs that haven't had the issue in weeks and neither of them are connected to Intune. However, I wonder if there is a security setting in M365 that DOES require a Mac be joined to Intune in order to save a connection, which was inadvertently turned on for environments experiencing this issue.
I hope it does stick for you, though. Mine has remained for the last 3 weeks without disappearing, so the issue appears to have been resolved for me without joining Intune, but if that is a surefire fix for others, this is pretty useful info.
I've been working on this problem for 5 days, Google doesn't seem to be helping and that is surprising. Lack of posts on the topic made me believe it was a differnt issue than this router, however this morning I have conclusively proved the problem is the TL-ER5120 V3 router. It may be a simple setup or configuration issue, but frankly I can't find it/figure it out. Yes I've RTFM. Yes i've googled the problem endlessly. Yes I've tried random things, yes I reversed those that failed before moving on. Yes, i've rebooted the router multiple times. Yes, I have disabled everything in "firewall" section of router setup. Yes, I have above average networking knowledge and can usually figure out the problem, however networking and/or IT is NOT my day job so i'm far from expert.
Used RDP via that setup locally and remotely for years. Locally RDP is available 24/7/365, when out of town, port forwarded and opened a high numbered port (49XXX) and forwarded it to the local machine IP:port 3389. Both setups, local and remote, worked perfectly--never had a problem. Therefor, I suspected it wasn't a problem with Windows Settings.
My cable providers connection is however problematic, and connectivity as a whole will randomly drop for awhile. For more than one reason, I decided to upgrade to a multi-WAN connection, thus the purchase of the TL-ER5120. The other WAN provider is a metered "unlimited" cellular connection with a 22gb/month high speed cap (i.e.weird American "unlimited but limited" cellular broadband).
I initially attempted to just hang the R7000 as is on port 5, disabling DHCP on the 5120, hoping that the 5120 could be a "failover" router and I could just continue to use the Netgear R7000 as the local network router. That worked somewhat, but I had a few devices (camera's and a dedicated equipment controller) that just didn't get along with double NAT.
Next the R7000 got switched to AP mode, and the TL-ER5120's DHCP server got turned back on. Some 50 devices are connected... windows laptop, iPhones, iPads, dedicated home automation equipment, Alexa devices, picture frames, sprinkler controllers, garage door contollers, etc. One device was problematic and didn't want to connect (phone home essentially). In following the troubleshooting steps on the manufactures site, I disabled everything possible in the Firewall section of the TL-ER5120 and got it working. (and haven't yet gotten to the step where i try rechecking the boxes one by one.)
Satisfied that every device was correctly connecting to the internet as it should, I moved on to my final setup steps, making certain I can reach my single windows 10 PC via Remote Desktop and setting up DDNS for that specific purpose. (everything else that connects at this point handles inbound connections by making an outbound connection to a cloud server instead.)
That should open the external port 3389. It doesn't, the port stays closed from the Public IP. Confirmed closed using GRC's Shields up (an online port scanning tool) and specifiying 3389, GRC actually returns "Stealth" which means it doesn't even reply as closed.
Additionally I can't connected via RDP on the local network!! Specifically with my laptop connected via WIFI or cable, and attemting to open a remote desktop at 192.168.1.10 or the machine name. I checked that both machines can Ping each other (they can). I located a troubleshooting steps to verify that 3389 was listenening on the target machine using ipconfig -a -o and looking up the PID of the listening PID to see what was listening. All good. I located a Microsoft page that suggested using telnet to see if 3389 was open from the remote machine--It's not. Yet remember both machines can ping each other.
In the TL-ER5120's interface the page that looks like it could have an effect is Preferences -> Service Type. I tried various entries on that page, with no luck. Firewall section is all still disabled at this point.
I then suddenly remembered that I had a brand new Netgear R7000 that was purchased long ago for a family member and never used. I popped open the still in factory shrink wrap R7000, connected it to the Cable modem and my laptop and upgraded the firmware to the current version. Then without even an address reservation I connected the WIN10 RDP target machine. Switched my laptop from cable to wifi and opended Remote Desktop from laptop to target on the first try. THE ONLY CHANGE IS THR ROUTER, I didn't even reboot either computer.
So in CONCLUSION: the TL-ER5120 breaks communication on port 3389. WHY? Is there a work-around or do i need to return the TL-ER5120, because no remote desktop is a deal breaker. I need it to work both Lan->Lan and Wan->Lan.
575cccbfa5