Microsoft Remote Desktop Mac Not Connecting
  1. Microsoft Remote Desktop Mac Not Connecting To Computer
  2. Microsoft Remote Desktop Mac Not Working
  3. Microsoft Remote Desktop For Mac Not Connecting To Windows 10
-->

Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.

Check the status of the RDP protocol

Aug 17, 2018 If you use the Microsoft Remote Desktop app in macOS to connect to another Windows PC on your network, you may see a warning about an unverified certificate when you try to connect. Here's how to configure your Mac to always trust that certificate so you'll no longer see the warning message.

Guides you to understand the most common settings affecting establishing a Remote Desktop session or Terminal Services session in an enterprise environment. Microsoft does not recommend changing the port assigned to RDP. Connecting To servername.Could not open connection to the host, on port 3389: Connect failed. Connecting to Azure Lab Services via MacOS. Using Microsoft Remote Desktop. Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin. With Microsoft Remote Desktop, you can be productive no matter where you are. 2018-1-31  I'm a new Windows user, I just installed Windows 10 Home (version 1709) on my Intel NUC7i5. I'm using RDP Wrapper to enable remote desktop, and I'm connecting from my Macbook Pro with Microsoft Remote Desktop 10. I can connect no problem from my home on my LAN. But I can't connect over the gateway.

Check the status of the RDP protocol on a local computer

To check and change the status of the RDP protocol on a local computer, see How to enable Remote Desktop.

Note

If the remote desktop options are not available, see Check whether a Group Policy Object is blocking RDP.

Check the status of the RDP protocol on a remote computer

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check and change the status of the RDP protocol on a remote computer, use a network registry connection:

  1. First, go to the Start menu, then select Run. In the text box that appears, enter regedt32.
  2. In the Registry Editor, select File, then select Connect Network Registry.
  3. In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
  4. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server.
    • If the value of the fDenyTSConnections key is 0, then RDP is enabled.
    • If the value of the fDenyTSConnections key is 1, then RDP is disabled.
  5. To enable RDP, change the value of fDenyTSConnections from 1 to 0.

Check whether a Group Policy Object (GPO) is blocking RDP on a local computer

If you can't turn on RDP in the user interface or the value of fDenyTSConnections reverts to 1 after you've changed it, a GPO may be overriding the computer-level settings.

To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command:

After this command finishes, open gpresult.html. In Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections, find the Allow users to connect remotely by using Remote Desktop Services policy.

  • If the setting for this policy is Enabled, Group Policy is not blocking RDP connections.

  • If the setting for this policy is Disabled, check Winning GPO. This is the GPO that is blocking RDP connections.

Check whether a GPO is blocking RDP on a remote computer

To check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:

The file that this command produces (gpresult-<computer name>.html) uses the same information format as the local computer version (gpresult.html) uses.

Modifying a blocking GPO

You can modify these settings in the Group Policy Object Editor (GPE) and Group Policy Management Console (GPM). For more information about how to use Group Policy, see Advanced Group Policy Management.

To modify the blocking policy, use one of the following methods:

  • In GPE, access the appropriate level of GPO (such as local or domain), and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Allow users to connect remotely by using Remote Desktop Services.
    1. Set the policy to either Enabled or Not configured.
    2. On the affected computers, open a command prompt window as an administrator, and run the gpupdate /force command.
  • In GPM, navigate to the organizational unit (OU) in which the blocking policy is applied to the affected computers and delete the policy from the OU.

Check the status of the RDP services

On both the local (client) computer and the remote (target) computer, the following services should be running:

  • Remote Desktop Services (TermService)
  • Remote Desktop Services UserMode Port Redirector (UmRdpService)

You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets).

On either computer, if one or both services are not running, start them.

Note

If you start the Remote Desktop Services service, click Yes to automatically restart the Remote Desktop Services UserMode Port Redirector service.

Check that the RDP listener is functioning

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

Check the status of the RDP listener

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work both locally and remotely.

  1. To connect to a remote computer, run the following cmdlet:

  2. Enter qwinsta.

  3. If the list includes rdp-tcp with a status of Listen, the RDP listener is working. Proceed to Check the RDP listener port. Otherwise, continue at step 4.

  4. Export the RDP listener configuration from a working computer.

    1. Sign in to a computer that has the same operating system version as the affected computer has, and access that computer's registry (for example, by using Registry Editor).
    2. Navigate to the following registry entry:
      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp
    3. Export the entry to a .reg file. For example, in Registry Editor, right-click the entry, select Export, and then enter a filename for the exported settings.
    4. Copy the exported .reg file to the affected computer.

  5. To import the RDP listener configuration, open a PowerShell window that has administrative permissions on the affected computer (or open the PowerShell window and connect to the affected computer remotely).

    1. To back up the existing registry entry, enter the following cmdlet:

    2. To remove the existing registry entry, enter the following cmdlets:

    3. To import the new registry entry and then restart the service, enter the following cmdlets:

      Replace <filename> with the name of the exported .reg file.

  6. Test the configuration by trying the remote desktop connection again. If you still can't connect, restart the affected computer.

  7. If you still can't connect, check the status of the RDP self-signed certificate.

