-->
Applies to: Windows 10, Windows Server 2016
- Microsoft offers a service pack that includes the missing TLS support for the Remote Desktop Server on Window 2008 but it might also allow the Remote Desktop Client to make more secure connections. If not, you should look into updating the RDC on your 2008 server or use an alternative.
- On the Select Computer screen, select Local Computer and then select the Finish button. Go back to the Add/Remove Snap-In dialog box and then select the OK button. In the left pane of the console window, expand Console Route Certificates (Local Computer) Remote Desktop Certificates. Double-click the Certificate in the middle pane to open it.
When you connect to your PC by using a Remote Desktop client, you're creating a peer-to-peer connection. This means you need direct access to the PC (sometimes called 'the host'). If you need to connect to your PC from outside of the network your PC is running on, you need to enable that access. You have a couple of options: use port forwarding or set up a VPN.
Enable port forwarding on your router
Port forwarding simply maps the port on your router's IP address (your public IP) to the port and IP address of the PC you want to access.
Specific steps for enabling port forwarding depend on the router you're using, so you'll need to search online for your router's instructions. For a general discussion of the steps, check out wikiHow to Set Up Port Forwarding on a Router.
I just tried my MacBook Pro and it connects. So, I believe it's something with the newest Mac OS Catalina update and Remote Desktop 10. Below are the credentials: MacBook Pro (which works): Mac OS High Sierra v 10.13.6. Microsoft Remote Desktop v 10.3.3. IMac (which does NOT work): Mac OS Catalina v 10.15. Microsoft Remote Desktop v 10.3.3.
Before you map the port you'll need the following:
PC internal IP address: Look in Settings > Network & Internet > Status > View your network properties. Find the network configuration with an 'Operational' status and then get the IPv4 address.
Your public IP address (the router's IP). There are many ways to find this - you can search (in Bing or Google) for 'my IP' or view the Wi-Fi network properties (for Windows 10).
Port number being mapped. In most cases this is 3389 - that's the default port used by Remote Desktop connections.
Admin access to your router.
Warning
You're opening your PC up to the internet - make sure you have a strong password set for your PC.
After you map the port, you'll be able to connect to your host PC from outside the local network by connecting to the public IP address of your router (the second bullet above).
The router's IP address can change - your internet service provider (ISP) can assign you a new IP at any time. To avoid running into this issue, consider using Dynamic DNS - this lets you connect to the PC using an easy to remember domain name, instead of the IP address. Your router automatically updates the DDNS service with your new IP address, should it change.
With most routers you can define which source IP or source network can use port mapping. So, if you know you're only going to connect from work, you can add the IP address for your work network - that lets you avoid opening the port to the entire public internet. If the host you're using to connect uses dynamic IP address, set the source restriction to allow access from the whole range of that particular ISP.
You might also consider setting up a static IP address on your PC so the internal IP address doesn't change. How to transfer my gmail contacts to iphone. If you do that, then the router's port forwarding will always point to the correct IP address.
Use a VPN
If you connect to your local area network by using a virtual private network (VPN), you don't have to open your PC to the public internet. Instead, when you connect to the VPN, your RD client acts like it's part of the same network and be able to access your PC. There are a number of VPN services available - you can find and use whichever works best for you.
-->This article provides a solution to an error that occurs when you try to connect to the Terminal service running on one of the affected products.
Original product version: Windows Server 2003
Original KB number: 555382
Symptoms
When you try to connect to the Terminal service running on one of the affected products, you receive the following error message:
Remote Desktop Disconnected
The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to accept new connections.
It is also possible that network problems are preventing your connection.
Please try connecting again later. If the problem continues to occur, contact your administrator.
OK Help
Additionally, when you view System Event log on the affected server you see the following event:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1036
Date: <DateTime>
Time: <DateTime>
User: N/A
Computer: Servername
Description:
Terminal Server session creation failed. The relevant status code was 0x2740.
For more information, see Help and Support Center at.
Resolution
To resolve the problem, make sure that the correct network adapter is bound to RDP-TCP connection. To do it, follow these steps:
- On the server, sign in to the server locally (not using Remote Desktop/Terminal Client).
- Select Start, Run, type tscc.msc /s (without quotation marks and select OK).
- In the Terminal Services Configuration snap-in, double-click Connections, then RDP-Tcp in the right pane.
- Select the Network Adapter tab, select the correct network adapter, and select OK.
- Make sure that you can establish an RDP connection to the server.
Alternative resolution steps.Use these steps only if you can't do local sign-in to the affected server.
Warning
Remote Desktop Troubleshooting
Using Registry Editor incorrectly may cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk and only after making backup of full Registry and the keys you are going to change.
Start Registry Editor (Regedt32.exe).
Select FileConnect network Registry. Enter computer name or IP address and select OK. Firewalls between your computer and the affected server may prevent successful connection. Remote Registry service should be running on the server.
Navigate to the following registry key (path may wrap):
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork{4D36E972-E325-11CE-BFC1-08002BE10318}Under this key are one or more keys for the globally unique identifiers (GUIDs) corresponding to the installed LAN connections. Each of these GUID keys has a Connection subkey. Open each of theGUIDConnection keys and look for the Name value. Choose the connection you want Terminal Services to use.
When you have found the GUIDConnection key that contains the Name setting that matches the name of your LAN connection, write down or otherwise note the GUID value.
Then navigate to the following key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Serverlanatable. Using the GUID you noted in step 5 select subkey. It's LanaId.Navigate to the following value:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-TcpLanAdapter.
Change it's data to the value you noted in step 6. If you want RDP to listen on all LAN adapters enter value of 0.
Microsoft Remote Desktop For Mac
Community Solutions Content Disclaimer
Remote Desktop
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.