Printing from Linux host fails LPDSVC: Event ID 4007. SimulatePassThrough ineffective

Discussion in 'Server Setup' started by Geico Caveman, Oct 13, 2010.

  1. Well, this is really not a server, but this set of groups are
    collectively perhaps the best place to ask this question.

    I have a windows only printer that is attached to a windows machine
    (Windows XP Professional SP 3).

    I have followed this guide to redirect the port and set up a dummy
    postscript printer to allow unix hosts to print:

    The two hosts are properly networked on the same subnet.

    LPD service is running, and I have changed its scope to accept
    connections only from the linux host.

    Yes, port 515 is open and I can telnet to it.

    In the Event Viewer, I have this persistent failure to accept print
    jobs from the linux host:

    Source: LPDSVC
    Event ID: 4007
    Type: Warning
    Illegal format used for commands received from : service refused

    ( is the linux host)

    Correspondingly, the error on the linux host is
    /usr/lib/cups/backend/lpd failed.

    I have tried to add (a) SimulatePassThrough (1) and (b)
    LpdPrinterPassThrough (1) keys to the registry using regedit:

    for the first one (a).
    and the printer under \Control\ for the second one (b).

    No use.

    Retstarted spooler and lpdsvc. Rebooted. Restarted cups on the linux host.

    No use.

    Suggestions ? (No, buying a decent cross platform printer is out of the
    question for the office, so I am stuck with this one.)
    Geico Caveman, Oct 13, 2010
    1. Advertisements

  2. you may have better luck sharing the printer as a windows share and
    setting up an smb client.

    Hre is a guide as to how to do that shamelesslessly cribbed

    Setting up a Linux client printing to a Linux Samba print server

    All you need to do is activate the Cups admin GUI and install a printer
    (not a physical printer), bearing in mind that you're printing to IP
    address where the queuename there is laserjet1020 (It's a HP
    Laserjet 1020). The steps are, screen by screen, as follows:

    * Open http://localhost:631 --> Administration --> Add Printer:
    enter a printer name, say hpviasamba, no spaces, and optionally a
    location and description.
    * In Device for hpviasamba, select from the drop-down list Windows
    printer via Samba.
    * In Device URI, enter smb://workgroup/
    If you have restricted access to the server, you must add the
    username and password in the URI; e.g.
    smb://workgroup/username:p[email protected]/laserjet1020.
    You can use the NetBIOS name instead of the IP address in the
    device URI but you need to have passed the browsing test that I gave
    above for good Name Resolution.
    * Select the printer manufacturer from list in cups database
    * Select the printer model from list in cups database
    * Click printers, click Configure Printer to set formatting settings
    * On the Printers page, click Print Test Page to check connectivity

    Or are you SURE the printer is 'windows only' I tend to attach printers
    either direct to the network, or to the linux machines on it..and then
    tal to them via either direct print or SMB if you want to set up samba
    and make them look like 'windows printers'

    Experience suggests the less you try and make windows smart, the better
    luck you have.
    The Natural Philosopher, Oct 13, 2010
    1. Advertisements

  3. For peculiar reasons, which are solid and will require a lot of
    irrelevant explanations, I cannot use this as a Samba printer
    (technically I can, but I do not want to, for very sound reasons).

    Oh please. Do you think I would inflict all this on myself if I was 1
    million percent certain that this was not a pure windows printer ? Its
    a Dell MFP 1125.

    True, but lpd is the only option in this case.
    Geico Caveman, Oct 14, 2010
  4. Ok, so connect it as a raw queue on Lunx, assuming it has parallel or
    USB, and then export the raw queue as a direct socket: The windows
    machines will use the correct drivers for the printer anyway.

    It wont be useable from Linux, unless your write a printer definition,
    but who cares? It never will be anyway.

    Fundamentally, you have to appreciate that printer DRIVERS are in the
    client machines. The print SERVER only pushes data to it.

    If the client machine hasn't got a driver, the printer will never be
    properly usable from that machine anyway, no matter which one its
    plugged into.

    Unless you fake up e,g. postscript to native emulation on the server.
    The Natural Philosopher, Oct 14, 2010
  5. Good clarification. It raises the question of whether this is ever going
    to work: at some stage you need a converter from postcript to this printer.

    If that's not available, its useless as a printer FROM linux.
    The Natural Philosopher, Oct 14, 2010
  6. Yes. I have done that. Consult the URL I included.
    Geico Caveman, Oct 14, 2010
  7. Thanks for the response, but if you had followed the URL in the
    original post, you would have seen that I have taken care of the
    postscript at windows end by setting up a dummy printer and redirecting
    ports. Please read the URL. The dummy printer prints postscript test
    pages fine from within windows.

    The issue is that windows LPDSVC, which expects certain characters in
    postscript input is not seeing them (there are reports of this all over
    the Internet). So, I need the windows LPD service to stop inserting
    itself in the process and just pass the incoming file to the printer
    itself. I have followed the commonly suggested registry hack, and it
    does not work.

    Why don't people read the *actual* question you pose, instead of diving
    into the deep end of a pool of assumptions ?

    Geico Caveman, Oct 14, 2010
  8. I have a humble request to make of you.

    Please go back to the original question and *actually* read what I
    wrote. Not skim, but *read*.
    Geico Caveman, Oct 14, 2010
  9. Except it doesn't actually work, does it?
    The Natural Philosopher, Oct 14, 2010
  10. I do not know if you are being facetious here, but I would think that
    anyone with basic comprehension skills would have gathered by now that
    the problem lies with the LPD server on the windows XP machine, and not
    with the postscript printer (which has been tested on windows XP).

    If you have nothing to add, and only wish to troll on the basis of a
    barely read post, feel free to do so, but I am currently more
    interested in solving a problem, than in listening to you pontificate
    about stuff that you clearly do not care to understand (I did not say
    you can't understand, just not care to understand).

    No offense is meant, but I would not care if any was taken. All I see
    you doing is taking this thread astray with your preconceptions.
    Geico Caveman, Oct 14, 2010
  11. Geico Caveman

    Rahul Guest

    With that sort of attitude I'd be amazed if you get much help. As far as I
    can see Robert and "Natural Philosopher" were sincerely trying to help you
    out. Take their advice or not, the least you can offer is some gratitude.
    Rahul, Oct 15, 2010
  12. I would rather not have such "help", given the reluctance of one of
    them to even read the post that asks for help.

    In any case, I solved this problem on my own.
    Geico Caveman, Oct 15, 2010
  13. Geico Caveman

    Chris Davies Guest

    Are these Q168457 and Q150930?

    Chris Davies, Oct 15, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.