Check the status of the RDP self-signed certificate

  1. If you still can't connect, open the Certificates MMC snap-in. When you are prompted to select the certificate store to manage, select Computer account, and then select the affected computer.
  2. In the Certificates folder under Remote Desktop, delete the RDP self-signed certificate.
  3. On the affected computer, restart the Remote Desktop Services service.
  4. Refresh the Certificates snap-in.
  5. If the RDP self-signed certificate has not been recreated, check the permissions of the MachineKeys folder.

Check the permissions of the MachineKeys folder

  1. On the affected computer, open Explorer, and then navigate to C:ProgramDataMicrosoftCryptoRSA.
  2. Right-click MachineKeys, select Properties, select Security, and then select Advanced.
  3. Make sure that the following permissions are configured:
    • BuiltinAdministrators: Full control
    • Everyone: Read, Write

Check the RDP listener port

On both the local (client) computer and the remote (target) computer, the RDP listener should be listening on port 3389. No other applications should be using this port.

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check or change the RDP port, use the Registry Editor:

  1. Go to the Start menu, select Run, then enter regedt32 into the text box that appears.
    • To connect to a remote computer, select File, and then select Connect Network Registry.
    • In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
  2. Open the registry and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<listener>.
  3. If PortNumber has a value other than 3389, change it to 3389.

    Important

    You can operate Remote Desktop services using another port. However, we don't recommend you do this. This article doesn't cover how to troubleshoot that type of configuration.

  4. After you change the port number, restart the Remote Desktop Services service.

Check that another application isn't trying to use the same port

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work locally and remotely.

Remote

  1. Open a PowerShell window. To connect to a remote computer, enter Enter-PSSession -ComputerName <computer name>.

  2. Enter the following command:

  3. Look for an entry for TCP port 3389 (or the assigned RDP port) with a status of Listening.

    Note

    The process identifier (PID) for the process or service using that port appears under the PID column.

  4. To determine which application is using port 3389 (or the assigned RDP port), enter the following command:

  5. Look for an entry for the PID number that is associated with the port (from the netstat output). The services or processes that are associated with that PID appear on the right column.

  6. If an application or service other than Remote Desktop Services (TermServ.exe) is using the port, you can resolve the conflict by using one of the following methods:

    • Configure the other application or service to use a different port (recommended).
    • Uninstall the other application or service.
    • Configure RDP to use a different port, and then restart the Remote Desktop Services service (not recommended).

Check whether a firewall is blocking the RDP port

Use the psping tool to test whether you can reach the affected computer by using port 3389.

  1. Go to a different computer that isn't affected and download psping from https://live.sysinternals.com/psping.exe.

  2. Open a command prompt window as an administrator, change to the directory in which you installed psping, and then enter the following command:

  3. Check the output of the psping command for results such as the following:

    • Connecting to <computer IP>: The remote computer is reachable.
    • (0% loss): All attempts to connect succeeded.
    • The remote computer refused the network connection: The remote computer is not reachable.
    • (100% loss): All attempts to connect failed.

  4. Run psping on multiple computers to test their ability to connect to the affected computer.

  5. Note whether the affected computer blocks connections from all other computers, some other computers, or only one other computer.

  6. Recommended next steps:

    • Engage your network administrators to verify that the network allows RDP traffic to the affected computer.
    • Investigate the configurations of any firewalls between the source computers and the affected computer (including Windows Firewall on the affected computer) to determine whether a firewall is blocking the RDP port.
-->

Applies to: Windows 10, Windows 8.1, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2

You can use the Remote Desktop client for iOS to work with Windows apps, resources, and desktops from your iOS device (iPhones and iPads).

Use the following information to get started. Be sure to check out the FAQ if you have any questions.

Note

  • Curious about the new releases for the iOS client? Check out What's new for Remote Desktop on iOS?
  • The iOS client supports devices running iOS 6.x and newer.
Microsoft Remote Desktop Mac Not Connecting

Get the Remote Desktop client and start using it

Download the Remote Desktop client from the iOS store

