Question

  Asked: Jul 22 2005   9:04 AM GMT
  Asked by: LeeJ75


LPR Printing in Windows server 2003


Microsoft Windows, Tech support, Help Desk, Vendor support, Windows Server 2003

I have just set up a shared generic line printer on one of our 2003 servers, and when I print a test page everything prints OK. However, when I map it as a network printer on another machine the print job is sent to the queue but stays there and nothing is printed. In the application log on the print server the following error is displayed:

Event Type: Warning
Event Source: LPR Print Monitor
Event Category: None
Event ID: 2004
Date: 22/07/2005
Time: 12:58:54
User: N/A
Description:
Printer bdwageslp on host 10.20.5.10 is rejecting our request. Will retry until it accepts the request or the job is cancelled by the user.

I end up having to cancel the job. I've seen lots of support articles for this problem on NT4 Terminal server but not on 2000 or 2003.

Any help would be appreciated.

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



From what your post suggest, this is an issue with terminal server connections and printing?
One little thing about Terminal Servers and printing with RDP connected clients, it is touchy and picky.
Make sure that the client computer is using the exact printer driver on the client that is installed on the terminal server. And that the printer is named the same. So if you have a printer installed on your terminal server called "hp officejet k series", the printer on the client must be an "hp officejet k series" with the same name.

I had the same problem with some of my termsrv clients. I had the drivers installed on my server, the client on theirs (and since these clients were geographicaly dispersed!)any way we found they were naming their printer driver something different than the default. Once that was resolved, they could print.

Hope this helps and best of luck

The HumbleNetAdmin
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Microsoft Windows and Channel.

Looking for relevant Microsoft Windows Whitepapers? Visit the SearchWinIT.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

LeeJ75  |   Jul 25 2005  5:58AM GMT

At first I thought it was a terminal server issue but I have tested it as a normal network printer from both windows 2000 and XP clients and I get the same error.