Keeping Up with Terminal Services - 15 Aug 2001

Redirecting a Client Drive in Terminal Services
Windows 2000 Server Terminal Services doesn't usually support client-side drive redirection on its own. However, the Win2K Resource Kit includes a tool that lets you automatically map client-side hard disks to a terminal session; the hard disks automatically reconnect each time the client initiates that session. See Microsoft article Q272519 to learn how to use this tool.

Can't Import drmapclt.reg File When Installing Drive Share Utility
When you install the Drive Share tool included in the Win2K Server Resource Kit on Terminal Server Client 4.0, you might receive an error message that tells you that the Registry Editor can't import drive:pathdrmapclt.reg because the file isn't a registry script. Programs earlier than Win2K use a different header for the Windows Registry Editor on Terminal Server Client. In addition, Unicode 1.x and 2.0 have limited functionality. To work around this issue, use the steps that Microsoft article Q268774 describes to manually edit the drmapclt.reg file.

Office Applications Fail To Run VBA Code
When a task is scheduled on Windows NT 4.0 Server, Terminal Server Edition (TSE) using the Task Scheduler Service and the task launches an Office application to run Visual Basic for Applications (VBA) code, the Office application might fail to run the code correctly or might cause Office to stop responding. The task might then fail and leave the Office application running in memory. The same task stops responding when you run it manually or when you run it from Task Scheduler while logged on interactively. (This problem doesn't occur with Terminal Services.) See Microsoft article Q275719 for suggestions about how to resolve this problem.

Terminal Server Clients Can't Connect To an Exchange Server
Microsoft Outlook (2002, 2000, 98, and 97) email client computers that connect to a Microsoft Exchange Server through a TSE server can't resolve the Exchange Server or the mailbox name, although they can PING the Exchange Server with the IP address and NetBios name. According to Microsoft articles Q279778, Q299531, Q299530, and Q299529, the remote procedure call (RPC) Configuration Service isn't installed on the terminal server. See the articles to learn how to install this service.

Installing Printer Drivers from a Trusted Print Server
This topic comes up frequently, so it's worth mentioning again. You can edit a terminal server's registry to load printer drivers only from a trusted source, so you can install only the drivers you've tested. See Microsoft article Q129830 to learn how to make the edits.

Unnecessary Security Failure Audit
When you use an RPC-based client/server program on a TSE terminal server, the following entry might appear in the Security event log: Event ID: 577 Source: Security Type: Failure Audit Category: Privilege Use. The security audit occurs when the RPC subsystem acquires the user's credentials for authenticated RPC. The code can do this two ways. If the first method doesn't succeed, the system tries the second method. In this case, the first method (calling the Local Security Authority—LSA—directly) doesn't succeed and generates an Audit Failure entry. This audit doesn't indicate a security breach; you can safely ignore it. See Microsoft article Q238185 for more information.

Windows Might Hang When You Try to Establish a TCP Connection to a Nonexistent IP Address
A TSE server with a recent post-Service Pack 6 (SP6) hotfix might stop responding (hang) if it attempts to make a TCP connection with an IP address that doesn't exist. See Microsoft article Q297040 for more information about this problem and to learn how to get another post-SP6 fix for it.

Can't Copy Large Files on Computers Running Win2K or NT 4.0
When you attempt to copy a large file on a Win2K or TSE terminal server (using a command prompt, the GUI, or FTP), the copy process might not work, and you might receive an error message. According to Microsoft article Q259837 (), this problem occurs because the Win2K and TSE copy utilities use buffered I/O to transfer data from the source file to the destination file, which results in a paged-pool memory overhead requirement that's proportional to the size of the file. Because paged-pool memory is a limited resource, the system has a limit on the size of file you can copy. All the paged-pool memory is allocated when you perform the first read or write procedure, so the file-copy operation fails immediately instead of halfway through the operation. Microsoft doesn't have a fix for this problem; the article recommends using the Backup tools to copy files. See the article for more details.

Redirected Drive Letters on Windows .NET Compared with NT and Win2K
You probably won't find Microsoft article Q302371 immediately useful, but you might find it interesting if you're considering .NET Server. On Win2K and TSE terminal servers, each session gets a unique set of drive letters. On.NET Server, each user logon session gets a unique set of drive letters. The article explains the differences and their implications in more detail.

Hardware-Encryption Devices Incompatible with TSE
Microsoft article Q187087 explains that hardware devices that provide encryption or security services to manage and control software don't work correctly on TSE and aren't supported.

Can't Install TSE on Compaq 6000 Computer
When you try to install TSE on a Compaq Proliant 6000-based computer, you might receive a STOP 0x0000000A error message in the scsiport.sys file on a blue screen. This error might occur if you boot from a CD-ROM or floppy disk. According to Microsoft article Q241290, if your Compaq Proliant 6000-based computer has a BIOS version dated January 29, 1999, the BIOS isn't completely compatible with TSE. The article recommends that you update the BIOS and reinstall TSE.

RAS with Multiport Digi Adapter Doesn't Answer Incoming Calls
According to Microsoft article Q243316, a TSE server running RAS with a Digi AccelPort 8r 920 multiple-port adapter doesn't answer incoming calls after the first call per line because the adapter connects to an RJ45 I/O serial box. This connection requires a 10-pin RJ45 connector-to-DB25 cable that Digi supplies. If you're using an 8-pin RJ45 connector-to-DB25 cable, pin 1 (Ring Indicator—RI) and pin 10 (Data Carrier Detect—DCD) aren't connected. RAS uses RI for answering incoming calls. To resolve the problem, use the 8-port Octopus cable with DB25 connectors.

Interix Doesn't Work with Win2K or TSE Terminal Services
When you try to use Interix with a Win2K or TSE terminal server, the Interix services might not work correctly or might hang. Microsoft article Q246442 explains that Terminal Services and Windows Clustering don't support Interix.

Redirecting a Client Drive in Terminal Services
Windows 2000 Server Terminal Services doesn't usually support client-side drive redirection on its own. However, the Win2K Resource Kit includes a tool that lets you automatically map client-side hard disks to a terminal session; the hard disks automatically reconnect each time the client initiates that session. See Microsoft article Q272519 to learn how to use this tool.

Can't Import drmapclt.reg File When Installing Drive Share Utility
When you install the Drive Share tool included in the Win2K Server Resource Kit on Terminal Server Client 4.0, you might receive an error message that tells you that the Registry Editor can't import drive:pathdrmapclt.reg because the file isn't a registry script. Programs earlier than Win2K use a different header for the Windows Registry Editor on Terminal Server Client. In addition, Unicode 1.x and 2.0 have limited functionality. To work around this issue, use the steps that Microsoft article Q268774 describes to manually edit the drmapclt.reg file.

Office Applications Fail To Run VBA Code
When a task is scheduled on Windows NT 4.0 Server, Terminal Server Edition (TSE) using the Task Scheduler Service and the task launches an Office application to run Visual Basic for Applications (VBA) code, the Office application might fail to run the code correctly or might cause Office to stop responding. The task might then fail and leave the Office application running in memory. The same task stops responding when you run it manually or when you run it from Task Scheduler while logged on interactively. (This problem doesn't occur with Terminal Services.) See Microsoft article Q275719 for suggestions about how to resolve this problem.

Terminal Server Clients Can't Connect To an Exchange Server
Microsoft Outlook (2002, 2000, 98, and 97) email client computers that connect to a Microsoft Exchange Server through a TSE server can't resolve the Exchange Server or the mailbox name, although they can PING the Exchange Server with the IP address and NetBios name. According to Microsoft articles Q279778, Q299531, Q299530, and Q299529, the remote procedure call (RPC) Configuration Service isn't installed on the terminal server. See the articles to learn how to install this service.

Installing Printer Drivers from a Trusted Print Server
This topic comes up frequently, so it's worth mentioning again. You can edit a terminal server's registry to load printer drivers only from a trusted source, so you can install only the drivers you've tested. See Microsoft article Q129830 to learn how to make the edits.

Unnecessary Security Failure Audit
When you use an RPC-based client/server program on a TSE terminal server, the following entry might appear in the Security event log: Event ID: 577 Source: Security Type: Failure Audit Category: Privilege Use. The security audit occurs when the RPC subsystem acquires the user's credentials for authenticated RPC. The code can do this two ways. If the first method doesn't succeed, the system tries the second method. In this case, the first method (calling the Local Security Authority—LSA—directly) doesn't succeed and generates an Audit Failure entry. This audit doesn't indicate a security breach; you can safely ignore it. See Microsoft article Q238185 for more information.

Windows Might Hang When You Try to Establish a TCP Connection to a Nonexistent IP Address
A TSE server with a recent post-Service Pack 6 (SP6) hotfix might stop responding (hang) if it attempts to make a TCP connection with an IP address that doesn't exist. See Microsoft article Q297040 for more information about this problem and to learn how to get another post-SP6 fix for it.

Can't Copy Large Files on Computers Running Win2K or NT 4.0
When you attempt to copy a large file on a Win2K or TSE terminal server (using a command prompt, the GUI, or FTP), the copy process might not work, and you might receive an error message. According to Microsoft article Q259837 (), this problem occurs because the Win2K and TSE copy utilities use buffered I/O to transfer data from the source file to the destination file, which results in a paged-pool memory overhead requirement that's proportional to the size of the file. Because paged-pool memory is a limited resource, the system has a limit on the size of file you can copy. All the paged-pool memory is allocated when you perform the first read or write procedure, so the file-copy operation fails immediately instead of halfway through the operation. Microsoft doesn't have a fix for this problem; the article recommends using the Backup tools to copy files. See the article for more details.

Redirected Drive Letters on Windows .NET Compared with NT and Win2K
You probably won't find Microsoft article Q302371 immediately useful, but you might find it interesting if you're considering .NET Server. On Win2K and TSE terminal servers, each session gets a unique set of drive letters. On.NET Server, each user logon session gets a unique set of drive letters. The article explains the differences and their implications in more detail.

Hardware-Encryption Devices Incompatible with TSE
Microsoft article Q187087 explains that hardware devices that provide encryption or security services to manage and control software don't work correctly on TSE and aren't supported.

Can't Install TSE on Compaq 6000 Computer
When you try to install TSE on a Compaq Proliant 6000-based computer, you might receive a STOP 0x0000000A error message in the scsiport.sys file on a blue screen. This error might occur if you boot from a CD-ROM or floppy disk. According to Microsoft article Q241290, if your Compaq Proliant 6000-based computer has a BIOS version dated January 29, 1999, the BIOS isn't completely compatible with TSE. The article recommends that you update the BIOS and reinstall TSE.

RAS with Multiport Digi Adapter Doesn't Answer Incoming Calls
According to Microsoft article Q243316, a TSE server running RAS with a Digi AccelPort 8r 920 multiple-port adapter doesn't answer incoming calls after the first call per line because the adapter connects to an RJ45 I/O serial box. This connection requires a 10-pin RJ45 connector-to-DB25 cable that Digi supplies. If you're using an 8-pin RJ45 connector-to-DB25 cable, pin 1 (Ring Indicator—RI) and pin 10 (Data Carrier Detect—DCD) aren't connected. RAS uses RI for answering incoming calls. To resolve the problem, use the 8-port Octopus cable with DB25 connectors.

Interix Doesn't Work with Win2K or TSE Terminal Services
When you try to use Interix with a Win2K or TSE terminal server, the Interix services might not work correctly or might hang. Microsoft article Q246442 explains that Terminal Services and Windows Clustering don't support Interix.