Microsoft Remote Desktop 0x3000067

This forum is for Apple's Remote Desktop and therefore not for you. Microsoft's Remote Desktop forum is here:

Microsoft

@Hrishi, I think MS Remote Desktop 8.x used TLS 1.0 while MS Remote Desktop 10.x used TLS 1.2 to communicate to RD Gateway. Note: Apple, Microsoft, Google & Mozilla will end support for TLS 1.0 & TLS 1.1 starting March 2020. Microsoft this week updated its Remote Desktop client for macOS, which allows users to access their computer through another device remotely. The latest update brought native support for the M1.



You should have a word with your network administrator and ask them the question. FWIW I think there's a certificate or a protocol setting that needs to be configured somewhere that will allow your Mac to 'pass-through'. This could be something built-in on a PC or pre-configured when your IT department roll out the setting to their PC clients. Be patient and persistent and don't let them fob you off simply because you're on a Mac and not a PC. They should be supporting you properly irrespective of platform. It's their job after all

DesktopMicrosoft remote desktop 0x3000067 download


Apr 3, 2020 4:17 AM

Microsoft remote desktop for mac

Microsoft Remote Desktop Assistant

Microsoft Remote Desktop 0x3000067

Microsoft Rewards

I'm not familiar with RDP Wrapper, so this may not help. However, when you setup your RDP session on the Mac, are you using your static IP address for your Gateway or for the Computer? I've had users with Macs try to place the RDP server address into the Gateway field and that won't work unless you are running an RDP Gateway.

Microsoft Remote Desktop 0x3000067 Free

I hadn't realized, until now, that Windows 10 Home doesn't allow for setting up RDP access. Is there a reason you may not use something like Google's Remote desktop, or Teamviewer, LogMeIn, etc? They would be safer than leaving port 3389 open for RDP on your home system.