31-03-2014, 02:47 PM
Is there now a solution around?
We have excatly the same error on our Windows Server 2012 R2.
Thanks
We have excatly the same error on our Windows Server 2012 R2.
Thanks
Windows 8.1 rtm issue RDP
|
31-03-2014, 02:47 PM
Is there now a solution around?
We have excatly the same error on our Windows Server 2012 R2. Thanks
We are deploying Windows 2012 R2 servers with the "Allow connections only from computers running RDP with network level Authentication" enabled.
I too am getting the error: The remote computer requires Network Level Authentication, which your computer does not support. The registry settings listed here don't fix my issue. I'm using ASG-RDversion 2012 7.3.4144.0 Installed on Windows 8.1 (I also tested on win 7 with same results) Connecting to Server 2012 R2 Datacenter
02-04-2014, 08:47 AM
No other solution at the moment - but reg edit should solve the problem...
Regards/Gruss
Oliver
16-04-2014, 09:43 PM
Registry changes worked for me.
04-08-2014, 10:13 PM
Any update to this? New patch? will 2014 fix this?
01-09-2014, 07:58 PM
When is it going to be released...???
02-09-2014, 09:58 AM
We will discuss it today - dev wants to release until friday - QA find still issues...
Regards/Gruss
Oliver
07-10-2014, 02:47 PM
Just an FYI, this is also an issue on Windows 10 technical preview, but the listed regfix fixes this on Windows 10 as well. When is 2014 going to be released?
07-10-2014, 03:09 PM
Currently we have RC4 and it's quite stable - at the moment we have the problem that another product line is going to be released and all test resources are shifted to that QA - and afterwards some people will be on vacation - so we do not get the QA for ASG-RD at the moment...
The RC-version will be updated as often as needed to support full functionallity - and it is fully supported, can be upgraded and so on... I do not have an RTM date at the moment (but will be in October)
Regards/Gruss
Oliver
To add to the thread for people that are trying the registry change but still getting the NLA error, note that you should be entering it on a separate line.
To recap from alkaline: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa In the details pane, right-click Security Packages, and then click Modify. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK. Below "" enter tspkg, mine looks like: "" tspkg That was the fix to get my copy of ASG-Remote Desktop 2012 (7.3.4144.0) working.
Hello,
I have done the register change and even installed the 2014 version RC5. But I'm still having the same issue. Any help would be greatly apriciated ?
20-11-2014, 09:41 PM
Which client system do you use? It was a rek key change from MS and we check only the RegKey - so if it not working on Win8/8.1 could you give me an export of your registry hive "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control"
Regards/Gruss
Oliver
21-11-2014, 10:40 AM
I still have problems, after I changed the reg key:
"" tspkg The NLA Message disappears, but when I try to connect to the server, nothing happens.
26-11-2014, 04:51 PM
Did you try to set other "Server Authentication" values? I don't know how you set this (Connection=>RDP=>Connection" - because there are 2 different things - one is the wrong check in version 2012 - and the other is "connecting to the server using mstsc-ActiveX" - if the connect does not work it must be something else
Regards/Gruss
Oliver
02-03-2015, 12:26 AM
(01-11-2014, 12:59 AM)Ro923 Wrote: To add to the thread for people that are trying the registry change but still getting the NLA error, note that you should be entering it on a separate line. FYI this workaround also works on Windows 10 TP 2 |
« Next Oldest | Next Newest »
|