• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2999
  • Last Modified:

Error printing from Mac OS 10.5.5 to Windows Server 2008 via LPD

I am trying to setup a new Windows Server 2008 print server, and I can print just fine from OS X via SMB, but I cannot print via LPD.  We have a lot of clients currently setup to print via LPD to our Windows Server 2003 print server, and I would like the transition to be as smooth as possible.  When I print from my Mac to the print server with via  LPD (lpd://xxx.xxx.xxx.xxx/CIT03p), I see the following error in the System log:

Log Name:      System
Source:        Microsoft-Windows-Spooler-LPDSVC
Date:          11/4/2008 3:19:58 PM
Event ID:      4009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      printserver.domain.com
Description:
The Line Printer Daemon (LPD) service refused a print job from xxx.xxx.xxx.xxx for printer \\xxx.xxx.xxx.xxx\CIT03p because the specified printer does not exist on this computer. Retry printing from the client using the correct printer name.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Spooler-LPDSVC" Guid="{9F44821F-1FD9-46BF-A09A-C7F751159AAF}" EventSourceName="LPDSVC" />
    <EventID Qualifiers="49152">4009</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-11-04T20:19:58.000Z" />
    <EventRecordID>20315</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>printserver.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">\\xxx.xxx.xxx.xxx\CIT03p</Data>
    <Data Name="param2">xxx.xxx.xxx.xxx</Data>
  </EventData>
</Event>

I have tried changing the queue from Standard TCP/IP using RAW on port 9100 to LPR on port 515, and have even tried installing the LPR Port Monitor and using that, but I get the same result every time.  I would appreciate any suggestions.
0
craigjm
Asked:
craigjm
  • 3
1 Solution
 
bhanukir7Commented:
Hi

i think the error seems to more for the type of printer the MAC OS x is referring to and that printer not being correctly configured.

http://technet.microsoft.com/en-us/library/cc773861.aspx

check this article and update

bhanu
0
 
craigjmAuthor Commented:
I saw that article, but it didn't seem to help.  By default, the Printer Name or IP Address field in the Port Settings is set to the IP address of the printer.  The Protocol is set to Raw, and the Port Number is set to 9100.  No matter what I change, if I use the queue name for the Printer Name or IP Address Field, or change the Protocol to LPR and the LPR Queue Name to match the Queue name, it still doesn't work.
0
 
craigjmAuthor Commented:
Well it looks like I found the problem and the solution.  After creating printers, I assigned them a standard set of permission for a bunch of different domain groups.  During the process, I removed the Local Administrators group permissions for the printers.  It appears the Local Administrators group needs the "Manage printers" permission for LPR printing to work.  I'll verify it with some more testing, but this looks like what was causing the problem.
0
 
craigjmAuthor Commented:
Yes, looks like that was it.  I can print from from any user account on a Mac to any printer on the Windows Server 2008 box without any issues now.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now