Link to home
Start Free TrialLog in
Avatar of catiline
catiline

asked on

Issues connecting to Windows Server 2012 Remote desktop server with Mobile 6.5

We have approximately 85 MC75A’s and we use the Remote Desktop Mobile client to connect to a Windows server that houses the application used by the MC75A’s. When users remote into the server our application is displayed on the MC75A’s. Our server was Windows Server 2008 Standard.

Our MC75A’s are running Windows Embedded Handheld 6.5 Classic (CE OS 5.2.29040 Build 2940.5.3.12).

We recently deployed a new server running Windows Server 2012 Datacenter 64 bit with the intention of replacing the 2008 server.

The problem is that our MC75A’s cannot connect to the new server using the remote desktop client. When we try to connect to the new server we get the following error message:

“Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again.” The title of the error message is “Connection status”.

I can’t tell what version of the Remote Desktop Mobile client we are running. The file name is wpctsc.exe dated 08-04-2011with a size of 102,896 bytes.
ASKER CERTIFIED SOLUTION
Avatar of hjgode
hjgode
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of catiline
catiline

ASKER

Thank you very much!
Is there anyway to fix this in Windows 2012 R2?
Can't seem to find any Remote Desktop Session Host Configuration.
You have to use local security policy (or group policy).  Run GPEDIT.MSC and navigate to:

Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host.

All the settings are in there.
The trick is to force RDS 2012 R2 to use lower encryption: http://www.hjgode.de/wp/2014/03/12/windows-server-2012-rds-and-windows-mobile-connection-error/

What MS says:

"RDS 2008, 2008R2, and 2012 will not allow connections from older RDP 5.x clients.

To get around this add the following registry key to the RDS Session Host

Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Registry entry: Use512LenPropCert
Data type: REG_DWORD
Value: 0 or 1

This is far less secure (512bit encryption vs 2048bit), and you won't be able to take advantage of the features of later versions of the RDP protocol, but older clients will be able to connect."
Top answer, thanks - only I didn't ask the question so I can't award you any points!  Will happily post one if you like, so you can answer it as I think you deserve it for solving our problem!