CUPS and network printer
Justin
the houses I apologise.
I have a network printer (Sharp AR335); it isn't supported directly by
CUPS but it accepts postscript so I'm sure I should be able to throw
postscript at it and get some output.
Currently I print to it from Win 9x clients via lpd on our network
server, this works because the Win clients know how to send the codes
the printer undersatnds. However, I'm evaluating Linux as a Win
replacement so those Win drivers aren't going to help me; therefore,
instead of having lpd forward everthing it is sent it isn't actually
going to be sent anything! (well, not in the way of codes), that's why
I'm trying to get CUPS working.
Once I have some out put I can then start looking at the inside of ppd
files and try and work out what I need to do to get the output I
require. At the moment I'm getting no output, CUPS is reporting:
Network host '192.168.1.110' is busy; will retry in 30 seconds... INFO:
connecting to 192.168.1.110 on port 631..."
Device URI: http://192.168.1.110:631/
I've telnet'd to the printer (it has it's own server attached) and
changed the port number to match that that CUPS mentions but still no
joy.
Is there a port the printing is usually sent to and if yes what is it?
Of the CUPS options I've tried the following protocols: http, ipp,
lpd/lpr. The (on-board) print-server manual says it accepts FTP printing
with "ftp://portn@<destination server ip address>" but CUPS doesn't seem
to like ftp. I've also given the port number as 1, because that is the
remote port as used in /etc/printcap of the office server.
I think there is some confusion there over the network IP port used and
the printer port (IIRC it can support two printers). From what I can
see, no changes I make from the CUPS web browser interface have any
effect at all... it could be that all settings I've used are wrong.
Any pointers would be gratefully received.
--
Justin C, smarter than the average bear.
John Winters
Justin <jus...@masonsmusic.co.uk> wrote:
>I don't know where best to start with all of this so if it goes around
>the houses I apologise.
>
>I have a network printer (Sharp AR335); it isn't supported directly by
>CUPS but it accepts postscript so I'm sure I should be able to throw
>postscript at it and get some output.
>
>Currently I print to it from Win 9x clients via lpd on our network
>server, this works because the Win clients know how to send the codes
>the printer undersatnds. However, I'm evaluating Linux as a Win
>replacement so those Win drivers aren't going to help me; therefore,
>instead of having lpd forward everthing it is sent it isn't actually
>going to be sent anything! (well, not in the way of codes), that's why
>I'm trying to get CUPS working.
>
>Once I have some out put I can then start looking at the inside of ppd
>files and try and work out what I need to do to get the output I
>require. At the moment I'm getting no output, CUPS is reporting:
>
>Network host '192.168.1.110' is busy; will retry in 30 seconds... INFO:
>connecting to 192.168.1.110 on port 631..."
>Device URI: http://192.168.1.110:631/
>
>I've telnet'd to the printer (it has it's own server attached) and
>changed the port number to match that that CUPS mentions but still no
>joy.
Eeek. This sounds like you're starting to flail around. You can't
change the port number of a device and expect it to suddenly start
understanding a new protocol.
Restore your print server to listening on its default port number, then
tell CUPS to talk to it using lpd protocol, the same way your
current clients get through. Choose the "Raw" option for the printer
driver in CUPS setup and then when the setup is complete, drop
your PPD file in /etc/cups/ppd as <printername>.ppd. Restart CUPS
to make sure everything is in step and all should be hunky.
I'm sure there's a more correct way of getting CUPS to use an extra
PPD file but I haven't found it yet.
HTH
John
--
The Linux Emporium - the source for Linux in the UK
See http://www.linuxemporium.co.uk/
We had a woodhenge here once but it rotted.
Jim Hague
>CUPS but it accepts postscript so I'm sure I should be able to throw
>postscript at it and get some output.
>
>
>Once I have some out put I can then start looking at the inside of ppd
>files and try and work out what I need to do to get the output I
>require.
I went through the same process some time ago to get the Xerox 432 at
work up and going. John's advice is, as ever, The Way To Go.
Before you hare off writing your own .ppd, I'll bet you can extract a
perfectly good one from the Sharp Windows driver. That's what I did with
the Xerox, and it works like a charm. I even get to do all the
double-sided, stapling etc. funkies from the KDE print dialog.
--
Jim Hague - jim....@insignia.com (Work), j...@bear-cave.org.uk (Play)
Never trust a computer you can't lift.
Roger Leigh
> Restore your print server to listening on its default port number, then
> tell CUPS to talk to it using lpd protocol, the same way your
> current clients get through. Choose the "Raw" option for the printer
> driver in CUPS setup and then when the setup is complete, drop
> your PPD file in /etc/cups/ppd as <printername>.ppd. Restart CUPS
> to make sure everything is in step and all should be hunky.
>
> I'm sure there's a more correct way of getting CUPS to use an extra
> PPD file but I haven't found it yet.
lpadmin -p printer -P PPD_file
--
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848 available on public keyservers
Matt
Justin
"http://localhost:631" is the URL for the CUPS admin interface. Point your
favourite browser at it and you're away.
lpd AFAIK doesn't have an explicit port No., but has named queues.
Your URI ought to look like "lpd://192.168.1.110/raw" where "raw" is the
name of the lpd queue and I am assuming the network address is the
printer's.
HTH
Matt