Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies To: Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
This section provides a description of client connectivity problems that you might experience when Terminal Server is enabled.
When troubleshooting client connectivity problems, it is most useful to first determine whether there are server configuration issues or problems with network connectivity. Keep in mind that all communication during the Terminal Server Licensing process occurs between the client and the terminal server, and between the terminal server and the license server. The Terminal Server client never communicates directly with the license server. Although Terminal Server Licensing issues often result in error messages appearing on clients, these issues are most frequently caused by problems with the Terminal Server license server or the terminal server.
From the following list, choose the problem that best describes your situation, and then step through the suggested fix:
The remote computer disconnected the session because of an error in the licensing protocol.
The remote session was disconnected because there were network problems during the license protocol.
A licensing error occurred while the client was attempting to connect. (Licensing timed out).
Because of a security error, the client could not connect to the terminal server.
Event ID 26: Your terminal services temporary client license will expire in N days.
Event ID 1026: The terminal server could not locate a license server in the domain.