The Logon Type field indicates the kind of logon that was requested. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
#Cannot remote desktop to server 2012 from windows 7 keygen
![cannot remote desktop to server 2012 from windows 7 cannot remote desktop to server 2012 from windows 7](https://www.net-usb.com/images/upload/UNG/ung@2x.png)
The Subject fields indicate the account on the local system which requested the logon. This event is generated when a logon request fails. Source: Microsoft-Windows-Security-Auditingįailure Reason: An Error occured during Logon. NOTE: The Server Manager\Remote Desktop Services\Servers screen in Windows Server 2012 shows Event Log information but it appears that it doesn't show everything relevant, because this error didn’t appear there so we chased our tails for a long time before actually finding this error in the Security Event Log. Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.Īfter a lot of time trying to work out why this single user could not connect we found an error in the Security Event Log looking similar to that shown below. Remote Desktop can't connect to the remote computer for one of these reasons:ġ) Remote access to the server if not enabledģ) The remote computer is not available on the network The error message the user was receiving was as follows (however as seems to be the case with RD Gateway sometimes a different connection failure would be randomly returned): The user was able to access the RDWeb page for the server, but launching any applications failed, as did launching them from RemoteApp RDP files.
![cannot remote desktop to server 2012 from windows 7 cannot remote desktop to server 2012 from windows 7](https://i0.wp.com/ravingroo.com/wp-content/uploads/2016/08/windows2012R2screenshot.png)
Having just built a nice new shiny Window Server 2012 VM with Remote Desktop Gateway Services installed we encountered a problem where one user was not able to start RemoteApp applications from their home PC even though they were able to launch them from the 2008 R2 server we were using previously.