- #Microsoft remote destkop on mac do not ask again for this connection for mac os x
- #Microsoft remote destkop on mac do not ask again for this connection update
- #Microsoft remote destkop on mac do not ask again for this connection mac
- #Microsoft remote destkop on mac do not ask again for this connection windows
You will be able to connect your SCSU laptop to a computer that is on campus while you are working off campus. Thanks in advance for your assistance.A Remote Desktop Connection allows access from one computer to another computer over a network connection. Everything seems in place but not having much luck.
#Microsoft remote destkop on mac do not ask again for this connection mac
Is there some configuration I’m missing? Should I uninstall RD Gateway? I’m just at a loss here since I’m not a Mac guy. Firewalls are completely off on the server. 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. When the client attempts to connect, it gives a generic error message. The server has all the RDS roles installed and a self-signed certificate but I’m not using RD gateway, just trying to allow Macs to RDP to the server desktop. VPN works great every time, but no joy on RDP. The RRAS PPTP VPN works great but for some reason no Mac RDP Client I’ve tried, including Microsoft’s, will connect to it. I’m setting up VPN access to let a bunch of designers access a standalone (workgroup) RDS server running 2012 (OG). Hey guys, maybe someone here can shed some light on an issue I’m having with the new MS RDP client.
#Microsoft remote destkop on mac do not ask again for this connection update
I was hoping the recent update to Office 2011 might have fixed the problem, but as at version 2.1.1 of the Microsoft RDP client, it is still broken. Sadly, it doesn’t appear that the RDP client itself can be configured to only use RDP mode. 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.
#Microsoft remote destkop on mac do not ask again for this connection windows
TLS by the way does work when communicating with Windows Server 2008 R2/2012. So we’re essentially forcing the RDP client NOT to use TLS. The Mac RDP client does support TLS – however when using TLS to communicate with 2012 R2, it fails and obstinately does not fall back to the RDP security layer. Why? Is it because the RDP client on the Mac does not support TLS? Actually. We need to change that setting to the RDP security layer. With a suitable risk assessment and potential mitigation, this may also be suitable in an enterprise environment. My home *cough* IPS *cough* will take care of that.
![microsoft remote destkop on mac do not ask again for this connection microsoft remote destkop on mac do not ask again for this connection](https://www.top-password.com/blog/wp-content/uploads/2022/01/add-remote-pc.png)
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. 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. 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. 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.
![microsoft remote destkop on mac do not ask again for this connection microsoft remote destkop on mac do not ask again for this connection](https://www.cnet.com/a/img/-7w_yJ1UOBzAmy9WKdIaDk3qxgw=/1200x675/2011/11/17/caafe43a-f0f0-11e2-8c7c-d4ae52e62bcc/chrome-remote-desktop.png)
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.
#Microsoft remote destkop on mac do not ask again for this connection for mac os x
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.
![microsoft remote destkop on mac do not ask again for this connection microsoft remote destkop on mac do not ask again for this connection](https://images.fpt.shop/unsafe/filters:quality(90)/fptshop.com.vn/uploads/images/tin-tuc/126306/Originals/2-Allow-remote-connections.png)
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.