Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Really? I could reproduce the issue on Win10 clients - and now it is working fine if I use the newest version. Did you check that you are really using the right build version (version from FTP server instead of standard download server)?
Which configuration do you have - client and destination?
Regards/Gruss
Oliver
Posts: 13
Threads: 1
Joined: Sep 2015
Reputation:
-1
20-04-2016, 02:18 PM
(This post was last modified: 20-04-2016, 02:32 PM by Tof006.)
Same as RCollewijn. I still have the same issue... and using 5223...
I'm using Windows 10 build 14316 Enterprise and connecting to Windows Server 2012 R2
What's the address of your FTP ? I've downloaded from the link that is 2 post before
Do I need to uninstall version 2015 ?
Posts: 24
Threads: 5
Joined: May 2009
Reputation:
0
Hi,
same issue with version 9.0.5223.0 also
Regards
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Win10 Build 14316 is not working at the moment - I know that - but for standard win10 it should work! We will try to find the issue with Preview build right now...
Regards/Gruss
Oliver
Posts: 2
Threads: 1
Joined: Apr 2016
Reputation:
0
9.0.5223.0 is working for me on Windows 7. Haven't tried any of my Win10 machines yet.
Posts: 1
Threads: 0
Joined: Apr 2016
Reputation:
0
Hi,
gleiche Problem mit der Version ASG2016 9.0.5223.0 und Windows 10 build 14316 Enterprise
Windows 10 build 14295 Enterprise funktioniert mit ASG2015/ASG2016 einwandfrei.
Posts: 2
Threads: 0
Joined: Apr 2016
Reputation:
0
I am now able to log into my W12R2 servers as well as my w2k8r2 server with no issues on this 5223 build.
Posts: 5
Threads: 2
Joined: Apr 2008
Reputation:
0
I have installed ASG Remote Desktop 2016 parallel to 2015 on Windows 10:
Windows 10 Pro x64, Version 1511 (OS Build 10586.218)
ASG Remote Desktop 2015 works without any problems.
ASG Remote Desktop 2016 does NOT allow connection to a Windows 2012 Enterprise Server
It shows the famous "The remote computer <ip> requires Network Level Authentication, which is not enabled in the RDP connection properties."
I am already using the mentioned version ASG2016 9.0.5223.0, but this did not change anything.
Please advise what to do.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
This should work now - perhaps a reboot of the machine is needed? Or did you try to uninstall and reinstall? The new Interop-Dll for MSTSC muss be in your directory - but the build number seems to be ok...
Regards/Gruss
Oliver
Posts: 24
Threads: 5
Joined: May 2009
Reputation:
0
Hi
full uninstall ASG RDP 2015 and 2016 (both versions)
install ASG RDP 2016
is working now ASG RDP 2016 version 9.0.5223.0
Regards.
Posts: 10
Threads: 3
Joined: Apr 2016
Reputation:
0
We did also a full uninstall and cleanup. After this we did a clean install, but the problem is still there.
We are working with Windows 10 x64 version (I read this on a other post) and it is not possible to change 6 management stations back to Windows 10 x86 versions.
Fortunately, there is only one management station with this problem because the rest is not yet upgraded, but it's pretty irritating and one management station is out of order.
I hoop they find a solutions quickly.
Robert
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Latest Win10 Beta build will resolve the problem - it was a bug in the previous windows build
Regards/Gruss
Oliver
Posts: 10
Threads: 3
Joined: Apr 2016
Reputation:
0
Everybody talks about the 14316 version and waiting for a the new Windows build.
But what about the problems with Windows x64 build 10586. We are still waiting for a solutions and before you begin with all kinds off trail and error attempts. Every suggestion from this forum we have already tried (except the Windows x32 version).
We hope that a solution is available in a short time, or must we look for a other program (are license is expires in a few mouths).
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
There should be no problems with standard Win10 builds anymore - do you use version 9.0.5223.0? We successfully tested it and many customers confirmed that the issue is solved
Regards/Gruss
Oliver