Knowledge Base

A limited user can no longer print to a shared printer from a terminal server session after you restart the Spooler service in Windows 2000

Article ID: 843259

Article Last Modified on 10/26/2006

APPLIES TO

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server

SYMPTOMS

Assume the following scenario on a Microsoft Windows 2000-based computer that is running Terminal Services in either Application Server mode or Remote Administration mode:

You create and then share a local printer that is connected to a remote print server.
You map an LPT port to this shared local printer. For example, you run a command that is similar to the following:

net use LPT1 \\servername\sharename /persistent:yes
A limited user logs on to a terminal server session and then receives an error message after that user tries to print to the shared printer.
You install the hotfix that is described in the following Microsoft Knowledge Base article to resolve the problem that the user experiences in step 3:

826026 Documents from Terminal Server users who map LPT1 to different printers appear on the same printer

After you install this hotfix, a limited user who tries to print from a terminal server session can print successfully. However, if either the computer or the Spooler service is restarted, limited users again experience the problem that is described in step 3.

In this scenario, you must reapply the hotfix that is described in Knowledge Base article 826026 to restore printing functionality from a terminal server session.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must be running Windows 2000 Service Pack 3 (SP3) or Windows 2000 SP4 to install this hotfix. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to obtain the latest Windows 2000 service pack

Additionally, you must have applied the hotfix that is mentioned in the following Knowledge Base article before you install this hotfix:

826026 Documents from Terminal Server users who map LPT1 to different printers appear on the same printer

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version            Size    File name
   -----------------------------------------------------------
   24-Mar-2004  02:17  5.0.2195.6824      42,256  Basesrv.dll      
   21-Sep-2003  00:45  5.0.2195.6824     236,304  Cmd.exe          
   11-Jul-2004  19:40  0.2.0.1           138,000  Faxui.dll        
   19-Jun-2003  20:05  5.0.2195.6660     233,744  Gdi32.dll        
   24-Mar-2004  02:17  5.0.2195.6897     742,160  Kernel32.dll     
   11-Jul-2004  19:40  5.0.2195.6960     256,784  Localspl.dll     
   24-Mar-2004  02:17  5.0.2195.6824      54,544  Mpr.dll          
   11-Jul-2004  19:40  5.0.2195.6958     335,120  Msgina.dll       
   24-Mar-2004  02:17  5.0.2195.6892      90,264  Rdpwd.sys
   04-Jun-2004  23:13  5.0.2195.6935   5,887,488  Sp3res.dll       
   11-Jul-2004  19:40  5.0.2195.6938      80,144  Spoolss.dll      
   24-Mar-2004  02:17  5.0.2195.6897     403,216  User32.dll       
   05-Aug-2003  22:14  5.0.2195.6794     385,808  Userenv.dll      
   10-Jul-2004  06:36  5.0.2195.6958   1,631,760  Win32k.sys
   19-Jun-2003  20:05  5.0.2195.6681      97,040  Win32spl.dll     
   11-Mar-2004  02:37  5.0.2195.6898     181,520  Winlogon.exe     
   11-Jul-2004  19:40  5.0.2195.6958     244,496  Winsrv.dll       
   24-Mar-2004  02:17  5.0.2195.6897     742,160  Kernel32.dll     
   10-Jul-2004  06:36  5.0.2195.6958   1,631,760  Win32k.sys
   11-Jul-2004  19:40  5.0.2195.6958     244,496  Winsrv.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbqfe kbhotfixserver kbtermserv kbprint kbbug kbfix kbwin2000presp5fix KB843259

Microsoft KB Archive/843259

Contents