On Mon, 23 Oct 2000 [EMAIL PROTECTED] wrote:
> I am having a problem printing from RedHat LINUX to a Canon GP200
> (Copier/Printer).
Okay, as I understand it:
You have a printer which is attached directly to the network via some kind
of embedded print server device. Said print server supports the Unix LPR
network printing protocol ("printer" or "spooler").
Printing from a Red Hat 6.1 laptop to the printer works fine.
Printing from a Red Hat 6.2 laptop to the printer fails. When you try to
print, the data light on the printer blinks, indicating it got something, but
it goes out without printing anything.
Is this summary correct?
> We had to load the printtool and the print filters rpms.
Make sure you have the latest errata updates from Red Hat's site. I believe
there is/was an LPR update in 6.1 or 6.2. If it was 6.1, install it on the
6.1 laptop, and see if you can still print. If not, then look at the release
notes for the update and figure out what changed.
> I was wondering if it could be a security issue? Could they have higher
> security (maybe Host.deny) then my LINUX box?
Your printer may well have security restrictions in place; you would have to
check the print server's manual for that. (Or contact your network admin, if
you're not the right guy for that.)
> Does anyone have any ideas or tests I can do to help troubleshoot this
> issue.
First, make sure the print configuration between the two laptops is the
same. You said the /etc/printcap files match, and that is a start, but Red
Hat's printing subsystem is a bit more complex than that. You will find
several files in the /var/spool/lpd/CP200 directory. Compare the contents of
"general.cfg", "postscript.cfg", "textonly.cfg", and "filter" (I recommend
"diff" for the last one).
If all of the above check out, then we should drop back to some low-level
network tests:
Try this command and observe the output:
ping name-of-printer
If it fails to resolve the name of your printer to an IP address, fix
that. If it gets that far, but the output looks like this:
64 bytes from 10.0.0.1: icmp_seq=0 ttl=60 time=1.6 ms
instead of this:
64 bytes from name-of-printer (192.168.10.5): icmp_seq=0 ttl=60 ...
then the IP address of the printer isn't resolving to a name. Fix that.
/etc/hosts can be used to fix either of these problems if you do not or cannot
use DNS to do so.
From a shell prompt on the non-printing laptop, issue the following command:
telnet name-of-printer 515
That should establish a connection and then sit there waiting for you to
start speaking LPR, or perhaps spit out an error and close the connection.
If needed, close the connection yourself: Hit the telnet escape command
(usually <CTRL>+<]>, you should see a message in the telnet connection banner
telling you what it is). You may need to hit [ENTER] after the escape. Then
enter the "close" command.
If you got a message like "Host unreachable" or "Connection refused", then
the TCP circuit between your laptop and the printer cannot be established.
This might be security, it might be a TCP configuration problem, but you know
where to start looking.
If that works... I dunno. Try a packet sniffer.
--
Ben Scott <[EMAIL PROTECTED]>
Net Technologies, Inc. <http://www.ntisys.com>
Voice: (800)905-3049 x18 Fax: (978)499-7839
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