Follow these steps to get started with Remote Desktop on your iOS device:

  1. Download the Microsoft Remote Desktop client from the iOS App Store or iTunes.
  2. Set up your PC to accept remote connections.
  3. Add a Remote Desktop connection or a remote resource. You use a connection to connect to a directly to a Windows PC and a remote resource to use a RemoteApp program, session-based desktop, or a virtual desktop published on-premises using RemoteApp and Desktop Connections. This feature is typically available in corporate environments.

Add a Remote Desktop connection

To create a remote desktop connection:

  1. In the Connection Center tap +, and then tap Add PC or Server.
  2. Enter the following information for the remote desktop connection:
    • PC name – the name of the computer. This can be a Windows computer name, an Internet domain name, or an IP address. You can also append port information to the PC name (for example, MyDesktop:3389 or 10.0.0.1:3389).
    • User name – The user name to use to access the remote PC. You can use the following formats: user_name, domainuser_name, or user_name@domain.com. You can also specify whether to prompt for a user name and password.
  3. You can also set the following additional options:
    • Friendly name (optional) – An easy-to-remember name for the PC you are connecting to. You can use any string, but if you do not specify a friendly name, the PC name is displayed.
    • Gateway (optional) – The Remote Desktop gateway that you want to use to connect to virtual desktops, RemoteApp programs, and session-based desktops on an internal corporate network. Get the information about the gateway from your system administrator.
    • Sound – Select the device to use for audio during your remote session. You can choose to play sound on the local devices, the remote device, or not at all.
    • Swap mouse buttons – Whenever a mouse gesture would send a command with the left mouse button, it sends the same command with the right mouse button instead. This is necessary if the remote PC is configured for left-handed mouse mode.
    • Admin Mode - Connect to an administration session on a server running Windows Server 2003 or later.
  4. Tap Save.

Need to edit these settings? Press and hold the desktop you want to edit, and then tap the settings icon.

Add a remote resource

Remote resources are RemoteApp programs, session-based desktops, and virtual desktops published using RemoteApp and Desktop Connections.

  • The URL displays the link to the RD Web Access server that gives you access to RemoteApp and Desktop Connections.
  • The configured RemoteApp and Desktop Connections are listed.

To add a remote resource:

  1. On the Connection Center screen, tap +, and then tap Add Remote Resources.
  2. Enter information for the remote resource:
    • Feed URL - The URL of the RD Web Access server. You can also enter your corporate email account in this field – this tells the client to search for the RD Web Access Server associated with your email address.
    • User name - The user name to use for the RD Web Access server you are connecting to.
    • Password - The password to use for the RD Web Access server you are connecting to.
  3. Tap Save.

The remote resources will be displayed in the Connection Center.

Manage your user accounts

When you connect to a desktop or remote resources, you can save the user accounts to select from again.

To create a new user account:

  1. In the Connection Center, tap Settings, and then tap User Accounts.
  2. Tap Add User Account.
  3. Enter the following information:
    • User Name - The name of the user to save for use with a remote connection. You can enter the user name in any of the following formats: user_name, domainuser_name, or user_name@domain.com.
    • Password - The password for the user you specified. Every user account that you want to save to use for remote connections needs to have an associated password.
  4. Tap Save.

To delete a user account:

  1. In the Connection Center, tap Settings, and then tap User Accounts.
  2. Select the account you would like to delete.
  3. Tap Delete.

Connect to an RD Gateway to access internal assets

A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet. You can create and manage your gateways using the Remote Desktop client.

To set up a new gateway:

  1. In the Connection Center, tap Settings > Gateways.
  2. Tap Add Remote Desktop gateway.
  3. Enter the following information:
    • Server name – The name of the computer you want to use as a gateway. This can be a Windows computer name, an Internet domain name, or an IP address. You can also add port information to the server name (for example, RDGateway:443 or 10.0.0.1:443).
    • User name - The user name and password to be used for the Remote Desktop gateway you are connecting to. You can also select Use connection credentials to use the same user name and password as those used for the remote desktop connection.

Navigate the Remote Desktop session

When you start a remote desktop session, there are tools available that you can use to navigate the session.

Start a Remote Desktop Connection

  1. Tap the remote desktop connection to start the remote desktop session.
  2. If you are asked to verify the certificate for the remote desktop, tap Accept. You can choose to always accept by sliding the Don't ask me again for connections to this computer toggle to ON.

Connection Bar

