Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Chicagotech MVP | About Us | Contact Us|


Troubleshooting Terminal Server Issues

A new console session cannot be established
An incorrect client name appears in TS
Solved: An incorrect client name appears in TS
Black screen while connecting to TS 1
Black screen while connecting to TS 2
Solved: Black screen when accessing TS using RDC
"Because of a network error, the session will be disconnected. Please try to reconnect"
Because of a protocol error, detected at the client (code 0x1104) this session will
be disconnected

Can tsweb internally but not from internet
Can't access TS because of multihomed computer
Can’t access TS with error code 0x1104
Can't access TS because of missing Terminal Services
Can access TS on ISA by using RDC but not TSWeb
Can't access TSWeb from the Internet
Can't access TS after installed ISA.
Can't access the server using RDC after changing IP
Can't see Windows XP/2003 in TS Manager
Cannot print to the TS client printer 
Client can't logon
This computer can't connect the to the remote computer
Computer is not configured for remote access
Connectivity to the remote computer could not be established.
Can’t access one of workstations using RWW or RDC
Errors: The license will be expired in x days message even you had the license installed
not be upgraded or renewed"  

Event ID: 1111, 1105 and 1106 - Local printer on TS issues
Faulting application spoolsv.exe or tcpmon.dll
I can't reconnect after disconnecting
If you wish to allow other users to log on to this PC with TS, you will need to change the security settings in GP after AD has been installed
It also possible that network problems are preventing your connection
local policy doesn't permit logon interactively
No suitable protocol found
"No TS licensing server error when run TS license manager"
"No Terminal Services licensing server is available in the current domain or workgroup"

No "Use log on using Dial-Up connection"
Object doesn't support this property or method.
Problem might be due to low virtual memory
Problems with this Web page might prevent it from being displayed properly or functioning properly.
RDC over VPN disconnects in a several minutes
Remote computer disconnected because of licensing protocol
Remote Desktop Connection works at home but office
Remote computer disconnected because of licensing protocol.
Remote connection might not be enabled or the computer might be too busy to accept new connections
RWW - Remote connections might not be enabled
Slow Logoff Terminal Server
SLOW VPN /w CiSCO CLIENT & MS ACCESS to SQL SERVER
Start the following program when the user logs on is grayed out
"The remote session was disconnected because the local computer's client access license could

"The remote session was disconnected because another user has connected to the session"
"The local policy of this system does not permit you to logon interactively."
The local policy of this system does not permit you to logon interactively
– Case Study
"The terminal server has exceeded the maximum number of allowed connections"
"Terminal Server sessions disabled. Remote logins are currently disabled"
The client could not connect to the remote computer by using RWW
The client could not connect to Remote Web Workplace from one office
"The client could not connect to the Terminal server. The server may be too busy"
The client could not connect to the remote computer using TSWeb
"The client  could not establish a connection to the remote computer"
"The client could not connect to the remote computer" - RWW related
The client could not connect to the remote computer - Case Study
The client could not connect to the Terminal server. The server may be too busy. Please try connecting later.
The computer might be too busy to accept new connections - RWW
The connection was lost due to a network error
"The terminal server cannot issue a client license
"
The Terminal server has ended the connection 1
The terminal Server has ended the connection 2
Terminal server has exceeded the maximum number
The TS limits two connections even the TS licensing server has been installed
There was an error found when printing the document “Test Page” to TS003
"Terminal Server has ended the connection"
"Terminal Services Client Disconnected"
"The Licensing Wizard cannot connect to the License Server Registry"
Top 10 Checklists of Group Policy Troubleshooting
Resolutions: TS or RDC client receive blue screen when logon.
TS bottleneck when connecting two sites
TS Error Messages 0 to 7999
TS Event ID 1011
TS license Error message 0x13A7, or 0x1391. 0x13A4, 0xFA1.
TS Logon Screen Takes 15 Seconds to Show Up
TS redirected printer cannot work properly
TS session without username
TS Stop 0x000000ab
TS won't allow remote printing through RDP with Event ID 55
Troubleshooting TS Error Code
TSWeb connect is grayed out
Two profiles when logon TS
"Unable to log you on because of an account restriction"
Unable to obtain Terminal Server User Configuration
VBScript: Remote Desktop Disconnected
"You cannot initiate a Remote Desktop Connection"
"You do not have access to logon to this Session"
You are already connected to the console of this console of this computer
"Your interactive logon privilege has been disabled. Please contact your system administrator"
Users can RDC to a DC but administrators - Case Study
You could not be authenticated on this server.
You must be granted the allow log on through terminal services
"Windows cannot connect to a licensing server"
Winlogon 1209 Unable to obtain terminal server user config
Why I can't see my local drives even I enable it

Troubleshooting Terminal Services Licensing issues
Troubleshooting Remote Desktop Connection
TS & RDC Printing issues

Black screen while connecting to TS

Cause: 1. MTU size may be too high. 2. you may have a print driver problem. 3. The profile is corrupted. 4. Some programs are running in the background.

"Because of a network error, the session will be disconnected. Please try to reconnect"
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.

Can access TS on ISA by using RDC but not TSWeb

Open the port 80. RL062004.

Can't access TSWeb from the Internet

Symptom: you can access TSWeb internally but not from the Internet.

Resolution: make sure all ports are opened.

Can't access TS after installed ISA.

To allow access to TS on ISA from the external interface, you may need to edit the packet filter to open the port 3389. Refer to RL062004.

Client can't logon

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.

 

Errors: The license will be expired in x days message even you had the license installed.

"No TS licensing server error when run TS license manager".

"The remote session was disconnected because the local computer's client access license could not be upgraded or renewed"  

Causes: Installed the TS licenses incorrectly. Refer to case: 0204RS.

Event ID: 1111, 1105 and 1106 - Local printer on TS issues

Causes: TS doesn't have the local printer drivers or can't redirect the local printer.

I can't reconnect after disconnecting

 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 Configuration.

"The local policy of this system does not permit you to logon interactively."

Symptoms: 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:

  • Account Operators
  • Administrators
  • Backup Operators
  • Print Operators
  • Server Operators
  • 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.

Resolutions:This 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.

"You do not have access to logon to this Session"

Symptoms: When trying to connect to a W2K server running Terminal Services with the Remote Administration, you may receive "You do not have access to logon to this Session" message.

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 logoff.

Resolution: this issue occurs  because the administrator has disabled logon by issuing the CHANGE LOGON /DISABLE command. In order to to enable logon, use the CHANGE LOGON /ENABLE command.

"The client could not connect to the Terminal server. The server may be too busy. Please try connecting later"

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 new connections...."

2. Under TS Manger, it shows Console only and not RDP-Tcp (listener).

Resolution: 1. Make sure that Remote Desktop is enabled
2. Reset connection
3. Reboot the server.

For consultants, refer to cannot connect to TS page.

TSWeb connect is grayed out

Q: I have been using my Desktop to access our TS via TSWeb. Now, I received a new laptop. When I try to access the TS using tsweb, the Conenct tab is grayed out and I can't access the TSWeb. Why?

A: You need to install Remote Desktop ActiveX Control. If you don't have rights to do so, have your administrator install it for you.

Q: Why am I unable to control another XP by using Remote Assistance?

A: To take over the control the remote XP computer, click the Take Control on the top right. If you can't take the control, make 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. The user 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

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2017 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.