Mac Remote Desktop Certificate Error
Contents |
Please enter a title. You can not post a blank message. Please type your message and try again. rcook349 Level 1 (4 points) Notebooks Q: Remote Desktop for Mac won't connect (but will from Windows) I'm trying to remote onto a Windows 2012 mac remote desktop connection cannot verify the identity of the computer that you want to connect to Server using Remote Desktop Connection for Mac. Using the same credentials, it works from microsoft remote desktop mac certificate my Windows PC (using Remote Desktop for Windows), but trying to do it from my Mac I get the error:Remote Desktop Connection
Microsoft Remote Desktop Mac Connection Refused
cannot verify the identity of the computer that you want to connect to.Try reconnecting to the Windows-based computer, or contact our administrator.Is it possible that the remote server allows connects from only Windows clients? Surely not.
The Certificate Or Associated Chain Is Not Valid Mac Rdp
Any help greatly appreciated. Posted on Jan 10, 2015 9:59 AM I have this question too Close Q: Remote Desktop for Mac won't connect (but will from Windows) All replies Helpful answers Page 1 Next by jaredfs, jaredfs Jan 12, 2015 11:05 AM in response to rcook349 Level 2 (309 points) Jan 12, 2015 11:05 AM in response to rcook349 It's more likely that its the Mac's fault than that the remote itap rdp server is refusing you. It's probably something to do with a failure to establish an encrypted connection to the Server. I'd recommend using Microsoft Remote Desktop. It's a free app in the app store for OS X and iOS devices and connects flawlessly to PCs from Apple devices. Helpful (3) Reply options Link to this post by rcook349, rcook349 Jan 12, 2015 11:41 AM in response to jaredfs Level 1 (4 points) Notebooks Jan 12, 2015 11:41 AM in response to jaredfs I am using Microsoft's Remote Desktop Connection for Mac. Like I said, on Windows machine (using RDC for Win) success. On Mac (using RDC for Mac) failure. Helpful (3) Reply options Link to this post by tablazines, tablazines Jan 21, 2015 10:10 AM in response to rcook349 Level 1 (0 points) Jan 21, 2015 10:10 AM in response to rcook349 Did this ever get resolved? I'm having the SAME EXACT problem. Using, Microsoft Remote Desktop... I can't connect remotely on my Mac... but I can connect without issue using the Windows version. Helpful (3) Reply options Link to this post by Antonio Rocco,★Helpful Antonio Rocco Jan 26, 2015 5:05 AM in response to rcook349 Level 6 (10,616 points) Desktops Jan 26, 2015 5:05 AM in response to rcook349 I doubt this a 'probl
that the materials estimate for the wine was incomplete. Written by Mike J McGuireOctober 15, 2013October 22, 2013 Why doesn't the Mac OS X RDP Client trust Windows Server 2012 R2? R2-D2, you know better than
Microsoft Remote Desktop Connection For Mac
to trust a strangecomputer! Ever since upgrading my home server from Windows Server 2012 to cord for mac Windows Server 2012 R2, I've been unable to RDP to it from my Mac OS X laptop. I use the Microsoft RDP client that remote desktop cannot verify the identity of the remote computer comes with Microsoft Office for Mac 2011. 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. Well, happy enough given I can't connect https://discussions.apple.com/thread/6770225?tstart=0 to my primary server. I would always receive the error ‘Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.' Most frustrating. 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 was able to fix the problem so that I could connect. This involved dictating which security layers will be used by https://blog.mikejmcguire.com/2013/10/15/r2-d2-you-know-better-than-to-trust-a-strange-computer-why-doesnt-the-mac-os-x-rdp-client-trust-windows-server-2012-r2-2/ 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. Negotiate. As it should be in most situations, Windows' first thought it to negotiate with the client to select a mutually supported security layer. RDP. This is the original RDP security layer, its supported by 3rd party RDP clients. TLS. TLS is the stronger security layer, but not as widely supported. This configuration item is applied by Group Policy. Specifically… Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security The setting is called Require use of specific security layer for remote (RDP) connections. 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. We're able to take a leaf out of some government play books here, which is to disable the negotiation option, and then hold fast on a weaker position. The fix here requires us to force the Remote Desktop Session Host to not negotiate the security layer, but rather use a weaker security layer than the default. I certainly don't mind making that change on my home system, given I'm not overly concerned about the risks associated w
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://apple.stackexchange.com/questions/71591/with-microsoft-rdp-client-how-do-i-mark-a-particular-server-certificate-as-trus Business Learn more about hiring developers or posting ads with us Ask Different Questions Tags Users Badges Unanswered Ask Question _ Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top With Microsoft RDP client, how do remote desktop I mark a particular server certificate as trusted? up vote 3 down vote favorite 1 I am using Microsoft's RDC client on Mac OS X, to connect to a Windows server. I am connecting to a RDC server that uses a self-signed certificate to identify itself. As a consequence, when I connect, my RDC client gives me a warning dialog like this: I can click "Connect" to continue, but then I have no security against man-in-the-middle microsoft remote desktop attack, because "Connect" instructs my client to ignore the server cert. I want to continue to connect, but in a way that is secure. Another option is to go to the Microsoft RDC client's preferences pane: and switch to "Always connect, even if authentication fails". This way, I'm never shown the warning again: it's as if I automatically clicked "Connect" every time. However, again, this is not secure: it skips authenticating the server, and thus is vulnerable to man-in-the-middle attacks. I want to be secure. Therefore, neither of the two approaches above is satisfactory. Conceptually, the obvious path forward is to somehow gain access to the server's self-signed certificate, and then ask the RDC client to treat it as trusted and never warn me about that certificate again. This would be secure (like SSH). However, I can't figure out how to get my RDC client to do that. How do I arrange for this server's certificate to be treated as trusted (despite the fact that it is self-signed), and have the system never warn me about connections that use that particular certificate, but still provide security (e.g., warn me if the certificate changes)? macos remote-desktop share|improve this question asked Nov 14 '12 at 21:45 D.W. 1,85251838 Have you tried adding the self-signed certificate to Applications>Utilities>Keychain Access? In this article about Chrome robpeck.com/20