The connection bar gives you access to additional navigation controls.

  • Pan Control: The pan control enables the screen to be enlarged and moved around. Note that pan control is only available using direct touch.
    • Enable / Disable the pan control: Tap the pan icon in the connection bar to display the pan control and zoom the screen. Tap the pan icon in the connection bar again to hide the control and return the screen to its original resolution.
    • Use the pan control: Tap and hold the pan control and then drag in the direction you want to move the screen.
    • Move the pan control: Double tap and hold the pan control to move the control on the screen.
  • Connection name: The current connection name is displayed. Tap the connection name to display the session selection bar.
  • Keyboard: Tap the keyboard icon to display or hide the keyboard. The pan control is displayed automatically when the keyboard is displayed.
  • Move the connection bar: Tap and hold the connection bar, and then drag and drop to a new location at the top of the screen.

Session selection

You can have multiple connections open to different PCs at the same time. Tap the connection bar to display the session selection bar on the left-hand side of the screen. The session selection bar enables you to view your open connections and switch between them.

  • Switch between apps in an open remote resource session.

    When you are connected to remote resources, you can switch between open applications within that session by tapping the expander menu and choosing from the list of available items.

  • Start a new session

    You can start new applications or desktop sessions from within your current connection: tap Start New, and then choose from the list of available items.

  • Disconnection a session

    To disconnect a session tap X in the left-hand side of the session tile.

Command bar

The command bar replaced the Utility bar starting in version 8.0.1. You can switch between the mouse modes and return to the connection center from the command bar.

Microsoft Remote Desktop Mac Not Connecting To Computer

Use touch gestures and mouse modes in a remote session

The client uses standard touch gestures. You can also use touch gestures to replicate mouse actions on the remote desktop. The mouse modes available are defined in the table below.

Note

Interacting with Windows 8 or newer the native touch gestures are supported in Direct Touch mode. For more information on Windows 8 gestures see Touch: Swipe, tap, and beyond.

Existing Office 2016 for Mac customers will be seamlessly upgraded to 64-bit versions of Word, Excel, PowerPoint, Outlook, and OneNote as part of the August product release (version 15.25). This affects customers of all license types: Retail, Office 365 Consumer, Office 365. How does microsoft office 2016 work on a mac. Install Office for Mac now Office 365 customers get the new Office for Mac first. You’ll have Office applications on your Mac or PC, apps on tablets and smartphones for when you're on the go, and Office Online on the web for everywhere in between. Microsoft Office 2016 for Mac is now available for people in 139 countries, as long as you have an Office 365 subscription or you’re a student. Standalone versions will go up for sale in September. Jun 01, 2018  I have a laptop with Office Pro Plus 2016 ( Win 10 ) and inthe next days I will get a Mac. If I uninstall the Office. Win laptop, would it be possible to reinstall it in the Mac? Will it work?

Mouse modeMouse operationGesture
Direct touchLeft click1 finger tap
Direct touchRight click1 finger tap and hold
Mouse pointerLeft click1 finger tap
Mouse pointerLeft click and drag1 finger double tap and hold, then drag
Mouse pointerRight click2 finger tap
Mouse pointerRight click and drag2 finger double tap and hold, then drag
Mouse pointerMouse wheel2 finger tap and hold, then drag up or down
Mouse pointerZoomPinch 2 fingers to zoom in or spread 2 fingers to zoom out

Supported input devices

Basic Bluetooth mouse support is available in iOS 13 and iPadOS as an accessibility feature. Deeper mouse integration in the RD Client is available by using the Swiftpoint GT and ProPoint mice. In addition, external keyboards that are compatible with iOS and iPadOS are also supported.

For more information about device support, see What's new in the iOS client and the iOS App Store.

Tip

Swiftpoint is offering an exclusive discount on the ProPoint mouse for iOS client users.

Use a keyboard in a remote session

You can use either an on-screen keyboard or physical keyboard in your remote session.

For on-screen keyboards, use the button on the right edge of the bar above the keyboard to switch between the standard and additional keyboard.

Microsoft Remote Desktop Mac Not Working

If Bluetooth is enabled for your iOS device, the client automatically detects the Bluetooth keyboard.

While certain key combinations might not work as expected in a remote session, many of the common Windows key combinations, such as CTRL+C, CTRL+V, and ALT+TAB will work.

Important

Microsoft Remote Desktop For Mac Not Connecting To Windows 10

Questions and comments are always welcome. However, please do NOT post a request for troubleshooting help by using the comment feature at the end of this article. Instead, go to the Remote Desktop client forum and start a new thread. Have a feature suggestion? Tell us in the client user voice forum.

⇐ ⇐ Download Microsoft Office For Mac Stanford
⇒ ⇒ Microsoft Remote Desktop Mac Dropping Connection