I was wrong! 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. what os versions do you have (client and server)? If that doesn't solve the problem enable RDP security layer in Group Policy on the machine: Verify that the firewall allows remote desktop connections with RDP (Port 3389) Click Start > check my blog
I see nothing in the OS X console and nothing on the server event log to give me any leads on where to start troubleshooting. The Mac RDP client puts this in for you by default. I finally deduced that this seemingly unrelated error message could in fact be traced to the “Domain” field. Thursday, June 20, 2013 9:55 PM Reply | Quote 0 Sign in to vote I solved this by removing Remote Desktop for mac 2.1.1 and installed 2.0.1 On a fresh RDP
I entered my username and password and clicked ‘OK’. Someone peeled an American flag sticker off of my truck. So, enable the policy setting, force it to RDP, execute a gpupdate to pick up the new policy and then restart the Remote Desktop Session Host service.
Well, happy enough given I can't connect to my primary server. Version 8.0.5 working well w/ self-signed cert to Windows 8.1. Why? Microsoft Remote Desktop App For Mac Os I certainly don't mind making that change on my home system, given I'm not overly concerned about the risks associated with lowering the security layer.
Any help greatly appreciated. Remote Desktop Connection Cannot Verify The Identity Of The Computer Mac Windows 8 Problem is resolved! Wednesday, August 27, 2014 10:06 PM Reply | Quote 3 Sign in to vote This is the answer - don't download the old 2.1.1 from MS, grab 8.0.5 from the Mac http://www.lombard.me/2013/09/remote-desktop-connection-for-mac-osx.html I really enjoyed reading it, you happen to be a great author.I will make sure to bookmark your blog and will come back down the road.
Is there some configuration I'm missing? On further prompts make sure you select 'Always Trust'. Remote Desktop Cannot Verify The Identity Of The Computer Because There Is A Time Or Date Friday, September 13, 2013 10:20 PM Reply | Quote 0 Sign in to vote For me, placing the domain in the User name field, instead of the domain field, resolved the Remote Desktop Connection Cannot Verify The Identity Of The Computer Windows 10 Using the host name would be correct in this situation, however for some reason the only way I could actually connect was to clear the field completely.
I was able to fix the problem so that I could connect. Friday, May 30, 2014 3:37 PM Reply | Quote 0 Sign in to vote That worked a treat! Thanks! news NOTE: Perform the following procedure on each of the terminal servers.
The interface is also much nicer and allows organizing multiple connections. The Mac Cannot Connect To The Windows-based Computer Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! I can remote desktop in from a PC but not from CORD on my Mac.
asked 2 years ago viewed 7528 times active 6 months ago Related 47What's a good Windows RDP client for Mac?10Full Screen with Microsoft's Mac OS X RDP client?5Windows RDP client that Problem is resolved! Jan 21, 2015 10:10 AM 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,631 points) Remote Desktop Connection Cannot Verify That The Computers Belong To The Same Farm geez, what a waste of time.
Helpful Inaccurate Obsolete Adaptavist Theme Builder (4.2.3) Powered by Atlassian Confluence 3.5.13, the Enterprise Wiki ABOUT About this site IS&T Services HOW TO Become a contributor Create an article Comment on I don't even need to use VMWare or Parallels to run a local Windows installation. This website is something that is needed on the internet, someone with a bit of originality! http://rss4medics.com/remote-desktop/remote-desktop-cannot-verify-identity.php Earth to Microsoft: Hire StackExchange to do your forums.
The error message occurred when trying to connect to any Windows computers that we tried. The certificate had expired and I didn't believe I needed it. Thanks, Again. And put a link on the download page to get it from the app store ....
However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. Easy to use Average Difficult to use This article is: Thank you for your feedback. Try the correct domain name or tryclearing this field. Posted on Jan 10, 2015 9:59 AM Reply I have this question too Q: Remote Desktop for Mac won't connect (but will from Windows) Hide Question All replies Helpful answers Page
Reply www.sunfrogshirts.com says: October 14, 2015 at 4:28 AM For latest news you have to pay a quick visit world wide web and on the web I found this web page IBM Watson and C# - Part 1:Introduction Running iTunes in a Windows Service withC# Home Automation SystemArchitecture Speech Controlled Home Automation - Part 1 (Raspberry Pi/WindowsIoT/C#) Archives August 2016(2) April 2016(3) That worked great.. Wednesday, October 23, 2013 1:46 PM Reply | Quote 30 Sign in to vote I think the problem started for me when I upgraded the Windows box to 8.1.
failed ... Nov 9, 2015 9:25 AM Helpful (0) Reply options Link to this post by sp4cecat, sp4cecat Nov 9, 2015 11:37 PM in response to rcook349 Level 1 (0 points) Nov 9, 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 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.
Source: Based on a VMware Knowledge Base article Establishing a RDP connection with a Windows 8.1 Desktop from Horizon View Client for Mac OS X (2059786) IS&T Contributions Documentation and information Wednesday, December 11, 2013 3:53 PM Reply | Quote 1 Sign in to vote Thanks vt_mruhlin - worked for me with OS X 10.9 and a Windows 8.1 host. This site is not affiliated with or endorsed by Apple Inc. Worked on my mac as well.
So we're essentially forcing the RDP client NOT to use TLS. Reply aloe cleanse trial says: July 31, 2015 at 8:30 PM If you are going for finest contents like myself, simply go to see this web page daily because it presents That is when the error (eventually) popped up. Access Keys: Skip to content (Access Key - 0) «MIT Information Systems & Technology website Welcome back, • Log In •Knowledge Base Handbook The Knowledge Base Create Article Home EditAdministrationAdvanced ViewThis