2017-11-3  i actually regret switching to new edge - no tabs set aside, inferior pdf annotation with the pen, unfinished collections and no reading list (collections are not its replacement, because they. Fix: Your Credentials Did not Work in Remote Desktop. Thus, if you want to login using a non-admin user account, you will have to grant the remote desktop users access. Here is how to do it. Microsoft Editor Reportedly Tells Users To Turn Off Grammarly To Avoid Conflicts. Enable remote login on the Mac. To set up the Mac build host, first enable remote login: On the Mac, open System Preferences and go to the Sharing pane. Check Remote Login in the Service list. Make sure that it is configured to allow access for All users, or that your Mac username or group is included in the list of allowed users. 2020-4-5  Log on as admin user with RDP Create a local (not Microsoft account) account with the name that would be before the @ (i.e. Qwerty if the MS email were qwerty@outlook.com) Give to the created local user the 'Remote Desktop Users' rights. Now log off as admin Remote desktop and use username.qwerty (note no @outlook.com). Support for the 'Prompt for Credentials on Client' RDP file setting when NLA is not negotiated. Support for smart card-based login via smart card redirection at the Winlogon prompt when NLA is not negotiated. Fixed an issue that prevented downloading feed resources that have spaces in the URL. Updates for version 10.2.1. Date published.

• Microsoft Remote Desktop Mac Invalid Ts Gateway Credentials
• User Credentials Are Invalid

-->

This guide provides troubleshooting steps for issues that may be encountered using the new connection manager, including connectivity and SSH issues.

Log File Location

• Mac – ~/Library/Logs/Xamarin-[MAJOR.MINOR]
• Windows – %LOCALAPPDATA%XamarinLogs

The log files can be located by browsing to Help > Xamarin > Zip Logs in Visual Studio.

Where's the Xamarin Build Host App?

The Xamarin Build Host from older versions of Xamarin.iOS is no longer required. Visual Studio now automatically deploys the agent over Remote Login and runs it in the background. There is no additional app that will run on either the Mac or Windows machines.

Troubleshooting Remote Login

Important

These troubleshooting steps are primarily intended for problems that happen during the initial setup on a new system. If you had previously been using the connection successfully in a particular environment and then the connection suddenly or intermittently stops working, you can (in most cases) skip straight to checking if any of the following helps:

• Kill the leftover processes as described below under Errors due to existing Build Host Processes.
• Clear the agents as described under Clearing the Broker, IDB, Build, and Designer Agents, and then use a wired internet connection and connect directly via the IP address as described under Couldn't connect to MacBuildHost.local. Please try again.
  If none of those options fix the issue, then please follow the instructions in step 9 to file a new bug report.

1. Check that you have compatible Xamarin.iOS versions installed on your Mac. To do this with Visual Studio 2017 ensure that you are on the Stable distribution channel in Visual Studio for Mac. In Visual Studio 2015 and earlier make sure that you are on the same distribution channel on both IDEs.

   • In Visual Studio for Mac, go to Visual Studio for Mac > Check for Updates.. to view or change the Update channel.
   • In Visual Studio 2015 and earlier, check the distribution channel under Tools > Options > Xamarin > Other.

2. Make sure that Remote Login is enabled on the Mac. Set access for Only these users, and make sure your Mac user is included in the list or group:

3. Check that your firewall allows incoming connections through port 22 - the default for SSH:

   If you have disabled Automatically allow signed software to receive incoming connections, OS X will present a dialog during the pairing process asking to allow mono-sgen or mono-sgen32 to receive incoming connections. Be sure to click Allow on this dialog:

4. Confirm that you are logged in to the user account on that Mac and have an active GUI session.

5. Make sure you are connecting to the Mac with the username rather than the Full Name. This avoids a known limitation for full names that include accented characters.

   You can find your username by running the whoami command in Terminal.app.

   For example, from the screenshot below, the account name will be amyb and not Amy Burns:

6. Check that the IP address you are using for the Mac is correct. You can find the IP address under System Preferences > Sharing > Remote Login on the Mac.

7. Once you have confirmed the IP address of the Mac, try a ping to that address in cmd.exe on Windows:

   If the ping fails, then the Mac is not routable from the Windows computer. That problem will need to be solved at the level of the local area network configuration between the 2 computers. Ensure that both machines are on the same Local Network.

8. Next, test if the ssh client from OpenSSH can connect successfully to the Mac from Windows. One way to install this program is to install Git for Windows. You can then start a Git Bash command prompt and attempt to ssh in to the Mac with your username and IP address:

9. If step 8 succeeds, you can try running a simple command like ls over the connection:

   This should list the contents of your home directory on the Mac. If the ls command works correctly but the Visual Studio connection still fails, you can check the Known Issues and Limitations section about complications specific to Xamarin. If none of those match your problem, please file a new bug report on Developer Community by going to Help > Send Feedback > Report a problem in Visual Studio and attach the logs described under Check the Verbose Log Files.

10. If step 8 fails, you can run the following command in Terminal on the Mac to see if the SSH server is accepting any connections:

11. If step 8 fails but step 10 succeeds, then the problem is most likely that port 22 on the Mac build host is not accessible from Windows due to the network configuration. Possible configuration issues include:

    • The OS X firewall settings are disallowing the connection. Be sure to double-check step 3.

      Occasionally the per-app configuration for the OS X firewall can also end up in an invalid state where the settings shown in System Preferences do not reflect the actual behavior. Deleting the configuration file (/Library/Preferences/com.apple.alf.plist) and rebooting the computer can help restore the default behavior. One way to delete the file is to enter /Library/Preferences under Go > Go to Folder in Finder, and then move the com.apple.alf.plist file to the Trash.

    • The firewall settings of one of the routers between the Mac and the Windows computer is blocking the connection.

    • Windows itself is disallowing outbound connections to remote port 22. This would be unusual. It is possible to configure the Windows Firewall to disallow outbound connections, but the default setting is to allow all outbound connections.

    • The Mac build host is disallowing access to port 22 from all external hosts via a pfctl rule. This is unlikely unless you know you have configured pfctl in the past.

12. If step 8 fails and step 10 fails, then the problem is likely that the SSH server process on the Mac is not running or is not configured to allow the current user to log in. In this case be sure to double-check the Remote Login settings from step 2 before you investigate any more complicated possibilities.

Known Issues and Limitations

Note

This section only applies if you have already connected successfully to the Mac build host with your Mac username and password using the OpenSSH SSH client, as discussed in steps 8 and 9 above.

'Invalid credentials. Please try again.'

Known causes:

• Limitation – This error can appear when attempting to log in to the build host using the account Full Name if the name includes an accented character. This is a limitation of the SSH.NET library that Xamarin uses for the SSH connection. Workaround: See step 5 above.

'Unable to authenticate with SSH keys. Please try to log in with credentials first'

Known cause:

• SSH security restriction – This message most often means that one of the files or directories in the fully qualified path of $HOME/.ssh/authorized_keys on the Mac has write permissions enabled for other or group members. Common fix: Run chmod og-w '$HOME' in a Terminal command prompt on the Mac. For details about which particular file or directory is causing the problem, run grep sshd /var/log/system.log > '$HOME/Desktop/sshd.log' in Terminal, and then open the sshd.log file from your Desktop and look for 'Authentication refused: bad ownership or modes'.

'Trying to connect..' never completes

• Bug #52264 – This problem can happen on Xamarin 4.1 if the Login shell in the Advanced Options context menu for the Mac user in System Preferences > Users & Groups is set to a value other than /bin/bash. (Starting with Xamarin 4.2, this scenario instead leads to the 'Couldn't connect' error message.) Workaround: Change the Login shell back to the original default of /bin/bash.

'Couldn't connect to MacBuildHost.local. Please try again.'

Reported causes:

• Bug – A few users have seen this error message along with a more detailed error in the log files 'An unexpected error occurred while configuring SSH for the user .. Session operation has timed out' when attempting to log in to the build host using an Active Directory or other directory service domain user account. Workaround: Log in to the build host using a local user account instead.

• Bug – Some users have seen this error when attempting to connect to the build host by double-clicking the name of the Mac in the connection dialog. Possible workaround: Manually add the Mac using the IP address.

• Bug #35971 – Some users have run across this error when using a wireless network connection between the Mac build host and Windows. Possible workaround: Move both computers to a wired network connection.

• Bug #36642 – On Xamarin 4.0, this message will appear anytime the $HOME/.bashrc file on the Mac contains an error. (Starting with Xamarin 4.1, errors in the .bashrc file will no longer affect the connection process.) Workaround: Move the .bashrc file to a backup location (or delete it if you know you don't need it).

• Bug #52264 – This error can appear if the Login shell in the Advanced Options context menu for the Mac user in System Preferences > Users & Groups is set to a value other than /bin/bash. Workaround: Change the Login shell back to the original default of /bin/bash.

• Limitation – This error can appear if the Mac build host is connected to a router that has no access to the internet (or if the Mac is using a DNS server that times out when asked for the reverse-DNS lookup of the Windows computer). Visual Studio will take roughly 30 seconds to retrieve the SSH fingerprint and eventually fail to connect.

  Possible workaround: Add 'UseDNS no' to the sshd_config file. Be sure to read about this SSH setting before changing it. See for example unix.stackexchange.com/questions/56941/what-is-the-point-of-sshd-usedns-option.

  The following steps describe one way to change the setting. You will need to be logged in to an administrator account on the Mac to complete the steps.

  1. Confirm the location of the sshd_config file by running ls /etc/ssh/sshd_config and ls /etc/sshd_config in a Terminal command prompt. For all of the remaining steps, be sure to use the location that does not return 'No such file or directory'.

  2. Run cp /etc/ssh/sshd_config '$HOME/Desktop/' in Terminal to copy the file to your desktop.

  3. Open the file from your Desktop in a text editor. For example you can run open -a TextEdit '$HOME/Desktop/sshd_config' in Terminal.

  4. Add the following line at the bottom of the file:

  5. Remove any lines that say UseDNS yes to make sure the new setting takes effect.

  6. Save the file.

  7. Run sudo cp '$HOME/Desktop/sshd_config' /etc/ssh/sshd_config in Terminal to copy the edited file back into place. Enter your password if prompted.

  8. Disable and re-enable Remote Login under System Preferences > Sharing > Remote Login to restart the SSH server.

Clearing the Broker, IDB, Build, and Designer Agents on the Mac

If your log files show a problem during the 'Installing', 'Uploading', or 'Starting' steps for any of Mac agents, you can try deleting the XMA cache folder to force Visual Studio to re-upload them.

1. Run the following command in Terminal on the Mac:

2. Control-click the XMA folder and select Move to Trash:

3. There is a cache on Windows as well that it may help to clear. Open a cmd prompt as Administrator on Windows:

Warning Messages

This section discusses a few messages that can appear in the Output windows and logs that you can usually ignore.

'There is a mismatch between the installed Xamarin.iOS .. and the local Xamarin.iOS'

As long as you have confirmed that both Mac and Windows are updated to the same Xamarin distribution channel, this warning is ignorable.

'Failed to execute 'ls /usr/bin/mono': ExitStatus=1'

This message is ignorable as long as the Mac is running OS X 10.11 (El Capitan) or newer. This message is not a problem on OS X 10.11 because Xamarin also checks /usr/local/bin/mono, which is the correct expected location for mono on OS X 10.11.

'Bonjour service 'MacBuildHost' did not respond with its IP address.'

This message is ignorable unless you notice that the connection dialog does not display the IP address of Mac build host. If the IP address is missing in that dialog, you can still manually add the Mac.

'Invalid user a from 10.1.8.95' and 'input_userauth_request: invalid user a [preauth]'

You might notice this messages if you look in the sshd.log. These messages are part of the normal connection process. They appear because Xamarin uses the username a temporarily when retrieving the SSH Fingerprint.

Output Window and Log Files

If Visual Studio hits an error when connecting to the build host, there are 2 locations to check for additional messages: the Output window and the log files.

Output Window

The Output window is the best place to start. It displays messages about the main connection steps and errors. To view the Xamarin messages in the Output window:

1. Select View > Output from the menus or click the Output tab.
2. Click the Show output from drop-down menu.
3. Select Xamarin.

Log Files

If the Output window does not include enough information to diagnose the problem, the log files are the next place to look. The log files contain additional diagnostic messages that do not appear in the Output window. To view the log files:

1. Start Visual Studio.

   Important

   Note that .svclogs are not enabled by default. To access them you will need to start Visual Studio with verbose logs as explained in the Version Logs guide. For more information, refer to the Troubleshooting Extensions with the Activity Log blog.

2. Attempt to connect to the build host.

3. After Visual Studio hits the connection error, collect the logs from Help > Xamarin > Zip Logs:

4. When you open the .zip file, you will see a list of files similar to the example below. For connection errors, the most important files are the *Ide.log and *Ide.svclog files. These files contain the same messages in two slightly different formats. The .svclog is XML and is useful if you want to browse through the messages. The .log is plain text and is useful if you want to filter the messages using command line tools.

   To browse through all the messages, select and open the .svclog file:

5. The .svclog file will open in Microsoft Service Trace Viewer. You can browse the messages by thread to see related groups of messages. To browse by thread, first select the Graph tab, then click the Layout Mode drop-down menu and select Thread:

Verbose Log Files

If the normal log files still do not provide sufficient information to diagnose the problem, one last technique to try is to enable verbose logging. The verbose logs are also preferred on bug reports.

1. Quit Visual Studio.

2. Start a Developer Command Prompt.

3. Run the following command in the command prompt to launch Visual Studio with verbose logging:

4. Attempt to connect to the build host from Visual Studio.

5. After Visual Studio hits the connection error, collect the logs from Help > Xamarin > Zip Logs.

6. Run the following command in Terminal on the Mac to copy any recent log messages from the SSH server into a file on your Desktop:

If these verbose log files do not provide enough clues to resolve the issue directly, please file a new bug report and attach both the .zip file from step 5 and the .log file from step 6.

Troubleshooting automatic Mac provisioning

IDE log files

If you encounter any trouble using automatic Macprovisioning,take a look at the Visual Studio 2017 IDE logs, stored in%LOCALAPPDATA%XamarinLogs15.0.

Troubleshooting Build and Deployment Errors

This section covers a few problems that can happen after Visual Studio connects successfully to the build host.

'Unable to connect to Address='192.168.1.2:22' with User='macuser'

Known causes:

• Xamarin 4.1 security feature – This error will happen if you downgrade to Xamarin 4.0 after using Xamarin 4.1 or higher. In this case the error will be accompanied by the additional warning 'Private key is encrypted but passphrase is empty'. This is an intentional change due to a new security feature in Xamarin 4.1. Recommended fix: Delete id_rsa and id_rsa.pub from %LOCALAPPDATA%XamarinMonoTouch, and then reconnect to the Mac build host.

• SSH security restriction – When this message is accompanied by the additional warning 'Could not authenticate the user using the existing ssh keys', it most often means one of the files or directories in the fully qualified path of $HOME/.ssh/authorized_keys on the Mac has write permissions enabled for other or group members. Common fix: Run chmod og-w '$HOME' in a Terminal command prompt on the Mac. For details about which particular file or directory is causing the problem, run grep sshd /var/log/system.log > '$HOME/Desktop/sshd.log' in Terminal, and then open the sshd.log file from your Desktop and look for 'Authentication refused: bad ownership or modes'.

Solutions cannot be loaded from a Network Share

Solutions will only be compiled if they are on the local Windows file system or a mapped drive.

Solutions that are saved in a network share might throw errors, or completely refuse to compile. Any .sln files used in Visual Studio should be saved on the local Windows file system.

The following error is thrown because of this problem:

related bug: #36195

Missing Provisioning Profiles or 'Failed to create the a fat library' Error

Launch Xcode on the Mac and ensure that your Apple developer account is logged in and your iOS Development Profile is downloaded:

'A socket operation was attempted to an unreachable network'

Reported causes:

• Enhancement #36118 – This error can prevent successful builds when Visual Studio is using an IPv6 address to connect to the build host. (The build host connection does not yet support IPv6 addresses.)

Xamarin.iOS Visual Studio plugin fails to load after reinstallation of beta/alpha channel

Relevant bug #40781.

This issue may happen when Visual Studio fails to refresh the MEF component cache. If that's the case, installing this Visual Studio extension may help: https://visualstudiogallery.msdn.microsoft.com/22b94661-70c7-4a93-9ca3-8b6dd45f47cd

This will clear the Visual Studio MEF component cache to fix issues with cache corruption.

Errors due to existing Build Host Processes on the Mac

Processes from previous build host connections can sometimes interfere with the behavior of the current active connection. To check for any existing processes, close Visual Studio and then run the following commands in Terminal on the Mac:

To kill the existing processes use the following command:

Clearing the Mac Build Cache

If you are troubleshooting a build problem and want to make sure the behavior is not related to any of temporary build files stored on the Mac, you can delete the build cache folder.

1. Run the following command in Terminal on the Mac:

2. Control-click the mtbs folder and select Move to Trash:

Related Links

-->

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

Now that you've set up the Remote Desktop client on your device (Android, Mac, iOS, or Windows), you may have questions. Here are answers to the most commonly asked questions about the Remote Desktop clients.

The majority of these questions apply to all of the clients, but there are a few client specific items.

If you have additional questions that you'd like us to answer, leave them as feedback on this article.

Setting up

Which PCs can I connect to?

Check out the supported configuration article for information about what PCs you can connect to.

How do I set up a PC for Remote Desktop?

I have my device set up, but I don't think the PC's ready. Help?

First, have you seen the Remote Desktop Setup Wizard? It walks you through getting your PC ready for remote access. Download and run that tool on your PC to get everything set.

Otherwise, if you prefer to do things manually, read on.

For Windows 10, do the following:

1. On the device you want to connect to, open Settings.
2. Select System and then Remote Desktop.
3. Use the slider to enable Remote Desktop.
4. In general, it's best to keep the PC awake and discoverable to facilitate connections. Click Show settings to go to the power settings for your PC, where you can change this setting.

   Note

   You can't connect to a PC that's asleep or hibernating, so make sure the settings for sleep and hibernation on the remote PC are set to Never. (Hibernation isn't available on all PCs.)

Microsoft Remote Desktop Mac Invalid Ts Gateway Credentials

Make note of the name of this PC under How to connect to this PC. You'll need this to configure the clients.

You can grant permission for specific users to access this PC - to do that, click Select users that can remotely access this PC.Members of the Administrators group automatically have access.

For Windows 8.1, follow the instructions to allow remote connections in Connect to another desktop using Remote Desktop Connections.

Connection, gateway, and networks

Why can't I connect using Remote Desktop?

Here are some possible solutions to common problems you might encounter when trying to connect to a remote PC. If these solutions don't work, you can find more help on the Microsoft Community website.

• The remote PC can't be found. Make sure you have the right PC name, and then check to see if you entered that name correctly. If you still can't connect, try using the IP address of the remote PC instead of the PC name.

• There's a problem with the network. Make sure you have internet connection.

• The Remote Desktop port might be blocked by a firewall. If you're using Windows Firewall, follow these steps:

  1. Open Windows Firewall.

  2. Click Allow an app or feature through Windows Firewall.

  3. Click Change settings. You might be asked for an admin password or to confirm your choice.

  4. Under Allowed apps and features, select Remote Desktop, and then tap or click OK.

     If you're using a different firewall, make sure the port for Remote Desktop (usually 3389) is open.

• Remote connections might not be set up on the remote PC. To fix this, scroll back up to How do I set up a PC for Remote Desktop? question in this topic.

• The remote PC might only allow PCs to connect that have Network Level Authentication set up.

• The remote PC might be turned off. You can't connect to a PC that's turned off, asleep, or hibernating, so make sure the settings for sleep and hibernation on the remote PC are set to Never (hibernation isn't available on all PCs.).

Why can't I find or connect to my PC?

Check the following:

• Is the PC on and awake?

• Did you enter the right name or IP address?

  Important

  Using the PC name requires your network to resolve the name correctly through DNS. In many home networks, you have to use the IP address instead of the host name to connect.

• Is the PC on a different network? Did you configure the PC to let outside connections through? Check out Allow access to your PC from outside your network for help.

• Are you connecting to a supported Windows version?

  Note

  Windows XP Home, Windows Media Center Edition, Windows Vista Home and Windows 7 Home or Starter are not supported without 3rd party software.

Why can't I sign in to a remote PC?

If you can see the sign-in screen of the remote PC but you can't sign in, you might not have been added to the Remote Desktop Users Group or to any group with administrator rights on the remote PC. Ask your system admin to do this for you.

Which connection methods are supported for company networks?

If you want to access your office desktop from outside your company network, your company must provide you with a means of remote access. The RD Client currently supports the following:

• Terminal Server Gateway or Remote Desktop Gateway
• Remote Desktop Web Access
• VPN (through iOS built-in VPN options)

VPN doesn't work

VPN issues can have several causes. The first step is to verify that the VPN works on the same network as your PC or Mac computer. If you can't test with a PC or Mac, you can try to access a company intranet web page with your device's browser.

For example, go to Word and choose About Word. In the dialog box that opens, you can see the version number as well as the license type. In the example below, the version number is 16.18 and the license is a one-time purchase of Office 2019 for Mac. Mar 19, 2020  Wordart is not printing correctly in Word for Mac (Word Version 16.16, Mac High Sierra 10.13.6) The printed does not fit on the page and is not in the same location as. Mar 10, 2020  Most current packages for other Mac programs from Microsoft. The following table provides information about the most current packages, including a download link, for other Mac programs from Microsoft that may be of interest to IT professionals. The build date is listed in parentheses, in a YYMMDD format, after the version number. Sep 24, 2018  Today, we are announcing the general availability of Office 2019 for Windows and Mac. Office 2019 is the next on-premises version of Word, Excel. Current microsoft word mac version 2017.

Other things to check:

• The 3G network blocks or corrupts VPN. There are several 3G providers in the world who seem to block or corrupt 3G traffic. Verify VPN connectivity works correctly for over a minute.
• L2TP or PPTP VPNs. If you are using L2TP or PPTP in your VPN, please set Send All Traffic to ON in the VPN configuration.
• VPN is misconfigured. A misconfigured VPN server can be the reason why the VPN connections never worked or stopped working after some time. Ensure testing with the iOS device's web browser or a PC or Mac on the same network if this happens.

How can I test if VPN is working properly?

Verify that VPN is enabled on your device. You can test your VPN connection by going to a webpage on your internal network or using a web service which is only available via the VPN.

How do I configure L2TP or PPTP VPN connections?

If you are using L2TP or PPTP in your VPN, make sure to set Send all traffic to ON in the VPN configuration.

Web client

Which browsers can I use?

The web client supports Microsoft Edge, Internet Explorer 11, Mozilla Firefox (v55.0 and later), Safari, and Google Chrome.

What PCs can I use to access the web client?

The web client supports Windows, macOS, Linux, and ChromeOS. Mobile devices are not supported at this time.

Can I use the web client in a Remote Desktop deployment without a gateway?

No. The client requires a Remote Desktop Gateway to connect. Don't know what that means? Ask your admin about it.

Does the Remote Desktop web client replace the Remote Desktop Web Access page?

No. The Remote Desktop web client is hosted at a different URL than the Remote Desktop Web Access page. You can use either the web client or the Web Access page to view the remote resources in a browser.

Can I embed the web client in another web page?

This feature is not supported at the moment.

Monitors, audio, and mouse

How do I use all of my monitors?

To use two or more screens, do the following:

1. Right-click the remote desktop that you want to enable multiple screens for, and then click Edit.
2. Enable Use all monitors and Full screen.

Is bi-directional sound supported?

Bi-directional sound can be configured in the Windows client on a per-connection basis. The relevant settings can be accessed in the Remote audio section of the Local Resources options tab.

What can I do if the sound won't play?

Sign out of the session (don't just disconnect, sign all the way out), and then sign in again.

Mac client - hardware questions

Is retina resolution supported?

Yes, the remote desktop client supports retina resolution.

How do I enable secondary right-click?

In order to make use of the right-click inside an open session you have three options:

• Standard PC two button USB mouse
• Apple Magic Mouse: To enable right-click, click System Preferences in the dock, click Mouse, and then enable Secondary click.
• Apple Magic Trackpad or MacBook Trackpad: To enable right-click, click System Preferences in the dock, click Mouse, and then enable Secondary click.

Is AirPrint supported?

No, the Remote Desktop client doesn't support AirPrint. (This is true for both Mac and iOS clients.)

Why do incorrect characters appear in the session?

If you are using an international keyboard, you might see an issue where the characters that appear in the session do match the characters you typed on the Mac keyboard.

This can occur in the following scenarios:

• You are using a keyboard that the remote session does not recognize. When Remote Desktop doesn't recognize the keyboard, it defaults to the language last used with the remote PC.
• You are connecting to a previously disconnected session on a remote PC and that remote PC uses a different keyboard language than the language you are currently trying to use.

You can fix this issue by manually setting the keyboard language for the remote session. See the steps in the next section.

How do language settings affect keyboards in a remote session?

There are many types of Mac keyboard layouts. Some of these are Mac specific layouts or custom layouts for which an exact match may not be available on the version of Windows you are remoting into. The remote session maps your keyboard to the best matching keyboard language available on the remote PC.

If your Mac keyboard layout is set to the PC version of the language keyboard (for example, French – PC) all your keys should be mapped correctly and your keyboard should just work.

If your Mac keyboard layout is set to the Mac version of a keyboard (for example, French) the remote session will map you to the PC version of the French language. Some of the Mac keyboard shortcuts you are used to using on OSX will not work in the remote Windows session.

If your keyboard layout is set to a variation of a language (for example, Canadian-French) and if the remote session cannot map you to that exact variation, the remote session will map you to the closest language (for example, French). Some of the Mac keyboard shortcuts you are used to using on OSX will not work in the remote Windows session.

If your keyboard layout is set to a layout the remote session cannot match at all, your remote session will default to give you the language you last used with that PC. In this case, or in cases where you need to change the language of your remote session to match your Mac keyboard, you can manually set the keyboard language in the remote session to the language that is the closest match to the one you wish to use as follows.

Use the following instructions to change the keyboard layout inside the remote desktop session:

On Windows 10 or Windows 8:

1. From inside the remote session, open Region and Language. Click Start > Settings > Time and Language. Open Region and Language.
2. Add the language you want to use. Then close the Region and Language window.
3. Now, in the remote session, you'll see the ability to switch between languages. (In the right side of the remote session, near the clock.) Click the language you want to switch to (such as Eng).

You might need to close and restart the application you are currently using for the keyboard changes to take effect.

Specific errors

Why do I get an 'Insufficient privileges' error?

You are not allowed to access the session you want to connect to. The most likely cause is that you are trying to connect to an admin session. Only administrators are allowed to connect to the console. Verify that the console switch is off in the advanced settings of the remote desktop. If this is not the source of the problem, please contact your system administrator for further assistance.

User Credentials Are Invalid

Why does the client say that there is no CAL?

When a remote desktop client connects to a Remote Desktop server, the server issues a Remote Desktop Services Client Access License (RDS CAL) stored by the client. Whenever the client connects again it will use its RDS CAL and the server will not issue another license. The server will issue another license if the RDS CAL on the device is missing or corrupt. When the maximum number of licensed devices is reached the server will not issue new RDS CALs. Contact your network administrator for assistance.

Why did I get an 'Access Denied' error?

The 'Access Denied' error is a generated by the Remote Desktop Gateway and the result of incorrect credentials during the connection attempt. Verify your username and password. If the connection worked before and the error occurred recently, you possibly changed your Windows user account password and haven't updated it yet in the remote desktop settings.

What does 'RPC Error 23014' or 'Error 0x59e6' mean?

In case of an RPC error 23014 or Error 0x59E6 try again after waiting a few minutes, the RD Gateway server has reached the maximum number of active connections. Depending on the Windows version running on the RD Gateway the maximum number of connections differs: The Windows Server 2008 R2 Standard implementation limits the number of connections to 250. The Windows Server 2008 R2 Foundation implementation limits the number of connections to 50. All other Windows implementations allow an unlimited number of connections.

What does the 'Failed to parse NTLM challenge' error mean?

This error is caused by a misconfiguration on the remote PC. Make sure the RDP security level setting on the remote PC is set to 'Client Compatible.' (Talk to your system admin if you need help doing this.)

What does 'TS_RAP You are not allowed to connect to the given host' mean?

This error happens when a Resource Authorization Policy on the gateway server stops your user name from connecting to the remote PC. This can happen in the following instances:

• The remote PC name is the same as the name of the gateway. Then, when you try to connect to the remote PC, the connection goes to the gateway instead, which you probably don't have permission to access. If you need to connect to the gateway, do not use the external gateway name as PC name. Instead use 'localhost' or the IP address (127.0.0.1), or the internal server name.
• Your user account isn't a member of the user group for remote access.