Remote Desktop Connection errors - Win 10 Redstone

[morthj]

Hi

After upgrading to the latest Redstone build i've been getting RDP errors when trying to connect to servers in ASGRD 2015 (latest build)
I get two different errors:
'An authentication error has occurred (Code:0x80004005) Remote Computer: <ipaddresshere>
and
'An authentication error has occurred.
The Local Security Authority cannot be contacted
Remote Computer: <ipaddresshere>
This could be due to an expired password.
Please update your pass...
For assistance, contact your admin....'

Connecting to servers work correctly using normal RDP (mstsc.exe)

I'm Running Win 10 Enterprise Build 14316.rs1_release.160402-2217

[DevOma]

Is this a preview/beta build? Didn't test it - but I will do asap...

[morthj]

Hi

It is the latest preview/beta build as fast ring insider.

I can connect to win 2k3 servers, but connecting to windows 2008 and later results in the error above.

[bschleifer]

I can report the same error on the latest insider build. I am on 14316 enterprise.

[stuclark]

I get the same error too on build 14316

Interestingly, ASG-RD 2012 works fine on this build of Windows

[reyesh]

I am having the same exact error. I am on the latest build of Windows 10. I hope there is a solution to this since I use ASG religiously and it is pain to use MSTC when having so many servers to manage.

---

I found a workaround for this problem until a patch is made available. if you open the RD settings on the connection you are trying to make, and disable CREDSSP the connection should work. However, if the settings on the server require network level authentication, then you will not be able to connect.


Connections-->"name of the server"-->RD-->Disable CredSSP

hopefully this will help you.

[david.gerdau]

i have the same error with the newest Windows 10 Build.

as a hint you can multiedit all connections to disable credssp. This should save some time (i have 200 connections in my ASG RD an didn't want to change every single one ;-) ).

[BFDHE]

I will throw my hat in the ring with the same issue. We use NLA, so the disable CredSSP isn't a fix. Looking forward to a patch as single RDP into 100's of servers isn't fun.

[reyesh]

I will throw my hat in the ring with the same issue. We use NLA, so the disable CredSSP isn't a fix. Looking forward to a patch as single RDP into 100's of servers isn't fun.

Tell me about it. I use this tool on a daily basis and it is pain to RDP manually to every server i need to manage.

[DevOma]

I guess at the moment that the newest build needs to have the latest RDP ActiveX - I tried with a test project and it is working - try to add asap - Release 2016 was planned for Friday - so we will decide if we can integrate and perhaps publish version 2016 1 or 2 days later :-)

[Tof006]

I report the same problem on Windows 10 Enterprise build 14316.
I'm using your tool every day... I don't want to go back to manual RDP.
Thanks

[DevOma]

It's fixed already - version 2016 will be available within some days

[Tof006]

It's fixed already - version 2016 will be available within some days

So I just have to wait for it
Thanks

EDIT : is it a free update ?

[BFDHE]

It's fixed already - version 2016 will be available within some days

Where should we look for new version? All Forums are labeled "2015"

[DevOma]

New release will be published today or tomorrow - we will provide links to the new version - update check will also notify for the new version...

[Tof006]

When will we be able to use this new version ? I'm tired of using mstsc over 250 servers...
Thanks

[DevOma]

Will be available in some minutes :-)

[bschleifer]

I am now getting an NLA error with this new version. The previous registry hack does not seem to resolve it.

The remote computer '%' requires Network Level Authentication, which is not enabled in the RDP connection properties.

[Tof006]

I'm really happy that, because of a new build of Windows 10, I have to upgrade to 2016... just to see that my license is not valid on 2016 and I have to pay for an update.
Really, I'm annoyed.
Either I downgrade my Windows build or I pay.... Not acceptable

[Tof006]

Now that I've paid for the update, I have the same NLA error....