Cw Web: Installing Microsoft Remote Desktop Client For Mac
I'm trying to remote onto a Windows 2012 Server using Remote Desktop Connection for Mac. Using the same credentials, it works from my Windows PC (using Remote Desktop for Windows), but trying to do it from my Mac I get the error: Remote Desktop Connection 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?
Any help greatly appreciated. I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for.
Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here. However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them.
By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X. You begin to solve the problem by asking your server administrator for the server's root certificate. He/she has to export this using the built-in tools.
They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the.cer file and when prompted install it as a system keychain. On further prompts make sure you select 'Always Trust'. Launch RDC for Mac and you should be OK? If your server administrator does not know how or, worse still, won't do this for you, then you have far deeper problems that go well beyond OS X in particular and IT as a whole in general.
I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for. Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here. However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them. By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X. You begin to solve the problem by asking your server administrator for the server's root certificate.
He/she has to export this using the built-in tools. They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the.cer file and when prompted install it as a system keychain. On further prompts make sure you select 'Always Trust'. Launch RDC for Mac and you should be OK? If your server administrator does not know how or, worse still, won't do this for you, then you have far deeper problems that go well beyond OS X in particular and IT as a whole in general.
I have been fighting this since first installing windows 10 on one of my test systems.i FINALY have the solution. So i HAVE been using CORD to log into my PCs from OSX. But it was not working on the Win10 box. I was in the insiders Beta program.
And after some update CORD finaly started working. Well as said above, that was short lived with the next update CORD stopped working again. Panasonic gobi drivers for mac. I can remote desktop in from a PC but not from CORD on my Mac.
So following the advice above i downloaded MICROSOFTS's remote desktop. And as soon as i tried to remote into my Win10 box, a message come up about generating a security certificate for this user. I said Yes, and boom! Remote desktop ed in perfectly! Sadly CORD (my preferred client) is still NOT working, but now we know WHY! Win 10 looks for this ' security certificate ' and if it doesnt find it Win10 will REFUSE the connection.
This must be a PC to PC handshake that we never see. So for CORD we need to ether: 1. Disable this ' security certificate' check in remote login (best solution) 2. Get CORD updated to deal with this ' security certificate' (doubt this will happen). So I did a inplace upgrade to Windows 10, from a Working window 7 system. CORD logged in PERFECTLY just as under Windows 7! Now I need to play the difference game.
What setting is WORKING on the newly upgraded box, that is not set on my original Windows 10 system. All the setting for Remote Administration looks the same. All the firewalls are off. Again the only lead I have is that Microsoft Remote Desktop app works on the original box, but not CORD. And i THINK this is due to a security certificate issue. Problem is I have not idea where to find that in Windows 10 Any new ideas?
Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only.
Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site.
Cw Web: Installing Microsoft Remote Desktop Client For Mac Pro
All postings and use of the content on this site are subject to the.