Posts: 678
Threads: 34
Joined: Aug 2006
Reputation:
17
Hi,
which exact version are you using ? Normally that error should not occur since a fix is already implemented. There is a manual fix for that "problem" that should not be needed any more (
https://remotedesktop.rocketsoftware.com...311&page=2 ) so that could be a quick workaround. And you already verified the correct setting as shown on your screenshot. What makes me wonder is that only some servers are affected so I assume they differ in some way to the working servers. What about udates on theses servers ?
best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Posts: 52
Threads: 24
Joined: Jan 2018
Reputation:
0
28-06-2018, 07:04 AM
(This post was last modified: 28-06-2018, 07:08 AM by chengjian.ye.)
Hello, my PC is Windows 10 Enterprise.
Version 1703 (15063.1088)
Server is Windows Server 2012 R2 standard.
Version 6.3 (Build 9600)
ASG RD 2018 ver 11.0.5924.0
Posts: 678
Threads: 34
Joined: Aug 2006
Reputation:
17
Thanks for your feedback,
hmm.. unfortunately my oldest Win10 is version 1709 and I tested that to connect to Win 2012R2 Server - Build 9600 - without any problems. And I used ASG-RD 2018P3 ( your version) also... no probs. So the only difference is the version of Windows 10. Is your Windows 2012 Server configured as a Remote Desktop Gateway ? Because Version 1703 of Windows 10 breaks RDP connectivitiy with RD GW servers and has issues with RDP. There are reports of people downgrading or upgrading to prevent those connectivity problems. Can't test it right now because I just have Windows 10 build 1709 and 1803 . Please see that
link
best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --