Remote printing is a function of listening on port 631
Out of the box, the cupsd.conf has # Only listen for connections from the local machine. Listen localhost:631 Listen /var/run/cups/cups.sockChange the localhost line to the hostname or IP address of your host and it will be capable of receiving remotely originated jobs.
You can also use the Port directive to have it listen on all interface for a specific port.
Hugh Jos Vos wrote:
On Fri, Oct 26, 2007 at 09:59:35AM -0400, Josh Kelley wrote:Did you check if SELinux is blocking the connection (by checking /var/log/audit/audit.log or by running setenforce permissive to temporarily disable SELinux )?I have SELinux not enabled.Our print server still runs RHEL 4, so I can't help much otherwise; sorry.My RHEL4 cupsd.conf works and I have put that in place, for the time being. I guess the stock RHEL5 cupsd.conf is more secure than the RHEL4 version, so some setting has to be changed explicitly to allow remote printing. I'll go through all the differences when I've more time. "Fighting" cupsd.conf is something occurring whenever you want to change something ;-). In the past, I also saw those "ghost changes" that made your print system not work anymore after a while, but since I found out what packages are "guilty" for that, I'm standard removing those on every system I install :).
-- System Administrator DIVMS Computer Support Group University of Iowa Email: [EMAIL PROTECTED] Voice: 319-335-0748
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
