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

Posted on 2008-11-04
Last Modified: 2013-11-12
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://, 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
The Line Printer Daemon (LPD) service refused a print job from for printer \\\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="">
    <Provider Name="Microsoft-Windows-Spooler-LPDSVC" Guid="{9F44821F-1FD9-46BF-A09A-C7F751159AAF}" EventSourceName="LPDSVC" />
    <EventID Qualifiers="49152">4009</EventID>
    <TimeCreated SystemTime="2008-11-04T20:19:58.000Z" />
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Security />
    <Data Name="param1">\\\CIT03p</Data>
    <Data Name="param2"></Data>

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.
Question by:craigjm
    LVL 23

    Expert Comment


    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.

    check this article and update

    LVL 1

    Author Comment

    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.
    LVL 1

    Accepted Solution

    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.
    LVL 1

    Author Comment

    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.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Are your corporate email signatures appalling?

    Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

    The /etc/authorization file in Mac OS X 10.x can be used to control access to the various panes of the System Preferences amongst other things. It’s used by some of us Mac Sys Admin’s to give Standard Users access to System Prefs panes that only adm…
    In this article we will discuss some EI Capitan Mail app issues and provide some manual process to resolve them.
    This tutorial will show how to inventory, catalog, and restore media from legacy versions of Backup Exec into both 2012 and 2014 versions of the software. Select Storage from the tabs along the ribbon bar as the top: Ensure the proper storage devi…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

    760 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now