Microsoft KB Archive/137065

= Print Jobs Looping Continuously in Print Manager =

Article ID: 137065

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 3.5
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q137065





SYMPTOMS
Your computer is running Windows NT and has a printer connected to a local port. After you share the printer for use by other users and then issue a NET USE command from a command prompt of the same computer to establish a connection to your own printer, your own print jobs do not print and appear to loop continuously as recursive documents called "Remote Downlevel Document" in the print queue.

Additional symptoms include event messages in the System event log:

Event ID: 10

Source: Print

User: NT AUTHORITY\ANONY

Type: information

Description: Document XXX, Remote Downlevel Document owned by was printed

on Printer_nameX via LPT1:. Size in bytes; ## pages printed: 0

This will only occur if you redirect LPT1: using the "Net Use" command to use the shared network printer connected to the local computer then print to it.

Net use LPT1: \\This_machine\printer_share



WORKAROUND
To work around this problem:


 * 1) Run Print Manager.
 * 2) Select the problem print queue.
 * 3) From the Printer menu, choose Pause Printer.
 * 4) Select the document caught in the loop.
 * 5) From the Document menu, choose Remove Document.
 * 6) At a command prompt, type:

net use /d lpt:

where  in lpt: is the number of your lpt printer port.
 * 1) From the Printer menu, choose Resume Printer.

Printing works correctly now.

Additional query words: prodnt endless

Keywords: kbprint KB137065

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.