Event ID 702 — RD Gateway Server Configuration
Applies To: Windows Server 2008 R2
For remote clients to successfully connect to internal network resources (computers) through a Remote Desktop Gateway (RD Gateway) server, the RD Gateway server must be configured correctly. The RD Gateway server must be configured to use an appropriate Secure Sockets Layer (SSL)-compatible X.509 certificate, and authorization policy settings must be configured correctly. Remote Desktop connection authorization policies (RD CAPs) specify who can connect to the RD Gateway server. Remote Desktop resource authorization policies (RD RAPs) specify the internal network resources that clients can connect to through an RD Gateway server.
|Product:||Windows Operating System|
|Message:||The exception code "%2" occurred in the authorization plug-in: "%1" loaded by the RD Gateway server. The RD Gateway server will be restarted. Continued failures might indicate a problem with the authorization plug-in.|
Register the authorization plug-in
To resolve this issue, do the following:
- Register the authorization plug-in
- Check the permissions on the authorization plug-in registry key
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Register the authorization plug-in
You can register the authorization plug-in by registering the DLL on the RD Gateway server, configuring the RD Gateway plug-in by registering it with WMI, and then restarting the RD Gateway service.
- Click Start, point to All Programs, point to Accessories, and then click Commmand Prompt.
- Navigate to the directory where the plug-in resides.
- Type regsvr32.exe <plugin>, where <plugin> is the name of the plug-in file, and then press ENTER.
- Call the WMI method SetAuthorizationPlugin to configure the authorization plug-in for RD Gateway.
- Restart the RD Gateway service.
Check the permissions on the authorization plug-in registry key
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
You can check the permissions on the authentication plug-in registry key by using Registry Editor.
To check the permissions on the authorization plug-in registry key:
- On the RD Gateway server, click Start, click Run, type regedit and then press ENTER.
- Navigate to the HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Gateway\Authorization plug-ins subkey, right-click the subkey, and then click Permissions.
- In the Permissions for Authorization plug-ins dialog box, under Group or user names, click SYSTEM. Under Permissions for SYSTEM, if Full control is not allowed, select the Allow check box adjacent to Full control.
- In the same dialog box, under Group or user names, click Administrators. Under Permissions for Administrators, if Full control is not allowed, select the Allow check box adjacent to Full control.
- Click OK.
To verify that the RD Gateway server is configured correctly, examine Event Viewer logs and search for the following event messages. These event messages indicate that the Remote Desktop Gateway service is running, and that clients are successfully connecting to internal network resources through the RD Gateway server.
To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.
To verify that the RD Gateway server is configured correctly:
- On the RD Gateway server, click Start, point to Administrative Tools, and then click Event Viewer.
- In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-Gateway, and then search for the following events:
- Event ID 101, Source TerminalServices-Gateway: This event indicates that the Remote Desktop Gateway service is running.
- Event ID 200, Source TerminalServices-Gateway: This event indicates that the client is connected to the RD Gateway server.
- Event ID 302, Source TerminalServices-Gateway: This event indicates that the client is connected to an internal network resource through the RD Gateway server.