| Event Information | According to Microsoft :
Cause :
This event is logged when the user on client computer did not meet connection authorization policy requirements and was therefore not authorized to access the TS Gateway server.
Resolution :
Ensure that the client meets the requirements of the TS CAP
To resolve this issue, ensure that the clients meet the requirements of at least one Terminal Services connection authorization policy (TS CAP).
To determine whether a client meets the requirements of at least one TS CAP, do the following:- Check the TS CAP settings on the TS Gateway server. For instructions, see "Check TS CAP settings on the TS Gateway server" later in this topic.
- Ensure that the local or Active Directory security group specified in the TS CAP exists, and that the user account for the client is a member of the appropriate security group.
Check TS CAP settings on the TS Gateway server
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check TS CAP settings on the TS Gateway server:- Open TS Gateway Manager. To open TS Gateway Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Gateway Manager.
- In the TS Gateway Manager console tree, select the node that represents the local TS Gateway server, which is named for the computer on which the TS Gateway server is running.
- In the console tree, expand Policies, and then click Connection Authorization Policies.
- In the results pane, in the list of TS CAPs, right-click the TS CAP that you want to check, and then click Properties.
- On the Requirements tab, do the following:
- Under Supported Windows authentication methods, check whether the specified method is compatible with the authentication method used by the client. The user on the client must use the same authentication method that is specified in the TS CAP.
- In User group membership (required), note the name of the user group so that you can ensure that the specified user group exists in Active Directory Domain Services or Local Users and Computers. Then, check whether the user account for the client is a member of this group.
- Under Client computer group membership (optional), check whether a client computer group is specified. If so, note the name of the client computer group so that you can ensure that the specified client computer group exists in Active Directory Domain Services or Local Users and Computers. Then, check whether the computer account for the client is a member of this group.
- Click OK.
- If the client settings and TS CAP settings are not compatible, do one of the following:
- Modify the client configuration.
- Modify the settings of the existing TS CAP.
- Create a new TS CAP.
Performing these procedures does not require membership in the local Administrators group. Therefore, as a security best practice, consider performing these tasks as a user without administrative credentials.
Confirm that the Active Directory security group specified in the TS CAP exists, and check account membership for the client in this group
To confirm that the Active Directory security group specified in the TS CAP exists:- On a computer running Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then press ENTER.
- In the console tree, expand Active Directory Users and Computers/DomainNode/, where the DomainNode is the domain to which the security group belongs.
- Right-click the domain, and then click Find. In the Find Users, Contacts, and Groups dialog box, type the name of the security group that is specified in the TS RAP, and then click Find Now.
- If the group exists, it will appear in the search results.
- Close the Find Users, Contacts, and Groups dialog box.
To check account membership for the client in this security group:- On a computer running Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then press ENTER.
- In the console tree, expand Active Directory Users and Computers/DomainNode/Users, where the DomainNode is the domain to which the user belongs.
- In the details pane, right-click the user name, and then click Properties.
- On the Member Of tab, confirm that one of the groups listed matches one of the groups that is specified in the TS CAP, and then click OK.
- If client computer group membership has also been specified as a requirement in the TS CAP, expand Active Directory Users and Computers/DomainNode/Computers, where the DomainNode is the domain to which the computer belongs.
- In the details pane, right-click the computer name, and then click Properties.
- On the Member Of tab, confirm that one of the groups listed matches one of the groups that is specified in the TS CAP, and then click OK.
Confirm that the local security group specified in the TS CAP exists, and check account membership for the client in this group
To confirm that the local security group specified in the TS CAP exists, and to check account membership for the client in this group:- On the TS Gateway server, open Computer Management. To open Computer Management, click Start, point to Administrative Tools, and then click Computer Management.
- In the console tree, expand Local Users and Groups, and then click Groups.
- In the results pane, locate the local security group that has been created to grant members access to the TS Gateway server (the group name or description should indicate whether the group has been created for this purpose).
- Right-click the group name, and then click Properties.
- On the General tab of the Properties dialog box for the group, confirm that the user account is a member of this group, and that this group is one of the groups that is specified in the TS CAP.
- If client computer group membership has also been specified as a requirement in the TS CAP, on the General tab, confirm that the client computer account is also a member of this group, and then click OK.
Verify :
To verify that the TS Gateway server is available for client connections, examine Event Viewer logs and search for the following event messages. These event messages indicate that the Terminal Services Gateway service is running, and that clients are successfully connecting to internal network resources through the TS 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 TS Gateway server is available for client connections:- On the TS 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 Terminal Services Gateway service is running.
- Event ID 200, Source TerminalServices-Gateway: This event indicates that the client connected to the TS Gateway server.
- Event ID 302, Source TerminalServices-Gateway: This event indicates that the client connected to an internal network resource through the TS Gateway server.
|