Keeping Up with Terminal Services - 14 Mar 2001

Connection Delay When Adding a Printer During a TSE Session
If you use a print server, you might occasionally experience a long delay (from 2 minutes to hours) when you add a printer during a Windows NT Server 4.0, Terminal Server Edition (TSE) session. If you view the printer queue status, you could receive a "Failed to connect, retrying" error message when the problem starts to occur. Running the Net View command for the print server could return error code 1727 ("The remote procedure call failed and did not execute"). If you receive the error message during the delay, you might not be able to connect to other print servers, although the print server might still allow new sessions from other computers and from other TSE-based servers.

This behavior can occur if you reach the maximum open-file handle limit (2048) for the virtual circuit between the TSE-based server and the print server. Typically, all TSE sessions multiplex file-handle operations over one virtual circuit; it's possible to reach this limit. Microsoft article Q290737 explains how you can edit the TSE's registry to force each client to negotiate its own virtual circuit to a remote server. (In Windows 2000, the limit is 8192, so this registry hack doesn't apply.)

Loading Printer Drivers From a Trusted Source
It's important to use the right printer drivers. Citrix MetaFrame XP includes printer-driver management, but if you use an earlier version of MetaFrame or aren't using it at all you have another option: Specify a path to a trusted print server, as Microsoft article Q239536 explains.

Post-SP6 Hotfix for Slow termsrv Process Performance
This item could get the "most vaguely worded Microsoft article of the week" award. According to Microsoft article Q291798, when the termsrv.exe process (the service required to support Windows 2000 Server Terminal Services) is running, "a performance loss may occur," and this problem could be more noticeable "when you start programs." This would seem to be a problem for a terminal server. Certain unnamed registry keys apparently cause the problem. Microsoft has a hotfix; the article explains how to get it.

Workaround for Connecting Clients to Load-Balanced Terminal Server
If you've installed Network Load Balancing (NLB) on a Win2K-based server that runs Terminal Services, the system could reject a client that attempts to connect to the cluster TCP/IP address with a "server too busy" error message, even if connecting to the host address of the Terminal Services server works correctly. According to Microsoft article Q280805, the problem is that RDP "listens" only on either one IP address or all addresses, but not a selection of addresses. The article tells you how to configure RDP to resolve the problem.

Troubleshooting a STOP 0X0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message
A "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message indicates that the kernel detected an unrecoverable error. The problems that can cause this kind of error are similar to the problems that cause a "STOP 0x0000000A" error message—bad pointers, invalid addresses, and other types of access violations. The STOP 0x0000001E bug check identifies an error that occurred in a section of code that doesn't have error handling routines. The system directly generates most exceptions in the section of code that's running. Check out Microsoft article Q275678 for more details about the STOP message's structure and how to debug it.

Only Domain Admins Can Access Internet Email From Outlook 98
After you use the Add/Remove Programs tool to install Microsoft Outlook 98 on a terminal server, users who aren't members of the Domain Admins group can't access Internet email from Outlook. The problem is that the users don't have permission to create the temporary files that Outlook 98 needs for Internet email. To fix this problem, run the compatibility script and edit the user permissions as Microsoft article Q255185 describes.

Win2K Can Leave an Unlicensed Connection Active After Logging Off a NetWare 4.X/5.X Server
When clients connect to a Terminal Services server or to Win2K Professional and connect to a Novell NDS tree through a logon script or a mapped drive using Client Services for NetWare (CSNW), the connection remains on the NetWare server after the client has logged off. When the client logs back on to access the NetWare server, it could reach the license limit on the NetWare server or the concurrent access limit. This behavior doesn't occur when you use NetWare Client32 version 4.71 or later. See Microsoft article Q263546 for a fix or workaround.

Post-SP6 Fix: Registry Setting Causes Stop Error When You Change Password
When you change the domain password with an enabled C2-security registry entry on a Service Pack 6 (SP6) machine, you might receive a "Stop 0x1E" error message. The system will then set the following registry entry:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value: EnhancedSecurityLevel (REG_DWORD)
Data value: 1

This key ensures that Object Manager changes the attributes of a kernel object in the Object table for the current process only if the previous caller mode is Kernel mode. If you attempt to change the password after you set this registry value, you'll generate a STOP error. See Microsoft article Q287634 for a hotfix or workaround.

Changes to Default Connection Permissions Aren't Applied to Edited Connection
If you want to make changes to the default security settings for all Terminal Services clients, you have to make the changes before you create and edit other connections. Otherwise, the changes you make to the default permission set won't apply to the edited connections. See Microsoft article Q225038 for a workaround (e.g., delete the existing connections and start over or manually edit the existing connections to the correct settings).

Users Can Remotely Control a Terminal Services Session After Removing the Permission
After an administrator removes the Remote Control permission for a user and/or group on an RDP-TCP connection on a Terminal Services computer, the user and/or group can continue to remotely control sessions that the administrator established before the change. According to Microsoft article Q235484, this isn't accidental—the permission applies only to connections made after the change, not to current sessions; otherwise, you could lose remote-control permission for a session while you're still connected to it.

Java Plug-In Leaves Browser Processes and NTVDMS Running After You Close the Browser
Programs such as Netscape Navigator, Internet Explorer (IE) 5.0, and RealPlayer, as well as 16-bit programs that run Windows NT Virtual DOS Machine (NTVDM), can continue to use process resources after you close the programs. You then have to use Task Manager to quit the process; otherwise, the OS memory will eventually run out of resources and you'll have to restart the computer. According to Microsoft article Q260256, Java Plug-In version 1.2.1 causes the problem, and you should download Java Plug-in 1.2.2.

Problems With IE 4.X Under TSE
The "server too busy" error message is often the terminal client's way of saying "I can't connect to the server, but I'm not sure why." According to Microsoft article Q268602, if the TSE licensing doesn't start and you see two particular entries in the NT Event Viewer (the article names the entries), you might have a clue to the problem. Installing IE 4.x makes changes to the Registry that are incompatible with TSE. See the article for more information.

TAGS: Windows 8
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.