Posts: 4
Threads: 1
Joined: Sep 2013
Reputation:
0
When I connect from ASG Remote Desktop 2012 v8, installed on an Windows 8.1 rtm machine, to for example an Windows 2012 machine, I get the notification: The remote computer 'X' requires Network Level Authentication, which your computer does not support.
Is this an known error and when will a patch be available?
Of course a sollution to this error is disabeling the need of Network Level Authentication in de Remote Desktop settings, but this isn't a nice sollution.
Posts: 15
Threads: 3
Joined: Sep 2011
Reputation:
0
Works here... 8.1 -> 2012 / 2012 R2
Are you able to RDP in with "normal" RDP?
Posts: 4
Threads: 1
Joined: Sep 2013
Reputation:
0
(02-09-2013, 02:52 PM)MichelZ Wrote: Works here... 8.1 -> 2012 / 2012 R2
Are you able to RDP in with "normal" RDP?
Connecting through normal RDP on the 8.1 RTM machine is no problem. No errors there. Only with ASG. Tried it on two different 8.1 RTM machines.
Connecting through ASG on the Windows 8.1 Release Preview was also no problem.
Connecting to 2012 R2 RTM is no problem by the way.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
I will try to reproduce asap
Regards/Gruss
Oliver
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
I also have no problems using ASGRD on Win8.1 and connect to W2K12 servers...
Regards/Gruss
Oliver
Posts: 2
Threads: 0
Joined: Sep 2013
Reputation:
0
08-09-2013, 11:17 PM
(This post was last modified: 08-09-2013, 11:18 PM by R2Arjan.)
Having exactly the same issues here.
Using the "leaked" Windows 8.1 version build 6.3.9600 (this version is supposed to be the RTM version)
NLA is not available on this computer.
I tried to start with and without administrator rights.
When i start remote desktop manually it works fine.
I have tried patch 7 and 8, but the error remains.
Posts: 1
Threads: 0
Joined: Sep 2013
Reputation:
0
I can confirm that this is an issue with the ASG Windows 8.1 RTM rdp client integration. Works fine if you connect to a machine that doesn't require NLA.
Windows 8.1 preview had no issues. Seems like Microsoft changed something in the RDP client for the RTM version.
I'm not running the leaked 8.1 version but the one you get as TAP partner, which is the real deal but I guess exactly the same.
Posts: 1
Threads: 0
Joined: Sep 2013
Reputation:
0
10-09-2013, 07:24 AM
(This post was last modified: 10-09-2013, 07:25 AM by alkaline.)
I have found this issue may not be due to a problem with the Remote Desktop tool but an issue with windows 8.1.
This is with the Windows 8.1 release from MSDN/Technet
• Configure Network Level Authentication
1. Open Regedit.
2. In the navigation pane, locate and then click the following registry
subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
I was left with "" and tspkg
5. In the navigation pane, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK. (This was already in my config so I didn't change it)
8. Exit Registry Editor.
9. Restart the computer.
Once done, ASG RD worked fine for all my connections again.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Thanks for your investigation :-)
Regards/Gruss
Oliver
Posts: 2
Threads: 0
Joined: Sep 2013
Reputation:
0
10-09-2013, 08:51 AM
(This post was last modified: 10-09-2013, 08:52 AM by R2Arjan.)
(10-09-2013, 07:24 AM)alkaline Wrote: I have found this issue may not be due to a problem with the Remote Desktop tool but an issue with windows 8.1.
This is with the Windows 8.1 release from MSDN/Technet
• Configure Network Level Authentication
1. Open Regedit.
2. In the navigation pane, locate and then click the following registry
subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
I was left with "" and tspkg
5. In the navigation pane, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK. (This was already in my config so I didn't change it)
8. Exit Registry Editor.
9. Restart the computer.
Once done, ASG RD worked fine for all my connections again.
I can confirm, this solution works.
Posts: 4
Threads: 1
Joined: Sep 2013
Reputation:
0
(10-09-2013, 07:24 AM)alkaline Wrote: I have found this issue may not be due to a problem with the Remote Desktop tool but an issue with windows 8.1.
This is with the Windows 8.1 release from MSDN/Technet
• Configure Network Level Authentication
1. Open Regedit.
2. In the navigation pane, locate and then click the following registry
subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
I was left with "" and tspkg
5. In the navigation pane, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK. (This was already in my config so I didn't change it)
8. Exit Registry Editor.
9. Restart the computer.
Once done, ASG RD worked fine for all my connections again.
Thanks for the suggestion. For me this sollution doesn't work. In fact I only get more problems.
- I changed the value on No.3 to "" and tspkg
- The value on No.7 was already credssp.dll
- I rebooted the system
- I still have the same problem
The system I changed it on shows a black screen after this change when I connect to it with RDP.
I'm also using the Technet download now by the way.
Posts: 7
Threads: 4
Joined: Mar 2010
Reputation:
0
This worked for me on Win 8.1 Pro RTM by changing Security Packages value to only have tspkg ie I replaced ""
Posts: 4
Threads: 1
Joined: Sep 2013
Reputation:
0
Thanks! This solved it for me as well.
(15-09-2013, 03:19 AM)leinad Wrote: This worked for me on Win 8.1 Pro RTM by changing Security Packages value to only have tspkg ie I replaced ""
Posts: 1
Threads: 0
Joined: Nov 2013
Reputation:
0
Thx! It worked for me as well. I only had a little Problem with the Security Package Registry Key:
First i put tspkg right behind "" which didn't work. I then tried it with a space between "" and tspkg which didn't work either...
I had type tspkg in the next line
Security Packages now Looks like this:
""
tpksg
Then it worked instantly even without a reboot.
Posts: 1
Threads: 0
Joined: Mar 2010
Reputation:
0
Same problem here.
Tried to modify the register keys without success.
Posts: 3
Threads: 1
Joined: Dec 2013
Reputation:
0
(10-09-2013, 07:24 AM)alkaline Wrote: I have found this issue may not be due to a problem with the Remote Desktop tool but an issue with windows 8.1.
This is with the Windows 8.1 release from MSDN/Technet
• Configure Network Level Authentication
1. Open Regedit.
2. In the navigation pane, locate and then click the following registry
subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
I was left with "" and tspkg
5. In the navigation pane, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK. (This was already in my config so I didn't change it)
8. Exit Registry Editor.
9. Restart the computer.
Once done, ASG RD worked fine for all my connections again.
Above solved my problem on OEM reinstall Windows 8.1 Pro.
Posts: 6
Threads: 0
Joined: Sep 2009
Reputation:
0
Windows 8.1 Enterprise.
This solution worked for me. I only had to add the tspkg entry as credssp.dll was already present.
Posts: 4
Threads: 0
Joined: Dec 2013
Reputation:
0
Hello
I have upgrade to Win8.1 enterprise build 6.3.9600
I have tried 3 version of visionapp vRDP2012_P4 P7 and the latest P8 and I have the same behavior in all version
when I connect with the normal mstsc.exe I get a good performance, but when I connect with vRDP it's really lagging, character appear slowly and windows are hard to move once connected.
I dont' have any error connecting but, it's really slooooow.
is there anything I could look for to improve this situation.
regards
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
I'm sorry, some people have performance problems - but I couldn't reproduce it at the moment - but we will offer some more time to find the reason and a possible solution - but not this year anymore - too many people on vacation
Regards/Gruss
Oliver
Posts: 4
Threads: 0
Joined: Dec 2013
Reputation:
0
Understand, if you I can help in anyway, let me know.
regards
|
