[nflug] printing

[Sam Stern]

> -----Original Message-----
> From: nflug-bounces at nflug.org 
> [mailto:nflug-bounces at nflug.org] On Behalf Of peter at thecybersource.com
> Sent: Wednesday, March 28, 2007 04:36 PM
> To: nflug at nflug.org
> Subject: RE: [nflug] printing
> 
> Yes, I know, I will check that out when I have the printer up again. I
> always use that for local stuff but never thought of trying to hit a
> remote (albeit internal)printer via the web interface on port 631.
> I think Sam thought I had the printer connected directly.
> 
> 

Close. I thought you had a remote printer, connected to cups and then shared
out again. I've never heard of remote printers that run cups -- lpr, custom
ipp stack, samba and/or jetdirect yes -- but not cups. This scheme (of
resharing a printer with cups) works amazing well and I've seen it in
several small offices esp. when the printer drivers are invasive (like hp
printer drivers) or unstable. I've also seen that done when the printer
itself has a flaky or odd web interface.

Thinking of it, if it's jetdirect (port 9100 is jet direct) there is likely
a snmp mib that you could load and thus discover the queue name of the
printer with (via snmp). Perhaps you could share a quick "nmap -sT
$pirnter_ip" of the ricoh and we can tell what services it exposes?




Sam S.

_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug