Windows Server 2016 | Remote Desktop will not connect

Hi guys

I started this blog when I started using Windows 7 initial release and was struck with end number of issues, mostly related networking.

I am turning my attention towards Windows OS, minimum for a while as I am dealing with another Windows OS, that is crap like no other times…Windows Server 2016, which, looks and feels like Windows 10 with server OS capacities (to certain extends). A totally screwed up Server OS which has half of the settings over modern layout and rest on the legacy

This time I am going to discuss about a peculiar situation that arises once after removing “Remote Desktop Services from Windows Server 2016 & trying to initiate a normal RDP session with the server.

It just won’t connect. That’s all. You check for the usual stuffs everywhere and realize that everything is set fine, firewall, permissions. Yet, you won’t able to connect.

After trying to fix “few” things myself, I gave up and started searching for some answers. One of the most interesting things I learned about Windows Server 2016 is, there are hardly any forums discussing anything at all about this particular OS. 99% of the results I am provided were either for Windows Server 2008  or 2012 & for few situations not a single result for 2016!

Anyway I landed on this thread

https://social.technet.microsoft.com/Forums/en-US/bb34981e-9489-4a0c-80fc-6fdea2cd5cd3/remote-desktop-not-working-after-uninstalling-remote-desktop-session-host-server?forum=winserverTS

& by the bottom of the page found a link to Dell site where a solution was provided for Windows Server 2012 R2 to recreate the RDP-TCP registry values. As I was dealing with a VM, which is already backup, I decided to give it a try

http://www.dell.com/support/article/us/en/04/sln286475/how-to-recreate-or-add-an-additional-rdp-listener-in-windows-server-2012-and-2012-r2?lang=en

I’m copying the instructions here, for the reasons that the above link may not be available after a while.

1. Recreate the default RDP Listener
How to recreate the RDP listener.
1. Export the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
2. Delete the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
3. Copy and paste the below text into notepad, and save the file as RDP-Tcp.reg. Additionally, if the operating system is 2012 R2, another file will be required with the contents of the second box.

[code language=”text” gutter=”false”]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
“fInheritMaxIdleTime”=dword:00000001
“fPromptForPassword”=dword:00000000
“fResetBroken”=dword:00000000
“PdClass”=dword:00000002
“LoadableProtocol_Object”=”{5828227c-20cf-4408-b73f-73ab70b8849f}”
“UserAuthentication”=dword:00000001
“fDisableCam”=dword:00000000
“fInheritAutoLogon”=dword:00000001
“InteractiveDelay”=dword:00000032
“Domain”=””
“fInheritReconnectSame”=dword:00000001
“SelectTransport”=dword:00000000
“MinEncryptionLevel”=dword:00000002
“fInheritShadow”=dword:00000001
“WFProfilePath”=””
“fReconnectSame”=dword:00000000
“PdDLL”=”tdtcp”
“PortNumber”=dword:00000d3d
“PdFlag1″=dword:00000000
“WdName”=”Microsoft RDP 8.0”
“fInheritMaxSessionTime”=dword:00000001
“WdFlag”=dword:00000036
“SelectNetworkDetect”=dword:00000000
“fLogonDisabled”=dword:00000000
“MaxDisconnectionTime”=dword:00000000
“Callback”=dword:00000000
“PdDLL1″=”tssecsrv”
“NWLogonServer”=””
“MaxIdleTime”=dword:00000000
“fDisableEncryption”=dword:00000001
“fInheritCallback”=dword:00000000
“fDisableCcm”=dword:00000000
“ColorDepth”=dword:00000003
“PdName”=”tcp”
“fEnableWinStation”=dword:00000001
“OutBufLength”=dword:00000212
“PdFlag”=dword:0000004e
“CallbackNumber”=””
“CdClass”=dword:00000000
“Shadow”=dword:00000001
“fDisableCdm”=dword:00000000
“PdName1″=”tssecsrv”
“fInheritSecurity”=dword:00000000
“CdDLL”=””
“LanAdapter”=dword:00000000
“fInheritResetBroken”=dword:00000001
“CfgDll”=”RDPCFGEX.DLL”
“InitialProgram”=””
“fDisableClip”=dword:00000000
“InputBufferLength”=dword:00000800
“fAllowSecProtocolNegotiation”=dword:00000001
“fDisableAudioCapture”=dword:00000000
“Password”=””
“CdName”=””
“fDisableLPT”=dword:00000000
“CdFlag”=dword:00000000
“PdClass1″=dword:0000000b
“fAutoClientLpts”=dword:00000001
“fAutoClientDrives”=dword:00000001
“fInheritCallbackNumber”=dword:00000001
“OutBufCount”=dword:00000006
“fInheritMaxDisconnectionTime”=dword:00000001
“MaxInstanceCount”=dword:ffffffff
“KeyboardLayout”=dword:00000000
“fDisableExe”=dword:00000000
“AudioEnumeratorDll”=”rdpendp.dll”
“Username”=””
“KeepAliveTimeout”=dword:00000000
“fUseDefaultGina”=dword:00000000
“fHomeDirectoryMapRoot”=dword:00000000
“fInheritColorDepth”=dword:00000000
“fForceClientLptDef”=dword:00000001
“WorkDirectory”=””
“SecurityLayer”=dword:00000001
“DrawGdiplusSupportLevel”=dword:00000001
“WdPrefix”=”RDP”
“fInheritAutoClient”=dword:00000001
“fDisableCpm”=dword:00000000
“Comment”=””
“OutBufDelay”=dword:00000064
“fInheritInitialProgram”=dword:00000001
“MaxConnectionTime”=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\VideoRemotingWindowNames]
“AGFullScreenWinClass”=”*”
“MacromediaFlashPlayerActiveX”=”*”
“EVRVideoHandler”=”*”
“MicrosoftSilverlight”=”*”
“ShockwaveFlashFullScreen”=”*”

[/code]

Additional 2012 R2 values:

[code language=”text” gutter=”false”]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
“UserAuthenticationBackup”=dword:00000000
“MaxMonitors”=dword:00000004
“MaxXResolution”=dword:00000a00
“MaxYResolution”=dword:00000640

[/code]

4. Double-click the RDP-Tcp.reg file and click Yes at the prompt.

Now, restart the box & you are back in the game once again.

Try it in case if you are “also” stuck & let me know about your experiences through comments.

regards,

rajesh

 

 

 

3 thoughts on “Windows Server 2016 | Remote Desktop will not connect

  1. Steve

    Hi Rajesh,

    Very interesting.

    I wonder if you can help me with something? I have a situation whereby I cannot run a published app from a Windows 10 client. It works perfectly well from Win7 PCs, Win 2008, 2012 and 2016 servers. But if I log into RDWEb from a Win 10 PC I can’t run the published apps. I get “logon attempt failed” every time – unless I add a registry value of “RDGClientTransport=1” to HKCU\software\Microsoft\TerminalServices on the client.
    That forces the connection to use RCP over HTTP and it works perfect;y. I cannot though add that key to the HKCU of every remote user registry.

    Do you know if there is a server side solution for this at all?

    Regards

    Steve

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.