Help and Support
 

powered byLive Search

Net Print Disassociates Printer Driver from Queue

Retired KB ArticleThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Article ID:107718
Last Review:October 31, 2006
Revision:1.1
This article was previously published under Q107718
On This Page

SYMPTOMS

Issuing the NET PRINT xxxx /ROUTE:yyyy command disassociates the printer driver name from the queue. Later attempts to remote print to the queue return error 71. Generally, printers become disassociated from the queue when manipulated with the NET PRINT command or from within NET ADMIN (View/SharedResources/Printers/Edit).

Back to the top

CAUSE

A LAN Manager design limitation causes this.

Back to the top

WORKAROUND

Use Print Manager. This sort of administrative tasks cannot be done over the network using command line interfaces and batch jobs.

Back to the top

STEPS TO DUPLICATE CONDITION

1.Create a printer, NullPtr, using IBMNULL driver directed to COM1.
2.Create a queue, NullQ, using NullPtr and the IBMNULL driver.
3.Share NULLQ.

NET SHARE NULLQ /PRINT
4.Use NULLQ.

NET USE LPT3 \\xxxx\NULLQ
5.Change the routing. (Simply issue the command; no change is necessary.)

NET PRINT NULLQ /ROUTE:COM1 (same as before)
6.Copy CONFIG.SYS to LPT3.

COPY CONFIG.SYS LPT3
This results in a SYS00071 error.

NOTE: This applies to all ports and drivers specified.

Back to the top

Keywords: 
KB107718

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by E-mail, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.