![]() ![]() Now this can be configured either by a group policy within an Active Directory environment, or by a local policy (Start -> Run -> GPEdit.MSC) if you don’t have a domain, or don’t want to create a GPO specifically for this purpose in your domain. The setting is called Require use of specific security layer for remote (RDP) connections. Specifically…Ĭomputer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security This configuration item is applied by Group Policy. TLS is the stronger security layer, but not as widely supported. This is the original RDP security layer, its supported by 3rd party RDP clients. As it should be in most situations, Windows’ first thought it to negotiate with the client to select a mutually supported security layer. ![]() This involved dictating which security layers will be used by the Remote Desktop Session Host on the server itself. There are three options to the security layer configuration, mind you it’s essentially two options with an auto-negotiate setting. I was able to fix the problem so that I could connect. Update (22 October): I’ve published a new post here describing the new Microsoft RDP Client for Mac OS X that is perfectly compatible with Windows Server 2012 R2. I would always receive the error ‘ Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.’ Most frustrating. Well, happy enough given I can’t connect to my primary server. There are other alternatives around that may be better – I’ve heard CoRD mentioned a few times, but I’m happy using the Microsoft one. I use the Microsoft RDP client that comes with Microsoft Office for Mac 2011. ![]() ![]() Ever since upgrading my home server from Windows Server 2012 to Windows Server 2012 R2, I’ve been unable to RDP to it from my Mac OS X laptop. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |