<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sam Stern wrote:
<blockquote cite="mid008901c77179$97a7da50$0700a8c0@cube" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:nflug-bounces@nflug.org">nflug-bounces@nflug.org</a>
[<a class="moz-txt-link-freetext" href="mailto:nflug-bounces@nflug.org">mailto:nflug-bounces@nflug.org</a>] On Behalf Of <a class="moz-txt-link-abbreviated" href="mailto:peter@thecybersource.com">peter@thecybersource.com</a>
Sent: Wednesday, March 28, 2007 04:36 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:nflug@nflug.org">nflug@nflug.org</a>
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.
</pre>
</blockquote>
<pre wrap=""><!---->
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
<a class="moz-txt-link-abbreviated" href="mailto:nflug@nflug.org">nflug@nflug.org</a>
<a class="moz-txt-link-freetext" href="http://www.nflug.org/mailman/listinfo/nflug">http://www.nflug.org/mailman/listinfo/nflug</a>
</pre>
</blockquote>
peter@Office:~$ nmap -sT 192.168.1.8<br>
<br>
Starting Nmap 4.03 ( <a class="moz-txt-link-freetext" href="http://www.insecure.org/nmap/">http://www.insecure.org/nmap/</a> ) at 2007-03-29
11:27 EDT<br>
Interesting ports on 192.168.1.8:<br>
(The 1669 ports scanned but not shown below are in state: closed)<br>
PORT STATE SERVICE<br>
23/tcp open telnet<br>
80/tcp open http<br>
515/tcp open printer<br>
631/tcp open ipp<br>
9100/tcp open jetdirect<br>
<br>
This is not the ricoh but a zonet print server but same issue. I know
that the queue is suppose to be lp1 but there is no mention of lp1
anywhere in the web interface of the thing and I have it called
zonet_print_server. So, how would one know what to call the print
queue? What currently works to these is something like
<a class="moz-txt-link-freetext" href="http://192.168.1.8:631/lp1">http://192.168.1.8:631/lp1</a> but there is NO mention of lp1 anywhere on
the devices web interface. Could I use this snmp command your talking
about to sniff this out?<br>
</body>
</html>