FC3 as a printserver

[Kevin Fries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

david walcroft wrote:

| Kevin Fries wrote:
|
|> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
|>
|> bengt.lindholm at salnet.fi wrote:
|>
|> |I am trying to get my FC3-box to print jobs sent from a RH9-box.
|>  | |FC3 printer configuration: Queue name office, queue type
|> locally-connected lp0, driver raw; Sharing properties LPD
|> protocol enabled, queue is allowed to all hosts. | |RH9 printer
|> configuration done by editing printcap.local: |office:\
|> |:rm=192.168.2.31:\  (and yes, the IP is OK) |:rp=office:\
|> |:sh=:\ |:mx=0:\ |:mc=0:\ |:ml=0:\ |:sd=/var/spool/lpd/office:\
|> |:if=/usr/local/bin/printerfilter: |There are the necessary lines
|> in /etc/printerfilter.conf: Printer office, Charset IBM437, Model
|> oliprinter, Staircase y. There have been no alterations with this
|> sending RH9-box. | |Everything worked fine as long as the
|> receiving FC3 box was still a RH9-box, but after installing FC3
|> (from cratch, firewall on and SELinux active) printing stopped.
|> RH9 and FC3 pings each other, the boxes are in the same lan and
|> network segment. What to do??
|>
|> Wow!  Doing things the hard way are we?
|>
|> I run a FC2 printer server for Fedora Core 2/3 and Winblows
|> 2000/xp clients.  Much more complex than your setup, and I would
|> never try this without CUPS.  Set up CUPS on the Fedora box (its
|> an rpm), set up CUPS on the RH box (again an rpm).  Now,
|> configure the Fedora box for the printer (see
|> www.linuxprinting.org if you need help).  The default behavior is
|> to share the printer.  The RH box should see the printer
|> automagically.
|>
|> If you want to print from Windows boxes, set up SAMBA on the
|> Fedora box.  Then, configure Windows printer shares, and use the
|> CUPS printer as the back end source.  You can go into allot more
|> automation with dealing with Windows printer drivers.  Linux
|> needs no such BS. Everything in Linux goes out postscript.
|>
|> Done.
|>
|> Kevin
|>
|>
| Kevin, Could you help me out as well please,I have similar problems
|  in CUPS between two FC3 box's, same LAN 192.168.0.0/24 the 2nd box
| uses internet and NTP,print config the same,sharing,all hosts they
| both see the print file but the printer does not print from the 2nd
| box. I tried different hosts ie: eth 0 eth1,single url, but nothing
| works.

I am at home right now, where I do not have the client server setup,
but will try best I can to help.

CUPS is both a client and a server.  It broadcasts and listens on port
631.  However, it can be configured to be silent.  The default
behavior from CUPS is to broadcast any printers attached to the local
machine.  Fedora also tries to install by default with an iptables
firewall.  Things I could tell you to search for:

~   -  Make sure the CUPS daemon is actually running in both locations
~   -  Make sure your firewall on both machines has port 631 open.
~   -  From the client, try to telnet to port 631 of the server. Try it
in the other direction too.
~   -  Check the configuration on the server for its "broadcast"
settings, it should show your intranet
~   -  Check the configuration on the client to make sure that it is
listening on the local intranet.

Something is trying to jog my memory about Fedora changing some
default behavior, but I just cant remember what.  Having set this up
on Redhat, Fedora, Debian, Mandrake, and Gentoo, it seems to me that
Fedora did something goofy.  I do remember I scanned the config files
and the broadcast and listening area are ringing a bell.  I also
remember using the Fedora system printer tools to help me diagnose.
They will also use CUPS by default.  LP and LPR commands are finally
on their way out, most every distro is configuring with CUPS
nowadays.  I just wish I were at work so I could review my config
files... it is just nagging at me that Fedora did something wrong in
the config, and they did it on purpose.  I just for the life of me
cant quite remember.  But it was something simple.

Once you change the behavior back to normal, this system is so easy a
child can make it work.  Its so automatic, its awesome.  Every time I
say, boy it would be great if this program works this way, I usually
find out that it actually does.

Kevin Fries

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB3gNgiFq1Eo16+CgRAn9kAKCv45xioX8X0bk63xlvMJi/IPhB4ACfe9qE
ykSLOSYRB2L+vqrWL1eDgjQ=
=zFK+
-----END PGP SIGNATURE-----