Download remote access faq pdf

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. 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. Mobile devices are not supported at this time. The client requires a Remote Desktop Gateway to connect. Don't know what that means? Ask your admin about it. You can use either the web client or the Web Access page to view the remote resources in a browser.

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. No, the Remote Desktop client doesn't support AirPrint. This is true for both Mac and iOS clients.

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. You can fix this issue by manually setting the keyboard language for the remote session.

See the steps in the next section. 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.

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. You might need to close and restart the application you are currently using for the keyboard changes to take effect.

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. Contact your network administrator for assistance. 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. In case of an RPC error 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 R2 Standard implementation limits the number of connections to The Windows Server R2 Foundation implementation limits the number of connections to All other Windows implementations allow an unlimited number of connections.

This error is caused by a misconfiguration on the remote PC. 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:. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Please rate your experience Yes No. Any additional feedback? Setting up Connections, gateway, and networks Web client Monitors, audio, and mouse Mac hardware Specific error messages The majority of these questions apply to all of the clients, but there are a few client specific items. I have my device set up, but I don't think the PC's ready.

Otherwise, if you prefer to do things manually, read on. For Windows 10, do the following: On the device you want to connect to, open Settings. Select System and then Remote Desktop. Use the slider to enable Remote Desktop. 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.

There's a problem with the network. Make sure you have internet connection. Click Allow an app or feature through Windows Firewall. Check the following: Is the PC on and awake? Did you enter the right name or IP address? Click Remote access dial-up or VPN to permit remote computers to dial in or connect to this network through the Internet.

Click VPN for virtual private access, or click Dial-up for dial-up access, depending on the role you want to assign to this server. In most cases, the DHCP option is simpler to administer. However, if DHCP is not available, you must specify a range of static addresses.

Windows calculates the number of addresses automatically. Accept the default setting of No, use Routing and Remote Access to authenticate connection requests , and then click Next.

Click Finish to enable the Routing and Remote Access service and to configure the remote access server. After you set up the server to receive dial-up connections, set up a remote access client connection on the client workstation. Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. To set up a client for virtual private network VPN access, follow these steps on the client workstation.

Click Connect to the network at my workplace to create the dial-up connection, and then click Next. You can use remote access policies to grant or deny authorization, based on criteria such as the time of day, day of the week, the user's membership in Windows Server based security groups, or the type of connection that is requested. If a remote access server is a member of a domain, you can configure these settings by using the user's domain account.

If the server is a stand-alone server or a member of a workgroup, the user must have a local account on the remote access server.

If you manage remote access on a user account basis, follow these steps to grant remote access rights:. If the VPN server already permits dial-up networking remote access services, do not delete the default policy; instead, move it so that it is the last policy to be evaluated. On the client workstation, click Start, click Network Connections, and then click the new connection that you created. If the network to which you want to connect has multiple domains, you may have to specify a domain name.

If you use a dial-up connection, check the phone number listed in the Dial box to make sure it is correct. Make sure that you've specified any additional numbers that you must have to obtain an external line or to dial long distance. Your computer establishes a connection to the remote access server. The server authenticates the user and registers your computer on the network. This section describes how to troubleshoot some issues that you may have when you try to set up remote access.

If the Windows Server based domain is using mixed mode, not all of the configuration options are available. Administrators can only grant or deny access to the user and specify callback options, which are the access permission settings available in Microsoft Windows NT 4.