Remote Desktop The Logon Attempt Failed Rd Gateway

So, my knowledge on Remote desktop services is not so good, but I managed to get it up and running last year, it's been working just fine for eight months. Now today no Remote desktop users can login. Console sessions are working fine though. I checked and the licensing is okay, no errors. But users trying to login are logged in the security. Devil may cry 5 gamefaqs ps4. I could get into the RemoteApps site, but when trying to launch an application I got prompted for my credentials and 'the logon attempt failed' at the bottom of the logon window. Thanks to Robert's post from above, I found out that it was the redirect I put in IIS7. My setup is one server acting as Gateway, Broker, and Web Access. What is a Remote Desktop Gateway. A Remote Desktop Gateway Server enables users to connect to remote computers on a corporate network from any external computer. The RD Gateway uses the Remote Desktop Protocol & the HTTPS Protocol to create a secure encrypted connection.

We setup an Azure Windows 10 VM for use by a remote contractor. We joined the machine to our Azure AD domain and created credentials for the contractor.

Failed

Remote Desktop The Logon Attempt Failed Rd Gateway Service

Using the contract's credentials, 2 workstations in our office connect fine via RDP. Usingthe same exact RDP file, when me or the contractor try to connect from our workstations we get 'The logon attempt failed'.We don't have a local AD.

Remote

The contractor and I can connect fine via his credentials against the portal. It is only our attempts at connecting via RDP that faile.We have scoured event logs but can't find any errors. We have tried turning off 'Only allow connections from computers running Remote Desktop with NLA' but it makes no difference.Given the fact 2 workstations connect fine while 2 others don't - it seems the problem must somehow be related to the workstations trying to connect and not the VM itself. Any help appreciated.Thanks. I can confirm the same as regards Windows version; host workstation and client are both running build 1703. Windows 10 Pro (not enterprise).In my case, I'm trying to connect to a Hyper-V VM in my development lab. I can connect to the VM using Hyper-V Manager but Enhanced Mode fails to connect.

The Logon Attempt Failed Rdp

There is a key difference between Hyper-V Enhanced Mode and regular RDP:With RDP I get a credential error. With Hyper-V Enhanced Mode I get a certificate error:'A certification authority could not be contacted for authentication. If you are using a Remote Desktop Gateway with a smart card, try connecting to the remote computer using a password. For assistance, contact your system administrator or technical support.' This is a brand new VM and I have not enabled Remote Credential Guard. For testing, I created a new registry DWORD as instructed to enable Remote Credential Guard, but I set the value to '1' instead of '0'.

Remote Desktop The Logon Attempt Failed Rd Gateway Computer

Logon

This has no effect.In my case, the client (source) computer is signed on with my Microsoft account and the destination is signed on with my O365 credential. In O365 I do NOT have AAD DS configured. According to that documentation, with Remote Credential Guard disabledit should just work.I don't know if any of this is helpful for anyone else, but if my situation shows any similarities to Tim's then it's a good bet we found a bug (or at least an 'Undocumented feature').Additional details:I do not have an RDS Gateway in this environment.I do not have on-prem AD in this environment.Azure AD is not on-perm AD integrated.Based on the documentation linked above, the local (client) machine must be domain joined to an integrated on-prem AD or to AAD. I might guess that this is because a client that is not part of the domain will not know where to send the authentication request?Maybe? But that only makes sense if Remote Credential Guard is enabled.