Resolution: this issue occurs because the
administrator has specified a maximum connection limit, and the limit has been
reached. To modify the limit, go to MMC>Terminal Services
Configuration>Connections, double-click a connection, i.e. RDP-TC, then select
the Network Adapter tab. At the bottom of this tab, change Unlimited
connections and Maximum connections.
SYMPTOMS: After a TS client loses the connection
to a Terminal Server, the client can't logon the Terminal Server and the TS
shows the client still connects to the server.
Resolution: Open Terminal Services
Configuration in Administrative Tools, double-click
RDP-Tcp in the Connections folder and click
the Sessions tab. Click to select
Override user settings and check Disconnect
from session, and select 5 minutes or so.
By default, the TS timeout settings are 120 minutes for Connection, 10
minutes for Disconnection, and 30 minutes for Idle. If a client disconnects
(rather than logging off), the session is not terminated. Rather, it is held
in memory so that the client can't reconnect and re-establish the session.
To fix this problem, you need to change timeout settings in TS Connection
When trying to connect to a W2K domain controller running Terminal Services
with Application Server mode for user access, you as
a TS user may receive "The local policy of this system does not permit you to
logon interactively" message. You may not receive this message if you logon
with a member of the following default groups:
Others based on services on the computer
such as TsInternetUser
Also, you will not receive this message when
you logon member and stand-alone servers since they have the users group
included in the "Log on Locally" user right.
issue occurs because the W2K domain controller running Terminal Services does
not have the Users, Authenticated Users, or Everyone global group added to
the Group Policy Object for the "Log on Locally" user right. "Log on Locally"
is a required user right in Microsoft Windows NT 4.0, Terminal Server Edition
and Windows 2000 Terminal Services. To
modify the Group Policy Object for the domain controller, go to
Administrative Tools>Domain Controller Security Policy>Security
Settings>Local Policies>User Rights
Assignment>Policy>Log on Locally>Add>Browse,
click the appropriate group, and then click Add. After
modifying the Group Policy, type
secedit /refreshpolicy machine_policy /enforce
at a command
prompt, press ENTER, and then press ENTER.
When trying to connect to a W2K server
running Terminal Services with the
you may receive "You do not have access to logon to this
Resolutions: this issue occurs because W2K
server running Terminal Services with the Remote Administration mode do not
permit users to logon by the default. Only two concurrent administrator
accounts for server management can connect to a W2K domain controller running
Terminal Services configured to use Remote Administration mode.
Resolution: use Active Directory Users and Computers to modify this
setting. To do this, open Active Directory Users and Computers, check "Allow
Logon to terminal server" box under the Terminal Services Profile
tab of the user account.
Causes: 1) the server has reached its
connection limit. Note: Terminal Servers in Remote Administration mode allow a
maximum of 2 concurrent sessions. 2) there are some unused session need to be
Symptoms: 1. When trying to access TS (administration mode), you may get
this message: "The client could not connect to the remote computer. Remote
connections might not be enabled or the computer might be too busy to accept
2. Under TS Manger, it shows Console only and not RDP-Tcp (listener).
Make sure that Remote Desktop is enabled
2. Reset connection
3. Reboot the server.
For consultants, refer to cannot connect to TS page.
A: To take over the control the remote XP
computer, click the Take Control on the top right. If you can't take the
sure Allow helpers to remotely control the computer under Offer Remote
Assistance Setting is enabled. By default, Offer Remote Assistance Settings is
disabled. To do enable it, open Group Policy by running gpedit.msc. go to Local Computer
Policy\Computer Configuration\Administrative Templates\System\Remote Assistance.
who will be giving assistance must be a member of the Local Administrators Group
on the receiving machine or you need to added as a Helper in the Offer Remote
Assistance Group Policy Setting. To add User and Groups to Group Policy: Go to
Offer Remote Assistance Group Policy, and in the Helpers area, click
Show. Click Add and then enter the Domain\user account