latxtra.blogg.se - Windows server 2012 remote desktop not working

#Windows server 2012 remote desktop not working full
#Windows server 2012 remote desktop not working code
#Windows server 2012 remote desktop not working windows

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. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. If you want RDP to listen on all LAN adapters enter value of 0. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\LanAdapter.Ĭhange it's data to the value you noted in step 6. Using the GUID you noted in step 5 select subkey. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\lanatable. When you have found the GUID\Connection key that contains the Name setting that matches the name of your LAN connection, write down or otherwise note the GUID value. Choose the connection you want Terminal Services to use. Open each of theGUID\Connection keys and look for the Name value. Each of these GUID keys has a Connection subkey. Under this key are one or more keys for the globally unique identifiers (GUIDs) corresponding to the installed LAN connections. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\ Navigate to the following registry key (path may wrap): Remote Registry service should be running on the server. Firewalls between your computer and the affected server may prevent successful connection. Enter computer name or IP address and select OK.

#Windows server 2012 remote desktop not working full

Use Registry Editor at your own risk and only after making backup of full Registry and the keys you are going to change. Using Registry Editor incorrectly may cause serious problems that may require you to reinstall your operating system. Use these steps only if you can't do local sign-in to the affected server.

Make sure that you can establish an RDP connection to the server.

Select the Network Adapter tab, select the correct network adapter, and select OK.

In the Terminal Services Configuration snap-in, double-click Connections, then RDP-Tcp in the right pane.

Select Start, Run, type tscc.msc /s (without quotation marks and select OK).

On the server, sign in to the server locally (not using Remote Desktop/Terminal Client).

To resolve the problem, make sure that the correct network adapter is bound to RDP-TCP connection.

#Windows server 2012 remote desktop not working code

The relevant status code was 0x2740.įor more information, see Help and Support Center at. If the problem continues to occur, contact your administrator.Īdditionally, when you view System Event log on the affected server you see the following event: Event Type: Error It is also possible that network problems are preventing your connection.

Remote connections might not be enabled or the computer might be too busy to accept new connections. The client could not connect to the remote computer. When you try to connect to the Terminal service running on one of the affected products, you receive the following error message:

#Windows server 2012 remote desktop not working windows

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.Īpplies to: Windows Server 2003 Original KB number: 555382 Symptoms