Skip navigation

JSI Tip 1584. Difficulty with Terminal Server Client connects.

If Terminal Server Clients are unable to connect, or browse some servers, it may be a tuning issue.

Various problems may be exhibited:

System could not log you on because domain <domainname> is not available.

You do not have access to logon to this session.

If the Terminal Server is a member server, the domain controller event log may contain any of the following:

Error 1727: The remote procedure call failed and did not execute

Event ID: 1311
Source: NetLogon
Description: There are currently no logon servers available to service the logon request.

Error 1722: The RPC server is unavailable.

Error 1723: The RPC server is too busy to complete this operation.

Error 1721: Not enough resources are available to complete this operation.

These errors do not appear to be dependent upon the the number of Licenses (License Logging Service), the amount of RAM, CPU speed, or number of CPUs on either the Terminal Server or domain controller.

To resolve this issue, try tuning MaxWorkItems and MaxMpxCt at:


in the domain controller.

NOTE: MaxWorkItems must be at least 4 times the value of MaxMpxCt.

NOTE: See tips 1181,1157, and 1123.

NOTE If you have W9x clients, see Q232890.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.