- #Microsoft remote desktop connection client for mac 2.1.1 install
- #Microsoft remote desktop connection client for mac 2.1.1 upgrade
- #Microsoft remote desktop connection client for mac 2.1.1 windows 8.1
- #Microsoft remote desktop connection client for mac 2.1.1 Pc
I prefer to do a clean install of a new OS, and that was my plan in this case.
#Microsoft remote desktop connection client for mac 2.1.1 Pc
I completely bypassed Windows 8/8.1 as this is a desktop/gaming PC so a touch interface is of 0 interest to me. It was reliable, everything just worked, and it wasn’t too much of a resource hog. I’ve been running Windows 7 since it went RTM and was very happy with it. Install this, try and connect to your Windows machine (Win10 for me) and you are in business. Via the AppStore, search for ‘Microsoft Remote Desktop’ – Version 8.0.36 (Build 27228) is what I have today. Microsoft Remote Desktop Connection Client for Mac doesn’t.įortunately there is an alternative that does. Because NLA relies on a technology called Credential Security Support Provider Protocol, if you’re using a Remote Desktop Protocol client for another OS, you’ll need a client that supports NLA. When using an RD Session Host server, a user typically enters credentials into a client-side dialog box. NLA forces the client computer to present user credentials for authentication before the server will create a session for that user.īecause of that process, it’s sometimes called “front authentication.” Servers that are running Windows Server 2008/Vista or later, and clients running Windows XP SP3 or later, support NLA. What’s the difference? When connecting to a Terminal Server, a user starts a session and types in their credentials. This happened the same time Windows moved from Terminal Services to Remote Desktop Services. It turns out that Microsoft improved the security of RDP (always a good thing) to make use of something called Network Level Authentication. Try reconnecting to the Windows-based computer, or contact our administrator.” you are thrown the very helpful error “ Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. On attempting to connect to anything half way recent e.g. And as luck would have it, OS X/macOS ships with a client called Remote Desktop Connection for Mac (version 2.1.1 build 110309) though from the copyright notices this looks like it hasn’t been touched since 2010… and that is the problem. As a long time windows user, my default goto for this is of course Microsoft’s Remote Desktop Protocol.
#Microsoft remote desktop connection client for mac 2.1.1 windows 8.1
It looks to be a completely new application, which in my opinion is much better than the original! Once I installed this, I could connect to my Windows 8.1 machine without any problems.So, I had occasion to try and connect to a windows machine from my Mac. However, if you look in the App Store, you'll find Microsoft Remote Desktop.
#Microsoft remote desktop connection client for mac 2.1.1 upgrade
just upgrade to the latest version of Remote Desktop client! My RDC client was originally installed alongside Microsoft Office for Mac and no updates are reported (the latest is 2.1.1). However, as I said, the solution is pretty simple. Online you will find various possible solutions, ranging from changing some options, combinations of setting the domain field, removing stuff from your Apple Key Chain or even some hardcore registry editing. Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. This worked perfectly until I recently upgraded to Windows 8.1.Īfter installing Windows 8.1, Remote Desktop would fail to connect, reporting: Today's challenge was making a Remote Desktop connection from my MacBook to my home server running Windows 8. I loathe those problems that require lots of fiddling but ultimately turn out to be very simple to fix! Hindsight is wonderful thing!
0 kommentar(er)
