Post-SP6 Fix for TSE on the Way
Microsoft article Q305399 describes a problem in the remote procedure call (RPC) service that can cause the service to fail. The RPC endpoint mapper lets RPC clients determine the port number that is currently assigned to a particular RPC service. Because the endpoint mapper runs within the RPC service itself, exploiting this vulnerability would cause the RPC service to fail, with the accompanying loss of RPC-based services and the potential loss of some COM functions. You can restore normal service by rebooting the system.
You can download a fix for Windows NT 4.0 computers; see the article for a link. Microsoft says that a fix for NT Server 4.0, Terminal Server Edition (TSE) is coming, but the company hasn't announced a date.
Can't Print to an IBM Network Printer That Uses LPR
When you use Windows 2000 or Windows NT TCP/IP Printing Services to print to an IBM network printer that uses the Line Print Remote (LPR) protocol, print jobs might not print. Although documents you send to the printer might look as if they're printing, the event log might report an event similar to the following:
Event ID: 13 Source: Print Type: Information Description: DocumentName owned by UserName was deleted on PrinterName
According to Microsoft, this problem isn't a failing of Win2K or TSE but can happen because certain models of IBM network printers require that the LPD queue have a specific name. Microsoft article Q282420 lists the printers for which this is a problem. If the LPD queue has a different name, the print job might not successfully complete. To resolve this issue, verify that the LPD queue name is either PASS or TEXT (in uppercase letters). See the article for more information.
Custom Forms Not Available with HP LaserJet 5SI MX Raster Driver
After you create and save a custom form for a Hewlett-Packard (HP) LaserJet 5Si MX printer using a raster driver in NT 4.0 or TSE, the form might not be available in the list of form names. Microsoft article Q237879 contains a link to a page on the HP Web site that documents the problem and suggests that you use the PostScript driver to use forms outside the printer's limitations.
Print to Local Printer from a TSE Terminal Server Client Session
Because TSE servers don't support automatic client printer mapping (even if the client uses RDP5), printing to a local printer from a TSE terminal server requires the preparation that Microsoft article Q243295 describes.
When you connect a client (RDP 4.0 or RDP 5.0) to TSE, the terminal server must have the client's printer driver installed at the server. Install the NT 4.0 printer driver on the terminal server regardless of which OS is running on the client computer. The terminal server must have NetBIOS name resolution to the client computer. Microsoft recommends you use WINS for NetBIOS name resolution. If you can't use WINS, use a static IP address if you're on a LAN or request a predetermined IP address if you're using a RAS or VPN client. The server's LMHOSTS file needs to resolve the client computer's NetBIOS name to the client computer's static or predetermined IP address. If you use a RAS or VPN connection, you must log on to the domain for NetBIOS functionality. You must share the local printer on the client computer.
Normal and Bold TrueType Fonts Look Alike on Monitor or Printer
Normal and bold TrueType fonts in your text might look alike on your monitor or printer because of the way an algorithm in NT 4.0 calculates the fonts. According to Microsoft article Q279173, Win2K uses the same algorithm for conventional TrueType functionality.
Add a Default Printer for All New Users
Microsoft article Q252388 describes how to edit the registry on a TSE server to make a particular printer the default printer for everyone who uses that terminal server, regardless of which groups they're in. This isn't a short process; see the article for details.