Error connecting truogh RD Gateway 2012 R2

In some cases you recieve an error when you try to connect trough the RD Gateway using a RDP Connection. The error is a generic error for the user and does not help you to find out the reason.

“Remote Desktop can’t connect to the remote computer “computername” for one of these reasons: …”

1

The Event Viewer on the RD Gateway server shows errors in the Microsoft\Windows\TerminalServices-Gateway\Operational log like this:

The user “domain\username”, on client computer “remote-ip”, did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server.
The following authentication method was attempted: “NTLM”. The following error occurred: “”

Also under the security logs you will find the Event 6274 Audit Failure. Error message: “The authentication or accounting record could not be written to the configured accounting datastore. Ensure that the logfile location is available, has available space, can be written to, and that the directory on the SQL server is available.”

2

Solution

Open up the Server Manager on your RD Gateway Server and expand Roles > Network Policy Server > NPS (Local) > Accounting. In the main section, click the “Change Log File Properties”.

3

 

Uncheck the checkbox “If logging fails, discard connection requests”. If you have a Server Farm for Gateways in use, make sure you configure all the Gateway Server the same way. After that try again to connect.

 

 

 

6 thoughts on “Error connecting truogh RD Gateway 2012 R2”

  1. Thank you for this! Had been trying to troubleshoot this problem and the initial error is unhelpful and indicated a problem with Connection/Resource authorization profiles. I then came across the Security Log message and that led me to your blog post. All working again!

    Like

  2. Unreal, this has been keeping us from standing up a Windows 2019 server for days. Thanks for the great tip! Microsoft is such a $#!+ shop…

    Like

  3. Thank’s a lot Al for this amzing tip!!! You save my life after a lot of days to search solution of this f…..g bug! You are the only to find this! Like YoYo i’am on Windows 2019 Std Server.
    Cheers, Nico

    Liked by 1 person

Leave a Reply to Nicolas Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s