Understanding TS Gateway Event Types

Applies To: Windows Server 2008

By using TS Gateway Manager, you can specify the types of events that you want to monitor, such as unsuccessful or successful connection attempts to internal network resources (computers) through a TS Gateway server.

The following table lists and describes the TS Gateway event types that you can monitor. For information about how to select the TS Gateway event types that you can monitor, see Specify TS Gateway Events to Log.

 

Event name Description Event ID

Successful User Disconnection from the Resource

By monitoring the timestamp for this event and the related Successful User Connection to the Resource event, you can verify the user session time and the amount of data (in kilobytes) that was sent and received by the client through the TS Gateway server.

303: When the client disconnects from the resource

202: When an administrator disconnects the client

Failed User Connection to the Resource

The remote client met the conditions specified in the Terminal Services connection authorization policy (TS CAP) and the Terminal Services resource authorization policy (TS RAP), but could not connect to the internal network resource (computer) through the TS Gateway server because the computer was unavailable.

By auditing this event, you can determine which connectivity issues are caused by problems with Terminal Services and Remote Desktop rather than the TS Gateway server.

304

Failed Connection Authorization

The remote client could not connect to a TS Gateway server because the client did not meet the conditions specified in the TS CAPs.

201

Failed Resource Authorization

The remote client could not connect through a TS Gateway server to the specified computer because no TS RAPs are configured to allow the user access to the specified computer.

For example, this issue might occur if the user attempts to connect to the computer by using its NetBIOS name when the TS RAP configured on the TS Gateway server uses an FQDN name for the remote computer.

301

Successful User Connection to the Resource

The remote client successfully connected to a computer through the TS Gateway server.

302

Successful Connection Authorization

The remote client successfully connected to the TS Gateway server because the client met the conditions specified in at least one TS CAP.

200

Successful Resource Authorization

The remote client successfully connected through the TS Gateway server to the specified internal network resource because the client met the conditions specified in at least one TS RAP.

300

Community Additions

ADD
Show: