Subject: Re: Need some help with printing on a LaserWriter IIg
From: David Lancaster (c4ng2@unb.ca)
Date: Fri Jun 16 2000 - 17:29:54 EDT
> Following your directions, I did checkpc -f which fixed a few on the
> niggling permission errors. It did, however, give me an error on my
> /dev/null file (I just created an empty document with ae named null.
> additionally, it says "cannot open log" but then again, I haven't done any
> printing with the spooler, so it is no surprise I have nothing in log.
Well, /dev/null shouldn't be just a normal file....it may end up working for
you, but I believe that there is a correct way to create one (possibly with
mknod or something, I'm not sure as it's outside my current area of
expertise). The log file thing is troubling, perhaps you should check the
permissions on the log file.
> I tied to print with lpr -P lp test1.ps and now get a "connection
refused"
> error.
> Specifically:
> LinuxBox2:/#lpr -P lp test1.ps
> connection to 'localhost' failed - Connection refused
> job ' cfA262LinuxBox2.thereedfamily.org' transfer to lp@localhost failed
>
> SO then I tried to telnet to 127.0.0.1 printer ... and got a similar
> connection refused error. Speifcally:
> LinuxBox2:/# telnet 127.0.0.1 printer
> telnet: Unable to connect to remote host: Connection refused
>
> I was able to ping 127.0.0.1,and telnet 127.0.0.1 with no problem so
> localhost is active in some way... I feel we are really on the cusp of a
> breakthough, you have any other good ideas?
Well, that sounds like your problem. Somewhere, there is a setting that is
either specifically denying you access, or you are not implicitly getting
access.
Try each one of these seperatly, and see if any of them solve your problem.
1. Try putting your hostname in /etc/hosts.lpd
2. Try putting your ip address in /etc/hosts.lpd
3. Try putting 127.0.0.1 in /etc/hosts.lpd
In theory, one of these (hopefully the first one) will ensure that lpd will
allow you to connect.
If none of these work, I'd check to see if you have any active firewall
rules that would be preventing connections on the printer port.
Well, that's all I can think of off the top of my head so far. Lemme know
if anything works, and if not...well, guess we'll have to try something
else.
D.
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:31:04 EST